How Proof Gating Works
Before any mint or burn proposal executes, the Operator Queue verifies a cryptographic proof of the corresponding Bitcoin transaction. This proof must show that the transaction:- Has reached the required number of confirmations.
- Originates from a whitelisted Series or Master Vault address.
- Matches the expected input and output values.
- **Deposit Proof: **When a lender sends BTC to a Series vault, the Operator Queue waits for the configured confirmation threshold (e.g., 3 blocks). Once verified, a proof is submitted to the contract, which mints the corresponding uBTC.
- Burn Verification: When a lender redeems BTC, uBTC is burned first on Nexio’s on-chain layer. The Operator Queue validates this burn event before releasing the signed PSBT to return Bitcoin from the vault.
- Continuous Reconciliation: Every mint, burn, or redemption updates the vault’s values to keep the two ledgers perfectly aligned.
2.19.49p.m..png?fit=max&auto=format&n=Dv9a64UftR3n6uVI&q=85&s=a519693d582a102a990c43c7a3d211f0)
Example: Proof Gating
Imagine a lender deposits 2 BTC into a 90-day Series vault.- After 3 confirmations on the Bitcoin Network (each confirmation is ~10 minutes), the Operator Queue receives proof of the deposit.
- The system validates the input, address, and amount, then mints uBTC at the current BTC/uBTC price.
- If the lender later redeems, their uBTC are first burned on-chain, and only then is the system co-signed to release their 2 BTC (plus accrued yield).