A witness is an entity representing a proof that a document existed at the time. It is used to comply with the law requirement of data conservation. It may be associated to a signature request or a signature request invite to prove that the document was signed at a given time. The witness itself doesn’t include the signature request or the signature request invite, but it is identified by the hash of the message it represents. This hash is replicated across multiple providers to ensure its integrity:Documentation Index
Fetch the complete documentation index at: https://docs.plumaa.id/llms.txt
Use this file to discover all available pages before exploring further.
A witness is an entity representing a proof that a document existed at the time. It is used to comply with the law requirement of data conservation.
A field whose value conforms with the standard mongodb object ID as described here: https://docs.mongodb.com/manual/reference/method/ObjectId/#ObjectId. Example: 5e5677d71bdc2ae76344968c
Hash of the document to witness.
The algorithm used for hashing the document.
SHA256 Organization that created the witness.
A date-time string at UTC, such as 2007-12-03T10:15:30Z, compliant with the date-time format outlined in section 5.6 of the RFC 3339 profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.
A date-time string at UTC, such as 2007-12-03T10:15:30Z, compliant with the date-time format outlined in section 5.6 of the RFC 3339 profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.
Subject designed as the first in the endorsement chain. Only a member of the operating organization can set this field. Once set, our on-chain relayer will submit a proof of endorsement to the Witness contract so that the corresponding token can be minted by the user later on the application.
Information required to claim a document in the Endorser contract. It is only present if the witness is processed and restricted to the initial owner.
If the witness has been claimed by the initial owner.
Signature Request the witness is associated with. May not be present if the witness was via the API.
Individual NOM151 conservation strategy.
Combined merkleized conservation strategy.
Earliest date when the hash was witnessed by any strategy. Unspecified if the witness is not processed.