Bedrock
Bedrock uniBTC Restaking With Secure Mint
Bedrock uniBTC represents a Bitcoin restaking position through a transferable token issued against supported deposits. Its Secure Mint integration connects issuance to reported Bitcoin reserves. Minting requires an accepted input on the selected network, functioning contract controls and sufficient capacity. Reserve checks address issuance risk; the underlying staking arrangements, token transfers and withdrawal access have separate conditions.
Jump to a section
A wrapped-Bitcoin balance, a uniBTC receipt and an available withdrawal describe different states of the position. The receipt represents the deposited position, while access to an underlying asset follows the selected redemption route and its conditions.
Bottom line: Secure Mint restricts issuance through reserve checks, while access to the underlying wrapped Bitcoin follows separate withdrawal conditions.
Wrapped Bitcoin, Vaults and the Liquid Receipt
Wrapped Bitcoin provides the deposit asset, while uniBTC represents the resulting restaking position. WBTC was the initial supported wrapped token; accepted inputs vary across networks. The principal relationship is expressed as one uniBTC for one unit of supported wrapped Bitcoin, subject to decimal rounding. That relationship describes the represented deposit. A market trade has its own execution price, and redemption can include deductions.
The Ethereum Virtual Machine (EVM) implementation separates the deposit vault from the uniBTC token contract. The vault holds deposited tokens; the token contract records the receipt balances that wallets hold. Token deployments also exist outside the EVM environment, including Aptos and Solana. Their presence does not establish an identical deposit interface. The input token, network and minting facility must match for the chosen path.
A native-asset mint entry point exists in an EVM vault variant, subject to explicit enablement. Its input is the native asset of that vault's chain environment. The wrapped-token-only variant omits that entry point.
Reserve Feeds and Minting Readiness
Reserve readiness requires usable collateral data as well as a minting contract that enforces a reserve condition. Chainlink Proof of Reserve publishes Bitcoin reserve information on-chain, which Secure Mint connects to issuance controls. The reported reserve amount and the supply figure have to describe compatible accounting scopes for their comparison to be meaningful.
The published EVM vault's reserve guard runs when both feed addresses are set and the adequacy threshold is positive. It rejects reserve reports older than its configured heartbeat. This implementation compares reported supply before issuance against reserves using its configured threshold. The selected token's reported total plus the new deposit must fit within a nonzero asset cap, so the reserve guard and deposit limit constrain different parts of minting.
A reserve figure measures backing. It does not show whether a particular wrapped asset is available for immediate withdrawal.
Wrapped-Token Minting With a Stale Reserve Feed
An outdated reserve report blocks this uniBTC mint until sufficiently recent data arrives, assuming the feed settings remain unchanged. This case assumes an EVM wrapped-token vault with its reserve guard enabled. The selected input and token allowance must already be ready. Existing approval cannot change the reserve report's timestamp.
| Mint Stage | Contract Action | Asset or Guard Scope |
|---|---|---|
| Service Availability | Reject an out-of-service vault | Selected EVM vault |
| Reserve Freshness | Reject an outdated reserve report | Configured reserve guard |
| Reserve Comparison | Enforce the configured reserve requirement | Reported reserves and supply |
| Asset Eligibility | Require an allowed, unpaused token | Selected wrapped Bitcoin asset |
| Amount and Capacity | Convert units, require nonzero uniBTC and enforce the asset cap | Selected asset's accounting |
| Deposit Transfer | Transfer approved tokens into the vault | Caller's wrapped-token balance |
| Receipt Issuance | Mint uniBTC to the caller | Network's uniBTC token contract |
An outdated report stops execution before the deposit transfer, so the reverted mint issues no uniBTC. Before a retry, the updated report must meet the configured age limit and reserve requirement. The token must remain allowed and unpaused. The deposit must produce nonzero uniBTC, and the reported asset total plus the deposit must remain within a nonzero cap. A newer timestamp resolves freshness only; it does not establish sufficient reserves.
The vault performs these checks within the mint call. A successful retry transfers the deposit and credits the caller's uniBTC balance.
What Does Secure Mint Protect Against?
Secure Mint enforces a configured reserve requirement during token minting where the guard is enabled. Unbacked token issuance can drain assets from liquidity pools that trade the affected token. It can also introduce unsupported collateral into lending markets. The reserve control's effectiveness depends on its data feed and deployed enforcement logic. Custody arrangements determine access to actual Bitcoin reserves, while staking conditions govern the underlying commitment. A lending market or liquidity pool that accepts uniBTC introduces its own contract exposure.
Babylon Staking and Reward Entitlements
Babylon provides the Bitcoin staking connection behind uniBTC's restaking role. Minting a receipt establishes the token position.
The native Bitcoin staking layer and the wrapped-token deposit layer operate in different environments. Connecting them requires arrangements that associate the deposited exposure with underlying BTC staking. The mint itself does not establish a particular reward distribution or guarantee an immediate staking payout. Staking availability, the underlying commitment and reward allocation rules determine that part of the position. uniETH has a separate ETH restaking model; its reward accounting cannot be applied automatically to the Bitcoin receipt.
Bedrock Diamonds are a separate incentive system associated with qualifying activity, including holding uniBTC. Campaign rules and multipliers can change. A points allocation describes participation credit under those rules. It does not establish a fixed Bitcoin yield or an immediately claimable token payment.
Additional yield from providing liquidity follows the selected pool's rules and exposures. Holding the receipt alone does not create a liquidity-provider position.
Cross-Chain Movement and Withdrawal Eligibility
Cross-chain transfer moves the liquid receipt between supported networks, while withdrawal concerns access to an underlying wrapped asset. Bedrock uses Chainlink Cross-Chain Interoperability Protocol (CCIP) for its documented uniBTC bridge. The uniBTC bridge applies source-to-destination transfer caps. The supported route and available capacity constrain a transfer; a request exceeding the route's remaining cap is rejected. The documented EVM bridge interface restricts cross-chain operations to externally owned accounts (EOAs).
Withdrawal requests require a supported network and wrapped asset. Requests below the applicable minimum or above the available quota cannot proceed, and the withdrawal contract's blacklist can block listed addresses from claiming their requested assets. A token balance on a destination chain does not establish a local withdrawal facility. Where withdrawal is enabled, holders request withdrawal, wait for processing and then claim the unlocked wrapped Bitcoin. Processing parameters and fees govern that exit. The amount displayed for a request therefore needs to be understood alongside the withdrawal deduction and claim state, rather than treated as an already received wallet balance.
Can Selling uniBTC Replace Protocol Redemption?
Selling uniBTC can provide a market exit when liquidity is available, while redemption follows the protocol's withdrawal conditions. A sale transfers the receipt to a buyer at the execution price. Pool depth, trading costs and price impact determine the proceeds. Protocol redemption instead returns an available wrapped-Bitcoin asset under its claim and fee rules. Sale proceeds can differ from the receipt's represented principal. Keeping the original wrapped token preserves exposure to that wrapper without adding the uniBTC restaking position; minting adds access to the liquid restaking receipt and its associated dependencies.
Before you start with Bedrock uniBTC
Is a New Token Approval Required for Every uniBTC Mint?
A new approval is unnecessary when the selected minting vault already has sufficient allowance for that input token. Approval belongs to a specific token and spender on a specific network. An allowance for another contract or chain does not cover this deposit, and a previously used allowance may be insufficient.
Does Burning uniBTC Return the Deposited Wrapped Bitcoin?
Calling the EVM uniBTC token's burn function destroys tokens without releasing collateral from the deposit vault. Token burning and protocol redemption have different effects. The withdrawal mechanism governs access to the underlying wrapped asset, so a direct token burn is not a substitute for an unstaking request.
Which Decimal Precision Does EVM uniBTC Use?
The EVM uniBTC token contract uses eight decimal places, making its smallest representable amount 0.00000001 uniBTC. For 18-decimal deposit tokens, the published EVM vault rounds the receipt amount down to eight decimals but transfers the full deposit. If the conversion produces zero uniBTC, the mint reverts. This precision describes token representation; deposit capacity and withdrawal charges follow separate rules.
Will Adding uniBTC to a Wallet Create Another Deposit?
Adding uniBTC to a wallet's token list changes the wallet display without minting tokens or creating a deposit. The wallet needs the correct token identity for its selected network to display the existing balance. Importing a token does not authorize the minting vault to spend a wrapped-Bitcoin asset.
Why Can a Funded wallet's uniBTC Transfer Still Fail?
Address-freezing controls can restrict a funded wallet's uniBTC transfers in the EVM token implementation. A frozen sender can transfer only to a designated recipient. A sufficient balance does not override that restriction, which is separate from a minting pause or a failed reserve check in the vault.
What Transaction Cost Remains After a uniBTC Mint Reverts?
An Ethereum mint included on-chain can consume gas even when execution reverts. The gas fee pays for computation already performed; the failed mint does not issue uniBTC. A wallet simulation that rejects the call before submission is different from an included, failed transaction and does not itself consume on-chain gas.
last updated