I read this with excitement. But I am not sure a lot of people grasps how significant this move is. So I will share my thoughts to help glean why I think this is the right move, and critically, the right response to the structural issues @N0xyGen and others have been raising.
This R&D effort is a deep architectural paradigm shift that could solve the structural problem beneath the “dying chain” symptoms (empty blocks, fragile DeFi dependencies, reliance on treasury subsidies to maintain Aave/RealT). Gnosis leads the charge when it comes to DeFi execution and innovation but the cost of ecosystem replication is brutal. Every isolated domain pays a bootstrapping tax and still, can’t out-spend mainnet’s liquidity gravity. Synchronous composability treats the disease where mercenary incentive program puts a band-aid on the symptoms.
Here is what i find most compelling compared to other L2 pivots:
1. It solves Gnosis’s specific existential problem: Synchronous composability means Gnosis doesn’t need to subsidize its own isolated Aave deployment or bootstrap a parallel DeFi ecosystem from scratch. It can compose directly with Aave on L1. This almost completely offloads the infrastructural burden that slowly kills most chains.
2. It turns Gnosis Pay into an anchor: The concern that a multichain Gnosis Pay would drain transactions from Gnosis Chain is valid. But if Gnosis Chain is synchronously composable with mainnet, Gnosis Pay running natively on Gnosis gets Ethereum liquidity by default. It removes the bridge or fragmentation worries and the multichain problem dissolves because Gnosis is no longer an island.
3. A genuine path to GNO value accrual: The current model (treasury-funded staking rewards) is replaced by a model where GNO finds genuine economic function emerging naturally from Jordi’s architecture, whether as sequencer collateral, preconf staking, or capturing fees from the cross-domain execution premium.
Technical Paradigm Shift
What makes Jordi’s execution table model architecture and the native rollup precompile, genuinely different is the atomicity guarantee. Bridges give us eventual consistency. Message-passing gives us asynchronous composability. But the ability to read and write state across domains within a single transaction changes what kinds of applications can exist. Any app that needs to reference state on multiple chains simultaneously (cross-chain liquidations, multi-venue settlement) currently has to fragment or centralize as they currently cannot operate atomically. Even state-of-the-art omnichain architectures like LayerZero OApps are fundamentally asynchronous. They require developers to fragment execution and build complex fallback logic because if the destination transaction fails, the source transaction has already finalized and cannot revert. Synchronous composability eliminates that forced choice, if one side of the cross-domain call fails, the entire transaction atomically reverts, exactly as it would on a single L1.
As this is pushed forward, there are two sharp R&D questions worth exploring in the 6-month sprint:
- Sequencer Incentive Alignment & DOS Vectors: In a based rollup model where L1 validators sequence L2 blocks, how do you prevent DOS or MEV centralization from proposers who have a head start on proof computation? As cross-domain MEV becomes the most valuable flow, keeping builder/sequencer incentives aligned will be uncharted territory
- Failure Mode Granularity: As Jordi noted in the linked post, if a rollup state update is skipped, the whole transaction fails. For a simple swap, all-or-nothing atomicity is fine. But for complex operations spanning 3+ domains, the blast radius of a single rollup hiccup is massive. Can we design graceful degradation into the execution table model, or is strict atomicity the only safe path?
Historical Risk
The honest strategic risk worth naming is historical: Gnosis’s track record of building brilliant public-good primitives (Safe, CoW, Conditional Tokens, and even pioneering the charge towards a crisis response framework - A Framework for the Future) that other ecosystems can leverage or capture the value from is both its greatest strength and a vulnerability.
Already noting that “Gnosis can define it and thereby ensure that we are positioned to benefit” is the right instinct. But defining the standard may not be enough. If this R&D produces a generalized synchronous composability framework, the value-capture mechanism needs to be designed deeply into the architecture, not bolted on after. Gnosis must be the canonical, highly-defensible implementation.
I remain excited to see where this goes as this is exactly the leadership this community and the entire crypto ecosystem needs.