Crypto Project Transparency FAQ — What to Publish and What It Costs

What is the test for whether something counts as transparency?

One question: could someone verify this claim without contacting us?

"Our tokenomics are fully transparent" fails. "Team tokens are locked in contract 0x… until 2027-03-01" passes, because anyone can check it.

Apply that test and most of the work sorts itself out.

Does the team have to be publicly identified?

No. Pseudonymity is normal in this industry and is not the problem.

Unreachability is. Questions arrive after listing — a migration, an exploit, a chain halt, a support case needing a project-side answer within hours. A project nobody can contact is one whose holders have nowhere to go.

The workable middle: named roles, clear decision authority, and a monitored contact channel, without necessarily publishing legal identities. Exchanges and holders generally care about accountability rather than passports.

Should I publish treasury addresses?

Generally yes, and the cost is real.

For: the addresses are discoverable anyway, and movements are visible on-chain whether or not you disclose. Publishing converts an inevitable discovery into a routine one, and removes the space for speculation.

Cost: your balance and every movement become public and will be commented on, sometimes uncharitably.

Most projects find it worth it, because the alternative is people guessing — and guesses are usually less flattering than reality.

Do I have to disclose privileged contract functions?

If you want to be listed anywhere reviewed, effectively yes — and it is in your interest regardless.

Mint, pause, blacklist, transfer fee and upgrade functions are discoverable by anyone reading your contract. Disclosing them is a technical statement; having them found is a credibility problem.

They are not disqualifying. A pause function behind a multisig and a timelock is a reasonable safety mechanism. The same function behind one hot key is a different proposition — and concealing either is worse than both. See smart contract review basics.

How specific does a vesting schedule need to be?

A table of dates and amounts, with lock contract addresses where locks are enforced on-chain.

"Vests over 24 months with a 6-month cliff" describes a schedule. A reviewer, and a holder, need the schedule itself.

Flag anything unlocking in the next 90 days explicitly. An unlock nobody expected is one of the most reliable ways to destroy trust; disclosed in advance it is a scheduled event people plan around.

Is publishing an audit enough?

Only if you publish it properly.

Name the auditor, attach the report rather than a badge, state which version was audited, and say whether it is the deployed one. For each unresolved finding, say what was done — fixed, mitigated, or accepted with reasoning.

"Audited" with no auditor named is not evidence. And note an audit cannot prevent liquidity removal or supply dumping, because neither is a code defect.

How should I report bad news?

State what happened, the impact, what you are doing, and what you do not yet know. Then publish the next update when you said you would.

Publish before you have all the answers — speed matters more than completeness, and a holder learning about it elsewhere first is much worse. "We do not know yet" is a complete answer and is far better received than a confident wrong one you later retract.

Projects that handle one incident well often emerge more credible than before. Projects that go quiet rarely recover. See how to write project updates.

What are the actual costs of transparency?

Worth being honest, since it is usually advocated as free:

You lose the ability to revise history quietly.
Treasury movements get scrutinised.
Missed timelines are visible.
Contract powers must be justified.
Every published specific is one you can be held to.

The trade is credibility in exchange for the ability to be vague. For a project intending to exist in three years it is clearly worth it — and the fact that it is genuinely costly is exactly what makes it a signal.

Does transparency help with getting listed?

Substantially, though not as a virtue score.

Listing review is a verification exercise, and the fastest applications are those where a reviewer can verify every claim without asking a question. A project already publishing verifiable specifics has effectively done the work in advance.

See coin listing requirements.

Project Transparency — Frequently Asked Questions