-
Notifications
You must be signed in to change notification settings - Fork 170
chore: release reforge #4518
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: release reforge #4518
Conversation
* cancel solana WaC if tx size is too large * align the comments with the code
…MsgUpdateParams (#4095) * update zeta evm * update commit * update to commit be548f7691876e656ec61aa46e31ed337be92f4e , on branch release/v34 --------- Co-authored-by: morde08 <peter@zetachain.com>
* use SAFE confirmation mode for all inbound votes * move confirmation mode update logic right before signing the inbound vote message
port PR 4090 to v34
… deltas on startup (#4126)
…#4125) * add conditional logic for erc20 module upgrade * bump cosmos version to run evm migration 6 to 7 * add unit tests * update handler to panic * add changelog * format files * update changelog * bump cosmos/evm to release/v35 * add back comments for IBC * add back comments for IBC
… a configurable parameter (#4154) * cherry pick * cherry pick * update unit tests * update unit tests * cherry pick * replace big int with uint64 * add check of older value * update upgrade test and changelog * fix function call * add v4 migration back for authority module * add v4 migration back for authority module --------- Co-authored-by: Tanmay <tanmay.bhattacharya.smit@gmail.com>
* skip writing config file * use the value of skip-config-overwrite flag without restrictions for mainnet * add comments * remove unused functions * remove unit tests for unused functions
…'CallOnRevert' flag (#4181) * unpack revert message from Bitcoin memo without considering flag * skip incompatible e2e test to allow CI upgrade test to pass
…context that can timeout (#4202) * backport changes for rescan logic * remove changelog * format files * use context with timeout * change error message * cherry pick changes for context with timeout * format package and fix lint --------- Co-authored-by: Lucas Bertrand <lucas.bertrand.22@gmail.com>
* fix(e2e): check test contracts deployment * add other contracts * fix chain to wait tx from * fix check
* add a note for releases * add release lifecycle docs
Signed-off-by: letreturn <letreturn@outlook.com> Co-authored-by: Charlie Chen <34498985+ws4charlie@users.noreply.github.com>
* chore: remove unused DynamicTicker from zetaclient/types * refactor: remove Msgf and refactor zerolog uses * Replace Msgf for Msg * Use '_' instead of '.' * Start logs with lowercase instead of uppercase characters * Use the constants in the logs module * Use With().Logger() instead of log fields when possible
* chore: remove unused Headers logger * refactor: remove (mostly) unused GasPrice logger * refactor: replace logs.FieldMethod with With().Caller() and standardize logs.FieldModule values * refactor: remove (mostly) unused log fields FieldTracker and FieldConfirmationMode * refactor: replace missed log instances of '.' for '_'
Signed-off-by: yajianggroup <yajianggroup@outlook.com>
Signed-off-by: mickychang9 <mickychang9@outlook.com>
* multiple evm calls in single tx * gen testdappv2 * cleanup after merge * ensure gateway proxy is deployed in e2e tests * fix upgrade tests * changelog * PR comments
|
!!!WARNING!!! Be very careful about using Only suppress a single rule (or a specific set of rules) within a section of code, while continuing to scan for other problems. To do this, you can list the rule(s) to be suppressed within the #nosec annotation, e.g: /* #nosec G401 */ or //#nosec G201 G202 G203 Pay extra attention to the way |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment @cursor review or bugbot run to trigger another review on this PR
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4518 +/- ##
==========================================
- Coverage 65.93% 64.67% -1.27%
==========================================
Files 451 473 +22
Lines 27251 29129 +1878
==========================================
+ Hits 17969 18840 +871
- Misses 8310 9255 +945
- Partials 972 1034 +62
🚀 New features to boost your workflow:
|
morde08
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do seem to be deleting an additional file: zetaclient/chains/testutils/mocks/evm_client.go when comparing develop branch to release-reforge branch develop...release-reforge#diff-1e5fce4478dd1fad8c7b8c88099684ffad6288f0c58075d5035c78da6e95a486 but if that's expected LGTM
That's fine , the testutils has been moved here the folder on develop is just the older code which was not removed |
|
Some addintional commits added would be backported to develop , no logical changes just unit tests and defensive checks |
ws4charlie
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the changes are unexpected. LGTM
Description
This PR updates main with all changes for the Reforge release
Important zetacored changes for review
Stability Pool Gas Refund Mechanism
Setting UserGasFeePaid: When a withdrawal CCTX is created, UserGasFeePaid = GasLimit × GasPrice is calculated from median gas values and stored in outbound params. This occurs in PayGasNativeAndUpdateCctx, PayGasInERC20AndUpdateCctx, or PayGasInZetaAndUpdateCctx depending on the coin type.
Refund Calculation: On outbound completion, the keeper calculates:
ActualFee = GasUsed × EffectiveGasPrice
RemainingFees = UserGasFeePaid - ActualFee
UsableRemaining = RemainingFees × 0.95
StabilityPoolAmount = UsableRemaining × (StabilityPoolPercentage / 100)
UserRefund = UsableRemaining - StabilityPoolAmount
For zEVM-originated withdrawals with valid hex sender, StabilityPoolPercentage is read from chain params (default 100%). Non-withdrawal transactions send 100% to the stability pool. The function returns early without action if EffectiveGasPrice is nil, ActualFee ≥ UserGasFeePaid, or UsableRemaining rounds to zero.
Remove an observer and test TSS migration with a reduced observer set
The MsgRemoveObserver is used to remove an observer from the set . It removes the observer from the observer set and node account list
There are two tests in the makefile
start-tss-migration-add-observerandstart-tss-migration-remove-observerwhich test both the flows.Another key thing to review is the TSS funds migration, this is. triggered between a tss generation and tss update to migrate funds . This should be done for all EVM and BITCOIN chains , however it has not been possible for us to test this against all evm chains on localnet , we just have ETH
Also added a new tool under zetatool , to fetch tss balances across all chains , this is specially important for BTC chains as we would neeed to use that to provide migration amount subtracting the expected fee
V2 ZETA deposits and withdraws , (and add a flag to toggle it on and off)
This enables zeta deposits and withdraws using connector v2 , but is disabled by the flag .
The new connectors would not be enabled initially , so v37 should still fully support legacy flows
After the upgrade , we can deploy the v2 contracts but will not migrate fiunds from old connector to new , nor update the connector address on zetacore , the the EnableV2ZETAFlows will be false by default.
This makes sure all zeta deposits and withdraw work as before using V1 flows until we decide to migrate to v2 and enable the V2ZETAFlows
make start-connector-migration-testtries to replicate this