Nostr + Bitcoin: Built-in Time Boxing 1. Your npub is a BTC address. 2. Pay npub (event hash in tx) -> means NOT-BEFORE block time. 3. Spend output -> means NOT-AFTER block time. Now Events are time-boxed between two blocks. It turns out that this is all you need to solve the double-spend problem. And hence to unlock smart social contracts.

"life is not black or white, and fastening your seatbelt when driving a car is safer even though some people die in car crashes" I remain a huge fan of bitcoin core. It is one of the most successful projects in the history of open source. But it got where it is by listening to the community. Controversial PRs, should not be merged too quickly. Bitcoin benefits enormously from stability. View quoted note →

375 down votes! The community has spoken. Do not merge, at least not in version 30. Push it out until version 31, if needs be, so that there is time to discuss. Everyone wins.

GitHub

Remove arbitrary limits on OP_Return (datacarrier) outputs by petertodd · Pull Request #32359 · bitcoin/bitcoin

As per recent bitcoindev mailing list discussion. Also removes the code to enforce those limits, including the -datacarrier and -datacarriersize co...

Designing yet another #testnet4 faucet

Satoshi knew

This is better than I expected. Someone should port it to nostr ASAP.

x402 - Payment Required

x402 is the internet's payment standard for agentic payments at scale.

#mindstr give me an update on the OP_RETURN debate on 20250505

With did-nostr you can have private direct messages that do not leak meta data.

3 questions: 1. What are the most important problems in your field? 2. Are you working on one of them? 3. Why not?

From 2 years ago: "I think it's unlikely that Bitcoin Core is going to make any changes in regards to OP_RETURN"

GitHub

Remove arbitrary restrictions on OP_RETURN by default by petertodd · Pull Request #28130 · bitcoin/bitcoin

Any number or size of data-carrying OP_RETURN outputs are allowed, and the -datacarrier option is removed. For those who want to limit data carryin...

"We can't stop something, therefore we should allow or enable it" is known as an appeal to futility, and it's often a subset of the either/or fallacy, also called binary thinking. It's a powerful framing shift: if you can't stop something 100%, then why bother trying at all? But the real world is messier than that. People have choices, but 80% follow defaults. Harmful behavior is possible, but not inevitable. And well-intentioned changes to working systems can have unexpected consequences. I'm a big fan of Bitcoin Core — it has brought us a long way. But no single developer always gets it right. Listening to the broader community often makes the system stronger.

#mindstr give me an update on the OP_RETURN debate

Qwen3-30B-A3B runs on NVIDIA 4090 at 100 tokens/s! It's a very good model, which will only get better. While everyone is waiting on deepseek r2 this little beauty might be all you need for consumer grade AI.