Skip to main content
Knowledge mapBase: an Ethereum Layer 2 in practiceExternal projects

You are here. See how this question connects to other ideas.

Select a node to open its page · Expand to read within the map

Knowledge mapFollow a connection. Understand a question.
← Blockchain and shared state

One question

Base: an Ethereum Layer 2 in practice

Follow the path from an L2 transaction to Ethereum.

Base is an Ethereum rollup. Its sequencer orders transactions into L2 blocks; a batcher publishes transaction data to Ethereum. Other nodes can reconstruct the L2 history from that data. The protocol also checks claims about L2 state: for example, the balances and contract data resulting from those transactions.

An early transaction response, data posted to Ethereum, and a completed withdrawal are different milestones. A payment application must choose which milestone permits delivery. Read the current network documentation for proof and withdrawal conditions rather than assuming every L2 has identical timing.

For a transfer, the first result tells the sender that the L2 has processed it. Published transaction data lets another node recompute the balance changes. A later withdrawal to Ethereum is a separate action with its own verification conditions.

Accounts, permission and fees

Start with Ethereum accounts and signatures. Base uses Ethereum-style accounts and contract execution. A signed request identifies the intended network and operation; the called contract still checks permission. The same address on Ethereum and Base does not merge their balances or contract state.

Base’s fee documentation separates execution on L2 from the cost of publishing data to Ethereum. This means a cheap contract operation is not the only contributor to the fee. Use the current fee reference when estimating a transaction, rather than a fixed price from an old example.

Continue through the Base learning path to connect authorization, fees, L2 confirmation and withdrawal.

How does this relate to ArcBlock?

Base supplies an Ethereum scaling and settlement environment. ArcBlock Chain is an application-oriented L1, while ARC is an application runtime. Comparing them requires naming the layer: chain execution, settlement, or application services.

An application can separate its interface, identity and private data from on-chain assets. That is an architectural option, not evidence that a particular ARC application already integrates Base. Continue with Ethereum and ArcBlock: applications and assets to examine this division and the documented ArcBridge connection.

Sources and further reading