Public nodes campaign
A draw for public nodes
Run a node the rest of the network can reach. Keep it reachable for 30 days and your node enters a draw for nineteen prizes, with a top prize of $800.
- Window opensWindow openedpassednext
11 public nodes, 3 of them onion, counted on 05 Nov 2026, before the announcement. A fixed figure, not updated.
- registration month
- Entries closeEntries closedpassednext
The last moment to file.
- measured month
- Measurement ends, the window closesMeasurement ended, the window closedpassednext
The window's last day, 07 Jan, is inclusive.
- The freezeList frozenpassednext
No later than 5 days after the window closes.
The frozen list is not on the page yet. It appears when the freeze is done, which can take hours.
- Chain height F is postedChain height F posted: {f}after the freezepassednext
It comes in a post in @monetarium_world.
- Deciding block is mined, then the drawDeciding block mined, draw doneabout a day after the postpassednext
- PayoutsAll prizes paidno later than 7 days after the deciding blockpassednext
What this is
A public node is one that other nodes can actually connect to: its P2P port is open, it answers, and it serves chain data to peers that ask. Most nodes are not public — they connect out and never accept anything in — and a network of those cannot introduce a new node to anybody.
This campaign pays for the other kind. You run a node with its port reachable from outside. Every few minutes your machine reports its IP address to us, and we poll that address every 15 minutes. A node that answers at least 90% of the rounds in the last 30 days of the campaign, each time keeping up with the chain, goes into a single draw for nineteen cash prizes, paid in USDT.
Nothing is sent to us and nothing is staked. There is no transfer, no deposit, no wallet, no signature, and no address of yours that money leaves. The only thing it costs you is running the node — and nothing at all if it is already running.
Terms
| Campaign window | 2 months, 09 Nov 2026 – 07 Jan 2027 |
| Registration month | from the start of the window to 09 Dec 2026: file and set up; your rounds are shown but not counted |
| Measured month | the last 30 days, 09 Dec 2026 – 07 Jan 2027, the same dates for everyone |
| Threshold | at least 90% of the counted rounds in the measured month |
| A round | one sweep of every entered address, every 15 minutes with jitter |
| A public node | reachable from outside over IPv4, completes the handshake, advertises full-node service flags, is no more than 3 blocks behind our own tip, and states a release of 1.3.14 or newer |
| Entries | one per node, filed during the registration month; none once measurement starts |
| What you run | one line in the task scheduler on the machine your node runs on; it reports your address and proves it is yours |
| What an entry binds to | a Tron address — no name, no email, no account |
| Prizes | nineteen: one of $800, three of $150, fifteen of $50 |
| Limits | one prize per Tron address, and at most two prizes per /24 subnet |
| The draw | the hash of block F + 288, where F is the chain height in our freeze post in @monetarium_world |
| Payout | USDT, TRC-20, one batch, no later than 7 days after block F + 288 is mined |
| Draw condition | subscribe to @monetarium_world and join @monetarium_world_chat, confirmed by the close of the window |
That is a list of prizes, not a pot that gets divided. Nineteen prizes are drawn once, from the entries that qualified. Prizes that are not won are not drawn again — if fewer entries qualify than there are prizes, the smaller prizes simply go unclaimed.
What counts as a public node
Five checks, and you can run all five yourself.
- Reachable. Something accepts a TCP connection on port
9508, the node’s default. - It is a Monetarium node. The connection completes the protocol handshake.
- It is a full node. The handshake advertises full-node service flags. The standard build always advertises them and there is no setting that turns them off, so nothing is lost here by anybody.
- It is keeping up. The same handshake carries your node’s current block height, and it must be no more than 3 blocks behind ours.
- It is up to date. The same handshake carries your node’s version, and it must be a release of 1.3.14 or newer. Older releases run different consensus rules, so the network can split and leave them behind. This minimum does not change before the campaign ends, and re-running the installer updates your node.
All five are checked in every round, over one connection, and a round is passed only when all five pass. A node that is stuck, or still catching up with the chain, has nothing current to give the peers that connect to it, and it is not what is being paid for here. Three blocks is deliberately generous: at a 5-minute target block time that is 15 minutes of slack, so a node that is honestly working and simply got a block a minute after we did is never penalised.
Every check runs against a public IPv4 address.
A node reachable only over IPv6 cannot take part, and neither can one published only as a Tor hidden service (.onion); the full terms say why.
What 90% actually forgives
At one round every 15 minutes, 30 days is about 2,880 rounds, so 90% forgives roughly 288 of them — about three days of downtime, taken all at once or spread out. The exact interval is randomised between 10 and 20 minutes, so there is no schedule to game.
The first month is for getting it right. From the day you file, the crawler polls your node exactly as it will during measurement, and your status page shows how it did, marked as practice. Nothing from that month counts for or against you.
If something fails on our side, it costs you nothing. A round our crawler never started does not exist, and a round it started and could not finish is struck for everyone: it counts neither against you nor towards you. Their number is published once for the whole list, so the arithmetic adds up in public.
Three steps to take part
- Run a node and make its port reachable. If the node sits at home behind a router, the port still has to be forwarded — that part is not optional and nothing else substitutes for it.
- Check yourself before you file. Run this on the machine your node runs on, the same machine that gets the report line (see “How you prove the node is yours” below):
Self-check
curl -4 -sS -X POST https://monetarium.world/promo2/api/selfcheck
The crawler dials from 88.99.60.167
On Windows, in PowerShell or cmd:
curl.exe -4 -sS -X POST https://monetarium.world/promo2/api/selfcheck
We try to connect to your node right now, exactly the way the crawler will. We dial from the same address the crawler dials from; that address is printed beside the command.
- File an entry.
You give your Tron address, your Telegram
@username, and tick three boxes: the channel, the group, and that you accept these terms. We never ask for your node’s address: we take it from your reports, and it can change as often as it likes. Then you prove the node is yours — see below — and that is the end of your part.
Filing is not a race, but it does have a deadline: entries close when the measured month begins, since a later entry could not be measured for the full month. The earlier you file, the longer you can watch your node pass real rounds before they count, and the longer you have to fix a mistake, because a mistake is fixed by filing a fresh entry.
Nothing on an entry can be edited after filing. If you get something wrong, file a fresh entry while registration is still open.
Whenever you refile, run the command from your new status page on the same machine, as the same user or administrator as before. It replaces the old report line with the new one; do not add a second line by hand. If the old line is left running — added by another user, or on another machine behind the same address — the new entry’s reports are refused for as long as the old one keeps reporting from the same address, and your new status page says so. With the old line gone the old entry falls quiet, and within 20 minutes the address is free for the new one.
How you prove the node is yours
Without this step anyone could read a list of nodes, file somebody else’s under their own Tron address and collect the prize. So the entry has to prove that the machine at the address it reports from is yours.
The report line
One line does it, and it keeps doing it. When you file, your status page gives you a ready-made command, and it stays there for as long as the campaign runs. You run it once on the same machine your node runs on, and it adds the line to the task scheduler — cron on Linux or macOS, a scheduled task on Windows; the page gives you the right form for yours. The line it adds:
The report line
*/5 * * * * curl -4 -fs -m 30 -H "Authorization: Bearer YOUR-TOKEN" https://monetarium.world/promo2/beacon
Every few minutes it sends us a short request. We take your address from where the request came from, never from anything written inside it — which is why the same report that tells us where your node is also proves you are behind that address. Nothing has to be opened for it: an outgoing connection passes through any router and any firewall, and a working node makes outgoing connections by definition.
That is the whole of it. No re-proving when your address changes: the next report carries the new address and proves it in the same breath.
Your token
The line is yours alone. The token in it belongs to your entry and is the same token that opens your status page: a line anyone could copy would prove nothing. Keep it to yourself: whoever holds it can point our dialling at their own machine, and we would stop measuring yours. Nobody can take your prize that way — it is paid to the Tron address on your entry, and that address cannot be changed — but you would lose the rounds. A token cannot be revoked or reissued. If yours leaks, file a fresh entry while registration is still open and replace the line; once the measured month has begun there is no remedy.
What it proves
Until your first report, every round fails. Before it we have no address for you and nowhere to knock. In the registration month that costs nothing; in the measured month it counts like any other failed round.
What it proves, and what it does not. It proves that the machine at that address is under your control. It does not separate your node from another machine on the same connection — the two share a public address. So the only person who could claim your node is someone who shares your public address with you. Someone who only read your address off the network can do nothing at all, and that is the case this check exists for.
The same fact has a second consequence, and it is worth knowing before you file. If someone else on your connection runs a node and files their own entry, the two entries would report from the same public address, and only one of you can, or one node could be filed twice: whichever is reporting from it already keeps it, and the other’s reports are refused. Nobody is disqualified for it, and the refused one sees it on their status page right away, not at the end. Settle it between you before either of you spends a month on it.
There is no message to sign: a node has no key, and a signature from a wallet or Tron address would say nothing about a machine.
Keeping it running
And the reports have to keep coming. Before each round we look at when your last accepted report arrived. If your machine has been quiet for longer than 20 minutes, that round is counted as failed without our even dialling: a machine that stopped reporting is a machine we cannot reach, and we no longer know where to knock. Nothing else happens to your entry: it stays in, and the first report to arrive after the quiet puts you back into the very next round. What the quiet costs is the rounds inside it, and nothing beyond. Your status page shows the time of your last accepted report, the one number to glance at if you want to be sure nothing has quietly stopped.
Your node can tell you whether its port is open: monetarium-ctl getpeerinfo lists its peers, and any peer marked inbound is a connection that came in from outside.
What none of this fixes. If your provider puts you behind carrier-grade NAT, incoming connections do not reach you at all — that is a property of the connection, not a rule of this campaign. The self-check tells you so in a few seconds.
The entry form
Entries close 09 Dec 2026
Entries open 09 Nov 2026
closed when the measured month began
The form is on its own page. Read the full terms
Your status page
When you file, you get one link. Save it.
We hold no email address of yours and there is no account: your entry is bound to a Tron address, not to a person, so there is nothing to send you and nowhere to log in.
If you lose the link, it is in your report line: your status page is monetarium.world/promo2/s/ followed by the token in that line.
That page is everything the campaign tells you personally: your report line, your rounds against the threshold, the address we are dialling and when your last report arrived, and whether your subscription and group membership have been confirmed. Its round figures are rebuilt once an hour, and the full list of what it shows is in the full terms.
Watch that page rather than waiting for the end. Measurement is sampling: a node whose true uptime is exactly 90% passes about half the time. The point of showing you a running count is that you can see your margin and fix things while fixing them still helps.
measured month: 9 December 2026 – 7 January 2027, 2,640 of 2,880 counted rounds passed, 91.6%, threshold met
More than one node
Running ten nodes is exactly what this campaign is for, and nothing here discourages it.
- One entry per node. More nodes, more entries, a better chance of being drawn.
- One prize per Tron address. Once an entry wins, every entry paying to the same Tron address leaves the draw. Give each node its own Tron address to keep them all in play.
- At most two prizes per /24 subnet, the subnet of your entry’s first accepted report.
The draw
The deciding block is named at the moment the list is frozen: 288 blocks, about a day, past the chain height at that moment. That is what keeps us from steering the result: when the list is fixed, nobody, us included, can know the hash of a block that has not been mined yet.
- Entries close when the measured month begins, and the window then runs to its end.
- The list is frozen and published on this page, no later than 5 days after the window closes, sorted by entry number, with a checksum. At the same moment a post in @monetarium_world gives the checksum and the chain height
Fat the time of the post — the number in the post is the one that counts — which makes blockF + 288the deciding block. That post is never edited, and from that moment the list does not change. - Block
F + 288is mined. Its hashhis visible to everyone on the explorer’s page for that block. - For prize number k, we compute
SHA-256(h ‖ k), read the result as an integer, and take it modulo the length of the current list. That position wins prize k. The winning entry is struck from the list, together with every entry sharing its Tron address and, if the winner’s subnet now holds two prizes, every other entry in that subnet; the list gets shorter and the same is computed for k+1. Prizes are drawn from the largest to the smallest, so the order does not depend on any choice of ours.
A worked example. The list has 100 entries. SHA-256(h ‖ 1) as an integer leaves remainder 37 when divided by 100, so the first prize goes to position 37 in the list (counting from zero). That entry is struck, 99 remain, and the second prize is SHA-256(h ‖ 2) modulo 99. And so on, nineteen times.
Anyone can recompute this: the list is public, the block hash is in the chain, and no third-party service is involved.
The time of the channel post shows that the list came first: compare it with the time of block F + 288.
Take your own copy on the day of the freeze, with its checksum and the height F.
The result is added to the same page, beside the frozen list and without changing it: the block hash, the computation for each prize and the winning entry numbers, announced by a second post in the channel.
After the payout, the hash of each prize’s USDT transaction is published beside that prize, so anyone can see that the prize was actually sent, not only drawn. A Tron transaction shows the address it went to, so for a winner the link between the entry number and its Tron address becomes public.
What we publish
At the freeze, for every entry, under its entry number, we publish enough for two things and no more: for a stranger to recompute the draw from start to finish, and for you to check your own result against what your status page had been showing you. The exact list is in the full terms.
Every filed entry is published, the ones that qualified and the ones that did not — otherwise there would be no way to see that the list was not trimmed before the draw.
Nothing that identifies you is published, at any level: no node address, no @username. An entry is its number.
Node addresses are discoverable anyway — anyone running a node sees them — but there is a difference between discoverable and indexed on a campaign page next to a history of when your machine was up.
That history is yours.
The full poll log is yours on request — round by round, with times and the reason for each failure.
It is what settles a disagreement, and it is given to the participant who asks rather than published, because it is data about one specific connection.
Ask at support@monetarium.world, with the link to your status page: that link is what shows the entry is yours.
The subscription and the group
Two conditions, checked separately: subscribed to @monetarium_world, and a member of @monetarium_world_chat.
Give the @username on your entry and tick both boxes.
They must be confirmed by the close of the window. We check entries as they arrive, not all at once at the end, and a confirmed entry is settled for good. If yours cannot be confirmed, a line appears on your status page — that is the whole notification — and you have until the window closes to fix it: subscribe or join, and we check again. After that it cannot be fixed; the full terms say why.
We will not write to you in Telegram about it, ever. See the next section for why that rule is worth more than the convenience.
How to tell us apart from an impostor
- This campaign never asks you to send coins. It involves no transfer of any kind. Anyone telling you to send VAR, USDT or anything else “to qualify”, “to register” or “to receive your prize” in this campaign is not us.
- Nobody will ever ask you for your seed phrase.
- We never write to you first, and nothing is settled in Telegram — not in a private message, not in the group; everything personal is on your status page.
- Two domains are ours and no others:
monetarium.world, which is this page and the full terms, andmonetarium.online, the block explorer. Anything else is not us, however close the spelling. - How things work is answered in the group — how the self-check works, where the report line goes, port forwarding, running a node. Those answers are the same for everyone and name nobody, and we give them there.
What happens to your data
Entries and the poll record are deleted in a single operation 30 days after the last payout.
The date is printed on this page.
Your entry goes with it: the address it reported from, its reports, its @username and its round-by-round record.
The network map is not part of that record and does not hold history — it shows the network as it is now, and it stays after the campaign ends.
Deletion date: set after the last payout.
Outside this campaign
While your node is running anyway
A node is most of the setup for mining and for staking, and if yours is already running the rest is a short step. What either of those earns is not something this campaign promises or estimates — the mechanics are on Ways to Earn, and the numbers are whatever the chain pays.