@vbel/adapter-identity-ledger
v0.1.0
Published
IdentityResolver over entity registrations carried in the ledger itself, rather than over a file the verifier has to be given separately.
Readme
@vbel/adapter-identity-ledger
An IdentityResolver over registrations carried in the chain itself, so a reader learns whose key signed a
record from the link alone and no registry has to be fetched.
pnpm add @vbel/adapter-identity-ledgerimport { LedgerIdentityRegistry } from "@vbel/adapter-identity-ledger";
// `registrations` are the EntityRegistrationPayloads found in the chain.
const resolver = new LedgerIdentityRegistry(registrations);
const attestation = await resolver.resolve("urn:example:org:supplier", event.envelope.issuedAt);A registration is a claim somebody signed and sent along. That makes it inspectable, not true. A key that
has only vouched for itself is self-asserted; a vouch from a key the verifier already trusts is what
raises it. A vouch can corroborate a key and can never introduce one.
Most applications reach this through buildIdentityContext in
@vbel/records rather than directly.
Part of VBEL
Signed, hash-chained records that anyone can check for changes, with optional anchoring on a public chain. The repository readme says what that does and does not prove.
Apache-2.0.
