Understanding Plasma’s modular node architecture and operator roles
Layer | Role | Trust Model |
---|---|---|
Consensus Layer (CL) | Propose and finalize blocks | PlasmaBFT |
Execution Layer (EL) | Process transactions, manage state, serve RPCs | Fully trusts its paired CL |
Goal | How Non-Validator Nodes Help |
---|---|
Keep validator set lean | Non-validator nodes don’t vote; only validators do. |
Unlimited horizontal scale | RPC providers can spin up hundreds of read/write RPC nodes, each with its own non-validator node, without requiring new validator seats. |
Maintain consensus correctness | Each execution node still follows exactly one CL. There’s no risk of state divergence. |
Reduce risk | Non-validator nodes are read-only and can’t affect consensus messages. |
Simplify failover | By following multiple validators, if one goes offline, they can switch to a new one automatically. |
Feature | Validators | Non-Validator Nodes |
---|---|---|
Consensus Participation | Full (propose, vote, finalize) | None (receive only) |
Message Types | All consensus messages | Block messages only |
Network Role | Active participant | Passive follower |
Resource Requirements | Higher (full consensus) | Lower (messaging only) |