Jan b

[Jan b @_jan__b]

@elonmusk Does it come with a person splitting laser ?

[International Cyber Digest @IntCyberDigest]

🚨 BREAKING: More than 400 Arch Linux User Repository packages have been compromised with infostealer malware and a rootkit.

Attacker posed as a trusted maintainer and "adopted" orphaned packages.

Arch maintainers are purging infected packages now. Audit your AUR installs.

[Bitcoin Core Project @bitcoincoreorg]

We have become aware of a privacy bug in the -privatebroadcast feature, newly introduced in Bitcoin Core 31.0, that may cause the originator’s IP address to be revealed to the receiving peer under certain network conditions. A fix is forthcoming and will be released with 31.1.

[Jan b @_jan__b]

PurpleKarrot makes a good point (imho) to drop BlockTreeEntry from Bitcoin kernel api.
https://t.co/3Yqu11WKj0

[Mike Schmidt @bitschmidty]

sedited (@sedited_), Bitcoin Kernel developer and Bitcoin Core maintainer, blog post on validation logic in Bitcoin Core:

"Block validation logic in Bitcoin Core is surprisingly complex. After more than a decade of engineering towards improving performance, Bitcoin Core has accumulated many caching layers, sub-steps, and optimizations before the node even calls the script interpreter. In the following, I’ll describe in broad strokes what these are, first roughly describing what validation is done in which order, then explaining why it was implemented in the way it is and the tradeoffs involved"...

https://t.co/uffITGS7Wu

[Jan b @_jan__b]

@evoskuil Interesting point of view ! Is the “kernel” project, to have a consensus library, than something positive (in the sense to build other nodes on) or are the different impl the way to “guard” consensus?

[Jan b @_jan__b]

@evoskuil Not what I meant, but I get what you are saying.

[Jan b @_jan__b]

@evoskuil But Libbitcoin is bug compatible on consensus level with core, right ? (Validates with the same bugs, as they now are part of consensus)

[Rene Pickhardt @renepickhardt]

Today is a sad day for the Lightning Network community as one of our very respected developers is moving on to new ventures.

At the same time, I am delighted that I had the opportunity to collaborate with @rusty_twit and learn so much from him. In any case, I wish him well!

[l0rinc @L0RINC]

4-10% script validation speedup by forcing a few inlines: https://t.co/a9Z1plsByt

[Mike Schmidt @bitschmidty]

Apple on their open-source tools for formal verification

"Deploying this new generation of algorithms at scale across all Apple platforms requires high assurance, so we developed rigorous new formal verification methods to prove the mathematical correctness of our implementation."

"The practical considerations are more complicated. Regardless of how it’s applied, formal verification requires a tremendous investment of time and deep expertise."

https://t.co/JmFAnRp6rx

[Jan b @_jan__b]

@0xB10C Cool ! (and funny that the produced binary can’t be used on nix)

[b10c @0xB10C]

I never thought this would be possible, but:

I built a bitcoind binary with Nix that is bit-by-bit identical to the Bitcoin Core v31.0 Guix-built release binary for x86_64-pc-linux-gnu. Big win for reproducible builds across different toolchains.

https://t.co/Ff1g6U8Hf9

[Mike Schmidt @bitschmidty]

Earlier this month, many Bitcoin Core developers met up in Barcelona, Spain as part of their regular twice-yearly in person meetings.

Attendees volunteered to take notes on the unconference-style sessions and the transcripts have been added to the BTC transcripts website:

- AI session
- ASMap
- BIP324 and group policy options
- BIPs editors
- Bitcoin TUI
- CAmount
- CDash
- Coins cache
- Erlay redesign
- External interfaces
- GUI repo
- Inventory send queue
- Kernel (laundry list, overview, session)
- Libevent
- Logging
- Modern crypto library
- Mutation testing
- Package relay
- Post-cluster mempool
- Private broadcast
- QML (planning, update)
- Silent payments
- Static builds
- SwiftSync
- TCP hole punching
- Template hash

Additional informal discussions, code reviews, working groups, or other sessions occurred on:

- Quantum
- Determinism in testing
- Testnet5
- MEVPool
- Wallet priorities
- Silent payments
- Coins caching
- Peer observer
- ASMap updates
- IPC updates
- Utility binaries
- Bitcoin Kernel
- QML GUI
- Deterministic simulation testing
- AI assisted code review
- BIP39 import
- BIP54
- Fuzz testing
- Mutation testing
- Static builds
- FIBRE updates
- Parallel block input fetching

https://t.co/Qr6UUz21Cg

[Stacker News @stacker_news]

📣 AMA ANNOUNCEMENT: Mike Schmidt, co-founder and executive director at Brink

by Scoresby in ~bitcoin, ~AMA
340 sats and 3 comments so far

https://t.co/vVyhEawR6i

[Antoine Poinsot @darosior]

I advanced BIP 54 status to Complete.

[Sparrow Wallet 🐦 @SparrowWallet]

Sparrow v2.5.0 released with:

Silent Payments (SP) wallets
SP-capable Frigate public server @2140_dev
https://t.co/C7r0pfBGD5 fee rates source

https://t.co/HOEwliSIRd

[The more things change.... @GKBoris]

Belasting betalen over geld dat je nog niet verdiend hebt, is absurd.

De @EersteKamer wacht een simpele IQ test. Ik heb er helaas weinig vertrouwen in dat ze zullen slagen.

#box3

[Jan b @_jan__b]

@levelsio Also, do not drink the coffee and tea onboard

[grsecurity @grsecurity]

Exploits are now appearing targeting pidfd, which is forced into all Linux kernels since 5.10 (2020), no module or initcall to blacklist this time, must patch ASAP!