@OGBTC@btchashpool malicious miners could lie about having a small hashrate, then spam/DoS pool with a lot of low-diff shares
vardiff doesn't prevent that from happening, but allows systems to self-correct over time
I encounter a lot of confusion about Sv2 from the open source mining community. I usually talk about encryption, efficiency, template submission. People's eyes glaze over and I lose them.
Let's back it up. Perhaps the most important property of Sv2 is that there is a spec. 🧵
Our fellow Vinicius has been exploring Bitcoin Core internals and just published a deep dive on what happens from the moment a transaction message reaches a node to when it enters the mempool.
If you’ve ever wanted to better understand transaction relay, validation, and mempool acceptance in Bitcoin Core, this is a great read:
From TX message to mempool
I made a new blog post: what Bitcoin Core does when a peer sends a TX message tracing the full path from message to the mempool.
https://t.co/J94ahpbjOA
Mining decentralization is a big priority for us too. We’re funding @plebhash’s work on Stratum V2, @johnnyasantos’ work on P2Pool V2, and training fellows like @jayrmotta on Mujina and @VCestarii on IPC work that interfaces with mining projects. Looking forward to collaborating with Localhost in yet another area.
I'm late to the party, but cmux is great. https://t.co/8uuStvqwcm
current split:
codex mac app: knowledege work, learning, reading
cmux + codex cli: coding
yeah maybe I should adjust my expectations
but I also can't ignore that @OpenAI + @AnthropicAI are only allowing us to use their beefy models at such low prices so they can get us hooked, and jack up the prices later
so either way, local FOSS models are the future of agentic development
@luisschwab_@karpathy deepseek4 is my new best friend, with gepeto as fallback for the heavy stuff
I'm soon gonna get some hw beef and I dream of having a purely FOSS/local workflow very soon
Great to see @StratumV2 support landing in BitAxe beta firmware.
If you want to help test it before it becomes available for everyone:
1. Download and update https://t.co/PfslKMrpgj
2. Point miner to BlitzPool or use SV2 UI.
I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.
I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).
It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.
The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.
We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.
I worry.
SRI JDC can connect to any template provider that serves Sv2 TDP
https://t.co/Yr6dfYRALQ has a working implementation (which used to be maintained by Sjors) that maintains feature-parity with Bitcoin Core v29
there's no one actively maintaining it, but I'm sure it can be used as inpiration for a Sv2-Knots port
SRI JDS depends on IPC (therefore v30+) but there's primitives for RPC alternatives
@oomahq@gitgab19@LukeDashjr@MarkOfBitcoin@GrassFedBitcoin@wk057 more specifically:
jd_server_sv2::job_declarator::job_validation::JobValidationEngine was written so you can implement an RPC-flavored engine and use it with the rest of the crate instead of v30+ IPC
https://t.co/q4eLMTING1
SRI JDC can connect to any template provider that serves Sv2 TDP
https://t.co/Yr6dfYRALQ has a working implementation (which used to be maintained by Sjors) that maintains feature-parity with Bitcoin Core v29
there's no one actively maintaining it, but I'm sure it can be used as inpiration for a Sv2-Knots port
SRI JDS depends on IPC (therefore v30+) but there's primitives for RPC alternatives