Every OA document's provenance can be verified and traced back to its creator or issuer. This is achieved by embedding an
identityProof property in the document, which serves as a claim for identity. During the verification phase, the claim is checked against external records.
In this example above, the document's issuer is bound to
In this guide, we will bind the document issuer's identity to a valid domain name. This domain will be displayed as issuer every time the document is rendered in an OA-compliant decentralized renderer.
We will be inserting a temporary DNS record on our DNS at
sandbox.openattestation.com so you do not need your own domain to follow the guide. If you prefer to use your own domain name for the identity, you may skip the steps involving the CLI and instead read the DNS Configuration Guide.
With your document store, run the following command:
open-attestation dns txt-record create --address 0xBBb55Bd1D709955241CAaCb327A765e2b6D69c8b --network-id 3
network-id corresponds to the network ID for the different Ethereum networks. We generally use only the following networks:
|Ethereum Testnet Ropsten|
|Ethereum Testnet Rinkeby|
Once the DNS TXT record has been successfully deployed, you will see the success message with the bound location.
✔ success Record created at few-green-cat.sandbox.openattestation.com and will stay valid until Thu Jul 02 2020 14:51:40 GMT+0800 (Singapore Standard Time)
In the example above, the document store
0xBBb55Bd1D709955241CAaCb327A765e2b6D69c8b, has been bound to the
few-green-cat.sandbox.openattestation.com location. Let's make sure the entry has been propagated to the DNS:
open-attestation dns txt-record get --location few-green-cat.sandbox.openattestation.com
which will display to you the list of the DNS TXT records associated to that location.
┌─────────┬────────────┬────────────┬───────┬──────────────────────────────────────────────┬────────┐│ (index) │ type │ net │ netId │ addr │ dnssec │├─────────┼────────────┼────────────┼───────┼──────────────────────────────────────────────┼────────┤│ 0 │ 'openatts' │ 'ethereum' │ '3' │ '0xBBb55Bd1D709955241CAaCb327A765e2b6D69c8b' │ false │└─────────┴────────────┴────────────┴───────┴──────────────────────────────────────────────┴────────┘
Note that it can take some time for the record to be correctly propagated to the DNS, even though it usually takes 10 to 15s.