RT @fanquake:

RT @bitcoinoptech: Gloria Zhao (@glozow) and Mike Schmidt (@bitschmidty) were joined by Tadge Dryja (@tdryja) and Anthony Towns (@ajtowns)….

Blahblah higher block relay latency. It means:.- more stale blocks, hurting all miners but especially smaller ones.- more reorgs, making payment confirmation more difficult.

RT @mononautical: Version 3 transaction adoption is starting to take off, just 10 months after being standardized in Bitcoin Core v28.0 htt….

RT @bitcoinoptech: Improve TxOrphanage denial of service bounds is a PR by @glozow that changes TxOrphanage eviction logic to guarantee eac….

RT @bitcoincoreorg: Bitcoin Core v28.2 was released!.It is available from: Release notes:

RT @dergoegge: Fuzzamoto just found its first bug on a Bitcoin Core PR🐛

Hosting a meeting today to Save The (Transaction) Orphans from churn and make 1p1c package relay more reliable! Please join us if you're into nerdy shit like:.- Defining a memory and CPU usage score to identify our DoSiest peers.- Attempting to ensure each peer has some.

RT @theinstagibbs: 🫡 also looks like truc/P2A/ephemeral dust is being supported by a number of mining pools .

RT @ChaincodeLabs: Nominations are open for the 2025 Bitcoin Research Prize!. Submit papers that made an impact on Bitcoin or Lightning pub….

Reminiscing about the "Brink has too many maintainers" days. The memes now are more creative though.

RT @coincenter: Update on the Blockchain Regulatory Certainty Act: . A joint statement with @btcpolicyorg @blockchainassn @coincenter @cryp….

A comment on whether this process was “rushed”. As someone who has both authored and merged mempool policy changes for the last 4 years, I’d say this is par for the course. - The original PR was discussed around 2 years ago (of course, echoing arguments that were made 10 years.

Link to the merge post: . @achow101 also reviewed this PR as a 5h livestream 2 years ago, I also wrote a summary for why #28408 should not be merged. It is similar: If you are interested in the PR review.

I posted a full writeup for the #32406 merge decision on the PR. These changes go into effect in v30, which is scheduled for release in October. The PR changes the defalt value of -datacarriersize. You will still be able to use -datacarrier and -datacarriersize options in v30,.

There have been a number demands that Bitcoin Core use transaction relay policy to prevent certain kinds of transactions from being mined based on use case. This idea has been controversial for various reasons, including:.- Bitcoin Core is a completely voluntary piece of software.

RT @bitcoincoreorg: A statement on Bitcoin Core development and transaction relay policy -

RT @ChaincodeLabs: Is Bitcoin ready for the quantum era?. Read our report at:. @ClaraShik & @ozdeadman explore the….

In case it wasn't already clear, this suggestion is the only PR that is open at the moment. #32406 changes the default -datacarriersize and leaves the config option intact.

Generally, it is resource intensive and unreasonable to demand a full refutation each time Luke makes an accusation against Core, and I'm not going to make this a regular thing. Instead, I request that everybody ask *him* to provide evidence when he makes claims.