Taking part: what one person can actually add
You will know which contributions genuinely move this network forward today, and how to make each one without putting your funds or your machine at risk.
Operate
A node in a new place is the contribution that counts most.
The gate no amount of code can close is the number of independent operators. A node run by a different person, on different hardware, behind a different provider, adds a failure domain the network did not have, and a node that also produces blocks adds to the count this site publishes. The mining course covers installing, keeping a node alive and validating; this lesson is here to say that it matters more than anything else on this list.
Verify
Check a release before you run it, and say so when it fails.
Every public node release is signed with a key printed in the public repository, alongside checksums, a bill of materials and build provenance. Run the verification script against what you downloaded instead of trusting the page that linked to it. If a signature fails, a checksum differs or the provenance names a different commit, that is a finding: report it in the public repository rather than working around it.
Report
A weakness goes to the security contact first, never to a public thread.
If you find something that could cost someone funds or split the network, send it privately to the contact this site publishes in its security.txt file, and allow time for a fix before it becomes public. Never include a recovery phrase, a private key or a keystore: no genuine report needs one, and the security.txt file itself tells you never to send them. Ordinary bugs and wrong figures on a page belong in the open.
Use, and question
Use the testnet as if it mattered, and hold every claim to the code.
Anchor a file, send testnet VIGI between your own addresses, build an escrow and exercise its release, read a block in the explorer and then again from your own node. Each is small, and each is a test nobody else ran in your conditions. When a page on this site says something the chain does not do, that is worth reporting too: this academy only holds together if its claims are checked by the people it teaches.
In short
- An independent node in a new failure domain is the most valuable thing you can add.
- Verify every release signature yourself, and report a failure in the public repository.
- Security weaknesses go privately to the security.txt contact; never send a phrase or a key.
- Using the testnet and checking this site's claims against the chain are contributions too.
Keep reading