EVM - Cosmos Convergence Research From Security
summary
CertiK’s research shows concrete failures when EVM logic runs inside Cosmos: EVM precompiles become stateful and can update Cosmos modules without committing their corresponding SDK state, producing partial state transitions on success, leaving shadowed bank/staking state, or failing to roll back on EVM reverts; precompiles can also leave partial writes when gas runs out (they need only several thousand gas). Practical fixes include new Cosmos decorators to reject misrouted EVM txs, authz disabling, and Go runtime changes to make precompile execution atomic and reversible. Layered setups using CometBFT + ABCI + Engine API are viable but require strict processProposal and duplicate-commit checks to avoid block acceptance and liveness exploits.
AI-written summary · about
chapters (5)
- 0:00CertiK and EVM Cosmos research
- 1:42Cosmos EVM integration
- 4:59EVM precompiles issues
- 8:59Layered architecture trends
- 13:27Further resources
related talks
30mPractical Zero Knowledge Proofs
28mThe Cosmos Stack and the Velocity of Web3
34mMEV & Interoperability: Rollups, Cross-L2 & Cross-chain
17mThe Future of Interchain Composability
30mStrengthening Reliable Decentralized Systems at Interchain
34mPrivacy All the Way Down: Tackling MEV at Different Layers via. Cryptography
14mExploring a New Nexus: Cosmos & Ethereum
10mClear as Mud