Identifier of anchor to update.

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

SHA256 hash (ie. the fingerprint) of the original data to anchor.

This property must not be provided when creating a signature anchor: it is set at creation time to the SHA256 hash of the signature property provided (so the signature is what is actually anchored in this case).

SHA256 hash (ie. the fingerprint) of the original data to sign.

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

Public key of the signee.

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 stored in the pubKey property.

Only Bitcoin signatures are currently supported.

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

Web hook to use to verify the signee's identity.

Calling this URL allows to verify that the owner of the URL (identified by the associated TLS certificate) also owns the public key used to produce the signature, by asking the URL to sign some random data.

This URL must use an HTTPS scheme with a valid and non expired TLS certificate.

This URL must implement the following GET operation:

input:

• pubKey: the public key to be verified
  
• leftData: the left part of the random data to be signed (generated by the caller)
  
  output:
  
• rightData: the right part of the random data signed (generated by the callee)
  
• signature: the signature of the string leftData + rightData produced using the public key pubKey

Web hook to be called by the platform whenever the anchor status change:
the platform does a POST request on this URL with the anchor as a JSON object in the request body.
Verifying the authenticity of the callback can be done by checking the HMAC-SHA1 signature of the request body provided by Woleet in the x-woleet-signature header.
For more information see the documentation.