did-btc-spec icon indicating copy to clipboard operation
did-btc-spec copied to clipboard

did:btc Method Specification

Results 15 did-btc-spec issues
Sort by recently updated
recently updated
newest added

The spec spends a fair amount of time explaining the advantages of the witness discount and the Ord/Rodarmor "envelope" `OP_FALSE OP_IF ...` construction, but then uses `OP_RETURN` instead for creation....

The spec uses only `TxRef`s (from [BIP-136](https://github.com/bitcoin/bips/blob/master/bip-0136.mediawiki)) to refer to `did:btc`s, but these have a few drawbacks: 1. They include the block height, meaning a `did:btc`'s `TxRef` cannot be known...

The [EXAMPLE 4](https://microstrategy.github.io/did-btc-spec/#example-a-did-btc-did-document-constructed-from-a-creation-transaction) in **§4.3.2 Read (Resolve)** has ```json "controller": "did:key:z6DtNrvHVvvKHB7m8LrCmt131TGH7DbzvcPo9mZRoCt5rqms", ``` Which is a Secp256k1 key (from the `z6Dt` prefix -> `0xE7` -> Secp256k1 compressed pubkey per the multibase/multikey...

Similar to #3, the [`did:keri`](https://identity.foundation/keri/did_methods/) method may be useful to compare to, or even take ideas from

Even though the main DID spec 'expects' JSON, you are already implicitly constructing that document for single-key `OP_RETURN` DIDs (as do other specs like `did:key`); so you could use [CBOR](https://cbor.io/)...

I had a bunch of suggestions after a read-through so I've added edits in multiple commits: - edit: Link to ordinals docs, use the name "envelopes" to more precisely describe...

Just in case your engineering and research team overlooked - [nostr](https://github.com/nostr-protocol) exists. Unlike decentralized in name only solutions such as [ATProto](https://atproto.com/), Nostr has the highest ratio of active devs to...

Currently the InterPlanetary File System (IPFS) URL points to https://www.ipfs.com which obviously is incorrect since this is completely different project [1], correct url is https://ipfs.tech/, similar reference on ION's page...

Added the Chinese translation of the protocol content.

I noticed a lack of comparison to the did:btco method, possibly because the authors aren't familiar. I'd be interested in seeing a comparison. You can read more about the method...