StaticexternalImplements 4.1.2 External Initial Document Creation.
Creates a did:btc1 identifier from some initiating arbitrary DID document. This allows for more complex
initial DID documents, including the ability to include Service Endpoints and Beacons that support aggregation.
Inputs include intermediateDocument, optional version and network returning initialDidDocument. The
intermediateDocument should be a valid DID document except all places where the DID document requires the use of
the identifier (e.g. the id field). These fields should use placeholder value
did:btc1:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx. The intermediateDocument should include at
least one verificationMethod and service of the type SingletonBeacon.
See Btc1CreateExternalParams for details.
Identifier network name.
Identifier version.
A Promise resolving to Btc1CreateResponses.
StatickeyImplements 4.1.1 Deterministic Key-Based Creation.
For deterministic key-based creation, the did:btc1 identifier encodes a secp256k1 public key. The key is then used to deterministically generate the initial DID document.
See Btc1CreateKeyParams for details.
did-btc1 bitcoin network.
public key bytes for id creation.
did-btc1 identifier version.
A response object of type Btc1CreateResponse.
Implements section 4.1 Create.
A did:btc1 identifier and associated DID document can either be created deterministically from a cryptographic seed, or it can be created from an arbitrary genesis intermediate DID document representation. In both cases, DID creation can be undertaken in an offline manner, i.e., the DID controller does not need to interact with the Bitcoin network to create their DID.
Btc1Create