- From: Gabe Cohen <gabe@tbd.email>
- Date: Mon, 1 May 2023 13:50:43 -0700
- To: Brian Richter <brian@aviary.tech>
- Cc: "W3C Credentials CG (Public List)" <public-credentials@w3.org>, Melvin Carvalho <melvincarvalho@gmail.com>
- Message-ID: <CAPPN6ph8Jq05PPVhVXz_CWD1N7RG__LmMLX4G23etwVicjFm8g@mail.gmail.com>
Cool work, Brian! I’m curious if you’ve run any numbers for how well the method scales? I see there’s a section on cost/transaction fees which mentions batching. Do you know the cost If, say 1000 or 10k DIDs were in it? I am trying to evaluate DID methods on a global scale. This means each human on earth could have multiple. So, if everyone on earth used the method (let’s say 10B DID:BTCOs), would it consume all Bitcoin block space and become untenable? If not, seems like it’s more of an experiment, which still has value — and is neat! Gabe On May 1, 2023 at 12:39:01 PM, Brian Richter <brian@aviary.tech> wrote: > Melvin, > > There is no proposal being made here for you to oppose. If inscriptions > were off-chain this would break the discoverability of the method and* r**equire > additional sidechains or tokens *which goes against the main goal of the > method. Since inscriptions are possible on the Bitcoin network *today* this > method is also already possible. > > Since the method inherits the security of layer 1 Bitcoin it is the most > decentralized and censorship-resistant method available. I am more > interested in hearing this community's thoughts regarding the technical > implementation, not the politics of whether Bitcoin should or shouldn't be > used for decentralized public key infrastructure. Bitcoin is so much more > than a financial network. > > Brian > > On Mon, May 1, 2023 at 12:22 PM Melvin Carvalho <melvincarvalho@gmail.com> > wrote: > >> >> >> po 1. 5. 2023 v 21:01 odesílatel Brian Richter <brian@aviary.tech> >> napsal: >> >>> Hello CCG, >>> >>> I have created *Yet Another DID Method*. This method uses Bitcoin >>> transactions directly on L1 to manage DID Document state. The full >>> specification can be found on github >>> <https://github.com/ordinalsreserve/btco/blob/main/spec.md>. I welcome >>> your feedback, questions, and suggestions as this method is developed and >>> refined. Please don't hesitate to send me questions about the method or >>> ordinals directly. >>> >>> 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. >>> >>> 1. Create a public/private key pair for cryptographic operations and >>> authentication. >>> 2. Define any necessary service endpoints for communication or >>> interaction with the DID. >>> 3. Create a DID Document with the required properties following the >>> DID Core Specification. >>> 4. 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* >>> >>> 1. Retrieve the inscription data from the satoshi associated with >>> the method-specific identifier. >>> 2. If this utxo has been spent, look for the next DID Document by >>> finding another inscription in the spending transaction. >>> >>> >>> *Updating a DID Document* >>> >>> 1. 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* >>> >>> 1. 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. >>> >> >> -1 to this. Strongly oppose. >> >> The bitcoin network works best as a financial network >> >> Inscriptions belong off-chain, with at most a reference to them, on-chain >> >> >>> >>> Best regards, >>> >>> Brian Richter >>> Founder / CEO >>> Aviary Tech / Ordinals Reserve >>> brian@aviary.tech >>> >>> >>>
Received on Monday, 1 May 2023 20:50:51 UTC