Abstract
Optional
sidecar: SidecarDataA unique identifier for the Beacon
The service endpoint of the Beacon
Optional
sidecarThe type of the Beacon
Abstract
serviceReturns the Beacon Service object.
Abstract
broadcastBroadcasts a Beacon Signal (implemented by subclasses). Implements IBeacon Method broadcastSignal.
Abstract
generateGenerates a Beacon Signal (implemented by subclasses). Implements IBeacon Method generateSignal.
Abstract
processProcesses a Beacon Signal (implemented by subclasses). Implements IBeacon Method processSignal.
Implements 5. Beacons. Beacons are the mechanism by which a DID controller announces an update to their DID document by broadcasting an attestation to this update onto the public Bitcoin network. Beacons are identified by a Bitcoin address and emit Beacon Signals by broadcasting a valid Bitcoin transaction that spends from this Beacon address. These transactions include attestations to a set of didUpdatePayloads, either in the form of Content Identifiers (CIDs) or Sparse Merkle Tree (SMT) roots. Beacons are included as a service in DID documents, with the Service Endpoint identifying a Bitcoin address to watch for Beacon Signals. All Beacon Signals broadcast from this Beacon MUST be processed as part of resolution (see Read). The type of the Beacon service in the DID document defines how Beacon Signals SHOULD be processed. did:btc1 supports different Beacon Types, with each type defining a set of algorithms for:
Beacon