Art that lives on Bitcoin

A hosted image depends on someone continuing to serve it. Inscribing the file puts its bytes into Bitcoin’s transaction history. People can recover and verify the work independently of this directory, compare its hash, and build new viewers around it. Onchain storage does not remove the need for nodes, indexers and compatible software; it makes the underlying material recoverable without relying on one publisher’s server.

Counterparty is the commercial unit: the asset name, supply, balances and transfers collectors trade. A token transfer does not automatically transfer an ordinal or the issuer’s authority to update an asset description.

Counters indexes qualifying files carried as Counterparty descriptions in Taproot witness data. In RARE’s dual-inscription approach, the artwork is placed in that description while the same content is inscribed as an ordinal. The Counter records the asset’s onchain file event; Ordinals identifies the inscribed sat.

These are linked records, not a protocol-enforced ownership bundle. RARE uses the Counterparty asset as the collecting and trading unit, with the ordinal as an artwork and provenance reference. A 300-supply asset can reference one master artwork; that does not create 300 independently redeemable ordinals. Each 1/1 edition needs its own explicit mapping.

After inscription, an asset description can be updated to an onchain JSON reference for wallet-friendly images and information. That changes the current description, not the historical artwork bytes. Counters retains qualifying inscription events; a later qualifying reinscription is another event. Token balances and the power to update descriptions remain separate responsibilities.

Ordinals can link children to a parent whose owner authorized their creation. Recursive artwork can reuse inscribed code, textures and other content. This lets shared building blocks serve many works instead of repeatedly storing the same material.

“Upgradeable” does not mean editable history. An artwork can be designed from the start to select later, authorized inscriptions through recursive rules. New versions add new bytes; the original stays intact. A delegate points to another inscription for its content, but delegation alone is not a mutable upgrade switch. The selection rules and who can influence them should be explicit.

Prepare the final file, record its hash, and decide the asset name, supply and rights before minting. Use a composer that supports the dual envelope and the Ordinals fields you need; test its output with both indexers before broadcasting.

1. Mint and inscribe together

   Compose the Counterparty issuance with the file as its description and a counterparty/ord Taproot envelope. Include the title and traits as Ordinals properties before signing the commit/reveal pair. Arbitrary CBOR metadata is a separate field; do not assume a tool’s metadata option writes properties. Save the confirmed transaction, asset and inscription IDs.

2. Inscribe a small token image

   Create a 48×48 RGB or RGBA PNG thumbnail and inscribe it with the correct image MIME type. Keep this wallet icon separate from the full artwork so small token lists do not load the original file.

3. Inscribe the linking JSON

   Create JSON with the exact asset name, a concise description and the thumbnail content URL. Include the full artwork inscription link using fields your target viewers support. Inscribe that JSON as application/json, then verify that its content and image URLs resolve to the intended bytes.

4. Update the Counterparty description

   From the address with issuance authority, update the asset description to the JSON reference without increasing supply. Keep description-update authority available until this step is complete. Record the update transaction alongside the original dual inscription.

5. Check every collecting surface

   Check the asset in Counterparty, its original event in Counters, and the artwork, thumbnail and JSON in Ordinals. Verify supply, issuer authority, content hashes and any parent/child relationships. Check the wallets and markets collectors will actually use.

A future vault could hold a corresponding ordinal and release it when the mapped Counterparty asset is locked or surrendered. That would need explicit custody, redemption and supply rules, proof of reserves, and protection against both representations being sold independently. It is a design possibility—not a redemption facility currently offered by RARE, nor a promise attached to every asset.