Create a new anchor.

post

https://api.woleet.io/v1/anchor

Use this operation to create a new anchor of one of these two types:

a data anchor (generating a proof of existence receipt) allows to prove the existence of some data at some point in time.
a signature anchor (generating a proof of signature receipt) allows to prove the existence of the signature of some data at some point in time, the validity of the signature and the signee's identity.

The properties id, created, lastModified, status, timestamp and confirmations are read-only and so must not be provided: they are managed by the platform and added to the returned anchor.

For data anchors, only the properties name and hash are required: the hash property must be the SHA256 hash of the data to anchor, and must be computed caller side. This allows not to leak the original data.

For signature anchors, only the properties name, signedHash, signature and pubKey are required (though the identityURL property is highly recommended): the signedHash property must be the SHA256 hash of the data to sign. This allows not to leak the original data and to keep the actual signed data small (signing the digest is equivalent to signing the original data).

Be sure to have at least 1 anchoring credit on your account. The signature property must contain a valid signature of the data property using the private key paired with the pubKey public key.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Anchor object to create.

name

string

required

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

hash

string

required

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

The value must be provided as an hexadecimal lowercase string.
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).

signedHash

string

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

The value must be provided as an hexadecimal lowercase string.
This property must not be provided when creating a data anchor.

pubKey

string

Public key of the signee.

Currently only Bitcoin addresses are supported.

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

signature

string

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.

identityURL

string

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

public

boolean

true (or unset) if the anchor is public. false if the anchor is private.

If this field is not set at creation time, the anchor is public by default.

notifyByEmail

boolean

true if the proof receipt must be sent by email once available, or false (or unset) if not.

`hash` property is automatically set to the SHA256 of the signature, which is what is actually anchored into the blockchain).

200The created anchor (for signature anchors, the hash property is automatically set to the SHA256 of the signature, which is what is actually anchored into the blockchain).

`hash` property is automatically set to the SHA256 of the signature, which is what is actually anchored into the blockchain).