WALLET / Code, builds & verification
Documents, versions and evidence
Where to find guides, source, reports and release notes.
One version, one evidence set
Each release needs a changelog, exact source version, dependencies, build instructions and required verification results. A hash binds a file to the reviewed set. A source or relevant dependency change does not automatically inherit an earlier result.
A clear structure
Guides belong in docs, vulnerability reporting rules in SECURITY.md, and release notes in releases. Verification metadata, scope and hashes belong in verification. Licenses and dependency provenance sit alongside the source. A local documentation kit prepares this structure.
When a verification badge is justified
A badge should link to a result for a specific version. An internal test covers only the executed scenario. A reproducible build needs an independent rebuild and a defined artifact comparison. An independent audit needs an external report stating its scope and finding status. These labels are not interchangeable.
What is ready for review
The local review contains clear articles, a technical overview, repository structure and a verification program. R10.1 defines allocation and Reserve and supersedes older monetary descriptions. The local overview includes these rules; publishing a full whitepaper requires separate approval. Keys, private data, unverified readiness claims and third-party material without distribution rights do not belong in a publication.