Nobody owns it. Anyone can improve it.
Genoryn Krypton is open source under MIT or Apache-2.0. There is no company behind it and no team to apply to: changes are proposed in public and judged on what they do. You do not need to be a programmer to help.
Pick what suits you
Bug reports
Tell the project what broke, clearly enough that someone can fix it. The most useful ten minutes you can give.
How to report a bugCode
Fix a bug, add a test, review a change. The node, the wallet, the miner and this website are all in one repository.
Build and testReview
Read the code that guards people's money and try to break it. There has been no independent audit yet; careful eyes are worth more than anything.
Where to lookDocumentation
If a page confused you, it will confuse the next person. Say so, or fix it.
Improve the docsTranslations
The wallet and this site are in English only today. Here is where that stands and what would help.
TranslationsTech support
Answer a newcomer's question. If you have mined for a week, you know things they are stuck on.
Help someoneRun a node
No skills needed, and it makes the network stronger from the first hour.
The full-node guideBuild it, test it, send a change
Everything is written in Rust and lives in one repository: github.com/genoryn/genoryn. You need Rust 1.89 or newer and no other toolchain.
git clone https://github.com/genoryn/genoryn cd genoryn cargo build --release # node, miner, wallets cargo test --workspace # all tests cargo fmt --all -- --check # formatting cargo clippy --workspace --all-targets -- -D warnings # lints python website/build.py # this website, into website/dist
Try your change on a private network of your own before you propose it. Never test against other people's funds or nodes:
kryptond --network devnet --no-seeds
Where things are
| Path | What |
|---|---|
crates/krypton-core | Consensus, transactions, emission, parameters |
crates/krypton-zk | The zk-STARK spend circuit, prover and verifier |
crates/krypton-crypto | Hashes, ML-KEM, signatures, key derivation |
crates/krypton-pow | KryptoHash proof of work |
crates/krypton-p2p, krypton-store, krypton-light | Network, storage, light client |
crates/krypton-wallet-core, krypton-swap | Wallet logic, atomic swaps and the offer board |
apps/kryptond, krypton-miner, krypton-wallet, krypton-wallet-cli | Node, miner, desktop wallet, command-line wallet |
docs/spec | Specifications |
website | genoryn.io |
A good pull request
- One change, with a few sentences on what it does and why.
- Tests for the behaviour it changes. Consensus, proof and wallet code is not merged without them.
- The four commands above pass. They run again on Linux, Windows and macOS when you open the request.
- Plain words in comments and documents, no unsafe code in networking, no new dependency without a reason.
- A change to the rules of the network needs an update of the specification in
docs/specand a block height at which it starts, announced in advance. Never an immediate switch: people's nodes must have time to update, and nobody's coins may be stranded.
The full guide is CONTRIBUTING.md. By contributing you agree that your work is licensed like the rest of the project, under MIT or Apache-2.0 at the user's choice.
Where careful eyes are worth most
The software has extensive automated tests and an internal review, and no independent audit yet. If you know cryptography, consensus or Rust, these are the places where a mistake would cost the most:
| The spend proof | The circuit that proves a transfer valid, and its zero-knowledge masking: crates/krypton-zk, docs/spec/spend-circuit.md |
| Consensus and reorganizations | crates/krypton-core/src/consensus.rs, crates/krypton-store |
| The light wallet's verification | crates/krypton-light |
| Keys and the wallet file | crates/krypton-wallet-core |
| The handshake between nodes | crates/krypton-p2p/src/session.rs |
If you find something an attacker could use, report it privately.
Make it clearer for the next person
Documentation is part of the software: a rule nobody can understand is a rule nobody can check. It lives in three places, all in the repository, all plain text you can edit in a browser on GitHub:
This website
The folder website: one HTML file per page, no framework. python website/build.py builds it. The list of updates comes from website/updates.py.
The README
README.md is the whole project on one page, for people who read on GitHub.
The specifications
docs/spec says exactly what the rules are: the spend circuit, consensus, rewards, the light client, addresses and the network, atomic swaps.
What helps
- Say where you got lost. Open an issue: "the page on swaps does not say what happens if I close the wallet". That alone is a contribution.
- Fix what is wrong or out of date. A number that changed, a button that was renamed, a step that no longer exists.
- Write it the way you would say it. Short sentences, ordinary words, what happens and what to do. No promises about price, ever: the project makes none.
- Check it. Run the command you describe. Documentation that is confidently wrong is worse than none.
Where they stand
Honestly: the wallet and this website exist in English only today, and the wallet has no system yet for showing itself in other languages. Its texts are written into the page it displays, so a translation cannot simply be dropped in.
That is worth changing. Money that only English speakers can read the warnings of is not money for everyone. What would help, in the order it has to happen:
Say which language you would use it in
Open an issue or add your voice to an existing one. Which languages come first should follow who is there to keep them current.
The wallet has to learn languages
Its texts need to move out of the page into one file per language, with English as the fallback. That is a code change, and a welcome one: see Code.
Then translate, and keep translating
A wallet's words are instructions about money. A translation has to be exact, has to keep words like recovery phrase and refund the same throughout, and has to be updated with every release. A language without someone to maintain it is worse than no translation.
Until then, translations of the documentation, written and kept by people who speak the language, are welcome as pages of their own. Mark clearly which version they describe, and link the English original.
Start small
Report one thing that confused you, or fix one sentence. That is how every contributor started.