Bedrock
Bedrock is a Multi-Asset Liquid Restaking Protocol With Eight-Day uniBTC Unstaking
Bedrock is a queued uniBTC exit in which a holder approves the withdrawal contract, submits an unstake request, waits eight days, and separately claims supported wrapped BTC. The request converts a liquid token position into a pending claim, so wallet balance alone no longer describes the user's status.
A 0.0001 uniBTC minimum sets the smallest direct unstake request before network and withdrawal costs are considered.
From wrapped BTC deposit to final claim
The Bedrock uniBTC lifecycle is a three-stage token workflow: mint from supported wrapped BTC, manage the resulting ERC-20 balance, and unwind through an unstake request plus a later claim.
Deposit and mint
Start by connecting a compatible wallet such as MetaMask and selecting the chain where the wrapped BTC already sits. On Ethereum, the documented path begins with WBTC. Bedrock sets no protocol deposit minimum, although its guide recommends 0.005 WBTC so gas does not dominate a very small position. A first-time wallet normally confirms two on-chain actions: ERC-20 approval and the mint. One WBTC deposited through that path mints one uniBTC under the protocol's 1:1 relationship. The new token then appears at the same address.
Balance and routine changes
The minted asset is non-rebasing, so its token quantity stays visible while the underlying value relationship carries accrual. Add the verified uniBTC contract to MetaMask if the wallet omits the symbol; an omitted display does not erase the on-chain balance. A transfer is a routine adjustment that moves only the selected portion to its recipient. If uniBTC sits in a Pendle position or another contract, it must return to the wallet before Bedrock can submit that amount for direct unstaking.
Request and return
To unwind, choose the supported network and wrapped BTC output, enter the uniBTC amount, and inspect the conversion shown before signing. A wallet with zero withdrawal allowance first submits an approval. The next transaction creates the unstake request and removes that amount from liquid use. The later claim is a separate state change. That makes three on-chain transactions from a fresh allowance state: approval, request, and claim. An existing sufficient allowance reduces the sequence to two. The pending amount cannot fund another transfer while Bedrock prepares the wrapped BTC return.
Queued redemption versus market exit
A queued Bedrock redemption is a protocol exit that preserves the displayed wrapped BTC conversion, whereas a market exit sells uniBTC through available liquidity and settles without the eight-day claim stage. Uniswap or PancakeSwap quotes reflect pool depth and price impact at that moment. The queue trades time for a protocol claim; the DEX route trades price certainty for immediate execution. uniBTC placed in Pendle must first return to the wallet before either route can use it. Choose on final output and required settlement date.
Reading balance, allowance, and request state
The uniBTC position record is an on-chain state trail made of the ERC-20 wallet balance, withdrawal-contract allowance, request transaction, and later claimable status.
Wallet amount
uniBTC on Ethereum uses 8 decimal places, making 0.00000001 uniBTC its smallest base-unit increment. One whole token therefore contains 100 million integer units. MetaMask may round the screen display, while the contract keeps the full integer. Before a request, balanceOf reports the transferable amount at the connected address. After submission, the requested portion changes from a liquid token balance into a pending withdrawal record. That distinction explains why a lower wallet balance is consistent with an unfinished claim. The two figures describe different stages of one position. Read both before making another adjustment.
Spending allowance
An ERC-20 allowance is a separate owner-and-spender value. Its initial value is 0 until the holder approves the withdrawal contract. Approval authorizes transferFrom up to the chosen amount; it does not itself create the withdrawal. Setting an exact allowance keeps the authorized quantity aligned with the intended request. If the contract consumes the full amount, remaining allowance returns to 0. Etherscan exposes balance and allowance as read-only values, so checking them requires no transaction or gas.
Request record
A confirmed Ethereum request carries a transaction hash with 32 bytes, rendered as 64 hexadecimal characters after the 0x prefix. The wallet address is 20 bytes, or 40 hexadecimal characters plus that same two-character prefix, for 42 characters total. Record the chain, requesting address, output token, amount, and confirmed time together. Etherscan supplies the raw transaction state, while the Bedrock interface translates the contract record into pending or claimable status. The claim belongs to that state record, not to the wallet's token list. This record remains useful after settlement.
How long does a uniBTC withdrawal take?
The uniBTC withdrawal lock is a fixed eight-day processing period that starts after the unstake request confirms and ends when the wrapped BTC becomes claimable.
Eight days equals 192 hours or 691 200 seconds. The countdown follows the confirmed request time, not the moment when the wallet first presents a signature. Ethereum schedules 12-second slots and groups 32 slots into a 6.4-minute epoch; those consensus intervals govern transaction inclusion and finality. They do not shorten Bedrock's application-level processing window. Use the confirmed timestamp to calculate the earliest claim date, then read the claimable state before spending gas. The interface still requires a final claim transaction after the timer expires. Network congestion changes inclusion, not the eight-day parameter, as described in Bedrock availability.
Calendar time, not wallet uptime, advances the lock. Reconnecting later only reads the contract state; it does not restart the eight-day period.
Claim conditions and partial exits
The uniBTC exit rules are fixed claim parameters covering minimum size, token precision, conversion relationship, and lock period; a live per-chain cap still limits accepted request size.
Sizing a partial request
Bedrock sets the direct unstake minimum at 0.0001 uniBTC. With 8-decimal precision, that threshold equals 10 000 base units. A partial request consumes only the chosen portion, leaving the remaining uniBTC liquid at the wallet address. The maximum must stay below the withdrawal capacity displayed for the selected chain and wrapped BTC. Capacity is a live operational input rather than a durable number. A request above it never enters the queue, while a smaller accepted request receives its own confirmed timestamp and eight-day clock.
| Fixed parameter | Required beforehand |
|---|---|
| Deposit floor - no stated WBTC minimum | Supported wrapped BTC balance |
| Mint relationship - 1 uniBTC per 1 WBTC | WBTC allowance to the mint contract |
| Unstake floor - 0.0001 uniBTC | uniBTC in the connected wallet |
| Token precision - 8 decimal places | Correct uniBTC contract imported |
| Processing period - 8 days | Confirmed unstake request |
| Claim action - 1 state-changing transaction | Claimable status and native gas asset |
Claiming the completed amount
When the status becomes claimable, reconnect the requesting wallet on the same network and review the output token and amount. Pressing Claim creates one state-changing transaction, which requires the network's native gas asset. Bedrock then releases the supported wrapped BTC to the connected address. After confirmation, compare the ERC-20 Transfer log with the application amount. The completed portion no longer qualifies for benefits tied specifically to uniBTC holdings, while any amount left outside the request continues as its own liquid position. This final transaction closes the recorded lifecycle.
The design logic behind the uniBTC lockup
The uniBTC lockup is an operational settlement layer between a transferable ERC-20 receipt and the wrapped BTC inventory that Bedrock releases after processing.
The product began with WBTC on Ethereum as the first documented mint asset. Bedrock describes uniBTC as a liquid restaking token connected to Babylon's Bitcoin staking design and built with infrastructure support from RockX. The receipt model keeps a transferable ERC-20 separate from the underlying operational settlement. Chainlink Proof of Reserve and Secure Mint add reserve-aware controls to the broader minting system, while Chainlink CCIP addresses cross-chain transfer as a different lifecycle. Those components do not collapse deposit, bridge, unstake, and claim into one action for the user (see also Bedrock alternatives ).
That history explains the wait without turning it into chain-confirmation folklore. Bitcoin targets a 10-minute block interval, and Ethereum assigns 12 seconds per slot, yet neither number defines the uniBTC claim date. Bedrock's eight-day lock is the controlling position rule. It gives the protocol time to process the selected wrapped BTC return before the holder submits the claim. The user's practical boundary is clear: a transferable uniBTC balance becomes spendable wrapped BTC only after the request matures and the claim confirms.
Questions and answers about Bedrock
Does native BTC work in the uniBTC deposit step?
No, the documented uniBTC mint path starts with supported wrapped BTC rather than native BTC in a Bitcoin wallet. WBTC on Ethereum was the first supported deposit asset, and Bedrock now presents accepted assets by network in its application. Native BTC and an ERC-20 token use different transaction models, so moving from native BTC requires a separate wrapping or supported entry route before minting.
Will a hardware wallet manage the Bedrock position lifecycle?
Yes, a hardware wallet works when its companion wallet supports the selected network and Bedrock's transaction requests. The device must sign the ERC-20 approval, unstake request, and later claim separately when those actions are required. Because the waiting period lasts eight days, keep access to the same account; a replacement interface is useful only if it can connect that account and display the relevant contract calls.
What happens to Bedrock rewards after uniBTC leaves the wallet?
Balance-based uniBTC rewards stop applying to the portion that has completed withdrawal and returned as wrapped BTC. During the pending stage, the wallet no longer presents that amount as freely transferable uniBTC, so do not infer reward eligibility from the pre-request balance. Any uniBTC left outside the request remains a separate liquid balance, while the claimed wrapped BTC follows its own token and protocol rules.
Are uniBTC amounts rounded differently from WBTC?
Both Ethereum uniBTC and WBTC use eight decimal places, so their smallest displayable unit is 0.00000001 token. Bedrock's direct unstake minimum of 0.0001 uniBTC therefore equals 10 000 base units, well above one atomic unit. Wallet interfaces may shorten what they display, but the signed transaction carries an integer base-unit amount; review that full value before confirming a partial request.
Do I keep Bitcoin price exposure during the eight-day lock?
Yes, a pending uniBTC withdrawal remains economically tied to the wrapped BTC amount scheduled for claim rather than freezing a fiat value. The eight-day lock fixes a token-denominated lifecycle, not a dollar price. WBTC continues to track Bitcoin through its custody-backed design, while any market deviation remains separate from Bedrock's request status. The application shows the wrapped BTC quantity that the claim is expected to release.
Updated