Task: manage assets from Portfolio
Source bitcoinuniverseio/core (private)
Path frontend/src/pages/Portfolio/, Marketplace v1 action flow
Chain bitcoin, dogecoin
Network mainnet
Verified 2026-09-01
Intended reader: someone who holds an asset and wants to sell it. Goal: an open listing, a repriced listing, or a delisted asset. Chain and network: Bitcoin or Dogecoin mainnet.
Prerequisites
Section titled “Prerequisites”- A supported wallet, installed from its own trusted release channel, holding the asset. See connecting a wallet.
- The protocol supports the action. Check its row in the
support matrix first. If
listisNofor your protocol, no amount of retrying will change that. - The protocol’s live authority is ready. A supported action whose authority is not ready appears as a disabled control with the reason below it.
- Enough ordinary spendable Bitcoin, held separately from the asset, to pay a network fee.
Safety considerations
Section titled “Safety considerations”- Read asset-bearing outputs before your first listing. An asset can be destroyed by a transaction Bitcoin considers valid.
- A broadcast transaction cannot be recalled.
- Nobody working on Bitcoin Universe will ever ask for a seed phrase or private key. There is no support process that needs either.
- Confirm you are on
www.bitcoinuniverse.iobefore connecting.
- Open Portfolio and connect your wallet, or use explore mode first to confirm the asset is where you expect.
- Find the asset. Its card shows its live market state below the artwork: Not listed with a List control, or an active listing with its atomic price and marketplace plus Edit and Delist.
- Choose the action. List, Edit, or Delist all open the same review flow. The asset detail page presents the identical controls, so there is no separate Portfolio-only workflow.
- Read the review screen. Before your wallet is asked for anything, the
service rechecks live readiness, ownership, the listing revision, and
protocol state. The screen shows the asset, the amount, the service fee, the
network fee estimate, and the total.
- The service fee is 1.5% of the gross sale price, charged independently to the buyer and to the seller, calculated in integer satoshis with deterministic half-up rounding.
- For an ARC-20 lot, the screen shows the seller service fee and the net proceeds for the specific colored lot you selected.
- Verify before signing.
- The protocol, the exact asset identity, and the quantity.
- The price and every fee.
- The wallet network and the connected account.
- The inputs and outputs, in your own wallet’s prompt. The wallet is the final authorization boundary, not the review screen.
- Approve in your wallet. The listing appears only after the signed offer passes ownership, outpoint, ticker, quantity, payout, and signature checks.
Expected result
Section titled “Expected result”- List: an open listing on that protocol’s market, visible from the card and the asset detail, with its atomic price and marketplace.
- Edit: the same listing at the new price, as a new revision.
- Delist: the asset back to Not listed.
How to verify
Section titled “How to verify”- Reload Portfolio. The card should show the new state after its listing read succeeds.
- Open the protocol’s market and find the listing there.
- Check the activity feed. The event appears dated from when it happened.
Common failure states
Section titled “Common failure states”| What happens | What it means | Recovery |
|---|---|---|
| The control is disabled with a reason below it | The protocol supports the action, but a live gate disagrees | Read the reason. Refreshing rechecks that exact route; an earlier ready result is never reused |
| No control at all | The protocol does not support the action | The support matrix gives the registry’s reason |
| The form is disabled with an unlock-and-reconnect message | The connected extension no longer exposes a signer | Unlock the wallet and reconnect. No listing transaction was prepared |
| The action fails after signing | A required ownership, output, fee, or signature check did not match | This is fail-closed behaviour, not a downgrade to an advisory warning. Refresh market state before retrying |
| You retry and worry about a duplicate | Retrying cannot create a second open listing for the same outpoint | Read the open listing from the market |
Refresh market state after any error before trying again. Never repeat a transaction from stale data.