Ethscriptions

There is no privileged entity that sequences transactions or produces blocks. This activity is permissionless and open to anyone.

Because the system derives L2 state from all valid ethscription transactions on Ethereum L1, users can circumvent censorship by submitting any transaction with valid Data URI calldata. There is no specific inbox address required.

Whenever a user submits a valid ethscription transaction on the L1, the message is automatically processed on the L2 and sent to the L2ToL1MessagePasser with a snapshot of that ethscription state. When the block containing that transaction is settled, the user can submit an L1 transaction to prove the ethscription state. The process of block finalization takes a challenge period of 7 days to complete. The challenge period can be shortened if the block is proven by providing a ZK proof.

The Ethscriptions AppChain operates as a derivation pipeline that converts L1 ethscription activity into canonical L2 blocks. A Ruby-based derivation node observes L1 blocks, parses ethscription intents from calldata and events, and constructs deposit-style EVM transactions. These are then executed by a modified geth implementation (ethscriptions-geth) that maintains EVM state and provides standard JSON-RPC interface.

Unlike traditional rollups, users do not submit transactions directly to the L2. All user interactions occur on Ethereum L1 through standard ethscription operations (creating via Data URIs in calldata or transferring via ESIP events). The L2 derives its state entirely from this L1 activity through the derivation pipeline. Consequently, there is no gas paid by users on the L2 - geth has been modified to execute derived transactions without charging gas fees. Users only pay L1 gas costs for their Ethereum transactions.