You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
Learning path
Understand Base from authorization to settlement
Connect Ethereum accounts, L2 execution, fees and withdrawal.
Start with the signed request and its contract permission. Then locate Base’s execution, fees and Ethereum data publication. Finish by explaining why an L2 response and a withdrawal back to Ethereum have different completion conditions.
For a sample payment, identify its network, signer, asset and required confirmation. Explain why reusing an address does not move a balance between networks, and why a bridge connection alone does not make another chain an L2.
Along this path
- How does Ethereum change shared state?
Separate execution rules from consensus.
- Ethereum accounts: what does a signature authorize?
Separate the wallet, account record, signed request and contract permission.
- Ethereum gas: why failed calls still cost
Separate execution work, transaction value and fees.
- Layer 2: what is inherited from Ethereum?
Separate settlement dependence from a connection through a bridge.
- Base: an Ethereum Layer 2 in practice
Follow the path from an L2 transaction to Ethereum.
- Ethereum rollups: which confirmation matters?
Distinguish an L2 response from settlement and withdrawal.
- Ethereum and ArcBlock: applications and assets
Compare responsibilities, then examine the bridge between them.
- Bitcoin, Ethereum, Solana, Circle Arc, Base and ArcBlock
Compare state, execution and application responsibilities.