Re: Introducing the Bitcoin Ordinals DID Method

Thanks Josh,

I will be distributing it more broadly to the channels and networks I have
today. Looking forward to hearing feedback about the technical
implementation details.

Brian

On Mon, May 1, 2023 at 7:09 AM Josh Eidem <josh@spaceten.com> wrote:

> Brian,
> Thank you for your insightful concise introduction to the Bitcoin Ordinals
> DID method; its balance of specificity and readability is very much
> appreciated.
>
> Melvin,
> Your response comes off as less than serious in that it addresses none of
> the substance or theory of the method proposed. Were you to provide clearly
> articulated reasoning in support of your opinion, we might thereby obtain
> the necessary foundation to begin a fulsome debate.
>
> Regards to all,
>
> Josh Eidem.
>
> On May 1, 2023, at 7:10 AM, Melvin Carvalho <melvincarvalho@gmail.com>
> wrote:
>
> -1 this is a bad idea
>
> Bitcoin is best used as a financial network
>
> Image data should be kept off chain, with perhaps references on chain
>
>
> On May 1, 2023, at 5:29 AM, Brian Richter <brian@aviary.tech> wrote:
>
> The Bitcoin Ordinals DID method is a decentralized identifiers (DIDs)
> solution that leverages the Bitcoin blockchain and ordinal theory. By
> uniquely identifying individual satoshis, this method enables creating,
> resolving, updating, and deactivating DIDs without altering the Bitcoin
> network or requiring additional sidechains or tokens.
>
> DID Syntax and DID Document
> DIDs in this method have a specific syntax, which includes a
> method-specific identifier derived from the Bitcoin address and the ordinal
> position of a satoshi. The syntax can be represented as did:btco:<satoshi>.
>
> A DID Document contains a DID's public key, authentication information,
> and service endpoints. The data model follows the W3C DID Core
> Specification, using JSON or JSON-LD as the serialization format.
>
> Creating a DID Document
> Select a unique identifier using ordinal theory to determine a specific
> satoshi within the Bitcoin blockchain.
>         • Create a public/private key pair for cryptographic operations
> and authentication.
>         • Define any necessary service endpoints for communication or
> interaction with the DID.
>         • Create a DID Document with the required properties following the
> DID Core Specification.
>         • Inscribe this document (long form json or short form text) onto
> the satoshi with the ordinal number mentioned in the identifier.
> Resolving a DID Document
>         • Retrieve the inscription data from the satoshi associated with
> the method-specific identifier.
>         • If this utxo has been spent, look for the next DID Document by
> finding another inscription in the spending transaction.
> Updating a DID Document
>         • Perform a Bitcoin transaction that sends the inscription to the
> control of a new public key (burns the current DID Document). In the same
> transaction, inscribe the new DID Document. The control will effectively
> transfer to this new DID.
>
> Deactivating a DID
>         • Perform a Bitcoin transaction that updates the DID but does not
> transfer control to a new DID.
>
> In summary, the Bitcoin Ordinals DID method provides a practical and
> secure solution for managing digital identities within the decentralized
> identity ecosystem. By leveraging the existing Bitcoin blockchain and
> ordinal theory, this method enables a range of innovative use cases and
> applications.
>
> The full specification can be found on github. I welcome your feedback,
> questions, and suggestions as this method is developed and refined. I look
> forward to collaborating with you and exploring new opportunities in the
> decentralized identity space.
>
> Best regards,
>
> Brian Richter
> Founder / CEO
> Aviary Tech / Ordinals Reserve
> brian@aviary.tech
>