Disclaimer & responsibility
Non-custodial
Bitcoin Tools never holds your private keys, your seed, or your funds. Any sensitive operation (signing, broadcasting) requires your explicit confirmation inside your wallet (Xverse). If you lose your seed, we cannot restore anything.
Irreversibility
Once broadcast and confirmed, a Bitcoin transaction cannot be cancelled. The Speed Up (RBF) and Cancel features only work while the transaction is unconfirmed. Always verify addresses, amounts and fees before signing.
Fee estimates
Fee rates displayed come from mempool.space and can change quickly. A βlowβ estimate at build time may be insufficient a few minutes later. No guarantee of confirmation within any given window.
Ordinals data
Ordiscan enrichment may be incomplete (quota exhausted, API outage, very recent inscription). Bitcoin Tools flags this with an unknown label. Do not sign while a UTXO involved is not fully resolved, unless you know what you are doing.
No financial advice
Bitcoin Tools makes no recommendation to buy, sell, mint or invest. Bitcoin Overview indicators (price, Fear & Greed, news) are purely informational.
Risks specific to ordinals, runes and BRC-20
- The value of inscriptions, runes and BRC-20 is extremely volatile and can fall to zero.
- A wrong move can permanently burn an asset (accidentally sent as fee, wrong runestone, spending a rare UTXO as payment).
- Standards evolve. Bitcoin Tools keeps its builders up to date, but a fork or protocol change can invalidate an in-progress PSBT.
Availability
Bitcoin Tools is provided βas isβ, with no availability guarantee. External APIs (Ordiscan, mempool.space) can go down. The team may enable maintenance mode or disable a tool without notice for security reasons.
Privacy
Bitcoin Tools records anonymized usage statistics (login: country/region, SHA-256-hashed IP; tool usage: counters; broadcasts: txid + tool + fee). No wallet data or private key is stored on the server. See Concept for details.
Open source & self-hosting
You can audit the code and self-host it if you wish. In that case, you are responsible for the configuration, API keys, and security of your deployment.
