BTC transfers
Move BTC from an entity’s multisig address
Bitcoin is not live yet. It will land in Smart Engines and HSuite Wallet together. There is no date. This page describes what Bitcoin support will offer.
Bitcoin is a UTXO-based chain: there are no account balances, only unspent outputs. It has no native token standard, so in Smart Engines Bitcoin will be transfer-only: you will be able to move BTC, but not mint, burn, pause, freeze or claw back. Each entity’s BTC will sit in a native P2WSH multisig address of the validators.
flowchart TD
BTC["Bitcoin (coming next)"] --> XFER["Transfer BTC<br/>(only native capability)"]
BTC --> NONE["mint / burn / pause / freeze / wipe<br/>not supported"]
BTC --> MS["P2WSH OP_CHECKMULTISIG<br/>(validator multisig)"]
BTC transfers
Move BTC from an entity’s multisig address
P2WSH multisig
m-of-n OP_CHECKMULTISIG addresses over the validators’ keys
Payer-signed transactions
Transfers are prepared as PSBTs for the payer to sign and broadcast
Fee estimation
Fee rates in sat/vByte, by priority tier
| Feature | Detail |
|---|---|
| Model | UTXO (not account-based) |
| Block time | About 10 minutes |
| Finality | Probabilistic |
| Native asset | BTC (8 decimals, satoshis) |
| Token standard | None native |
Bitcoin has no native token or NFT standard, and Smart Engines will not add one. Ordinals, inscriptions, BRC-20 and Runes are not part of the planned integration.
Bitcoin entities will use Bitcoin’s native multisig rather than a single aggregated key:
OP_CHECKMULTISIG script over the validators’ keys. It follows from those keys and the threshold, so nothing is submitted to create it: the payer’s funding transaction is the entity’s first transaction.OP_RETURN output.Bitcoin takes no part in genesis. Genesis runs on Hedera (HCS topics) and XRPL (the HSUITE token and the membership NFTs) only.
| Unit | Decimals | 1 BTC = |
|---|---|---|
| BTC | 8 | 100,000,000 sats |
| Satoshi | 0 | Smallest unit |