Public nodes campaign Terms
Terms
One rule about where things live: nothing that could surprise a participant is in the small print. What follows is definitions and procedure, not disclaimers.
Exact definitions
- Public node
- a node that, from outside your network, accepts a connection on port
9508at a public IPv4 address, completes the protocol handshake, advertises full-node service flags, and states in that handshake a best block no more than 3 blocks behind ours, and a release version of 1.3.14 or newer; a build with a pre-release mark fails whatever its number. All five are read from the connection itself, not from anything you tell us about your setup. An address reachable only over IPv6 is not one: one machine holds a whole block of them for free. A Tor hidden service (.onion) is not one either: the protocol cannot carry such an address, so it cannot be measured. That is not a judgement about Tor: the network map counts onion nodes as a number of their own. - Round
- one sweep of the poll across every entered address. The interval is 15 minutes with jitter: each round is scheduled uniformly between 10 and 20 minutes after the last.
- Struck round
- a round our own crawler did not complete, one in which the service that receives your reports was unreachable, or one in which no entry passed. It is removed for every participant at once, counts neither for nor against anyone, and the number of struck rounds is published once for the whole list.
- Campaign window
- the two months of the campaign, 09 Nov 2026 to 07 Jan 2027: the registration month, then the measured month. Exact opening and closing times are published in UTC, so nobody has to work out whose midnight is meant.
- Registration month
- the part of the window before 09 Dec 2026. Entries are accepted, and your node is polled exactly as it will be later, but none of it counts for or against you.
- Measured month
- the last 30 days of the window, 09 Dec 2026 to 07 Jan 2027, the same for every entry. Only its rounds decide who qualifies. The 30 days are the calendar’s, not your node’s: your node is allowed to be down for the 10% inside them.
- Threshold
- at least 90% of the counted rounds in the measured month. Counted rounds are the rounds of the measured month that were not struck; that number is the same for every entry.
- Entry
- one node, one Tron address, one entry number assigned at filing and stable thereafter. Filed during the registration month. Two entries may not report the same address: a report is refused while another entry is reporting from it, and nobody is disqualified for it.
- Report
- the request your machine sends us every few minutes, carrying the token issued with your entry. The address it arrives from is the address we dial; nothing inside the request sets it. The first report proves the node is yours; every later one re-proves the address it arrives from. An entry that never reports fails every round and does not qualify. The same token opens your status page, and it cannot be revoked or reissued.
- Entry deadline
- the close of entries, 09 Dec 2026, the day the measured month begins.
- The freeze
- the moment of the post in @monetarium_world that gives the checksum of the final list and the chain height
F; the list with that checksum is published on the campaign page at the same time, sorted by entry number. It comes no later than 5 days after the window closes, and nothing about any entry changes after it. - Deciding block
- block
F + 288, whereFis the chain height stated in the post that announces the freeze. It is named at the freeze and mined about a day after it. Its hash is the randomness the draw runs on. - Group numbers
- the published list shows neither an entry’s subnet nor its Tron address, so each entry in the draw carries two numbers instead: entries in the same /24 subnet share one, entries paying to the same Tron address share the other. The numbers let anyone check that no Tron address won twice and no subnet more than twice. Your subnet is the one your first accepted report came from.
- Draw condition
- subscribed to @monetarium_world and a member of @monetarium_world_chat, both confirmed by the close of the window, checked against the two lists under the
@usernameon your entry. A confirmed entry stays confirmed. - Payout
- USDT on TRC-20, to the Tron address on the winning entry, in one batch no later than 7 days after block
F + 288is mined. Network fees are ours, not deducted from a prize.
The prizes in full
Nineteen prizes: one of $800, three of $150, fifteen of $50.
- One prize per Tron address. When an entry wins, every entry carrying the same Tron address leaves the list.
- At most two prizes per /24 subnet. When a second entry from one subnet wins, every other entry in that subnet leaves the list.
- Prizes that are not won are not drawn again. If the list runs out before the prizes do, the remaining prizes are simply not awarded. Because prizes are drawn from largest to smallest, what goes unawarded is the tail of $50 prizes, never the top one.
- A prize is sent once, to the Tron address on the winning entry. That address cannot be edited after filing, so check it before you file: if a prize cannot be delivered to it, it is not re-drawn and not reissued elsewhere.
- There is no minimum number of entries, and no rule that reduces or withholds a prize because turnout was low or high.
How the draw is computed
For prize k, counting from 1, with h the hash of block F + 288 and N the length of the list at that moment:
The formula
index(k) = SHA-256(h ‖ k) mod N
h is the block hash exactly as the explorer shows it — 64 lowercase hex characters — followed by k in decimal, both as plain ASCII text; the 32 bytes of the digest are read as a big-endian integer.
The list is the entries in the draw, sorted by entry number and counted from zero, so echo -n "<hash>1" | sha256sum is all it takes to check the first prize yourself.
After each prize the winning entry is removed 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; N shrinks, and the next prize is computed with k+1.
Everything needed to recompute the result — the frozen list, its checksum, the height F, this formula — is public before the deciding block is mined.
What your status page shows
- your entry number;
- the Tron address your prize will be paid to, exactly as we hold it;
- your report line;
- rounds passed, rounds counted, and rounds struck for everyone because of a failure on our side;
- in the measured month, your figures so far and whether they clear the threshold; before it, how your node did over the last day, marked as practice;
- the time of the last failed check;
- the address we are dialling, when your last accepted report arrived, and whether your latest report was refused because another entry is reporting from the same address;
- whether your channel subscription and group membership have been confirmed.
A line on it reads like this:
measured month: 9 December 2026 – 7 January 2027, 2,640 of 2,880 counted rounds passed, 91.6%, threshold met
Until the measured month is over, the page says so in as many words alongside the running figure, so that the first number you see is not read as final.
Round figures are updated once an hour, and the page prints when they were last updated. The address we are dialling, the time of your last report, a refused report and the subscription check update as soon as they change.
What is published at the freeze
Published with the frozen list:
- whether the entry is in the draw — without this nobody outside could work out the length of the list the formula divides by;
- its rounds passed, the same figure you watched on your status page;
- once for the whole list, how many rounds the measured month held and how many were struck because of a failure on our side — both are the same for every entry, and
2,600 of 2,880without them adds up for nobody and reads as our mistake; - two group numbers for each entry in the draw — one shared by entries in the same subnet, one shared by entries paying to the same Tron address. Both caps remove entries from the list mid-draw, and without the numbers an outsider would see the list shrink by more than one and have no way to tell a legitimate removal from a rigged one. Neither the subnet nor the Tron address is published (a winner’s address shows through the payout transaction, see the draw), and the numbers are handed out in list order rather than computed from an address, so neither can be worked back out of them.
How disagreements are settled
The poll record is the evidence, and you can have all of it.
Ask at support@monetarium.world, quoting the link to your status page, and you get the full round-by-round log for your entry: every round in the window, the time, and the reason each failed one failed.
It is the same record the result was computed from.
What we cannot settle after the freeze is anything that changes who is in the draw: a subscription confirmed after the close of the window, an entry that never reported, and a mismatch you spot in the published figures alike. The list is published before the deciding block is mined, and that sequence is the only reason the draw can be checked by anyone at all. Correcting the list after the block would replace a verifiable result with our word for it.
What is not promised
- No return is promised, estimated or implied — not from this campaign, not from mining, not from staking.
- A prize is a draw, not a payment for uptime. Qualifying puts your entry in the list; it does not entitle you to money.