Hashrate Escrows (Consensus layer)

The five-minute read

One action, walked through

1. Open BIP 300 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: BIP-300 enables a new type of L2, where "withdrawals" (the L2-to-L1 txns) are governed by proof-of-work -- instead of a federation or fixed set of pubkeys.
3. Name the object that changes: Hashrate Escrows (Consensus layer).
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing BIP 300 at the status the text itself states: Draft.
• The object that has to change is Hashrate Escrows (Consensus layer). A neighbouring document with a similar name is not this one.
• This page is not a guide to moving funds.

What happened after the paper

The source marks this draft. It is not a live consensus rule just because it has a number. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What is the timeout in Hashrate Escrows (Consensus layer), and who can take the coins when it expires?
• Which chain, if any, adjudicates the dispute?
• Which fields are committed: Hashrate Escrows (Consensus layer)?

Terms

BIP 300

The public text titled Hashrate Escrows (Consensus layer).

Draft

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

A payment or a bridge that cannot name the dispute path is a custodial promise with extra steps.

What the design proposes

• BIP-300 enables a new type of L2, where "withdrawals" (the L2-to-L1 txns) are governed by proof-of-work -- instead of a federation or fixed set of pubkeys.
• BIP-300 emphasizes slow, transparent, and auditable withdrawals that are easy for honest users to get right and hard for dishonest miners to abuse.
• The main design goal for BIP-300 is ''partitioning'' -- users can ignore BIP-300 txns if they wish; it makes no difference to L1 if the user validates all, some, or none of them.

How the mechanism is specified

• Taken from the specification, the next constraint is: BIP-300 emphasizes slow, transparent, and auditable withdrawals that are easy for honest users to get right and hard for dishonest miners to abuse.
• Locate Hashrate Escrows (Consensus layer) in BIP 300 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• A specification of a hash lock is not a working route, and not a guarantee the counterparty is online.
• This page is not a guide to moving funds.
• The source marks this draft. It is not a live consensus rule just because it has a number.

Why a venture studio still reads it

Use BIP 300 when a pitch says 'Hashrate Escrows (Consensus layer)' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.