Skip to content

Safety in sixty seconds

Source bitcoinuniverseio/core (private)
Path Marketplace v1 action flow, frontend market state components
Chain bitcoin, dogecoin
Network mainnet
Verified 2026-09-01

Six things. Read them before your first transaction; the linked pages have the detail.

Core is non-custodial. It never holds your keys and never moves an asset without a signature you approve in your own wallet.

Nobody working on Bitcoin Universe will ever ask for your seed phrase or private key. There is no support process that needs either. Treat any such request as an attack, whoever it appears to come from.

Core is at www.bitcoinuniverse.io. The bare bitcoinuniverse.io redirects to a different application.

A market that says its reader is unavailable is telling you the read failed, not that the market is empty. A figure shown as a dash was not measured; it is not a zero.

Do not create or repeat a transaction from stale market data. Reading the numbers.

4. An unavailable action is a safety decision

Section titled “4. An unavailable action is a safety decision”

An action Core will not perform is not proof that an asset or market does not exist. Nine of the 29 marketplace protocols support neither buying nor listing, thirteen sit behind a feature gate, and any protocol’s live authority can close at any time. The support matrix says which, and why.

Core’s checks fail closed: a required mismatch blocks an action rather than downgrading to a warning you can click past.

An output holding an inscription looks exactly like ordinary change. Spend it as change or use it as fee padding and the asset is gone, in a transaction Bitcoin considers perfectly valid.

Worse, a malformed rune marker destroys every rune balance a transaction spent, and no validity check can see it. Core reads that marker and refuses. Asset-bearing outputs.

Core’s review shows the asset, the amount, the service fee, the network fee estimate, and the total before your wallet asks you to sign. That is a summary of what Core intends.

Your wallet shows the transaction’s own inputs and outputs. Read them there. The wallet is the final authorization boundary.

A broadcast transaction cannot be recalled.