Bedrock alternatives are BTC restaking choices by custody model

Bedrock alternatives are BTC receipt-token protocols best separated by who authorizes reserve movements: a threshold-signature network, an institutional consortium, or named custodians. SolvBTC, Lombard LBTC, pumpBTC, and Lorenzo stBTC expose different control paths, redemption mechanics, and on-chain representations for users moving beyond Bedrock uniBTC.

Key takeaway: Lombard requires 10 of 14 consortium approvals, while SolvBTC moves Bitcoin through a FROST threshold-signature network.

Native BTC entry without a WBTC conversion

Native BTC holders reach a receipt token directly through Lombard LBTC, SolvBTC, or Lorenzo stBTC, avoiding a WBTC-first entry path.

Lombard assigns a fresh Bitcoin deposit address and mints LBTC after 6 confirmations. Solv Protocol monitors Bitcoin deposits into protocol-managed vault addresses, then issues SolvBTC on Ethereum or another supported EVM chain; users convert that base asset into yield-bearing xSolvBTC. Lorenzo accepts a Bitcoin transaction addressed to an approved Staking Agent and carries destination details in OP_RETURN. Since 1 BTC equals 100 000 000 satoshis, the deposit record must reconcile satoshis, the EVM recipient, and the quantity minted at the stated 1:1 mapping.

Wrapped-BTC holders follow another branch. PumpBTC accepts established assets such as WBTC, BTCB, and FBTC through chain-specific staking contracts, while Bedrock uniBTC began with WBTC. The existing asset therefore narrows the custody decision before yield, liquidity, or DeFi integrations enter the comparison.

SolvBTC and Lombard distribute signing authority

SolvBTC and Lombard distribute reserve authorization across multiple operators, but they organize the signers through different control planes.

SolvBTC: FROST reserve control

Solv Protocol uses Flexible Round-Optimized Schnorr Threshold signatures, or FROST, so each node holds a key share rather than a complete reserve key. The SolvBTC architecture links 5 operating components: the FROST Network, Vault Pool, on-chain smart contracts, an Indexer, and Auditors. A native redemption begins with a token burn; the Indexer assembles the Bitcoin request, Auditors approve it, and FROST nodes sign the transfer.

Lombard: consortium authorization

Lombard's Security Consortium has 14 institutional members, and at least 10 must approve a critical operation under its two-thirds rule. CubeSigner hardware security modules protect member keys, while the Bascule Drawbridge checks deposits before a mint proceeds. Chainlink reserve feeds update every 10 minutes, adding a supply check alongside signer approval.

Both designs distribute control, yet their accountability differs. SolvBTC emphasizes cryptographic key shares and separate operational roles. Lombard identifies a defined institutional membership and records decisions through the Lombard Ledger. Select the model whose signer replacement, approval evidence, and service continuity fit the operating mandate.

PumpBTC and Lorenzo name custody operators

PumpBTC and Lorenzo expose named operational custodians, making vendor concentration, reserve reporting, and settlement responsibilities easier to map.

PumpBTC: Cobo and Coincover custody

PumpBTC routes deposited assets into a custody stack that names Cobo MPC and Coincover. The custodian delegates equivalent native BTC through Babylon while pumpBTC circulates on supported EVM networks. Each pumpBTC represents a 1:1 reserve claim, and aggregate liabilities equal the combined token supply across chain-specific contracts. Cross-chain movement burns pumpBTC on the source chain and mints it on the destination, while quarterly custody-control reports supplement the on-chain reserve dashboard.

Lorenzo: agent-based issuance

Lorenzo organizes issuance around a whitelisted Staking Agent and names Cobo, Ceffu, and ChainUp within its custody framework. stBTC represents principal, while a Yield Accruing Token, or YAT, records the associated reward claim.

Native deposits must exceed 0.00003 BTC, equal to 3 000 satoshis. Lorenzo's OP_RETURN layout allocates 20 bytes to the destination EVM address, 4 bytes to the chain ID, and 8 bytes to the plan ID. Its documented confirmation ladder starts with 3 confirmations below 0.0004 BTC and reaches 6 above 0.5 BTC. Larger deposits therefore cross a deeper Bitcoin settlement boundary before stBTC issuance.

What should decide the custody model?

The custody model for Bedrock alternatives should match the required reserve control, entry asset, exit path, and operational evidence.

Use this decision checklist before comparing advertised yields, because the yield does not change who can move the backing Bitcoin:

• Choose SolvBTC when the mandate requires threshold Schnorr signing without one named reserve custodian.
• Choose LBTC when a 10-of-14 institutional consortium and non-rebasing exchange-rate accounting fit the control policy.
• Choose pumpBTC when WBTC, BTCB, or FBTC is the entry asset and named custody partners are acceptable.
• Choose stBTC when separate principal and YAT reward claims fit reporting and agent-based settlement.
• Keep uniBTC when Bedrock's WBTC route, Secure Mint reserve gate, and established integrations already match the workflow.

