How to report a bug responsibly so maintainers can actually fix it

A vague bug report wastes everyone's time. This guide shows community members how to write a clear, reproducible bug report and how to handle security-sensitive issues responsibly.

Finding a bug is genuinely helpful to the Malairte project, but only if you report it in a way someone can act on. "It doesn't work" tells a maintainer nothing. A good bug report is a small act of community service: it saves the maintainer hours of guessing and gets the problem fixed faster for everyone.

Before you report, reproduce

Try to make the bug happen again on purpose. If you can reproduce it reliably, write down the exact steps. If it only happened once and never again, say so honestly; intermittent bugs are still worth reporting, but maintainers need to know they are intermittent.

Check it is not already known

Search the project's issue tracker for your symptom before opening a new issue. Duplicate reports scatter the discussion and frustrate maintainers. If you find an existing issue that matches, add your details there instead of starting a new one.

What a good bug report contains

What you expected to happen in one sentence.
What actually happened, with the exact error message copied as text, not a blurry photo of your screen.
Steps to reproduce, numbered, that someone else could follow.
Your environment: operating system, wallet or node version, and relevant hardware.
Logs, if you can find them, pasted in a code block.

Write it like you are helping, not complaining

Tone matters more than people think. Maintainers are usually unpaid volunteers. A report written like a polite teammate gets attention; a report written like an angry customer gets quietly deprioritised. State the facts, leave out the frustration, and thank them in advance.

Security bugs are different

If you think you have found a security vulnerability, something that could let an attacker steal funds, crash nodes, or forge transactions, do not post it publicly. Look for the project's security contact or responsible-disclosure address and report it privately. Public disclosure of a live security hole puts every user at risk before a fix exists. Responsible disclosure gives maintainers time to patch and protects the whole community. This is one of the most important pieces of etiquette a contributor can learn.

Published May 12, 2026

Frequently asked questions

How do I run a meetup without it feeling like a sales pitch?

Lead with the wallet, lead with safety, and lead with hands-on. Have attendees set up the official Malairte wallet on their own laptop and run a few minutes of mining live during the session. Talk openly about realistic earnings, electricity costs, and the difference between Malairte and the coins they have seen advertised. Avoid speakers selling courses or hardware.

How many people should I invite to my first Malairte meetup?

Four to eight people is the sweet spot for a first meetup. Small enough that you can answer every question, large enough that conversation flows without you carrying it. Invite ten and assume two will not show; that is normal for any free event. Resist the urge to scale up early. A meetup of six attentive humans creates more long-term community than a room of thirty distracted ones, because each person leaves with a wallet, a question answered, and a face they recognise next time. After your second or third successful small event, you will know which attendees want to help host the bigger one. Build the regulars first, then grow.

Do I need any special permission to run a Malairte workshop in a public library?

In most public libraries, you only need to book a meeting room like any community group. Be straightforward with the librarian about what you are teaching: open source wallet software and the basics of mineable cryptocurrency. Describe the session as educational, free, and non-commercial. Hand them a one-paragraph summary they can share with their manager if asked. Libraries are usually fine with this once they understand you are not selling anything. If the library has a no-cryptocurrency policy, respect it and find another venue rather than arguing; the goodwill matters more than the room. Always follow the venue rules on food, noise, and tear-down time, and leave the room cleaner than you found it.

See all Community FAQs →

Start mining Malairte the right way

Malairte (MLRT) is a CPU and GPU mineable coin — no ASICs, no specialized hardware. Download the official wallet and put this guide into practice on the computer you already own.

Download the wallet Try the Community tools

Educational resource only — not financial advice.