Changelog

Documentation version history

This changelog covers the documentation, not the TAP protocol. TAP is defined upstream in the Trac ecosystem and has its own release history.

2.0.0, 1 September 2026

A rebuild from a short marketing site into a complete protocol dossier, with every rule traced to code that Bitcoin Universe runs.

• Added a normative specification with numbered rules covering the carrier, the byte level payload contract for token-transfer, ticker rules, decimals and amounts, the operation table with per operation fields, the authority model, state transitions and every invalidity condition.
• Added a test vectors page with accepted and rejected payloads taken from the indexer's own test suite, each mapped to the rule that decides it.
• Added a client side payload validator that ports the indexer's transfer content parser.
• Rewrote the guide around the two step inscribe then send transfer, with worked payloads and the failure that costs holders money.
• Rewrote the reference with confirmation, mempool and reorg semantics, a concrete BRC-20 comparison, fee and size considerations, limitations, security considerations and an implementation checklist.
• Replaced the general claim that TAP supports authorities with the specific, grounded statement: a deployment binds an authority through prv, authority bearing operations require its authorisation, and Bitcoin Universe's TAP indexer does not index them.
• Recorded the support matrix from the Bitcoin Universe protocol registry and its generated capability snapshot, including the one unsupported marketplace action and its recorded reason.
• Corrected the repository and site links, which previously pointed at an organisation name that does not own this repository.
• Added client side search, a theme toggle, a 404 page, a sitemap, a robots file and an accurate llms.txt.
• Rebuilt the visual language around authorisation: indigo for ordinary operations, gold reserved for authority bearing ones, with signature flow diagrams.

Facts preserved from version 1.0.0: TAP uses Ordinal inscriptions to create transferable token actions; deploy, mint and transfer form the foundation; a transfer becomes an inscription that is sent to its destination; TAP supports a broad character space for tickers; authorities, peer to peer trading and DMT extend the basic set; transferable inscriptions need protecting from accidental spending.

1.0.0, 12 August 2026

• Initial public pages: a home page, a discovery page and a getting started page, written as an introduction rather than as a specification.
• Established the accurate core claims listed above, which this version keeps.

Versioning policy

• Major when a normative rule changes meaning, when a rule is removed, or when the document is restructured enough that rule identifiers move.
• Minor when rules or vectors are added without changing existing ones.
• Patch for corrections that do not change any rule.
• Rule identifiers such as EN-7 are stable within a major version. Vector identifiers such as R-9 are stable within a major version.

Known gaps

Stated openly rather than papered over:

• The authorisation format for token-send and the authority inscription format are not specified here at field level. They do not appear in Bitcoin Universe's code in a form this site could verify, so the upstream Trac documentation is the reference for them.
• There are no authority vectors, for the same reason.
• The maximum inscription content size for a transfer is a deployment configuration value rather than a fixed protocol constant, so rule EN-1 states the shape of the limit rather than a number.
• Support claims cover Bitcoin Universe surfaces only. No claim is made about third party wallets, indexers or marketplaces.