Claim profile

Say what your project says, with how each statement was established beside it

A report is written about a token without asking the project anything. This is where the project answers. State what you say about your own token — the addresses that hold its authorities, your links, your supply figures, what you have changed — and Evidesa compares what it can against the evidence it reads for that mint, then hands back a document where every statement carries how it was established.

Some statements can be compared with the chain, and one kind of mismatch is reported as a contradiction. Most cannot be compared at all, and are recorded as your statement, unchecked, in those words. That distinction is the entire point of the document: a statement nobody checked, printed beside one that was checked, otherwise reads as though both were.

Nothing you submit is stored. What you type exists for the length of one request: it is bounded, compared with evidence read in the same request, rendered into the document, and returned to your browser. There is no database record, no file, no queue and no analytics event. Close the tab and it is gone — including from us.

Nothing you submit is published by Evidesa. The document is not attached to any report, does not appear on any page here, is not indexed, and is not shared with anyone. It is handed to you and to nobody else.

We cannot confirm that you speak for the project. This build has no accounts, no sign-in and no wallet connection — the privacy page promises exactly that — so there is no mechanism by which a submission could be shown to come from the project it names. Anyone can fill this in about any token. The document says so in its own header, which is why it can be produced at all.

What you get back is a document you publish yourself. Plain text, yours to copy. Put it on your own site, in your docs, or in a reply — under your own name, where your name is the thing standing behind it. That is the only kind of attribution this build can honestly offer.

Required. Every statement below is checked against evidence read for this mint at the moment you submit. The mint address is sent to the Solana RPC provider and the market-data provider to read that evidence; nothing else you type leaves this server.

Project

A project name and a token's metadata name are different things, so the two are not compared. This is recorded as your statement.

Official links

Each link is compared with the links carried by the token's own metadata, as read for this submission. A link that is not in the metadata is recorded as your statement, never as wrong — most projects' metadata lists a subset of where they actually are, and plenty of tokens list nothing at all.

Authorities

An address here is compared with the address the chain records for that authority, which is the one case where a mismatch is reported as a contradiction. A signer threshold is checked against the account that actually holds the authority — and only where it is an SPL Token multisig; a Squads or SPL Governance arrangement comes back as not checked, because this build cannot read it.

Recorded as your statement. Intent leaves no on-chain trace, so there is nothing to check it against.

Recorded as your statement. Intent leaves no on-chain trace, so there is nothing to check it against.

Recorded as your statement. Intent leaves no on-chain trace, so there is nothing to check it against.

Supply

A total supply figure is compared with the mint account, with the mint's decimals applied. A circulating figure is never checkable here: the chain records total minted supply and nothing about which of it your definition excludes.

Liquidity pools

A pool account is compared with the pools the market-data provider returns for this mint. That list is a floor rather than a census — the provider caps its response and does not cover every venue — so a pool that is not on it is recorded as unchecked, never as wrong.

Lockups and vesting

Whether tokens are locked, vested or burned is not evaluated in this version, and nothing you write here will be checked. It is recorded as your statement, and the absence of the check is neither evidence that the tokens are locked nor evidence that they can be withdrawn.

Audit report references

An audit report is a document published off chain by a third party. This build does not fetch it, does not read it, does not check that the named firm wrote it, and does not contact them. An audit reference is not evidence of low risk.

Declared changes

Only the three changes that leave a visible end state on chain are offered here, and what is checked is that end state — not when it changed, and not that you are the party who changed it. Anything else you have changed belongs in the response below, where it is recorded as your statement.

Response

Your own words, reproduced in the document exactly as submitted and labelled as yours. This is also where a disagreement with a published finding goes: this page is not attached to a generated report and knows no finding ids, so it cannot accept a structured correction request that names one.

Up to 2,000 characters. Line breaks are collapsed: the document is plain text on a fixed width, and your paragraph is wrapped into it.

No score moves. Nothing submitted here changes any report about the token. A profile full of statements that match the chain does not lower a risk score, and one full of contradicted statements does not raise it. The moment a submission could move a score, the score would be measuring willingness to submit rather than evidence — so a right of reply is a right to be recorded, and deliberately nothing more.

Where our gaps fall. Our coverage is incomplete in known places: the pool list is a provider sample, only SPL Token multisigs can be decoded, lockups and vesting are not evaluated in this version, and no audit document is fetched or read. Wherever the evidence is a floor rather than a census, a mismatch is recorded as unchecked rather than as wrong. The cost of our gaps falls on your ability to earn a match — never on your reputation.

What the chain does not record. A signer threshold states how many signatures a program requires. It does not establish that the keys are held by separate people, and nothing on chain does. A matched statement means the evidence we read agrees with what you wrote — not that the arrangement it describes is a good one.

Your words are yours. Text you submit is reproduced in the document as written, on the line beneath the label that says it is your statement. It is not edited, not summarised and not interpreted — a right of reply that rewrites the reply is not one.

Evidesa is not financial advice and does not certify safety.