Crypto Project Due Diligence: Evidence and Red Flags
Crypto due diligence separates a project’s claims from verifiable technical, legal and economic evidence. It cannot certify future returns, but it can expose unsupported assumptions and avoidable operational risks.
How it works
Identify the actual chain, contracts, issuer or legal entity, administrative keys, distribution, treasury controls and revenue or usage claims. Read primary documents and match audits to deployed code. Separate fee-generating activity from subsidized incentives and token-price appreciation. Track what cannot be independently confirmed.
Worked example
A fictional app advertises a 20% annual yield. Its published breakdown shows 3% from borrower interest and 17% in newly issued reward tokens valued at today’s price. Those are different sources: if reward prices halve, the quoted currency yield changes even with unchanged borrower payments. Withdrawal restrictions, contract losses and fees can reduce the result further.
Amounts, prices and scenarios are fictional teaching examples. They exclude any effects not explicitly stated and are not trade recommendations.
Limits and common mistakes
Anonymous ownership is not automatically fraud, and a named team is not proof of honesty. Audits, exchange listings and endorsements do not remove permission, liquidity or counterparty risks. Do not send a real deposit merely to verify a promotional promise.
Knowledge check
What should happen when a material claim cannot be verified?
Read the explanation
Record it as an uncertainty and assess whether the decision depends on it. Do not replace missing evidence with a confident assumption or a token-price chart.
References and further reading
These sources explain the underlying concepts and specifications. They do not endorse QBMFX Academy. Check the relevant market, protocol version and reporting rules before applying an example.