Skip to content

Commit 4087870

Browse files
committed
try heading hierachy
1 parent c016f63 commit 4087870

File tree

1 file changed

+3
-3
lines changed
  • Intro-to-blockchain-and-ethereum/intro-to-blockchain

1 file changed

+3
-3
lines changed

Intro-to-blockchain-and-ethereum/intro-to-blockchain/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,17 +10,17 @@ At a high level, three parts cooperate: an execution layer that deterministicall
1010

1111
A consensus mechanism is how the network agrees on the next valid block. For example, **proof-of-stake**, where validators bond capital and can be slashed, and or **proof-of-work**, where miners prove computational effort.
1212

13-
### Execution Layer
13+
## Execution Layer
1414

1515
The execution layer defines how transactions are interpreted and applied to state, step by step, the same way on every node. For example, on EVM chains (Ethereum and many L2s), contracts compile to EVM bytecode.
1616

1717
Note: Execution is separate from consensus; a network can change how it reaches agreement without changing how code runs, and vice versa.
1818

19-
### State changes
19+
## State changes
2020

2121
Users submit signed transactions that describe intended changes (transfer value, call a contract). Nodes execute these deterministically and, if valid, include them in blocks that extend the chain.
2222

23-
### Immutability
23+
## Immutability
2424

2525
Immutability isn’t “forbidden by code”; it’s economically enforced. On Ethereum, blocks become finalized when ≈ two-thirds of staked validators attest to the relevant checkpoints. Reverting a finalized block would require creating conflicting finality—an act that implies slashing at least one-third of the total staked ETH. With roughly ~35–36 million ETH staked today, that’s on the order of ≥11–12 million ETH at risk, which makes rewriting finalized history prohibitively costly.
2626

0 commit comments

Comments
 (0)