Most pro110 miners are renting rigs from sites that don't accept bip110 coins. Those pro110 miners can only keep mining if they maintain a reserve of non110 coins, to pay with those. That means the most economically significant pro110ers will still be supporting the non110 chain!

Here's something that interests me about the coldcard bug: it had 2 random number generators. The "bad" one was seeded with data including keypresses, the timestamp, and the device id. I can understand that, it's probably how I would seed it. What was the "good" one seeded with?

Another piece of LN infrastructure goes down this week:

ZEUS Blog

Security Update - August 5th, 2026

UPDATE (Aug. 8, 2026) Our primary Lightning node, Olympus by ZEUS, is back online. Users whose channels were not closed during the security incid...

Last year the US government sent a bailout to Argentina. Now it is apparently sending a bailout to Japan:

CNBC

U.S. Treasury intervenes to support yen after Japan steps in, FT reports

It was Washington's first yen-buying intervention with Tokyo in more than a decade as it languishes near 40-year lows.

View quoted note →

A bittersweet day approaches. In this, the last period before mandatory bip110 signaling, there are so few blocks left that even if bip110ers mined them all, they would still fail to achieve 55%. So they will fork off in 1018 blocks. Come back with a better proposal than bip110.

This cool new block explorer emphasizes the data footprint of various transactions, especially the difference segwit made: beta.satoshi.space H/t x.com/uanbtc

I think this news indicates that one aspect of the marketing by Ocean Pool and DMND Pool has been effective. Namely, enough hashers want a say in how the blocks they produce look, that older pools are trying to find ways to give them that say, lest they go to pools that offer it.

X (formerly Twitter)

Bitcoin News (@BitcoinNewsCom) on X

FOUNDRY ASKS MINERS TO VOTE ON BIP-110 SIGNALING Foundry USA Pool has begun asking its mining customers how the pool should signal on BIP-110. Ac...

I would love it if a web wallet similar to coinos allowed me to give it a list of N preimages and have it create the next N lightning invoices using those preimages. This would allow me to make a digital downloads store that has no backend logic. I could upload files to my server that are encrypted with a certain key, and then use the web wallet to sell users "secret" preimages which, when added to a corresponding "public" string, create the decryption key. The logic could therefore all be done on the frontend: show the user an invoice, check if it is paid via the web wallet's api, get the preimage, construct the decryption key, and give the user their now-decrypted file. Thus the server for a webstore could be a simple file storage system, such as Github Pages, and all the logic could be done on the the frontend, except for the delivery of the secret, which is done by the web wallet, in a way that the frontend can detect.

I would love it if a web wallet similar to coinos allowed me to give it a list of N preimages and have it create the next N lightning invoices using those preimages. This would allow me to make a digital downloads store that has no backend logic. I could upload files to my server that are encrypted with a certain key, and then use the web wallet to sell users "secret" preimages which, when added to a corresponding "public" string, create the decryption key. The logic can therefore all be done on the frontend: show the user an invoice, check if it is paid via the web wallet's api, get the preimage, construct the decryption key, and give the user their now-decrypted file. Thus the server for a webstore could be a simple file storage system, such as GitHub pages, and all the logic could be done on the frontend, except for the delivery of the secret, which is done by the web wallet, in a way that the frontend can detect.

BIP110 reached 1% of hashrate today. 18/(1743+18) = 0.0102 I recommend reviewing my URSF110 proposal:

GitHub

GitHub - supertestnet/URSF-110: A POC app for using bitcoind's "invalidateblock" command to reject BIP110

A POC app for using bitcoind's "invalidateblock" command to reject BIP110 - supertestnet/URSF-110

Today I noticed this in the original LN whitepaper: "A Funding Transaction may have multiple outputs with multiple Commitment Transactions...[One output could] requir[e] additional signatures from security services." The first sentence suggests the possibility of batch txs for opening channels, and the second sentence suggests the possibility of multiparty channels. Those are both ways to scale up lightning usage beyond just "raise the block size." Not only can several users share a funding tx, they can also share an *output* in that tx. Source: https://lightning.network/lightning-network-paper.pdf",

Chris has done a good thing, and has made honest his list of economic nodes in favor of bip110. Review it here:

v0 App

Created with v0

X (formerly Twitter)

Chris Guida | ⚡🪢 BIP110 (@cguida6) on X

@SuperTestnet @BitcoinScoresby Ugh. No it isn't lol Anyway the list is updated now

Very cool View quoted note →

Today the BIP110 people made a list of economically significant people and groups who currently support or plan to support bip110. Such a list is definitely useful. Sadly it looks like this one is largely a bunch of made up nonsense. Review the list here: v0-bitcoin-companies-table.vercel.app

Possibly the biggest news of the last five years, imo: Lightning Dev Kit might have just fixed the lightning problem where your payment fails if the recipient is offline. They not only have a protocol spec, but code + a guide for adding support in wallets:

Async Payments: Getting Paid While Your Node Is Offline | Lightning Dev Kit Documentation

Async payments let an often-offline node receive Lightning payments without trusting a custodian and without locking up network capacity with long-...