Live stats
The price list and the delivery record for the advertising space on this board: what a rank costs and what the ranks above it have been getting. None of it counts a person, because a board that tracks nobody can only count events, and the last section is how to check all of it without us.
- Visits
- 309
- Clicks sent out
- 0
- Click-through
- 0.0%
- #1 costs
- 0.06 XMR
- XMR per click
- –
What each rank costs
Every rank on the board with what it is holding, what it has received, and what it would take to pass it. This is the table to bid from.
| # | Listing | Holding | Clicks | Per day | Pass for |
|---|
Amounts in XMR. “Per day” is that listing's clicks divided by the days it has been on the board, a rough rate, and a new listing has had no time to earn one.
Traffic
Views of the board, the clicks it sent out, and what those views arrive on. Each breakdown is its own counter, they are never stored together, so they cannot be crossed.
| Hour | Visits | Clicks | CTR |
|---|---|---|---|
| 27 Aug 21:00 | 6 | 0 | 0.0% |
| 27 Aug 20:00 | 17 | 0 | 0.0% |
| 27 Aug 19:00 | 16 | 0 | 0.0% |
| 27 Aug 18:00 | 47 | 0 | 0.0% |
| 27 Aug 17:00 | 41 | 0 | 0.0% |
| 27 Aug 16:00 | 15 | 0 | 0.0% |
| 27 Aug 15:00 | 36 | 0 | 0.0% |
- direct99%308
- t.co0.3%1
- google.com0.3%1
Referrer
3 entries · 310 total
- direct99%308
- t.co0.3%1
- google.com0.3%1
- Firefox39%117
- Safari34%104
- Other15%45
- Chrome11%34
- Opera0.3%1
- Edge0.3%1
Browser
6 entries · 302 total
- Firefox39%117
- Safari34%104
- Other15%45
- Chrome11%34
- Opera0.3%1
- Edge0.3%1
- macOS41%127
- iOS33%102
- Other17%52
- Windows5.8%18
- Linux2.6%8
- Android1.0%3
Operating system
6 entries · 310 total
- macOS41%127
- iOS33%102
- Other17%52
- Windows5.8%18
- Linux2.6%8
- Android1.0%3
- desktop66%205
- mobile34%105
Device
2 entries · 310 total
- desktop66%205
- mobile34%105
- Direct99%308
- Search0.3%1
- Other0.3%1
How they arrive
3 entries · 310 total
- Direct99%308
- Search0.3%1
- Other0.3%1
- 🇪🇸 Spain51%158
- 🇺🇸 United States15%45
- 🇸🇬 Singapore12%38
- 🇭🇰 Hong Kong SAR China3.2%10
- 🇨🇳 China2.6%8
- 🇳🇱 Netherlands2.3%7
- 🇧🇷 Brazil1.9%6
- 🇰🇷 South Korea1.9%6
- 🇩🇪 Germany1.6%5
- 🇯🇵 Japan1.6%5
Country
19 entries · 308 total
- 🇪🇸 Spain51%158
- 🇺🇸 United States15%45
- 🇸🇬 Singapore12%38
- 🇭🇰 Hong Kong SAR China3.2%10
- 🇨🇳 China2.6%8
- 🇳🇱 Netherlands2.3%7
- 🇧🇷 Brazil1.9%6
- 🇰🇷 South Korea1.9%6
- 🇩🇪 Germany1.6%5
- 🇯🇵 Japan1.6%5
Money moving
0 bids settled in the last 24 hours, worth 0.00 XMR. What is being paid, how often, and for which rankings.
What it costs to keep this alive
Every year of running costs that comes in buys another year, first.
- A year of it
- $3,242
- Paid up until
- 2027-08-27check
- Taken so far
- 0 XMR
- Paid ahead
- 6.985 XMR
- The domainxmrbid.lol itself. If this lapses the board is gone, whatever else is paid for, which is why it is first.$35until 2027-08-27
- The serverEight cores and 8GB running the board, its database and a full Monero node. Nothing here sits on somebody elses platform.$480until 2027-08-27
- The disk250GB for the Monero blockchain, which is what lets this board verify its own income instead of asking a stranger's node.$152until 2027-08-27
- Mailhelp@ and abuse@ delivered straight to an encrypted mailbox, with no forwarder in between.$175until 2027-08-27
- CloudflareThe edge the clearnet site is served through: the tunnel that keeps the origin unreachable, the firewall rules and the rate limits.$2,400until 2027-08-27
- Tor and I2PBoth cost nothing to run and are not going anywhere. Listed so the answer is complete rather than only the parts with invoices.freenothing to lapse
Renewals are bought as soon as the money for them arrives, rather than at the end of a term when it might be gone. Everything beyond that is the operator's income and is not spent on the board. This is a business and it is said here plainly; the point of the page is that the part keeping the site alive is bought first and its dates can be checked without asking us.
The figures are invoiced in dollars because that is how the invoices arrive, and the board is paid in Monero. 0 XMR is about $0 at 1 XMR = $464.12, the rate this page was built with, so the multiplication can be redone rather than taken on trust.
Spent trying to grow itnone of this keeps the board alive
- Finding readersA quarter of everything the board takes goes back into advertising it. A fixed budget is a number nobody can check and one that goes stale the moment the board grows; a share can be multiplied out against a figure already on this page, and a quiet month spends less without anybody deciding to.0XMR, 25% of 0
Counted on its own because if it stopped tomorrow the board would carry on exactly as it is. Adding it to the cost of staying alive would make surviving look more expensive than it is.
Check it yourself
A board grading its own homework is worth nothing. Here is what you can check without us, and the one thing you cannot.
- Check the money against the chain. The figures on this page are traffic; the ones the board is actually judged on are the payments, and those do not come from us at all. Every settled bid carries a Monero InProof, published at /proof and in /stats.json. Run
check_tx_proofin any wallet, against any node, and the amount comes back from Monero rather than from this server. Their sum has to equal the total printed on the board. - Count it in your own analytics. Every outbound click carries
utm_source=xmrbid.lol, and the referrer sayshttps://xmrbid.lol/. Your logs, not ours, are what you should be bidding against. - Watch your own counter. Each listing's clicks are on the board in public, beside the bid that bought them.
- Take the raw numbers. /stats.json is CORS-open so anybody can fetch, archive and diff them. Not on request and not under a licence: the whole record is open data, including to somebody building a board to compete with this one.
- Check the chain. Each finished day is sealed with
sha256(previous hash + newline + payload), so an old figure cannot be quietly corrected, chain.json. - Check that we could not have written it later. A chain proves an edit; it does not prove the chain itself was not rebuilt from scratch this morning. So each sealed day's hash is submitted to OpenTimestamps, which folds thousands of strangers' digests into one Bitcoin transaction. The proof that comes back says the hash existed before that block did, and no amount of rewriting produces one of those. Nothing is anchored yet.
- And the one you cannot check: the visit count itself. Nobody can prove how many requests a server answered. The chain and the timestamps prove the figure has not been altered since the day it was sealed; they cannot prove it was right when it was written, and no cryptography fixes that for anybody. So treat visits as our number and clicks as yours: a click lands in the listing owner's own logs, which is why every claim this board makes about delivery is made in clicks.
What these numbers actually count
This is the part most boards leave out, and it is the part that says what a privacy-first directory actually costs to run. There is no analytics script on these pages and no row per visit in the database, so the figures above are thinner than the ones an ordinary dashboard prints. They are also the only ones that can be produced without keeping a record of the people who came here looking for a wallet, a VPN or a way off an exchange, which is a record we would rather not be holding when somebody asks for it.
Every number on this page counts events, not people. A visit here means one page opened, not one person: somebody opens the board and one is added to today's counter, and one to each of a few buckets, mobile, Firefox, arrived from Hacker News. Somebody clicks a listing: one is added to that listing and one to today. Then it is over. Nothing is written down about who it was.
Those buckets are separate numbers that never meet. The board knows it served some visits to Chrome and some visits from Reddit. It cannot tell you whether those were the same visits, because nothing ever recorded them together. Answering that would need one row per visit, and there is no such table.
Which is why some familiar figures are missing. No unique visitors: counting people means recognising them when they come back. No bounce rate and no session length: both need several requests tied to one person. The board does not do that, so it cannot report it. The pill says “visits in the last hour” for the same reason: one person refreshing thirty times looks exactly like thirty arrivals, and nothing here can tell them apart.
Anything that says it is a machine is kept out of these numbers. A crawler that carries a crawler's name is counted separately and appears nowhere in visits or clicks, which matters because a modern crawler otherwise arrives wearing a full Chrome user agent and lands in the figure an advertiser is reading. What is not attempted is catching a crawler that lies about itself: that needs every visitor fingerprinted and watched to find the ones behaving oddly, which is the thing this board exists to not do. So the claim is exact, and it is the strongest one that can be made without profiling anybody: nothing here declared itself a machine.
Which is why clicks is the number to judge this board by, and the only one on this page you do not have to take our word for. A click is a visitor leaving for your site, it carries utm_source=xmrbid.lol, and it lands in your own server logs where you can count it yourself. Read visits as the ceiling instead: the most people it could have been, never the number it was, because one person refreshing thirty times is recorded exactly like thirty arrivals and nothing here can tell them apart.
Where AI traffic shows up
When somebody asks an assistant for, say, a no-logs VPN and follows a link it gave them, that visit arrives with the assistant as its referrer. Those are pulled out of the referrer list into their own card, so reach through models is counted separately from reach through forums and search. It is a different kind of visibility and it is worth watching on its own.
Assistants only cite pages they can read, so the board is built to be readable: every listing has a plain page of its own at /@handle, server-rendered, with no script needed to see the content, and it is in the sitemap. Nothing here is behind an interaction.