Interface iAttestationProofDoc<T>

interface iAttestationProofDoc<T> {
    _docId: string;
    _id?: string;
    anchors?: {
        message?: string;
        txHash?: string;
    }[];
    attestationMessages: string[];
    createdAt: T;
    createdBy: string;
    dataIntegrityProof: {
        publicKey?: string;
        signature: string;
        signer: string;
    };
    description: string;
    displayOnProfile: boolean;
    entropies?: string[];
    image: string;
    messageFormat: "plaintext" | "json";
    name: string;
    proofOfIssuance: {
        message: string;
        publicKey?: string;
        signature: string;
        signer: string;
    };
    scheme: "bbs" | "standard";
    updateHistory?: iUpdateHistory<T>[];
}

Type Parameters

Hierarchy (view full)

Implemented by

Properties

_docId _id? anchors? attestationMessages createdAt createdBy dataIntegrityProof description displayOnProfile entropies? image messageFormat name proofOfIssuance scheme updateHistory?

Properties

_docId

_docId: string

A unique stringified document ID

Optional_id

_id?: string

A unique document ID (Mongo DB ObjectID)

Optionalanchors

anchors?: {
    message?: string;
    txHash?: string;
}[]

Anchors are on-chain transactions used to prove certain things about the attestation. For example, you can anchor the attestation to a transaction hash to prove that the attestation existed at a certain time.

attestationMessages

attestationMessages: string[]

Thesse are the attestations that are signed. For BBS+ signatures, there can be >1 attestationMessages, and the signer can selectively disclose the attestations. For standard signatures, there is only 1 attestationMessage.

createdAt

createdAt: T

When the attestation was created.

createdBy

createdBy: string

The address of the user who created the attestation.

dataIntegrityProof

dataIntegrityProof: {
    publicKey?: string;
    signature: string;
    signer: string;
}

This is the signature and accompanying details of the attestationMessages. The siganture maintains the integrity of the attestationMessages.

This should match the expected scheme. For example, if the scheme is BBS+, the signature should be a BBS+ signature and signer should be a BBS+ public key.

description

description: string

Metadata for the attestation for display purposes. Note this should not contain anything sensitive. It may be displayed to verifiers.

displayOnProfile

displayOnProfile: boolean

Optionalentropies

entropies?: string[]

Entropies used for certain data integrity proofs on-chain (e.g. HASH(message + entropy) = on-chain value)

image

image: string

Metadata for the attestation for display purposes. Note this should not contain anything sensitive. It may be displayed to verifiers.

messageFormat

messageFormat: "plaintext" | "json"

The message format of the attestationMessages.

name

name: string

Metadata for the attestation for display purposes. Note this should not contain anything sensitive. It may be displayed to verifiers.

proofOfIssuance

proofOfIssuance: {
    message: string;
    publicKey?: string;
    signature: string;
    signer: string;
}

Proof of issuance is used for BBS+ signatures (scheme = bbs) only. BBS+ signatures are signed with a BBS+ key pair, but you would often want the issuer to be a native address. The prooofOfIssuance establishes a link saying that "I am the issuer of this attestation signed with BBS+ key pair ___".

Fields can be left blank for standard signatures.

scheme

scheme: "bbs" | "standard"

The scheme of the attestation. BBS+ signatures are supported and can be used where selective disclosure is a requirement. Otherwise, you can simply use your native blockchain's signature scheme.

OptionalupdateHistory

updateHistory?: iUpdateHistory<T>[]

Settings

Member Visibility

On This Page

Properties