Dad first. Bulldogs, hashes & hustles 🧱⚡
Bitcoin mining class of 2014. Built on Linux, networks & security.
Not a UFC/NFL/NBA analyst… but I play one on X.
Pool Directory is live.
Every pool we track now has a profile with hashrate, payouts, stratum details, verified blocks, and StratumRace data.
What’s missing? What would you like to see? Let us know.
https://t.co/1AmiAA63Wp
We talk a lot about mining pools. Who’s on a lucky run, who’s in a dry spell, who’s getting new work out the fastest, who’s attracting more hashrate, and who’s running cool promotions.
But one thing we don’t talk about nearly enough is the people behind these pools. The guys putting in the hours to keep everything running.
CKPool: My first interaction with Con was back around 2014. The man has literally helped shape solo mining into what we know today. His code has powered or influenced countless pools and mining software projects over the years. His contributions go well beyond CKPool itself. I have the utmost respect for him and what he’s built.
AtlasPool: Newer name in the community over the last couple of years, but he brings real networking expertise. He’s pushed things forward on the infrastructure side, building out a global presence and always looking for ways to improve things. I’ve worked through some interesting technical challenges with him, and I’m happy to call him a close friend.
HeliosPool: What started as a small side project from our neighbor to the north has grown into a niche community with a nearly global footprint. He’s put in the work, and one thing I’ve always respected is that I’ve never heard him say a bad word about anyone else in the space. He’s just focused on growing his project and taking care of his users. Always happy to see his name pop up in my messages.
Parasite: These guys didn’t just spin up another mining pool. They brought an entirely different community of enthusiasts into mining, many of whom probably wouldn’t have gotten involved otherwise. They put their own fun spin on it, and they’ve accomplished a lot in a relatively short amount of time. I’ve talked shop with the pool admin a few times, and he’s a genuinely good dude who knows his stuff.
The list goes on. Plenty of others I’ve worked through problems with or just talked shop with over the years.
And that’s really the point.
Behind most of the solo pools in our little corner of the mining world, there’s often just one or two guys keeping the whole thing going. They have jobs. They have families. They have lives outside of Bitcoin. Yet they still find the time to build, maintain, and improve these services.
Sure, there’s competition. There should be. Competition pushes everyone to build better things. But sometimes we get so caught up comparing pools that we forget about the people actually building and running them.
These guys aren’t just running pools. They’re putting in the work behind the scenes and helping keep the independent mining community alive.
@Ms_L_E Don’t we all do this? Haha. I see a solo block hit on some random pool I’ve never even used, and I immediately check mine, you know, just to be thorough. 🤣
Haven’t hit a block in over 10 years, so I must be due, right? 😂
Everything’s coming up CKPool lately. Another solo block, this time from someone hashing at ~470 TH/s.
One thing I’ve learned over the years is that while mining is completely random, there are definitely hot and dry spells. CKPool is on a hell of a run lately.
Always good to see solo miners hitting blocks. It’s good for the independent mining community.
@neo_hayirdir CKPool went through a pretty unlucky stretch before this. Over time, variance tends to even things out and blocks should average out according to the pool’s share of the network hashrate.
@JoelHodlman@grok From one dad to another, lots and lots of fluids. Kids are incredibly resilient, and staying hydrated does more than we sometimes give it credit for. Hope your little guy feels better soon!
The observant amongst you may have noticed this tiny luck addition to https://t.co/k9E44gIzeZ. It shows what the probability is of reaching this pool difficulty and is a surrogate marker of "luck." We are a long way from the worst luck the pool ever saw which I searched for and found was on Christmas day 2016 at a truly horrendous 789%.
Footnote: This value is never perfectly accurate because it does not take into account diff changes over the block solve duration, underestimating it when diff is rising, and vice versa.
One of the best things about Bitcoin mining has been the people I’ve met along the way, including Matt, who I’m lucky to call a friend. A good chunk of my daily texts are with people I’ve gotten to know through mining, and half the time we’re not even talking about Bitcoin anymore.
A big milestone for AtlasPool. Our first four endpoints — Ashburn, Portland, Frankfurt, and Hong Kong — are now running our newest build, and the early results on https://t.co/vEKnO8ig3p are incredibly promising. Over the past 24 hours AtlasPool has won roughly 4 out of 5 block notification races against 25+ monitored pools.
This build is the culmination of a lot of research and hard work chasing one goal: the most performant Bitcoin pool available to miners. Without going too deep into the weeds, it pairs the latest Bitcoin Core and ckpool with our own self-built tooling to squeeze out every last drop of performance, all running on blazing-fast AWS Graviton EC2 instances placed in some of the most interconnected locations in the world.
It's been a real learning journey, and I'd be remiss not to thank a few people who helped along the way:
@ProofOfMike — whose idea and early work measuring block notification speed eventually grew into https://t.co/vEKnO8ig3p, and who's been a great sounding board for ways to improve the pool.
@philip_dath — who has worked with me on a range of performance improvements across both the node and the stratum server. We're still at it today, and I really appreciate his expertise and his friendly attitude.
Aviral at @Altair_tech — who understood AtlasPool from our very first conversation, and has supported the pool with important introductions, giveaways, and no shortage of encouraging words.
@mutatrum — a longtime friend of the pool and a valuable technical sounding board, who helped pin down a few bugs. An all-around good dude.
@WantClue — First person to interview me for a podcast and also added AtlasPool to the BitForge Nano firmware. And last but not least,
Con Kolivas (CK) — whose awesome stratum server implementation is the bedrock of AtlasPool.
A huge thank-you as well to our AtlasPool Discord crew, who keep the pool going with hashing, humor, and expertise: metaprinter (our first moderator, GZR, Travetown, RBX (first Aussie on the pool!), Beckels, Happy Day, Jeebz, BlackHole, proandres6 (biggest share so far at 66T), Mr. KV3 (we miss you!), Blockdyor (who wrote the first AtlasPool review), and many more.
And a thank-you to DTV Electronics and the South African Bitcoin community for the sponsorship that helps power our London and Cape Town endpoints. If anyone else out there would be interested in sponsoring an endpoint, I'd love to hear from you.
I'll be honest: it's a little disappointing that after nearly a year of operation AtlasPool hasn't found a block yet. But every one of these improvements shortens the odds, and I believe that moment is coming soon. Until then, I'll keep building and operating the most performant and reliable Bitcoin pool I can.
Onward. 🧡
For the love of God, more code, more tests, and more process don’t necessarily mean more progress.
Sometimes you’re just engineering a more sophisticated way to get absolutely nothing done.
Got into a theological debate with a priest while waiting for coffee this morning. Finally had to pull rank and inform him I’m an ordained minister of the Church of the Latter-Day Dude. Got my credentials online 20 years ago. Father, it’s Sunday. You’re making me late for football. The Dude abides.
1/ We've temporarily removed NexusPool from StratumRace and recalculated the leaderboards without it. Its full-template results were being scored on a partial template, not its complete one. It can return once our collectors credit every pool at its first complete template.
WHERE ARE THE SOLO MINING BLOCKS?! ⛏️
CKPool: 286% of expected work
Parasite: 228%
AtlasPool: 128%
Across their respective droughts, that’s ~6.4 blocks’ worth of work with NOTHING to show for it.
Screw you, variance.
SHOW ME A HOME MINER BLOCK.
Glad we’re all in agreement. We’ll update the About page to explicitly name AtlasPool rather than relying on the existing hyperlink. The relationship was already disclosed on X, the About page, and in the code itself, but happy to make it even clearer.
Let’s leave this thread up so I can point people to it if this ever comes up again.
And since we’re talking about good practices, that includes coming to the table with facts and data before making accusations. As I’ve said all along, the project is open source, our relationships are disclosed, and the results are independently verifiable.
Glad we can finally put this to bed. Good night, gentlemen.