Bug reports
A good bug report is the fastest way to get something fixed, and one of the most useful things anyone can give to the project. It takes ten minutes. This page says where to send it and what makes it good.
Is it a vulnerability? If what you found could let someone take coins, break privacy, crash other people's nodes or forge anything, do not report it in public. Report it privately instead, and give the project time to fix it before anyone else learns how. See below.
How to report a bug
Make sure it is still there
Update to the newest version (About → Check for updates) and try again. The list of updates says what each release fixed.
See whether it is known
Search the issues, open and closed, for the words of the error. If someone has reported it, add what you saw to their report rather than opening a second one.
Find the smallest way to make it happen
"Send fails" cannot be fixed. "Sending 5 GNR to a short address fails with no node knows the full address, every time, since 1.0.43" can.
Write it up
Open a new issue and choose Bug report. The form asks for what is listed below. You need a free GitHub account, which needs no real name.
A report someone can act on
- Which part: desktop wallet, miner, swaps and the offer board, full node, command-line wallet, API or SDK, website or explorer.
- The version, exactly: the wallet's About tab, or
kryptond --version. - Your system: Windows 11, Ubuntu 24.04; for mining the graphics card and its driver.
- What you did, step by step, from a state someone else can get to.
- What you expected and what happened instead.
- The exact text of any message, copied, not retold. A screenshot helps for anything you see; hide balances and addresses you do not want to show.
- How often: every time, sometimes, once.
Where to find details
- The wallet shows its last error in a bar at the top, and the status of every swap and offer in the Swap tab. Its Console answers
getversion,getnetworkinfoandgetblockchaininfo: copy what they say. - The miner shows why it stopped in the Mining tab.
- A node run as a service writes to the system log:
journalctl -u kryptond --since "1 hour ago". Started by hand, it writes to the terminal;RUST_LOG=debug kryptondsays more. - Transaction and block ids are public. They tell a developer exactly where to look.
Never post
No fix has ever needed a recovery phrase. Anyone who asks for yours "to look into the bug" is a thief.
What happens to your report
Reports are read in public, by whoever maintains the code and by anyone else who cares. A report that can be reproduced gets fixed; one that cannot gets questions. Answer them if you can: the person asking does not have your computer.
When a fix ships, the release that carries it is listed under News and the issue is closed with a note. Fixes to the rules of the network itself take longer: they need a specification, tests, and a block height announced in advance, never an overnight switch.
Nobody is paid to answer, and nobody owes an answer by a certain day. Clear reports get faster ones.
Report security problems privately
A bug that an attacker could use is different from a bug that annoys. Published before it is fixed, it puts everyone's coins at risk. So:
- Use GitHub's private vulnerability reporting on the project's repository. Only the maintainers see it.
- Say what the problem is, what an attacker gains, and how to reproduce it.
- Test only against a private network of your own (
kryptond --network devnet --no-seeds), never against other people's nodes or funds. - Do not publish details until a fixed version is out and people have had time to install it.
The parts most worth a careful look are listed in the security policy: the spend proof, consensus, the light wallet's verification, key handling and the handshake between nodes. The software has many automated tests and an internal review, and no independent audit yet; the policy says so too.
Ideas and questions
An idea
Something the software should do and does not. Choose Feature request and say what problem it would solve for you.
Suggest itA question
You are not sure whether it is a bug, or how something is meant to work.
Get helpA fix
You found the bug and the line that causes it. Even better.
Contribute code