Delegated Proof of Stake (DPoS)
Democratic blockchain consensus via elected delegates.
Proposed by Dan Larimer in 2013, DPoS was designed to solve the [scalability issues](/ko/terms/scalability-issues) of Proof of Work and early Proof of Stake. In a DPoS system, the community elects a fixed number of delegates (typically 21 to 101) through a continuous voting process. These delegates are responsible for reaching consensus and generating blocks in a round-robin fashion. If a delegate fails to produce a block or acts maliciously, they can be voted out instantly. This structure allows for exceptionally fast block times (0.5s to 3s) and high throughput.
🛡️ Trust Score
✅ 검증된 기술 정보
- • DPoS involves token holders voting for block producers (delegates).
- • The number of block producers in a DPoS network is typically limited (e.g., 21 or 101).
- • DPoS is generally faster and more scalable than Proof of Work.
- • Delegates can be voted out by the community for poor performance or malice.
- • DPoS requires a lower hardware barrier than PoS for non-delegates.
- • EOS, Tron, and Hive are major implementations of DPoS.
graph LR
Center["Delegated Proof of Stake (DPoS)"]:::main
Pre_proof_of_stake_pos["proof-of-stake-pos"]:::pre --> Center
click Pre_proof_of_stake_pos "/terms/proof-of-stake-pos"
Pre_consensus_mechanism["consensus-mechanism"]:::pre --> Center
click Pre_consensus_mechanism "/terms/consensus-mechanism"
Rel_validator["validator"]:::related -.-> Center
click Rel_validator "/terms/validator"
Rel_governance_token["governance-token"]:::related -.-> Center
click Rel_governance_token "/terms/governance-token"
Rel_mainnet["mainnet"]:::related -.-> Center
click Rel_mainnet "/terms/mainnet"
classDef main fill:#7c3aed,stroke:#8b5cf6,stroke-width:2px,color:white,font-weight:bold,rx:5,ry:5;
classDef pre fill:#0f172a,stroke:#3b82f6,color:#94a3b8,rx:5,ry:5;
classDef child fill:#0f172a,stroke:#10b981,color:#94a3b8,rx:5,ry:5;
classDef related fill:#0f172a,stroke:#8b5cf6,stroke-dasharray: 5 5,color:#94a3b8,rx:5,ry:5;
linkStyle default stroke:#4b5563,stroke-width:2px;
🧒 5살도 이해할 수 있게 설명
🚜 Imagine a city (the [blockchain](/ko/terms/blockchain)) where instead of everyone voting on every single law (which would be slow), citizens ([token](/ko/terms/token) holders) elect a small group of 21 council members (delegates). These members represent the people and make decisions quickly. If a council member lies or does a bad job, the citizens can fire them and elect someone new in real-time.
🤓 Expert Deep Dive
DPoS technicals rely heavily on Scheduled Block Production and Asynchronous Byzantine Fault Tolerance (aBFT). Unlike probabilistic PoS, DPoS networks know exactly who is supposed to produce the next block, allowing for sub-second latency. A critical risk is Voter Apathy: if only a small percentage of tokens are used for voting, the cost to take over the 'witness' set drops significantly. Furthermore, the 'Trade-off of 21' (the common limit of block producers) is a central point of debate; while it enables high TPS, it creates a target for censorship and regulatory pressure. Advanced DPoS systems like Hive incorporate 'Resource Credits' to avoid transaction fees, while EOS uses a resource allocation model based on staked tokens.