This guide explains BIP 197 collateral contract in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
TL;DR
- What it is: BIP 197 is a Draft cross-chain debt design using two Bitcoin P2SH collateral contracts and hash- and time-locked state transitions. A borrower locks refundable and seizable collateral while a lender supplies principal on another blockchain.
- Why it matters: BIP 197 shows how difficult cross-chain collateral is: funds remain safe only when scripts, secrets, deadlines, chain assumptions and non-cooperative recovery paths are validated as one state machine.
- Current position: BIP 197 is a Draft cross-chain debt design using two Bitcoin P2SH collateral contracts and hash- and time-locked state transitions.
BIP 197 collateral contract in simple English
BIP 197 collateral contract: Funds are split between Refundable Collateral and Seizable Collateral scripts according to an off-chain agreement. Their separate recovery paths determine who can claim value after different deadlines.
Simple example
A node operator is checking BIP 197 collateral contract. Approval precedes the loan period. Default can lead to bidding and liquidation. Seizure gives the lender a bounded claim.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Draft boundary
The BIP remains Draft and its linked implementation is historical evidence, not proof of audited or maintained production safety. Pin code, script bytes and the exact document revision.
Two collateral scripts
Funds are split between Refundable Collateral and Seizable Collateral scripts according to an off-chain agreement. Their separate recovery paths determine who can claim value after different deadlines.
Secret graph
The borrower, lender and optional bidder create distinct secret hashes. Revealing one secret on either chain can advance another branch, so uniqueness, entropy, indexing and observation are critical.
Time periods
Approval precedes the loan period; default can lead to bidding and liquidation; seizure gives the lender a bounded claim; a final refund path protects the borrower if seizure is not exercised.
Cross-chain assumptions
Safety depends on confirmation policy, clock and block-time interpretation, reorganisation handling, fee availability and reliable monitoring on both chains. One chain cannot guarantee the other remains available.
Script discipline
The proposed scripts allow chosen hash and timeout opcodes and include secret-length checks. Compile from reviewed parameters, compare exact redeem scripts and prohibit silent opcode or byte-order changes.
How specialists test it
Developers test the proposal with made-up data on an isolated test network. They check normal cases and deliberately invalid cases. Different implementations should reach the same result before anyone relies on the proposal.
Frequently asked questions
What is the main point of BIP 197 collateral contract?
BIP 197 collateral contract: Funds are split between Refundable Collateral and Seizable Collateral scripts according to an off-chain agreement.
For BIP 197 collateral contract, what should a beginner know about draft boundary?
The BIP remains Draft and its linked implementation is historical evidence, not proof of audited or maintained production safety.
For BIP 197 collateral contract, what should a beginner know about two collateral scripts?
Funds are split between Refundable Collateral and Seizable Collateral scripts according to an off-chain agreement.
For BIP 197 collateral contract, what should a beginner know about secret graph?
The borrower, lender and optional bidder create distinct secret hashes. Revealing one secret on either chain can advance another branch, so uniqueness, entropy, indexing and observation are critical.
Conclusion
BIP 197 shows how difficult cross-chain collateral is: funds remain safe only when scripts, secrets, deadlines, chain assumptions and non-cooperative recovery paths are validated as one state machine.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.