Awarded once after a correct answer.
Evaluate a system through explicit trade-offs
Useful first : Consensus and finality · From signing to settlement
Reading path · 4 / 41 · Intermediate
A secure base chain can host an insecure application.
The essentials
A secure base chain can host an insecure application. Consensus, contracts, oracles, bridges, interfaces and key custody each create separate risks. A technically valid signature can transfer assets to an attacker after a deceptive approval request.
How it works
Layer 2 systems move some execution away from the base layer. Rollups use published information and proofs or challenges to connect the result to the settlement layer. Evaluate sequencers, upgrade powers, data availability and exit paths rather than assuming every system inherits identical security.
What to watch
A soft fork tightens validity rules with a form of backward compatibility; a hard fork changes rules incompatibly and may split participants. Software adoption involves people and organisations. Similarly, a token representing an external asset needs enforceable legal rights, reliable custody and redemption processes: recording a claim does not ensure the claim can be honoured.
Understand the details
Throughput measures processed activity, latency measures waiting, and finality concerns reversal assumptions. A fast interface can hide a centralized sequencer or a later settlement step. Compare systems using the same workload and security boundary: transfers are not equivalent to complex contract calls, and a laboratory peak is not sustained public-network capacity.
Boundaries and common mistakes
Decentralization has several dimensions: block production, software clients, hosting, governance and access to data. More validators do not automatically mean more independent operators. Upgrades can repair defects but may introduce privileged control. The useful question is which failures the system tolerates, which actors must cooperate and whether users can exit during an incident.
The mechanism at a glance
- 01Workload
- 02Security assumptions
- 03Failure scenario
- 04Recovery and exit
Read these as connected concepts, not necessarily consecutive steps.
Read the explanation
Throughput measures processed activity, latency measures waiting, and finality concerns reversal assumptions. A fast interface can hide a centralized sequencer or a later settlement step. Compare systems using the same workload and security boundary: transfers are not equivalent to complex contract calls, and a laboratory peak is not sustained public-network capacity.
Put the mechanism into context
Network A reports very low fees but depends on one transaction-ordering service. Network B costs more but permits several independent submission paths. Prepare a comparison with cost, censorship, outage recovery and exit conditions. Neither fee alone nor operator count alone resolves the decision.
Apply it in the workshop →What this mechanism does not guarantee
Decentralization has several dimensions: block production, software clients, hosting, governance and access to data. More validators do not automatically mean more independent operators. Upgrades can repair defects but may introduce privileged control. The useful question is which failures the system tolerates, which actors must cooperate and whether users can exit during an incident.
The distinction that changes the analysis
A ledger may accurately record “parcel delivered” even when an operator entered that claim incorrectly. Evaluate the source of the statement as well as the integrity of its storage. An immutable mistake still requires an explicit correction process.
Explain it yourself
Revisit the case above. Name what is established, what remains to be checked and the evidence needed to conclude. A strong answer addresses both sides of the diagram.
Apply the lesson to a case
Network A reports very low fees but depends on one transaction-ordering service. Network B costs more but permits several independent submission paths. Prepare a comparison with cost, censorship, outage recovery and exit conditions. Neither fee alone nor operator count alone resolves the decision.
Identify the measurement period, transaction type, data-availability assumptions, upgrade powers and tested recovery process. Separate normal operation from failure behavior. Write one unanswered question for each network; uncertainty should remain visible instead of being converted into a numerical score without evidence.
Terms in this lesson
- Oracle
- A mechanism that supplies a contract with information originating outside its immediate execution context.
- Rollup
- A scaling system that links off-chain execution to a base layer using published information and a proof or challenge mechanism.
Prepare a correction note
Describe the passage and the proposed correction. This creates a local note for you to share; it sends nothing. Do not include personal or confidential information.