Identifier of anchor to update.

Name of the anchor (doesn't need to be unique).

SHA256 hash of the data to anchor.

The value must be provided as an hexadecimal lowercase string. The hash of the empty file is forbidden.

This property must not be provided when creating a signature anchor: it is automatically set at creation time to the SHA256 hash of the signature property provided, meaning that the signature is the actual anchored data.

SHA256 hash of the signed data.

The value must be provided as an hexadecimal lowercase string. The hash of the empty file is forbidden.

This property must not be provided when creating a data anchor.

X500 Distinguished Name representing the signed identity.

This property must not be provided when creating a data anchor.

Domain name of the identity server.

If set, the domain name of the identity URL must be included in the signedIssuerDomain domain name.

This property must not be provided when creating a data anchor.

Public key of the signer.

Currently only Bitcoin addresses are supported.

This property must not be provided when creating a data anchor.

Signature of the signedHash property using the public key pubKey, or, if any of the signedIdentity or signedIssuerDomain properties are provided,
signature of SHA256(signedHash + signedIdentity + signedIssuerDomain) using the public key pubKey.

Only Bitcoin signatures are currently supported.

This property must not be provided when creating a data anchor.

Web hook of the identity server to use to verify the signer's identity.

It is used to verify that the server knows the pubKey public key and to get or check the identity of the user owning that key.

For proofs of seal, it is also used to verify that the identity server (itself identified by the TLS certificate of the URL)
controls the key used to sign (ie. owns the private part of the key pair) by requesting it to sign some random data.

Please refer to Woleet.ID Server documentation for more details.

Web hook to be called by the platform whenever the status property of the anchor changes.

The platform does a POST request on this URL with the anchor as a JSON object in the request body. The domain of the URL must resolve to an external IP address.

Verifying the authenticity of the callback can be done by checking the HMAC-SHA1 signature of the request body provided by the platform in the x-woleet-signature header.

Please refer to this documentation for more details.