Stratum V2 and https://t.co/FrW30Os9sI experiment.
https://t.co/it5O94b8Cf - stratum V2
https://t.co/A2YK5PASoB - stratum V2 with job declaration support
Pool Stats: https://t.co/ENvtS79Qpi
User Stats: https://t.co/lPBNcRIYir
I have experimental code implementing stratum V2 for ckpool and want to conduct an experiment to see how much demand there is for the protocol. This required a vast chunk of code in ckpool and I'd like to gauge what level of interest there is for supporting the protocol. If you are running an SV2 compatible miner, or have an SV2 proxy, and mining on solo ckpool, I'd appreciate testing of the implementation. This being experimental means it will likely not be a permanent setup, nor have guaranteed uptime whilst improvements/fixes are committed.
It's worth pointing out that although SV2 offers encrypted communications, privacy, protection against MiTM attacks, and some trivial decrease in bandwidth, adding an SV2 proxy at the client end adds latency compared to regular stratum, or hardware that natively supports SV2.
Far more important to point out, though, is that despite job declaration (mine your own transactions and templates) being the main feature people are seeking with implementing SV2, it is only of meaningful benefit for a shared (i.e. non-solo) pool as it adds quite a bit of latency that can not be obviated by the pool implementation, as the protocol will make clients refuse any templates from the pool. This is despite the fact the pool hardware is going to be vastly faster at updating blocks than client level implementations. Furthermore, if you are doing job declaration at your miner end, you already have _everything you need_ to mine solo locally at the miner, so there is precisely zero point using SV2 with job declaration to a solo pool apart from feeling good about the templates - you'll just waste a lot more work, and have a significantly higher risk of stale aka orphaned blocks.
That said, the experimental code has been created, and would still be useful for a non-solo install of ckpool. I'm curious to see how many miners will try it out. SV2 suffers from a chicken-and-egg problem that hardware doesn't support it because pools don't, and pools don't because hardware doesn't.
@w_s_bitcoin Isn't the force-close presigned with fixed inputs, so you adding additional inputs would break the sig? Then that only works on the anchor bump and your sweep. For the commit tx it's back to the fee game, and a big maxmempool counters it.
Go Brrr Pool Updates merged, Version 1.2.1 is live in the @umbrel App Store. 🚀
Updates include CKpool improvements, UI fixes, and the Mempool App is now optional. If not installed, Go Brrr Pool will default to the @mempool .space API, so it's now compatible with pruned nodes.
Your phone holds more than calls and texts.
Photos, Passwords, Banking Apps...
The USB Data Blocker physically blocks the USB data lines while allowing power to pass.
-
Protect what you can control.
🔗 https://t.co/aXxvbYAbdx
#USBDataBlocker#Bitcoin#OPSEC#CryptoMachine
Can you actually leave?
We tested it on mainnet: forced a 100k sat Blink wallet out of Spark, back onto Bitcoin.
No operators, just the seed and a saved recovery bundle.
Costs, lessons, code and txIDs onchain: https://t.co/j2tPMa219S
Trust model reiterated. In-app exit next.
Honestly, I was blown away by @matthewvuk2 & @luca0x46 presentation.
After installing the Bark plugin merchant can literally accept not only Ark, but lightning payments right away!
Wishing that @secondhq keeps rocking & hoping to see more quality @BtcpayServer plugins 💪
BTC Tech Nerd Army
TNA OS Avalon Q - 95TH/1550W
Thank you @altair_tech for supporting TNA and to all the TNA members who contributed to make this happed.
BETA testing is open
If interested pop in to TNA Discord
Follow for more updates, Reverse engineering report dropping soon.