There are few feelings like waiting 119 years to win a trophy. A true fairy tail incluing twice heartbreak, creation of the devil, and coming back from a 9-0 defeat. Well done Crystal Palace!

"A perfectly valid alternative to this would be to cut all aid to Gaza and just wait for the population to starve to death." No. It's not. View quoted note →

What if sending a payment was as easy and as fast as sending a nostr note?

Potential weaknesses in the argument pushing for change in the standardness rules: View quoted note →

#mindstr summarize the latest commentary on OP_RETURN debate by proposers

Folks are sleeping on how good, open-source AI Qwen 32B is. It made this in ONE SECOND!

Outstanding! Trust the community. #bitcoin

Core VS Knots: Health Battle!

Bitcoin Core vs. Bitcoin Knots repository health comparison - Arcade Style!

If we had someone who could act as an honest Oracle, we could make an AMM for this event on nostr using digital signatures, and on-chain commitments. People could bet on the team of their choice, and the odds would adjust according to how much is staked. At the end the contract pays out to all the bets made. However, you you need someone impartial to report the winner of the tournament. If the wrong winner is called the funds would go to the wrong place. View quoted note →

#agenticnostr powered by did-nostr

Try this (view source):

nostream

View quoted note →

Stating the obvious. Bitcoin is a financial network, not a general-purpose data store. Storing large files like images directly on-chain is inefficient and a form of spam. A better pattern is to store a small pointer on-chain (e.g., CID) and host the file off-chain ... via IPFS, torrents, Blossom, or other distributed systems. Using block space responsibly helps preserve Bitcoin's long-term utility. Storing large files directly should be discouraged.

"And since only about 18% of the hashing power seems to mine them, they had to wait 5-6x longer to confirm" Excellent point! Lower that number down from 18% and lower the spam. View quoted note →

Just scored 11 points in Nostr Snake! 🐍⚡ #NostrSnakeScore Play at

Nostr Snake - A Retro Game on Nostr Protocol

Play the classic Snake game powered by Nostr protocol. Challenge your friends and compete on the global leaderboard.

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 →

During the last civil war, the “more-change” faction vowed to push ahead no matter what anyone said. UASF was a big factor, but what really stopped them was skin in the game: futures markets showed they’d lose a lot of money if they followed through. Seeing those numbers, they backed down and chose to delay. Postponing a proposal doesn’t kill it. it just gives everyone breathing room.

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