Skip to content

Taproot Assets user guide - #58

Merged
bitcoinuniverseadmin merged 4 commits into
developfrom
agent/taproot-mainnet-20260925
Sep 26, 2026
Merged

bitcoinuniverseadmin merged 4 commits into
developfrom
agent/taproot-mainnet-20260925

Conversation

@bitcoinuniverseadmin

Copy link
Copy Markdown
Contributor

Adds a Taproot Assets user guide (protocols/taproot-assets.mdx) covering mints (paid by Universe or paid from your wallet), holdings, receive, send, proofs, Universe browsing and the hosted asset Lightning balance, with what you sign, who pays and what is final. It also adds a short summary in other.mdx and small wallet, glossary and transfer notes. Mainnet wording follows the product release in bitcoinuniverseio/inscribe#263.

🤖 Generated with Claude Code

Add protocols/taproot-assets.mdx, a user guide to the Taproot Assets
workspace: both mint funding modes, holdings, receive addresses, sends with
either fee payer, proofs, Universe browsing, hosted asset Lightning, what
each action signs and what is final, limits, and Signet versus mainnet.
Mainnet is described only as "when enabled".

Summarise Taproot Assets in protocols/other.mdx with a link to the guide,
and note Taproot Assets where transfer-an-asset, the wallet matrix and the
glossary were incomplete.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Mainnet mints and sends are paid from the owner's wallet (Universe pays only
on Signet), asset Lightning runs on Signet only, the wallet-paid mint can run
as a Composer step, and receive addresses are version 1 for one asset.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@bitcoinuniverseadmin
bitcoinuniverseadmin merged commit 4220a6c into develop Sep 26, 2026
1 check passed
@bitcoinuniverseadmin
bitcoinuniverseadmin deleted the agent/taproot-mainnet-20260925 branch September 26, 2026 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant