Hi Insiders. This is Tuma, open-source reporter from the Insider Edition.
In this week’s update we feature Nut November, the month-long hackathon of the Cashu ecosystem coming back for the second edition.
We also cover several news from the Bitcoin ecosystem. A new BTCPay Server vulnerability has been discovered, Fedimint is experimenting with the Ark protocol through Bark, Librería de Satoshi is rebranding to ISMOS, and the updated security policy in Bitcoin Core.
#
Highlights from the Bitcoin developer ecosystem
I spent 10+ hours in open-source developer calls in the Bitcoin ecosystem last week. Here is what caught my eye:
- Nut November — the month-long hackathon of the Cashu ecosystem — comes back for its second edition.
- During the monthly call, on Thursday 29th, Cashu developers announced the second edition of Nut November, a month-long hackathon focused on Cashu.
- The event features 6 different prizes. Other than the best overall, developers can participate to win a prize for the most difficult technical challenge, the craziest experiment, the best design, and the best tool for value4value. A special prize will also be awarded to first-time contributors to the Cashu ecosystem.
- At the time of writing, the prize-pool amounts to more than 1 milion sats. It is possible to contribute directly to the pool on the hackathon website.
A BIPs Update
In the last days there was some movement in the BIP repository. Specifically, one new BIP has been assigned a number by BIP maintainer Murchandamus.
Numbered BIPs#
A list of recently published BIPs
BIP333: BIP324 One-Byte Message Type ID Alias Assignment#
Assigned On: October 28th, 2026
Layer: Peer Services
PR2301 introduces BIP333, which defines a new set324alias message that permits peers using BIP324 — version 2 of the P2P encrypted transport protocol — to assign one-byte message type ID aliases to improve bandwidth usage for their outbound messages. BIP324 assigns one-byte IDs via a fixed table, requiring centralized coordination and introducing risks of conflicts. This new proposal allows peers to choose their own one-byte IDs at runtime for their own outgoing messages.
Other News from the Bitcoin World
BTCPay Server Vulnerability: On Sunday, November 1st, the BTCPay Server team warned users that they were receiving reports of hot wallets being drained. The team recommended to shut down instances to prevent loss of funds
- The vulnerability was confirmed this morning, November 2nd. The BTCPay Server team identified an attack vector targeting instances of the software running versions v2.4.1 and older. At the time of writing, no details about the vulnerability were released.
- According to the team, users running v2.4.7 — the latest release — seems not to be affected by the vulnerability, since no credible report has been produced. The team recommends keeping instances up-to-date with the latest security releases.
Fedimint <> Bark: Fedimint creator Eric Sirion published a video demoing a Fedimint Lightning Gateway based on Bark — the Ark implementation by Second.
- A Federation usually needs to run a Lightning Node to connect its users to the Lightning Network. This experiment demonstrated the possibility to run a Federation’s Gateway based on a simple Ark wallet.
Librería de Satoshi is now ISMOS: From the largest technical education organization focused on teaching Bitcoin to Spanish-speaking individuals, Librería de Satoshi is evolving into a global, full developer pipeline that aims to bootstrap careers in the freedom tech and open-source as ecosystem, called ISMOS. Check out my latest article about ISMOS.
Security policy update in Bitcoin Core: Following the wave of LLM-assisted vulnerability reports, Bitcoin Core developers decided to update the security policy of the reference implementation.
- The update covers those vulnerabilities that are deemed “easily discoverable” thanks to the help of LLM-assisted tools. For this specific case, security patches will be releases as soon as possible and the fix backported to any maintained version.
- The new rule has already been applied. Three vulnerabilities have been fixed and disclosed right away — namely PR3665, PR36667, and PR36669. Since these fixes have been merged after v32.0 had already been tagged, the major release was never published. Instead, v32.1 — containing those fixes — has been officially published this week.
More from BTC++ Insider Edition
News Hour#
- BTC++ News Hour: Check out our Friday livestream, where Matthew Vuk and I discuss the most interesting news of the week from the Bitcoin developer ecosystem. This time, we hosted Dulce Villarreal to discuss the recent rebranding of Librería de Satoshi to ISMOS.
Videos#
- James Pierog — BTC++ Insider Interviews: James Pierog — co-founder and CEO of Glimpse — talks to the Insider about the motivations behind building a prediction market on Bitcoin.
- Jesse Shrader — BTC++ Insider Interviews: Jesse Shrader — Amboss co-founder — explains to the Insider why he believes embracing stablecoins can benefit Bitcoin and the Lightning Network, and why he’s excited about Wavelength.
- Dario Nakamoto — BTC++ Insider Interviews: Dario Nakamoto of Lightning Labs explains to the Insider how Wavelength works and how VTXOs carry Taproot Assets, secured by the Ark policy tree.
- Alessandro Grasso — BTC++ Insider Interviews: Alessandro Grasso — Career Service Specialist of Blox Space — talks to the Insider about how the Turin hub channels the city’s Bitcoin ecosystem by connecting local talent with the companies hiring them.
- Birk — BTC++ Insider Interviews: Birk — COO of the RGB Association — explains to the Insider how RGB brings digital assets and private contracts to Bitcoin through client-side validation and off-chain, UTXO-based transfers.
- Dario Zeugmaster— BTC++ Insider Interviews: Cashu developer Dario demos live to the Insider tap-to-pay UX on Nucula: open hardware for “everything that used to have a coin slot.” Vending machines, laundromats, ticketing.
Articles#
Looking for an opportunity to join up with some bitcoin devs in person? Join us in Seoul this November 5-6 to talk about privacy in Bitcoin!
Comments
No comments yet. Start the conversation.