Zack Wins

Wait, Bitcoin is Internet? Ordinals are Internet? Don’t miss this live with @shruggr and @wildsatchmo 👇 twitter.com/i/spaces/1kvKp…

BSV transaction finality: instant with 0-conf. BTC transaction finality: 10 minutes, maybe if fees are right, ask your node. User experience!

Is your “favorite maxi” bullsh1t artist?

@DevelopingZack To the 🌙

What is going on here? BSV

@TeamSatoshi Sure, its can. That’s “Fat Protocol Theory” Vs “Skinny Protocol Theory”

@DevelopingZack The market cap of the coins is a major issue. A 350k size can’t do a billion dollars in txns. BSV is a BitDNS proof of concept.

BSV can handle Wikipedia's entire edit history on-chain. BTC can handle... a JPEG of a rock for $300k. Different value propositions.

@NetworksChat @TeamSatoshi Satoshi said that BitDNS was supposed to be its own network anchored to Bitcoin.

@TeamSatoshi @DevelopingZack If the networks were ready then then BITdns would’ve happened. Good thing I have super node a working title of a much nicer system. An AI controller that can control both web browser and CLI, including its own code to run the swap Nakamoto agientic program just needs the nodes.

.@clemensley how are you doing?

I’m just gonna drop this right here…

Coinbase non-technical teams shipping code

You can store data on-chain with Bitcoin permanently and cheaply. For records, contracts, and timestamping, that’s genuinely useful infrastructure.

I’ve been 10 toes down since the beginning…

BSV’s commitment to stable protocol means developers can build without fear of consensus changes breaking their applications. Predictability has value.

BSV big blocks for normes: Imagine a group of delivery drivers who all share information about packages before anyone ships them. Most drivers agree to only deliver packages that pay enough money. So they all already know about those packages ahead of time. Now imagine one driver decides to deliver a bunch of cheap, low-pay packages that nobody else wants. When that driver announces their delivery route, the other drivers go: “Wait… we’ve never heard of half these packages. Now we have to stop and check them.” That delay matters. Because while everyone is busy checking those unfamiliar packages, another driver might finish a different delivery first and the network will accept that one instead. When that happens, the first driver’s work gets thrown out. That’s called an orphaned block. So: Majority miners ignore low-fee transactions A minority miner includes them anyway Their blocks spread slower because others haven’t seen those transactions yet Slower blocks = higher chance their block gets rejected In plain English: If you include weird stuff nobody else is using, your block takes longer to verify, and you’re more likely to lose the race.

"BSV is centralized!" There are like 8 mining pools. BTC has like 10. Someone explain the decentralization math here. Slowly.

"BSV price is down 95%!" So is their fee market. Perfectly balanced. As all things should be. Thanos was onto something.

@denverbitcoin So do it…

Yeah and it only costs ~$25k/day to 51% attack BSV network (total hashrate of 230PH/s or 0.02% of BTC hashrate ROFL) could successfully attack BSV with <1,000 miners 🤣 🤣 Bitcoin costs $400-$500M per day to attack 👀 Soooo… $0.0001 for 0% security/immutability? Or $20 for 100% security?? Tough choices… 🤦‍♂️ 🤡

BSV can timestamp legal documents for $0.0001. BTC can timestamp them for $20. Both are immutable! One makes financial sense

BSV transaction throughput: theoretically unlimited. BTC transaction throughput: 7 per second. Both work... One works better.

BTC: "We're a store of value now!" (Translation: we gave up on payments) BSV: "We're still doing payments." (Translation: we read the white paper)