What Is a Bitcoin Digital Object?
A Bitcoin Digital Object (BDO) is a digital object whose ownership is secured by Bitcoin. Unlike a traditional digital file, a BDO can be owned by a person rather than by an application, verified from public evidence without relying on the platform that issued it, and carried across compatible applications.
BDO is an open category — not a protocol, a token standard, a company, or a product. It describes what kind of thing an object is, the way “document” or “photograph” describes a kind of thing, independent of any particular software. The category is defined publicly, in the open, and no organization owns it.
What makes something a BDO
An object qualifies as a Bitcoin Digital Object when it has three properties:
- Own — ownership belongs to the user who holds it, anchored to Bitcoin. No application, marketplace, or platform is intended to be the ultimate source of truth for who owns the object.
- Verify — its integrity and its issuer's signatures can be checked independently, from public, portable evidence, without relying on the issuing platform.
- Carry — the object, together with the evidence needed to keep recognizing and verifying it, can travel with its owner across compatible applications.
These properties are conceptual: they say what must be true of the object, not which technology must make it true. How they are realized is the job of open technical specifications — the first of which is STAS-01, an open interoperability specification for representing BDOs using the Taproot Assets protocol on Bitcoin.
What a BDO is not
- Not a protocol. Protocols (such as Taproot Assets) provide ways to own and transfer Bitcoin-secured state. BDO defines what that owned state means as a portable digital object.
- Not a token standard. Specifications like STAS-01 define how BDOs are represented technically; the category itself is independent of any of them.
- Not a company or a product. No vendor owns the category. Platforms can implement it; none of them is required to create, hold, or verify a BDO.
The kinds of BDOs
Within the STAS-01 specification family, RFC-0017 — currently In Review — defines the proposed vocabulary of object Types, each with explicit real-world semantics:
| Type | What it is | What presenting it does |
|---|---|---|
collectible | a digital collectible; the media is the object | nothing — it is never consumed |
ticket | an admission entitlement (event, ticket type, validity) | admission consumes it |
membership | a grant of access (scope, validity) | it is checked, never consumed |
redeemable | a promise that can be redeemed a declared number of times | each redemption consumes one use |
certificate | a certification statement about a subject — for example the authenticity of a physical item | nothing — it is presented and verified, never consumed |
Under STAS-01, the Type travels inside the object's signed document, fixed at issuance by the issuer's own signature — a ticket is a ticket because its issuer signed it as one, not because a database says so. This is also how BDOs can represent memberships, tickets, certificates of authenticity, and links to physical products, not only collectibles.
Who can create BDOs
Anyone. The category is open, and open specifications for it are public. Creating, holding, and verifying BDOs does not require any specific vendor or platform — existing implementations are simply the ones that exist so far (see Implementations). The definition of the category lives in a public repository, and the specifications developed for it evolve through open RFC processes.
Go deeper: Own, Verify, Carry — the principles · STAS-01, an open specification for BDOs · FAQ — including how a BDO differs from an NFT · BDO-01, the category's defining document (GitHub)