
Your work, confirmed by the people who saw it.
Atesta helps contributors carry credible records of what they built, and lets anyone check who approved the work.
- No wallet needed to start
- Private until you share
- No scores, no tokens
Daniel Okafor
Frontend engineer · 2 verified contributions
October 2026
VerifiedProposal review interface
August 2026
VerifiedMentored three hackathon teams
June 2026
In reviewContributor onboarding guide
The tools change. Accountability travels.
A mark once showed who stood behind a piece of work. A signature carried that approval forward. Atesta gives approved contributions a portable record that anyone can check.

A mark made its issuer visible.
A visible sign could tell the next person that someone had reviewed and approved.

A signature made it portable.
Approval could travel with the work, attributed to the person who gave it.
- Organisation approved
Atesta · sample
Contribution record
Open the record. Recompute its fingerprint. Check the NEAR testnet entry.
Try the sample checkNow anyone can check the record.
Atesta links the approved description to an organisation and a public NEAR testnet anchor.
Don’t take our word for it. Check it.
Every approved record has a digest: a fingerprint of the whole record, computed with SHA-256. Change anything, even one word, and the fingerprint changes completely.
On a real record, the digest you compare against is read from the NEAR testnet registry, not from Atesta. This one is a sample, so it lives on this page.
Four steps, each taken by someone different.
Nobody verifies their own work, and Atesta never verifies it for them.
- Step 1
Describe one piece of work
What you did, for which project, in what role. Attach the pull request, document or demo.
- Step 2
Confirms it, or asks for more
Only a reviewer they have authorised can decide. Never the person who made the claim.
- Step 3
Anchors the record on testnet
Signed in the organisation's own wallet. Only a fingerprint goes on-chain, never your details.
- Step 4
Checks it in seconds
Open the record, recompute its fingerprint, compare it with NEAR. No account needed.
Honest about what it proves.
A record is an organisation’s word about one piece of work. No more, no less.
It proves
- A named organisation approved this exact description of the work
- It did so on the date shown, through a reviewer it authorised
- The record has not been changed since it was approved
- Whether it still stands. Revoked records stay visible, marked as revoked
It does not prove
- That every detail of the claim is objectively true
- That the person is better than someone else
- That you should trust the organisation. That call is yours
Did the work? Keep a record that outlasts the Discord server.
One profile across every project you contribute to, built from records each organisation has confirmed.
Run the project? Put your name to the work you stand behind.
Review claims against the evidence, issue records from your own NEAR account, and revoke one if it turns out to be wrong.