Time to read: 1 min
Trust-Minimized Transfers via Union Bridge (BitVMX)
The Union Bridge is a next-generation bridging protocol that utilizes BitVMX to move assets between Bitcoin and Rootstock with a 1-of-N trust assumption. Unlike traditional federated bridges, Union requires only a single honest functionary to ensure the integrity of the peg.
Prerequisites
- Taproot Wallet: A Bitcoin wallet capable of sending to and receiving from Taproot (P2TR) addresses.
- Rootstock Account: A standard address to receive
uBTC(Union BTC). - Union CLI or SDK: Installed in your development environment.
Getting Started
1. The 1-of-N Security Model
Union uses optimistic verification. When BTC is locked on Bitcoin, a "Challenge-Response" window opens. Functionaries monitor the chain; if an invalid peg-out is attempted, a single honest functionary can trigger a BitVMX fraud proof to stop the transaction.
2. Performing a Peg-In
To move BTC to Rootstock, you must lock funds into a BitVMX-secured VMXO.
- Request a Deposit Address: The Union API generates a unique Taproot address for your session.
- Lock Funds: Send your BTC to the generated address.
- Wait for Confirmations: The bridge requires 6 Bitcoin block confirmations (~60 minutes) to ensure finality before minting
uBTCon Rootstock.
3. Performing a Peg-Out
Peg-outs are facilitated by "Operators" who front the BTC to you on the mainchain in exchange for the locked VMXO on the bridge.
// Example: Initiating a Peg-out via the Union SDK
const tx = await unionBridge.initiatePegOut({
amount: parseUnits("0.05", 8),
destinationBtcAddress: "bc1p..."
});