Christine D. Kim

Christine D. Kim

BTC Before Light

BTC Before Light: Issue 44 ☀️

BIP-39 native-language display wordlists

Christine D. Kim's avatar
Christine D. Kim
Jun 16, 2026
∙ Paid

Good morning,

Today, I’m discussing a small improvement to Bitcoin wallet UX that was recently raised on the Bitcoin Development mailing list.

The proposal is an opt-in wallet feature that could make bitcoin self-custody easier for non-English speakers by allowing users to view and input BIP-39 recovery phrases in their native language, while preserving compatibility with the standard English BIP-39 flow.

Even though consensus on larger changes to Bitcoin, such as quantum security, remains elusive, work continues in other ways to make Bitcoin more accessible, usable, and safe for a global audience.

Let’s get into it.

Yours truly,

Christine D. Kim


⏱️Core Release Schedule

First, a quick overview of Bitcoin Core’s software release schedule and the status of the next major release:

Latest Stable Major Release: Bitcoin Core 31.0

  • Release Date: April 20, 2026

Upcoming Major Release: Bitcoin Core 32.0

  • Target Release Date: October 10, 2026

  • Open issues: 22

  • Closed issues: 35

  • Milestone progress: 61%

Last week’s snapshot showed 22 open issues, 32 closed, and a 59% milestone progress.


🖊️ Meeting Log

An overview of the Bitcoin Core developers meeting that took place last Thursday, June 11, 2026, sourced from Internet Relay Chat (IRC) logs recorded by Chaincode Labs.

Issues

Descriptions of bugs and areas for improvement in Bitcoin Core and their respective status:

Open

  • Bitcoin/bitcoin, Issue #35457—Partial IBD speed regression between 9c150222604478431669b66b2caa0d75e8324d4c and 1ea532e590cdc16b86436a2bc4f92d74082307f9

Closed

  • Bitcoin-core/meta, Issue #46—Clarifying Moderation Policies for External Behavior

Pull Requests (PRs)

Proposed code changes to Bitcoin Core and their respective status:

Work-in-progress

  • Bitcoin/bitcoin, PR #35465—coins: compact chainstate regularly after post-IBD flushes

Ready for review

  • Bitcoin/bitcoin, PR #35295—validation: fetch block input prevouts in parallel during ConnectBlock

  • Bitcoin/bitcoin, PR #35465—coins: compact chainstate regularly

Merged

  • Bitcoin-core/bitcoin-core.org, PR #1255—posts: add notice about private broadcast IP leak in 31.0


🌟 PR Spotlight

PR #1255

Category: Bitcoin-core/bitcoin-core.org, the source code for the Bitcoin Core project website.

Title: “posts: add notice about private broadcast IP leak in 31.0”

Author: “andrewtoth”

Status: Merged

Date opened: June 6, 2026

Most recent update: June 11, 2026

What it does: PR #1255 adds a notice to the Bitcoin Core website warning users about a privacy bug in Bitcoin Core 31.0’s new privatebroadcast feature. The notice explains that, under specific network conditions, a transaction broadcast using sendrawtransaction may fall back from a Tor-routed v2 connection to a direct v1 IPv4/IPv6 connection, potentially revealing the sender’s IP address to the receiving peer. A fix is expected in Bitcoin Core 31.1, and the notice gives affected users temporary workarounds.

A more detailed explanation of the bug can be read in this BTC Before Light newsletter.

Why it matters: The bug is not a funds-at-risk issue, but it is important for a narrow set of users who rely on Bitcoin Core v31 to hide their IP address when transacting on Bitcoin.

Last Thursday, developers discussed whether to publicly disclose the bug before a fix is released in Bitcoin Core v31.1. Because the issue had already been discussed publicly at a prior Bitcoin Core developers meeting, developers agreed to publish a formal notice on the Bitcoin Core website and provide temporary workarounds for affected users until the fix is ready.

The discussions about how to properly disclose the bug highlight a recurring tension in open-source software development between transparency and user safety. Because publicly disclosed bugs can be exploited before a fix is available, developers tend to be cautious about discussing and announcing vulnerabilities too early.

In this case, because the bug had already been publicly discussed, it did not put funds at risk, and affected only a limited set of users, developers prioritized alerting users of the privacy risks in v31 as widely as possible ahead of the formal fix.


☁️ That’s all for my summary of Bitcoin Core development. Continue reading for my insights. To read the rest of the newsletter, make sure you are signed up for a premium subscription:

⛅ Interested in being a featured sponsor of this newsletter? Learn more about sponsorship opportunities available for BTC Before Light:

☀️ I also run a research and advisory firm called Protocol Watch for businesses building on Bitcoin and Ethereum. Learn more about how I can help your business understand and stay ahead of protocol changes:

Protocol Watch


🧭 Insights

A new discussion on the Bitcoin Development mailing list highlights a small but potentially useful effort to make Bitcoin wallets easier to use for non-English speakers.

User's avatar

Continue reading this post for free, courtesy of Christine D. Kim.

Or purchase a paid subscription.
© 2026 Christine D. Kim · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture