Delayed Proof-of-Work
3 min read
Pronunciation
[di-leyd proof-uhv-wurk]
Analogy
Think of Delayed Proof-of-Work as a small town hiring the security services of a much larger city. The town maintains its own local police force (native consensus) for day-to-day operations and first response, but periodically sends snapshots of important records to be stored in the larger city's heavily fortified vault (Bitcoin blockchain). If criminals ever overpower the local police and try to rewrite the town's records (51% attack), the tamper-proof copies in the distant vault can prove what the original records contained. This arrangement gives the small town security that approaches the level of the big city, without having to maintain an equally expensive security force or surrender its self-governance.
Definition
A security mechanism that enhances the protection of smaller blockchains by periodically recording their block data onto a more secure, higher hash-rate blockchain like Bitcoin. Delayed Proof-of-Work (dPoW) allows chains to maintain their own consensus rules while leveraging the security of a more established network to prevent 51% attacks, creating a layered security approach without sacrificing independence.
Key Points Intro
Delayed Proof-of-Work implements four key innovations that create its layered security approach.
Key Points
Notary Nodes: Specialized validators elected by stakeholders that periodically create checkpoints of the blockchain's state.
Cross-Chain Notarization: Process of recording cryptographic fingerprints of the smaller chain onto the security chain through specialized transactions.
Independent Consensus: Allows the protected blockchain to maintain its own consensus rules and block validation process for normal operations.
Security Inheritance: Leverages the accumulated proof-of-work of the security chain to protect against deep reorganization attacks.
Example
A privacy-focused cryptocurrency with moderate hash power implements Delayed Proof-of-Work to protect against potential 51% attacks. The blockchain operates normally using its own consensus mechanism for transaction validation and block creation. Every 10 minutes, special elected notary nodes create a checkpoint by taking a cryptographic hash of the current block and recording it in a Bitcoin transaction. If an attacker later acquires a majority of the network's hash power and attempts to rewrite transaction history, they would need to not only overpower the original network but also create an alternative version of the Bitcoin blockchain from the point where the checkpoint was recorded—a computationally and economically infeasible task given Bitcoin's massive hash power. This allows the smaller blockchain to achieve security approaching that of Bitcoin without adopting Bitcoin's consensus rules or scalability limitations.
Technical Deep Dive
Delayed Proof-of-Work implements a multi-layered security architecture through a notarization process involving specially elected nodes. Notary nodes are selected through a stake-weighted voting mechanism where network participants elect approximately 64 nodes per season (typically lasting one month). These notary nodes participate in a modified Tendermint-based consensus protocol to agree on checkpoints of the protected chain, requiring 13 notaries to form a notarization quorum. The notarization process involves creating a special transaction containing the block hash of the protected chain, which is then submitted to the security chain (typically Bitcoin) through a pay-to-script-hash output with multiple notary signatures. The system employs a backup notarization mechanism to an alternative security chain (typically Litecoin) as a redundancy measure. For validation, nodes on the protected chain can verify the existence of notarization transactions on the security chain through simplified payment verification (SPV) proofs. The protected chain implements consensus rules that prevent reorganizations beyond the most recent notarized block, effectively limiting the depth of possible chain rewrites to the notarization interval (typically 10-30 minutes), regardless of hash power. This creates a security model where attacking the protected chain becomes as difficult as attacking the security chain after the notarization confirms, while maintaining the protected chain's independence for consensus rules, features, and governance.
Security Warning
While Delayed Proof-of-Work provides strong protection against deep reorganizations, the security guarantees only apply after notarization is confirmed on the security chain. For high-value transactions, wait until at least one notarization has been confirmed before considering the transaction finalized.
Caveat
Despite its security benefits, Delayed Proof-of-Work introduces additional complexity and potential points of failure. The system depends on the reliable operation of notary nodes, creating a semi-centralized security layer that could become a target for attacks or collusion. The notarization process also adds latency to achieving final security guarantees, creating a trade-off between immediate finality and ultimate security. Additionally, the mechanism depends on the continued operation and accessibility of the security chain, potentially exposing the protected chain to risks if the security chain undergoes significant changes to its protocol or fee structure that might affect the viability of the notarization process.
Delayed Proof-of-Work - Related Articles
No related articles for this term.