Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Socratic 33 #29

Merged
merged 11 commits into from
Apr 23, 2024
Merged

Add Socratic 33 #29

merged 11 commits into from
Apr 23, 2024

Conversation

stickies-v
Copy link
Contributor

Topics and links can be pushed directly to this branch, or added as comments/review.

Copy link

netlify bot commented Apr 16, 2024

Deploy Preview for londonbitdevs ready!

Name Link
🔨 Latest commit dde8c67
🔍 Latest deploy log https://app.netlify.com/sites/londonbitdevs/deploys/66280fcaa4ccf500080d0148
😎 Deploy Preview https://deploy-preview-29--londonbitdevs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@AngusP
Copy link
Contributor

AngusP commented Apr 21, 2024

Suggestion for Mining:

0xB10C on Nostr and other places nostr:note1qckcs4y67eyaawad96j7mxevucgygsfwxg42cvlrs22mxptrg05qtv0jz3 17th Apr 2024

Looking at the merkle branches that mining pools send to miners as part of stratum jobs, it's clear that the BTCcom pool, Binance pool, Poolin, EMCD, Rawpool, and possibly Braiins* have exactly the same template and custom transaction prioritization as AntPool.

Stratum v1 jobs include (parts of) the coinbase transaction and the merkle branches a miner needs to compute the merkle root. If all branches are equal across pools, the block template is exactly the same.

This is a smaller merkle-tree with the stratum job branches highlighted.

Here, branch0 is the txid of the first transaction in the block after the coinbase.

In the AntPool/Binance/BTCcom/.. template, it's a manually prioritized transaction paying 9.03 sat/vbyte https://mempool.space/tx/c938e8027a7fba782a092695a53d37654021bf20df71ca91b4a6daa9198b0c73

Many of the other pools didn't prioritize a transaction and included the highest feerate transaction https://mempool.space/tx/96608dc747677d6dfbc3a2b37f8a0146abae132799b13c130066bd3716fdf91a paying 301 sat/vbyte. ViaBTC prioritized another transaction and has a vastly different template.

This indicates that F2Pool currently is not using the AntPool templates, even if they share the the same custody provider. We know from multiple occasions that F2Pool has been building their own templates (https://b10c.me/o11, https://b10c.me/o9, https://b10c.me/o8)

Note that SigmaPool and SecPool both seem to share the same template (distinct from AntPools template). Two names, but probably one pool.

Some overlap in the first branches of distinct pools is expected as these branches consist of few (usually high feerate) transactions. For example, Ocean's "default" and "core" templates overlap up to branch3. At least the first 15 tx (2⁴ - 1) in the template are equal.

* similar to EMCD in the picture, Braiins sometimes differs from AntPool in the later branches of the template. This could indicate they're only helping with AntPools transaction accelerator and directly syncing with AntPools mempool, causing occasional differences in templates.

I've heard speculation about this all being liked to an FPPS partnership with AntPool/Bitmain.

Bitmain insures against bad pool luck but you have to use Bitmains templates/transaction prioritization and pay the mining reward to the insurer for later distribution.

Essentially a pool of pools and a lot of mining centralization.

@ariard
Copy link
Contributor

ariard commented Apr 21, 2024

Looking at the merkle branches that mining pools send to miners as part of stratum jobs, it's clear that the BTCcom pool, Binance pool, Poolin, EMCD, Rawpool, and possibly Braiins* have exactly the same template and custom transaction prioritization as AntPool.

Sounds good to be added if Stephan or another host wanna to present on this.

Added my topics here: ariard@213ae95

First one is “Great Consensus Cleanup Revival” on the mailing list, the other one is “Libbitcoin answer on CVE-2023-39910” (milk.sad)

We did present on milk.sad from the viewpoint of the reporter during Socratic Seminar #27, then a full-report was published by the libbitcoin open-source team just after, so I think it’s reasonable to present their viewpoint too, even if the report is months old now.

@AngusP
Copy link
Contributor

AngusP commented Apr 22, 2024

May also be worth discussing testnet reset if there is interest/opinions/questions? https://groups.google.com/g/bitcoindev/c/9bL00vRj7OU/m/ptiO3328AQAJ and bitcoin/bitcoin#29775

@stickies-v
Copy link
Contributor Author

Added your suggestion @AngusP, thanks a lot for chiming in!

Also added all the usual topics. Will push some more ad-hoc ones later today. Going to merge later tonight.

@glozow
Copy link
Contributor

glozow commented Apr 23, 2024

Added some xz links I ripped from berlin bitdevs and a couple more things. Don't have much else, thanks for putting it all together @stickies-v !

@stickies-v stickies-v force-pushed the announce-33 branch 2 times, most recently from c60f876 to a1830c2 Compare April 23, 2024 19:41
@stickies-v stickies-v merged commit a8daaff into londonbitdevs:main Apr 23, 2024
4 checks passed
@stickies-v stickies-v deleted the announce-33 branch April 23, 2024 19:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants