[DO NOT MERGE] Mainnet vs main: EVM bridge contract upgrade diff#210
Closed
vishalchangrani wants to merge 2 commits into
Closed
[DO NOT MERGE] Mainnet vs main: EVM bridge contract upgrade diff#210vishalchangrani wants to merge 2 commits into
vishalchangrani wants to merge 2 commits into
Conversation
This represents the versions to be upgraded to from mainnet. DO NOT MERGE — this is a review-only branch showing mainnet → main diff.
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
This was referenced Apr 16, 2026
Closed
Closed
Closed
Closed
Author
|
Closing in favour of a simpler PR using main directly. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR exists solely for multi-signer upgrade review. It shows the exact diff between the contracts currently deployed on Flow mainnet and the target versions on
main.How to read this PR
vishal/mainnet-deployed0x1e4aa0b87d10b141,0x93c18b0282a6b82c,0xf1ab99c82dee3526vishal/targetmain— what will be upgraded toGreen (additions) = new code being introduced by the upgrade
Red (deletions) = existing code being replaced/removed
Contracts covered (27 files)
Bridge contracts (
0x1e4aa0b87d10b141)FlowEVMBridge— core bridge logicFlowEVMBridgeAccessor— bridge accessorFlowEVMBridgeConfig— configurationFlowEVMBridgeCustomAssociationTypes— custom association typesFlowEVMBridgeCustomAssociations— custom associationsFlowEVMBridgeHandlers— token/NFT handlersFlowEVMBridgeNFTEscrow— NFT escrowFlowEVMBridgeResolver— bridge resolverFlowEVMBridgeTemplates— templatesFlowEVMBridgeTokenEscrow— token escrowFlowEVMBridgeUtils— utilities (largest change)CrossVMNFT,CrossVMToken,FlowEVMBridgeHandlerInterfaces,IBridgePermissions,ICrossVM,ICrossVMAsset,IEVMBridgeNFTMinter,IEVMBridgeTokenMinter,IFlowEVMNFTBridge,IFlowEVMTokenBridgeArrayUtils,ScopedFTProviders,Serialize,SerializeMetadata,StringUtilsExample/handled token contracts
ExampleNFT,ExampleToken(0x93c18b0282a6b82c)USDCFlow(0xf1ab99c82dee3526)Key changes to review
FlowEVMBridgeUtils(largest diff) —EVM.Result/call()→EVM.ResultDecoded/callWithSigAndArgs()API migration for reduced computation costFlowEVMBridge— updates to use new EVM call API throughout core bridge logicFlowEVMBridgeAccessor— bridge accessor using new EVM APIFlowEVMBridgeHandlers— handler updates for new EVM APIUSDCFlow— USDC handled token contract changes🤖 Generated with Claude Code