BTCVM alpha terms of use

BTCVM and its BTC bridge are alpha software: new, experimental, and not yet externally audited. Please read this page before you use them. By using this site, the BTCVM chain or the bridge, you agree to these terms.

Last updated 1 October 2026

What this is

• BTCVM is a separate blockchain, a Layer 1 on Metal Blockchain, that uses Bitcoin's address formats and transactions. It is not the Bitcoin network.
• The bridge moves BTC between Bitcoin and BTCVM. BTC you deposit is locked on Bitcoin in a multisig address, and the same amount, less a small fee, is issued to you on BTCVM. When you withdraw, BTC on BTCVM goes back to the bridge, which pays BTC on Bitcoin to the address you choose.
• The web wallet and the Mac app keep your key on your own device. We never see it.

Alpha means real risk

• You could lose what you send. The software may have bugs that lose, freeze or delay funds. Only use amounts you can afford to lose.
• Limits apply. During the alpha, each deposit and the total on BTCVM are capped: at the time of writing, 0.001 BTC per deposit and 0.01 BTC in total. The current limits are always shown on the site. A deposit that doesn't fit isn't credited: see held deposits.
• The operator holds the bridge's keys during the alpha. The multisig keys that control the locked BTC are held by the operator, Paul Grey. You are trusting the operator to run the bridge honestly and keep those keys safe. If they were lost or stolen, the locked BTC could be lost. Moving the keys to independent operators is on the roadmap; it isn't done yet.
• No audit, no insurance. The bridge hasn't had an external security audit. Funds aren't insured or protected by any government scheme, and the operator isn't a bank.
• Pauses. The bridge may be paused at any time, for maintenance or security, without notice. Deposits made during a pause are credited after it resumes; withdrawals wait until then.
• Timing. Payments on BTCVM are usually final in under a second. Moving BTC onto or off BTCVM waits for confirmations on Bitcoin, and can take longer when that network is busy or the bridge is paused.

Your key, your responsibility

• Your key is stored only in your browser or the app. Back it up. If you lose it, or your browser's data is cleared, nobody can recover your BTC.
• Check addresses before you send. A payment sent to the wrong address or the wrong network may be unrecoverable. Bitcoin and BTCVM addresses look the same: make sure you're on the network you mean.

Fees

Network fees on both chains, and the bridge's fee, are taken from the amount moved. They're shown before you confirm.

Held deposits and refunds

• A deposit that is too small, too large, sent without a destination, or that can't be credited for another reason is held. It can be refunded to the sender on Bitcoin, less network fees. A deposit too small to be worth the network fee may not be refunded.
• Refunds are made by the operator on request, after checks. See contact.

Changes, and ending the alpha

The limits, fees and these terms may change, and the alpha may end. If the service ends, the operator intends to give notice on this site and let you withdraw your BTC first.

What you agree not to do

• Use the service where it is unlawful for you, or if you are subject to sanctions.
• Use it for anything illegal, or try to attack, overload or exploit it. If you find a vulnerability, please report them privately instead; we're grateful for it.

No advice, no warranty, limited liability

Nothing on this site is financial, investment, legal or tax advice. You're responsible for your own decisions, and for any taxes on your transactions.

The software and the service are provided as is, without warranties of any kind. To the fullest extent the law allows, the operator isn't liable for any loss of funds, data or profits, or for indirect losses, arising from your use of the service. Where the law doesn't allow this, liability is limited to the amount you deposited.

Open source and contact

The software is open source: github.com/MetalBlockchain/btc-vm. Developed by Paul Grey @ metallicus.com.

Questions and refund requests: open an issue on GitHub, or contact Paul Grey via metallicus.com. Security issues: report them privately.