Satoshi Scoop Weekly, 16 May 2025
🍨 Your weekly bite of the latest updates from the Bitcoin ecosystem!

Search for a command to run...
🍨 Your weekly bite of the latest updates from the Bitcoin ecosystem!

No comments yet. Be the first to comment.
Take a bite out of the latest weekly updates in the Bitcoin ecosystem. We've got the scoop on what's cooking in the blockchain kitchen. All things #POW and #UTXO.
🍨 不可错过的每周比特币生态深度速览
🍨 Your weekly bite of the latest updates from the Bitcoin tech ecosystem!

🍨 不可错过的每周比特币技术生态速览

🍨 Your weekly bite of the latest updates from the Bitcoin tech ecosystem!

🍨 不可错过的每周比特币技术生态速览

🍨 Your weekly bite of the latest updates from the Bitcoin tech ecosystem!

On this page
Bitcoin developer Ruben Somsen mentioned that while researching SwiftSync (a method to accelerate Bitcoin node synchronization; see next item for details), he discovered a theoretical consensus vulnerability in BIP. BIP30 was designed to prevent duplicate transaction IDs from creating inconsistencies in the UTXO set by invalidating blocks that contain outputs already present in the UTXO set. However, it makes exceptions for certain anomalous coinbase transactions from 2010 (the Coinbase TxIDs in blocks 91722 and 91812 are duplicates) which may cause node state inconsistencies or even forks under extreme block reorganizations. Although current checkpoint mechanisms prevent such reorganizations, removing checkpoints in the future might reintroduce the issue. Additionally, BIP30’s approach to checking the entire UTXO set is inefficient, hindering implementations of new technologies like SwiftSync, Utreexo, and zero-knowledge proofs.
The current Bitcoin Core validation requires these steps: sequentially traversing the blockchain while performing context-independent checks, adding outputs to the UTXO set, and removing spent outputs. Typically, the UTXO set cannot fit in memory, causing further slowdown due to disk I/O.
SwiftSync introduced by Ruben Somsen brings a near-stateless, fully parallelizable validation method that uses hints about which outputs remain unspent. This approach eliminates the need for database lookups during validation, drastically reducing memory usage to near zero and enabling full parallelization of validation steps. As a result, memory, disk I/O, and single-thread performanceCPU performance are removed. The new bottlenecks become CPU power and network bandwidth, meaning validation speed scales with better hardware and connectivity.
Bitcoin Core contributor Ava Chow explained OP_RETURN’s 12-year history in a live stream. Key points are summarized in this overview by Claude 3.7.

Antoine Poinsot recommends removing OP_RETURN limits, arguing they neither effectively prevent abuse nor provide full visibility into all transactions for node operators, thus harming network efficiency.
BitMEX argues that images or other non-financial data stored on Bitcoin shouldn’t be broadly categorized as spam. Only provocative or intentionally harmful content qualifies as spam, but storing images for profit or entertainment is not. The economic reality is that miners are incentivized to produce the most profitable blocks, and if users pay higher fees for transactions containing “junk” data, miners will include them. Blockchain is already heavily used for images, so OP_RETURN limits won’t change that.
Given recent “out of control” commentary on OP_RETURN, Bitcoin Core’s Matthew Zipkin suggests introducing a new procedural step for policy changes. The biggest problem was many users first hearing about this on Twitter rather than participating in initial mailing list discussions, making them feel disenfranchised and triggering uninformed, repetitive debates. Matthew Zipkin proposes adding an intermediate step between mailing list discussion and GitHub pull request to bridge the gap and improve community engagement and feedback quality while reducing misunderstandings.
This article discusses fundamental problems with the Bitcoin mining protocol Stratum v1 and calls for a community-wide shift to the more secure, decentralized DATUM or Stratum v2.
The author argues that Stratum v1’s architecture leads to centralized mining where “miners” merely provide hash power, but block construction and transaction ordering are controlled by separate “node runners.” They run nodes to verify their payments but do not contribute CPU to securing chain integrity. They make up the absolute majority of today’s Bitcoin nodes, contradicting Satoshi’s envisioned decentralized lottery-like mining.
In the context of recent OP_RETURN debates, the author contends that protocol-level changes (like adopting DATUM or Stratum v2) are a more fundamental solution to centralization than any spam-filtering policy.

The Bitcoin community swimming in a centralized Stratum v1 mempool, blissfully unaware of the chemicals in the water.
Following.space is a new Nostr tool addressing a major pain point of the protocol: finding people worth following in the absence of an algorithm. Now users can directly follow “Follow Packs” (curated follow lists) created by others or create, curate, and share their own custom follow lists.
Coinbase Developer Platform introduced the x402 open protocol, a payment protocol that enables instant stablecoin payments directly over HTTP. Built on the HTTP 402 “Payment Required” status code, it creates a native web payment layer allowing websites and applications to request immediate payments from users or AI clients-without requiring API keys, logins, or credit cards. This simplifies payments and improves efficiency. It supports multiple blockchains and stablecoins like USDC. The protocol is open-source on GitHub.
Unlike many other cryptography conferences that publish peer-reviewed papers, the Real World Crypto (RWC) 2025 conference features talks showcasing the most interesting research papers and industry projects. The 3-day event included 46 talks covering nearly all cryptography topics, including encrypted messaging, TLS and Web PKI, and advances in post-quantum cryptography.
a16z’s Field Notes highlights themes such as:
Using zero-knowledge proofs for identity systems
Attacks on zero-knowledge proof systems
Implementing cryptography with deep neural networks
Apple’s large-scale deployment of homomorphic encryption in real products
Security and liveness are classical security properties of consensus protocols. Recent research introduced “accountability” to strengthen security: if security is violated, it can prove that a sizable fraction of adversarial nodes misbehaved. However, accountability for liveness remains underexplored. This paper investigates to what extent liveness can also be made accountable.
Read the full paper.
An article highlights Asia as a hotspot for Bitcoin adoption, with different countries embracing Bitcoin uniquely—from institutional investors in Singapore, grassroots adoption in Indonesia, to Vietnam’s strong P2P usage for daily transactions and remittances— a diverse picture of Asia’s Bitcoin ecosystem driven by innovation, regulation, and community.