Source.
Builds. Verification.

How the wallet source is organized, which projects it builds on and what is being prepared for publication.

What should be public

Users should see where a release came from and what it contains. Developers should understand how to repeat the build and report a problem.

Source with exact versions

Clear instructions and licenses

Verification with stated limitations

quinvarium-wallet/
├── README.md
├── SECURITY.md
├── LICENSE + THIRD_PARTY_NOTICES.md
├── CHANGELOG.md
├── core/             Rust · transaction & key authority
├── apps/flutter/     Dart presentation only
├── bridge/           generated asynchronous Rust bridge
├── platform/         native OS adapters
├── docs/
│   ├── start/
│   ├── wallet/
│   ├── security/
│   ├── architecture/
│   └── releases/
├── tests/            vectors · lifecycle · devices
├── evidence/         versioned public summaries
└── .github/          issues · checks · release policy

The preparation kit is assembled locally

It contains documents, an evidence-record schema, release checklist, bug report template and proposed repository layout. It is not mobile-app source or a new public repository.

Download kit .zip Read the contents

Provenance and licensing

The current public-wallet donor is Gem 2.114.11. Critical QNV logic remains Rust-owned. Onebitx design assets and derived files need their own publication-rights review. The software donor’s license and the purchased UI kit license are separate bases.

Secrets are not part of open source

Seeds, keys, wallet databases, credentials and user data are excluded. Source and evidence receive a separate review before leaving the local environment.

Data boundaries