Is Bitcoin Culture Dead? | Pete Rizzo
By Danny Knowles
Aired Sep 19, 2025 · 1h 30m · Last boosted Oct 5, 2025
Chapters
Show Notes
Pete Rizzo breaks down how Bitcoin’s culture and institutions are being reshaped in 2025. From Trump’s executive orders and the creation of a strategic Bitcoin reserve to the rise of treasury companies and institutional adoption, we explore why this cycle feels different — and why that may not be entirely bullish for freedom money. We get into the shifting monocultures of Bitcoin, from grassroots self-custody to Saylor's vision. Rizzo explains why treasury companies must prove they can outperform Bitcoin itself and the risks if hundreds of them collapse in the next bear market. In this episod...
Nostr Boost Stats
- sats
- 2k
- boosts
- 9
- boosters
- 7
Nostr Community
Everyone who has boosted Is Bitcoin Culture Dead? | Pete Rizzo on Nostr, ranked by sats sent, all time.
- ndeet 1.3k sats
- npub1m0gm4…7lad 250 sats
- Wartime 133 sats
- Hern88 100 sats
- Stop Loss 100 sats
- John Gold 100 sats
- jgbtc 100 sats
Episode Boosts
Every boost sent to this episode, as published to Nostr, newest first.
-
⚡️ ₿ ⚡️Stop loss, use ₿itcoin, safe lifetime!
-
There is a big difference if you signal shitcoins are welcome or you focus on money and discourage non-monetary use cases. There are plenty of shitcoins they can play on. Nodes and users are important otherwise it deceases to be Bitcoin and becomes captured and centralized.
-
What bs are you talking abou Rizzo, lol.
-
I have never heard that knots supporters argue that they don't believe that a fee market establishes in the future. Hmm, why you think Luke is for 300kb blocks 🤔
-
-
What do you expect working for shitcoin magazine
-
This guy 🙄
-
The best advice when listening to podcasts is to skip the first three to 5 minutes to skip the bs. I hope someone will develop a podcast player that can skip the read ads that are so annoying. I don't want to fucking listen to the 109th fucking river fuck ad again and again.
-
At 54:30, Pete compley loses the plot. Core is making this change not knots. Pointing out the problem doesn't create the problem. Core is creating the problem and ignoring it, as Pete seems to prefer, doesn't make it disappear. It's a truly bizarre argument to blame the messenger. Also there is zero need for knots to ever fork. We just want the ability to configure a limit on op_return. Core certainly wants knots to…