A treasury with native BTC and a signer-distribution requirement reaches a different answer from a wallet already holding WBTC on Ethereum. Record the acceptable reserve controller, destination chain, receipt-token format, and redemption authority before authorizing the deposit, which is examined in Bedrock availability.

Receipt-token accounting changes the exit

Receipt-token accounting determines whether yield changes the token balance, exchange rate, or a separate claim during custody.

LBTC is non-rebasing: the wallet balance stays constant while its BTC exchange rate incorporates distributed rewards. Solv's xSolvBTC exits into SolvBTC by burning xSolvBTC and minting an equal amount of the base reserve token. PumpBTC maintains 1:1 liability accounting across its chain contracts. Lorenzo divides the position into stBTC principal and a YAT reward instrument. Bedrock uniBTC also uses a non-rebasing design, so its quantity remains separate from its changing redemption value.

Token precision matters during reconciliation. WBTC uses 8 decimal places, matching Bitcoin's satoshi precision, while each receiving contract enforces its own integer accounting. A wallet balance alone does not show the reserve exchange rate, pending reward claim, or native redemption amount. Store those fields separately under the chosen reporting standard.

Entry preparation across Bitcoin and EVM chains

Entry preparation starts by matching the deposited BTC format to the protocol's monitored address and destination-chain token contract.

A native-Bitcoin route requires the generated deposit address, intended amount, destination EVM address, and enough confirmations for the issuer's minting rule. Ethereum Mainnet uses chain ID 1, BNB Chain uses 56, and Arbitrum One uses 42161. Treat those identifiers as distinct execution environments because the same ticker on another chain points to a different contract and transaction history.

A wrapped-asset route adds an ERC-20 approval before the deposit call. Confirm whether the protocol accepts WBTC on Ethereum, BTCB on BNB Chain, or FBTC on the selected network, then approve the exact amount required by the vault. EVM addresses contain 20 bytes, whereas a Bitcoin address belongs to a different transaction format. MetaMask and similar wallets display the user-side approval, but the receipt contract controls minting after the deposit. Archive both transaction hashes and reconcile the minted balance.

Redemption timing and fixed protocol charges

Redemption design determines whether an exit uses Bitcoin unbonding, an on-chain reserve conversion, or a custodian release process.

Bitcoin settlement windows

Bitcoin targets an average 10-minute block interval, but 6 confirmations describe six mined blocks rather than a guaranteed 60-minute deadline. Lombard waits for 6 confirmations before minting and places an LBTC redemption behind Babylon's unbonding process, which extends up to 10 days. A secondary-market transfer moves the receipt token without moving the backing BTC through that release cycle.

Protocol-defined deductions

Lombard applies a fixed 0.0001 LBTC unstaking charge. Its documented minimum withdrawal is 0.000033 LBTC, producing a combined minimum position of 0.000133 LBTC after adding the charge. Lombard also deducts 8% from Babylon staking rewards before those rewards enter the LBTC reserve and exchange rate. These amounts affect different layers: the fixed charge reduces an individual exit, while the percentage reduces the reward flow shared through the reserve.

Two-stage exits

xSolvBTC converts into SolvBTC on-chain with zero waiting period, but native BTC redemption remains a separate reserve workflow. PumpBTC burns the receipt before its custody process releases an accepted backing asset, while Lorenzo routes settlement through its Staking Agent. Choose the exit asset first - native BTC, a wrapped token, or a base reserve token - then map every required stage and charge before execution.

Reserve verification after minting

Reserve verification should reconcile token supply, backing assets, signer approvals, and the chain where each receipt circulates.

Bedrock's Secure Mint enforces at least 100% reserve coverage by rejecting a uniBTC mint that would push supply above verified Bitcoin backing. Lombard publishes a Chainlink Proof of Reserve update every 10 minutes for LBTC and BTC.b. SolvBTC combines Bitcoin vault monitoring, Auditor approval, and FROST signing records. PumpBTC's dashboard compares custodian holdings with the aggregate pumpBTC supply across chains. Each mechanism answers a different question: reserve coverage measures liabilities, while authorization records identify who approved movement. Preserve both measurements in the position record.

Custody operations beneath the receipt token

Custody operations convert a deposit event into an authorized Bitcoin movement, then bind that movement to an EVM token supply.

RFC 9591 defines FROST as a 2-round Schnorr process: participants publish one-time commitments, then return signature shares for aggregation. The complete secret does not need reconstruction during signing. Bitcoin's BIP 340 format uses 32-byte x-only public keys and 64-byte Schnorr signatures. These mechanics let a threshold-controlled vault produce a compact signature while distributing signing power, although governance still selects participants, thresholds, Auditors, and operating policies.

A named-custodian path turns the deposit event into an instruction for an identified operator to hold, delegate, or release native BTC. The receipt contract then mints or burns the EVM claim against that operational record. Bedrock alternatives should therefore be approved from a written authority map that states who controls reserve keys, who validates supply, who changes signers, and who completes redemption.

10 August 2026 Updated