SYSTEM / 00
Proofmesh is a consent layer for contribution claims.
Projects can sign what happened. Contributors control whether the claim becomes part of a public Passport. Readers verify the source instead of trusting a screenshot.
Four roles, four boundaries.
Mints one Passport, accepts claims and controls their visibility.
An approved project address that creates structured work attestations.
A DAO, application or person querying public accepted records.
Approves issuers during the test phase; cannot accept proofs for a contributor.
Small enough to audit.
The registry stores the issuer and subject addresses, a schema identifier, an evidence hash, timestamp, consent state, visibility and revocation status.
{
"schema": "proofmesh.work.v1",
"subject": "0xContributor",
"issuer": "0xProjectMultisig",
"evidenceHash": "0x…",
"accepted": false,
"visible": false
}The original evidence may live in a repository, storage network or private archive. The onchain hash lets a permitted reader verify that it has not changed.
Claims move only through explicit actions.
Three contracts, separate responsibilities.
A prototype non-transferable credential: one per wallet. Full token-standard conformance is not claimed.
Issuer permissions, work claims, consent, visibility and revocation.
A fixed-supply ERC-20 artifact for a future review market.
Network and verified addresses remain separate from contract code.
Design around what can go wrong.
Testnet approval limits who can issue; production requires transparent issuer policy and challenges.
Only commitments belong onchain. Sensitive source material should never be published by default.
The current Passport contract has no recovery mechanism. Copy must not claim otherwise.
Frontend minting stays disabled until a verified address is configured.
Honest before impressive.
Source and bytecode are compiled. Robinhood Chain Testnet connectivity is live. Contracts, verified addresses and successful transactions are still pending.