What a testnet campaign can and cannot prove
A testnet lets a project observe usage before a production launch. Completing tasks may provide feedback or points, but it does not prove that a token, amount, or eligibility rule will follow.
Look for official documentation that explains the network, faucet, supported wallet, and current phase. Keep promotional language separate from technical evidence.
Use a dedicated test wallet
Create a wallet used only for testnet activity. Never reuse a wallet that holds valuable assets, and never share its seed phrase with a faucet, support account, or project form.
Bookmark the official network and explorer pages yourself. Fake faucets and fake explorers are common ways to turn a harmless task into a signing or approval trap.
Record actions instead of chasing volume
A simple log is more useful than repeating the same transaction. Note the date, network, contract, transaction hash, task, and any error message.
Avoid unnecessary volume. If a task is unclear, ask whether it improves the product or simply increases cost and exposure.
Current testnet records
Our directory currently marks a small set of records as Testnet. The category page is a research index, not a claim that any listed project will distribute a reward.
- Read the project documentation first.
- Use a separate wallet and small test balances.
- Keep transaction hashes and screenshots in your own log.
- Recheck eligibility and deadlines before any later claim.