Miners, take a look at this first case study, your profits might increase while using @StratumV2.
Provide your feedback, and join us in the mission of innovating the Bitcoin mining space.
We are a FOSS project, and we cannot make it without your help and support ⛏
🚀New Case Study: How SV2 Increases Mining Profits by at least 7.4% improving:
📊Share Acceptance
🟩Block change latency
🧑🏭Job latency
⬛️Block propagation
🥷Hashrate hijacking
A community research with many contributors led by @HashlabsMining @DEMAND_POOL and SRI.
🔗Link 👇
ESP-Miner v2.14.0b4 for #Bitaxe is released. If all is well this is the final beta for v2.14.0.
The list of changes is long:
* Stratum V2
* Dashboard powered by websockets
* Improved testnet/regtest support
* The infamous Bitmain register 10 for nonce search space control
@oomahq@asanoha_gold@CobraBcash@ocean_mining On the specs there's also defined the so called "COINBASE_ONLY" mode, where the miner doesn't send any tx data to the Pool.
In order to make this sound though, as we wrote on the specs, we might need a specific ZK proof which proofs to the pool the validity of the template.
@oomahq@asanoha_gold@CobraBcash@ocean_mining +1 :)
That's exactly what I wrote here: https://t.co/GbM6xufQbq
And that's also the reason why Sv2 specs has the OPTIONAL `DeclareMiningJob` message, which has always been used for propaganda against Sv2. The reason for it has always been to avoid these attack risks instead.
@asanoha_gold@CobraBcash@ocean_mining Assuming the template generated by the miner is always valid is a good assumption.
If you want to be ready (as a pool) for possible invalid-templates attacks, you have to know the txs list, to fully validate every share.
That's the reason why Sv2 has an OPTIONAL message for it.
@asanoha_gold@CobraBcash@ocean_mining Assuming the template generated by the miner is always valid is a good assumption.
If you want to be ready (as a pool) for possible invalid-templates attacks, you have to know the txs list, to fully validate every share.
That's the reason why Sv2 has an OPTIONAL message for it.
@asanoha_gold@CobraBcash@ocean_mining How can a pool verify that a miner is working on a consensus valid template without knowing the full txs list's data?
Se non puoi venire al @BitcareForum, non temere. Stream SPACE di Atlas21, direttamente dal Teatro Clerici di Brescia.
Un menù di 6 ore di talk in live streaming condotte da @federico_rivi, @marcocostanza_ e @Plak_btc con le voci più interessanti del panorama Bitcoin italiano. Si parte alle 10:40, fino alle 17:30.
Se ci sarai, passa a fare un saluto!
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.
⛏️ Un bel segnale da parte delle più grandi mining pool!
Il gruppo di lavoro @StratumV2 annuncia l'adesione di 7 aziende per lavorare all'adozione del protocollo che protegge Bitcoin da uno dei suoi grandi problemi: la centralizzazione del mining.
🎙️ Nell'ultimo episodio!
👇
@oomahq@LukeDashjr@MarkOfBitcoin@GrassFedBitcoin@wk057 This description is about our (SRI) current JDC (Job Declarator Client).
As I told you in the other comment, in theory you can do JD even without using TD (Template Distribution) at all, if you want.
In that case you'd lose the benefits of TD, but it's technically doable.
@oomahq@LukeDashjr@MarkOfBitcoin@GrassFedBitcoin@wk057 Basically if you want to use the IPC mining interface, you need to run Bitcoin Core v30+, because it has been introduced there.
Otherwise you can have any TDP server which gives you templates (and the other TDP messages) over TCP.
@LukeDashjr@MarkOfBitcoin@GrassFedBitcoin@wk057 Our JDC (Job Declarator Client) supports both direct IPC connection with the node (that's why you need v30+ of Bitcoin Core) and TDP (Template Distribution Protocol) over TCP.
To make it work with Knots, for example, you could both add IPC mining interface or TDP in Knots.
@oomahq@LukeDashjr@MarkOfBitcoin@GrassFedBitcoin@wk057 Of course it is, the Sv2 protocol specification has always been modular in order to allow for multiple combinations, based on the specific needs of a specific implementation.
You can use JD protocol without having to use TD (Template Distribution) if you really want.