Connecting
Should I use the public node or run my own?
Your wallet holds your notes. It still has to follow the network — whether a note is real, whether a payment landed. Since v2.85 it does that in a light way by default: it connects to a public computer for the chain, but keeps its own copy of the pool, the list of every live note, which it takes as of the trustees' latest anchor, checks against the trustees' signatures and the block's commitment, and follows block by block. Which notes are yours it looks up in that copy. The public computer is never asked.
| Public computer, light wallet | Your own node | |
|---|---|---|
| Ready | In seconds | After it catches up, about an hour on a fast machine |
| Disk | A few megabytes | Several gigabytes, and it grows |
| Who sees your notes | Nobody | Nobody |
| Who sees your address | Whoever runs the computer, if you keep a ledger account | Nobody |
| Mining | No | Yes |
What a public computer can see. The chain records that a note was retired and a new one issued. It never records who did it, or that the two belong to the same person — that is the whole design. A wallet that asked a computer about its own notes would hand it that linkage, because the questions arrive together from one address; that is why the light wallet asks for the whole pool and looks locally. What the public computer still sees is the transactions you send through it, at the moment you send them, and your ledger address if you keep a ledger account. A public computer too old to serve the light wallet is asked the old way, and the wallet says so.
What a node cannot do. It cannot spend your notes, see your keys, or stop you paying someone. Your money is not at risk either way. What is at stake is only whether a stranger can tell your notes apart from everyone else's.
A reasonable rule. The light wallet is the right choice for almost everyone. Run your own node when you want to mine, keep a ledger account nobody sees, or serve the network. In the wallet:
When a wallet opens without a connection, and when you type
connect, the wallet asks: 1, a public computer while
your own copy downloads, for privacy — the light wallet, the recommended
choice; or 2, your own copy without a public computer — a full
node of your own, slow at first, the way to mine. The desktop app asks the
same on its open screen. No separate program to install or supervise; the
full node, when you want one, runs inside the wallet. You can switch
whenever you like; the notes are yours either way.
Who runs the public node?
We do. It is the same machine that runs one of the network's seed nodes, and it can see exactly what the answer above describes: the address you connect from, and which notes your wallet asks about.
We would rather say that plainly than have you assume a public node is neutral. It is not — no node is. That is why the wallet can run its own.
How much disk and time does running my own node take?
Several gigabytes, growing as the chain does, and the first run has to download and verify the chain before your balance is accurate. You can keep using the wallet while it catches up; figures will be incomplete until it has.
It lives beside your wallet files, so deleting your Marigold directory removes both — you will not be left with gigabytes you cannot account for.
Notes and money
What is a note, exactly?
A key that is worth a fixed amount. Not a balance in an account — an object you hold, like a banknote. Holding the key is owning the money, and handing the key over is paying someone. There is no sender, no receiver and no account anywhere in it.
Notes come in fixed sizes — 0.01, 0.1, 1, 10, 100 and up — so one 10 MAGLD note looks exactly like every other 10 MAGLD note.
Why do notes have serial numbers?
A note is a value, a key, and a serial number. The key says who may spend it. The serial says which note it is — and something has to, because one key can hold several notes of the same size, like several ten-dollar bills in the same pocket. Without a serial the system could not tell them apart, could not prove that this note still exists when someone hands it to you, and could not stop a used payment from being replayed against a new note on the same key.
The serial is not a number anyone hands out. It is computed from the transaction that created the note, the way a receipt number comes from the till, so there is no counter and no register of serials anywhere. And it does not follow the money: every payment retires the old serial and gives the new note a fresh one, so a note's serial says nothing about where it has been. It is the name of the note for as long as that note exists, and nothing more.
What happens if I lose my notes?
They are gone. This is the part of bearer money that has no soft edge: there is no recovery, no support line, no way to reverse it, exactly as with a banknote you drop in the street.
So keep a backup — the wallet can keep one for you, see the answers below — and please read them rather than assuming it works the way other wallets do. It does not.
Are the 24 recovery words a backup of my money?
No — and this is something you really must understand about Marigold.
In most crypto wallets a recovery phrase is the money: type the words into a new device and every coin reappears, because the coins are entries on a ledger and the phrase derives the keys that claim them.
Marigold does not work like that. Every note is its own independent secret. Nothing derives them, because if anything could, they would not be bearer instruments. The notes are files in your wallet. The words unlock those files — they are not a copy of them.
| What you have | What you can recover |
|---|---|
| A backup + the 24 words | Everything |
| A backup + your wallet password | Nothing. A backup never opens with the password (see the next answer) |
| The 24 words alone | Nothing. A key to notes that are not there |
| A backup alone, no words | Nothing. Files nothing opens |
So you need both, and they should not share a fate. Keep a copy of the wallet's files somewhere the original disk failing will not take with it, and keep the words somewhere separate — a fire that reaches one should not reach the other.
In the wallet, backup writes the encrypted backup to a file
and telegram backup has the wallet keep one current in your
Telegram chat by itself. Both cover every wallet on your computer, each
sealed with its own 24 words. Restoring takes the backup and the words:
wallet restore <file> or telegram
restore, then the 24 words of each wallet you want back at the
prompt.
Why does a backup open with the 24 words and not with my password?
Because a backup lives on servers you do not control — Telegram, a cloud drive, a USB stick in a drawer — where whoever holds a copy can attack it offline, at leisure, for as long as they like.
Your wallet password is something you type every day and chose to be
able to remember. That makes it, by construction, not random, and a
not-random secret is what an unhurried attacker brute-forces. The 24 words
are 256 bits that nobody chose; they cannot be guessed. So every backup the
wallet makes — the file from backup and the copies it posts to
Telegram — is sealed to a key derived from the words, and the password
never opens one. Since October 2026 a backup holds every wallet on the
computer, and each wallet's part is sealed to a public key its own words
name, so each part opens with its own words alone — never with another
wallet's.
That is why the wallet shows you the words when it is created, explains them, and asks you for two of them by number before it lets you go on. Write them on paper and keep it somewhere a fire that reaches your computer will not reach, or keep them in your password manager — the wallet prints them so they copy clean. Never as a screenshot or a photo: those end up in a photo library and its cloud backup, unencrypted, often on every device in the family.
The automatic backup, plainly: after you run telegram backup
once, the wallet posts an encrypted copy of every wallet on the computer
into your bot's chat and keeps it current while it is open — a full copy every day, the changes
within minutes of a payment, silently, only the last two full copies
kept in the chat. To restore on a new machine, run
telegram restore there, forward the bot everything from
the last dashed line in the chat to the end, and give the words of the
wallet you want back; do it once per wallet.
I forgot my wallet password. Is my money gone?
No. Your money is sealed with your 24 words; the password only guards
the wallet on this computer. Close the wallet and type
wallet password reset <name> in the terminal wallet. It
asks for the 24 words, checks them against the wallet, asks for a new
password, and leaves your notes exactly as they were. The old keys file
stays beside the wallet in case the old password comes back to you.
To change a password you still know, open the wallet and type
wallet password. Backups are never affected either way: they
are sealed with the words, not the password.
Does the backup cover all my wallets, or only the one that is open?
All of them, since October 2026. A wallet you put aside and never open is exactly the one a dead disk would take for good, so whichever wallet is open backs up every wallet in the folder: its own files and the others'.
Each wallet's part is sealed to a public key that its own 24 words name;
the matching private key is never written anywhere, and the public one sits
beside the wallet as backup.pub. That is what lets a closed
wallet be backed up without its words or its password being around, and it
keeps the promise that a wallet's words open that wallet and no other. The
backup names its wallets in the clear, so the restore can ask for the right
words; what is inside stays sealed.
A wallet made before this change has no such key until it is opened once
with its password — the wallet says so — or until you type its 24 words
once: at open the wallet lists the wallets still waiting,
explains why, and asks (Enter skips one for now, never leaves
it out; telegram cover asks again). The words are checked
against one of that wallet's notes before anything is written. The desktop
wallet has the same box on its Backup tab. telegram shows
which wallets are covered and which are waiting.
Do I need to be online to pay? Do I need a wallet that is always on?
No, and no. Bitcoin can be kept offline as a QR code, but it cannot be spent that way: paying with it means broadcasting a transaction, so somebody has to be online, and a wallet that is never online cannot pay.
A Marigold note is the key itself. It can pass from hand to hand offline, exactly like a banknote — printed, texted, shown as a QR code — and the network is touched only when the new holder decides to swap the lock, which they can do whenever they next have a connection. Nothing about paying requires your wallet to be connected at that moment, or to be permanently online at all.
Can I keep notes on my phone as QR codes?
Yes, and it is worth being clear about what that is. Marigold has no standalone phone app on purpose: the full wallet runs on a computer or a server you control. Your phone can still be used in two ways — as a remote control through Telegram, with the wallet open on a connected machine, or simply as a place to keep pictures of note QR codes, the way you keep banknotes in a wallet.
A note is a key, and a QR code of that key is the money. Anyone who sees, copies or scans the picture can claim the note by putting their own lock on it. So treat those pictures exactly like cash: not in a shared album, not in a chat, not on a screen someone else can photograph.
What does it cost to pay someone?
0.01 MAGLD — one hundredth of a coin — for any everyday payment, however much you are sending. The fee is a single small note handed over with the payment, so a coffee and a car cost the same to move. Only unusually large operations, bundling dozens of notes at once, step up to two or three hundredths.
And when a hundredth of a coin stops being small change? The smallest note is 0.01 MAGLD and the fee is one such note. Should 1 MAGLD come to be worth more than about a dollar, the plan on record is to add a 0.001 note (or smaller) by a network upgrade and make the fee that new smallest note. Every existing note stays exactly as it is; the table of note sizes has room reserved for the new rung. The ladder does not start at a petal because every note size is a separate key to rotate on every payment — cash stops at the cent for the same reason.
Your phone and your bot
How do I make the Telegram bot, step by step?
Ten minutes, once. You make a bot of your own in Telegram, hand its token to your wallet, and pair the two with a code. From then on your phone is a remote control for the wallet at home, and the bot's chat holds your backup. Nothing of ours is in between.
- Open Telegram on your phone (or the desktop app) and
search for
BotFather. Pick the one with the blue verified tick,@BotFather. Tap Start. - Send it
/newbot. - It asks for a name: anything you like, this is what
the chat is called. For example
Dom's Marigold. Send it. - It asks for a username: letters, digits and
underscores, it must end in
bot, and it has to be one nobody has taken. For exampledom_marigold_bot. If BotFather says it is taken, try another. Send it. - BotFather answers Done! Congratulations on your new bot and
shows a token, a line like
8012345678:AAHx…. Tap it to copy it. Treat the token like a password: whoever has it can talk to your wallet through the bot. Do not paste it in any chat. - Give the token to your wallet. Terminal wallet: with
the wallet open, type
telegram linkfollowed by a space and the token. Desktop wallet: Backup tab, paste the token into Bot token. Either way the wallet asks for a PIN: four digits or more, something you will type on the phone before the bot pays. It is not your wallet password. Type it twice. - The wallet shows a line like
/start 482913. Back in Telegram, open your new bot: tap the link BotFather showed (t.me/dom_marigold_bot) or search for its username. Tap Start, then send it that line,/start 482913, within fifteen minutes. The bot replies Paired and shows its keyboard: Balance, Pay, Request and the rest. - Turn on two-step verification in Telegram: Settings → Privacy and Security → Two-Step Verification. That Telegram account can move money now, and Telegram accounts recover by SMS otherwise.
- The wallet now asks, once, whether to back itself up
automatically to the bot's chat — in the terminal at the next
open, in the desktop wallet as a banner. Say yes. It posts an encrypted full copy and keeps it current by itself; it opens with your 24 words and nothing else.
Afterwards: telegram in the terminal shows where things
stand — who the bot is paired with, the daily limit (telegram limit
<amount> changes it), and the state of the backup. The bot
answers as long as your wallet is running, in the terminal, in the desktop
app, or as a service. If the token ever leaks, send BotFather
/revoke, pick the bot, and telegram link again
with the new token; the old one stops working at once.
Can one bot serve several wallets?
Yes, for wallets on the same computer, opened one at a time. Telegram
allows twenty bots per account, so a bot per wallet would not scale; link
each wallet to the same token with telegram link and the bot
follows whichever wallet is open. Two wallets open at once with the same
bot are told so and take turns: a bot has one listener.
The backups need nothing more: every backup covers every wallet on the
computer (see above), so whichever wallet is open keeps the one chat
current for all of them. Answering is the one thing kept apart — a
payment code in a chat should come from one wallet — so the bot's private
chat answers for the wallet that paired first, and a second wallet is told,
when it pairs, that the bot can answer it in a group of its own if you want
that: make a group, add the bot, then telegram home
<group id> in that wallet. The backups then go to that group
too, with every wallet in them, and the restore stays "forward everything
from the last dashed line in this chat". Make the bot an admin of the
group and it can tidy old copies there at any age.