Frequently Asked Questions

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.

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.

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.

Lead with what you have in common, not with the coin. Most veteran groups respond well to topics framed around self-reliance, learning a skill, and using equipment they already own. Open with a single sentence: "This is a free software workshop where you can mine a small amount of cryptocurrency on the laptop you already own." Then stop. Let them ask. Avoid any language about returns, gains, or financial freedom. Bring printed handouts so people can take information home and decide in their own time. Offer a follow-up coffee for anyone who wants to dig deeper. Many veterans appreciate a slow, no-pressure introduction more than a polished presentation, and word of mouth in veteran communities is strong once trust is earned.

Use a single demo laptop that you control, with a wallet created only for teaching. Never ask children to enter their own information, install software on their own devices, or touch a real personal wallet. Mine on the demo machine while the children watch the block explorer update on a projector. Any coins earned during the session stay on the demo wallet or go to a community education address. Keep the session under an hour, talk about electricity and effort in plain language, and finish with a short conversation about online scams aimed at kids. Send parents home with a one-page summary so they can continue the conversation. The goal is curiosity and critical thinking, not ownership.

Tell them directly: nobody legitimate ever doubles your coins. That is the single most reliable rule in cryptocurrency. Any message offering to multiply funds in exchange for sending some first is a scam, every time, without exception. Walk them through the specific message together. Point out the urgency, the impersonation of a known person or project, and the address they were asked to send to. Suggest they block the sender and never reply, because replies confirm the account is active and invite more attempts. Encourage them to ask you before acting on any unsolicited crypto message for the next few months. Most scam victims report later that they sensed something was wrong but had nobody to check with.

Absolutely, and most contributors are not full-time developers. The project needs people to improve documentation, report bugs clearly, answer beginner questions in the chat, test new releases on their own hardware, and translate the wallet and website into other languages. Every one of those tasks makes the project better and none require programming. A good first step is to read the contributing file, lurk in the community chat for a few days to learn the culture, then fix one small thing, like a confusing sentence in the install guide. Small, reliable contributions get noticed and mentored. The fastest way in is often through your local meetup, where an experienced member can walk you through your first contribution in person.

No single person is in charge, which surprises most newcomers. Decisions are made through rough consensus, a process common to open-source projects. A proposal moves forward when the people who care about it have been heard, the serious technical objections have been resolved, and nobody with a sound reason is still strongly opposed. It is not a majority vote and it is not a dictatorship. The emphasis is on addressing real objections rather than counting supporters, which means a good technical concern from a newcomer carries the same weight as one from a veteran. If you want your voice to count, raise specific, addressable objections rather than vague unease. That is how a decentralised project moves forward without a boss.

A code of conduct is a short, public document that sets the behavioural ground rules for a community: be respectful, assume good faith, no harassment, no discrimination, and stay on topic. It exists to make the project welcoming to newcomers, who are exactly the people most easily driven away by a hostile chat or meetup. It is not censorship of opinions; you can disagree strongly about technical decisions and still follow it. The code of conduct typically explains how to report a problem and who handles reports. Enforcing it consistently, even when the person breaking it is popular or skilled, is what keeps a community healthy. Moderators and meetup hosts are usually the people who uphold it day to day.

Start by partnering with an existing veteran organisation rather than building from nothing. Approach your local VFW, Legion, RSL, or equivalent and offer a free, no-pressure software workshop framed around self-reliance and learning a skill using equipment members already own. Lead with what you have in common, not with the coin, and avoid any language about returns or financial gain. Bring printed handouts so people can take information home and decide in their own time. Offer a follow-up coffee for anyone who wants more. Trust builds slowly in veteran communities but word of mouth is strong once earned. If you are a veteran yourself, say so; a shared background opens doors that a polished outsider presentation never will.

You become a mentor mostly by showing up consistently and being patient. You do not need to be an expert; you only need to be a step or two ahead of the person you are helping and willing to answer the same beginner questions without sighing. Start by hanging around after meetups for one-on-one questions, because that is when shy newcomers ask the things they were too nervous to raise in the group. Walk someone through their first wallet setup, their first contribution, or their first node. Point people to documentation rather than just answering, so they learn to find answers themselves. Mentoring is the quiet engine of community growth: most active contributors got there because someone sat with them once.