bots: @sats_per_dollar @sats_per_euro @sats_per_aud @sats_per_ruble @taproot_signal @500_headlines code: https://xitter.cf/t.co/Xwg6zsuAl6 LN/nostr: ⚡️[email protected]
mainnet
Joined October 2019
- Tweets21.1K
- Following2.8K
- Followers3.3K
- Likes15.3K
mutatrum retweeted
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 stratumrace.com 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 stratumrace.com, 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. 🧡
Base-172808 encoding, so I can fit 256-bit values, like “96cca2a0c8a3263c74ef36274abf55f410d992034d16e8285811a9ad3fc59c13”, into short 25 character strings, like “ₖΔ»Ұў⛄ԃҳІƑ※‶∻ď”.
Base-1353 encoding, so I can fit 256-bit values, like “96cca2a0c8a3263c74ef36274abf55f410d992034d16e8285811a9ad3fc59c13”, into short 26 character strings, like “ᓒᔳᣏዧᐎᑙᖜዌᙔᐸƫȶƃᒨዊጶᙵኻѫyፐᎉᑫᖫᘪᒩ”.
Also, I think these sigils are beautiful.
johnservil.github.io/sigil/p…
It's Halloween. Or April 1st, not sure, maybe both.
Base-1353 encoding, so I can fit 256-bit values, like “96cca2a0c8a3263c74ef36274abf55f410d992034d16e8285811a9ad3fc59c13”, into short 26 character strings, like “ᓒᔳᣏዧᐎᑙᖜዌᙔᐸƫȶƃᒨዊጶᙵኻѫyፐᎉᑫᖫᘪᒩ”.
Also, I think these sigils are beautiful.
johnservil.github.io/sigil/p…
mutatrum retweeted
I just made a programming language doing exactly this. As many address-space-reserved huge stacks as the program statically needs, with bump alloc, stable pointers, all compile time safe and yet way faster than what you can do in C++/Rust: github.com/aardappel/goose
mutatrum retweeted
I'm speaking at @bitcoinconfams on 5 & 6 Nov in Amsterdam and I've got 5 GA passes to give away.
Like, retweet & reply with your favourite Bitcoin conspiracy to win a ticket(or 2)!
I'll pick 5 winners on Oct 28.
Pls, only enter if you can actually make the trip.
Is this just an android phone?
LEDGER UNVEILS NEW SECURITY DEVICE WITH AI AGENT CONTROLS AND ADVANCED ANTI-TAMPERING PROTECTION
Ledger has announced Ledger Atom, a new security and privacy device that combines Android-based applications with Ledger’s secure operating system to protect Bitcoin, digital identities, private communications and AI agent activity.
Unlike traditional hardware signers, Ledger Atom can run everyday applications while isolating sensitive operations in a separate Secure Mode.
Key features include:
AI Agent Security:
Users can authorize sensitive actions performed by AI agents through physical confirmation on the device, including integration with OpenClaw.
Advanced Anti-Tampering: New protections designed to detect unauthorized opening of the device or removal of its display, alongside additional safeguards for internal components.
Hardware Privacy Switch: A physical switch cuts power to the cameras and microphone, preventing software from activating them.
Encrypted Messaging: OpenPGP support allows messages to be encrypted and decrypted in a secure environment, without exposing plaintext to messaging applications.
Post-Quantum Security: Hardware-accelerated cryptography designed to support emerging post-quantum encryption standards.
Secure Transactions: Users can initiate transactions and approve them on the device’s trusted display.
The announcement comes amid growing scrutiny of Ledger’s hardware security following the discovery of malicious physical implants in devices distributed through third-party retailers.
Ledger says Atom will feature its most advanced anti-tampering and tamper-evident protections to date.
The company is positioning Atom as a broader security platform that extends beyond cryptocurrency custody to AI agents, communications and digital identity.
If you have ooen source and closed source, how do you call something you've written only for yourself?
