From a claim to a record anyone can check.
A contributor describes one piece of work. The organisation it was done for reviews it. If the organisation approves, the record is frozen and its fingerprint is anchored on NEAR testnet. Here is each step, and exactly what it does and does not establish.
The contributor makes a claim.
A claim is a description of one specific contribution, not a job title or a list of skills.
What you did, for which project, in what role, and when.
It can stay a private draft for as long as you like. No wallet is needed for any of this.
One or more links to evidence.
A pull request, an issue, a document, a demo, a video. Only https links are accepted. Atesta does not open or scan them; a reviewer judges them in context.
Send it to the organisation you did the work for.
Until an organisation approves it, the claim is yours alone and is labelled self-reported wherever it appears.
The organisation reviews it.
Only a person the organisation has given a reviewing role can decide, and the contributor can never review their own claim, whatever role they hold.
The organisation stands behind the claim as written.
The approved text and evidence links are frozen at that moment. Nobody, including Atesta, can edit them afterwards.
The reviewer requests more information.
They must say what is missing. The contributor answers, adds evidence if needed, and the claim returns to the queue.
The organisation declines, and must say why.
The contributor sees the reason. The claim can be reworked and submitted again as a new request.
The organisation anchors it on NEAR.
Approval and anchoring are two separate facts, and Atesta shows them separately.
When a claim is approved, Atesta builds a fixed record of it: the claim, the evidence links, who issued it, who it is about and when. That record is put into a standard canonical form and hashed with SHA-256. The result is the digest, a fingerprint of the whole record. A random value inside the record stops anyone reconstructing the digest by guessing.
The organisation then signs a transaction from its own NEAR account, in its own wallet, writing the digest to the Atesta registry contract. Atesta never holds a wallet key and cannot sign for an organisation. The record is shown as anchored only after the transaction is confirmed and the digest on NEAR matches.
What goes on NEAR, and what does not
- On NEAR: the attestation’s identifier, its digest, the issuing account, and whether it has been revoked.
- Not on NEAR: names, email addresses, the text of the claim, evidence links, reviewer notes, or anything else personal.
This build uses NEAR testnet only. Testnet is a public test network; its records carry no real-world value and nothing here runs on mainnet.
Anyone can check it.
Checking a record needs no account and no trust in Atesta.
The attestation’s public page.
It shows the exact claim that was approved, the evidence, the issuing organisation and the date.
The digest, from the record in front of you.
Your browser does the hashing. The sample on the home page works this way.
With the digest stored on NEAR.
If they match, the record is the one the organisation anchored. If the registry marks it revoked, the page says so.
How much weight to give the issuer.
Atesta shows who the organisation is and whether Atesta has reviewed it. Whether to trust its judgement is yours to decide.
What each status means.
Every status is written in words and carries its own symbol, so none depends on colour.
Self-reported
The contributor wrote this. No organisation has reviewed it. It is never shown as verified.
Awaiting review
Sent to the organisation. Private to the contributor and that organisation’s reviewers.
Approved, awaiting NEAR anchor
A reviewer approved it and the record is frozen. No confirmed NEAR transaction exists yet, so it is not shown as anchored.
Verified and anchored
A confirmed NEAR testnet transaction from the organisation’s account stores a digest that matches the record.
Anchor failed
The transaction failed or was declined in the wallet. The approval still stands and the organisation can try again.
Revoked
The organisation withdrew it and gave a reason. The record stays visible, marked as revoked.
Superseded
Replaced by a corrected attestation. Both stay visible and link to each other.
When a record is wrong.
Nothing is edited after approval. Corrections leave a trail.
If an organisation finds that an attestation it issued is wrong, it revokes it and gives a reason. The revocation is recorded on NEAR from the same issuing account. If the claim needs correcting rather than withdrawing, the organisation issues a new attestation that supersedes the old one.
In both cases the earlier record stays publicly visible with its status shown plainly. Revoking an attestation does not erase its history on NEAR, and it is not meant to.
Atesta’s own administrators can review and suspend organisations. They cannot issue, change or revoke an organisation’s attestations.