Well, it finally happened. My 1 TB Bitcoin full-node drive ran out of space. Time for a 2 TB upgrade. 🧱⛓️ Actually fuck it, getting a couple of 4TB I run a Bitcoin node locally on my Mac and another on a Raspberry Pi 4. Both have 1TB, both can’t sync now

People often use this Satoshi quote: "If you don't believe me or don't get it, I don't have time to try to convince you, sorry." But what was Satoshi actually referring to? Bitcoin in general? Not at all. He was referring to the fact that users DON'T NEED TO RUN A NODE.

Imagine explaining a "sandwich attack" to someone who just lost 215 grand dealing with stablecoins.

Bitcoin with unlimited data storage is gross.

They are trying to push Chat Control through again. firefly.social/post/x/207460…

Yes, you read that correctly: the majority present voted _against_ chat control. But due to the absurdly undemocratic, illegal, procedure they're using, it comes into law anyway after being rejected multiple times before in previous votes. Insane.

Can you DM me your username? I’ll take a look and see if we can get this resolved. I’m really sorry. Unfortunately, UK regulations force our hand here. This isn’t a reflection of our values, it’s us complying with local law so we’re able to offer the service in the UK at all

June 17, 2010. Satoshi Nakamoto, in his own words: "I wanted to design it to support every possible transaction type I could think of." Read that again. Every possible type. Not "every payment type." Not "every type I approve of." He explains why in the same post. Handling each transaction type with special-case code "would have been an explosion of special cases." So he built Script, a general system where nodes evaluate whether conditions are met. Nothing more. Then he lists what the design already supports: escrow, bonded contracts, third party arbitration, multi-party signatures. And he says the part that matters most: "they all had to be designed at the beginning to make sure they would be possible later." He was building for transaction types he could not predict. That was the point. #Ordinals and #Runes are transaction types Satoshi could not predict. They pay full fees. They pass consensus. They use Script exactly as designed. BIP110 is the "explosion of special cases" Satoshi rejected in 2010. A growing list of rules deciding which valid transactions deserve to exist. He answered that question 16 years ago. The design decides. Not the filter. Primary source in the image. Verify it yourself: satoshi.nakamotoinstitute.or…

BIP-110ers stopping spam with <1% of hashrate

NEVER DELETING THIS APP

There is no question that BIP110 stems from the block size limit. Of course there isn't any room for jpegs. There isn't even any room for a fraction of global monetary transactions (which would require 17GB blocks at minimum). The entire problem is the 1MB limit. Lift the limit and spam is no longer an issue. This isn't even complicated and should never have been controversial. It was literally supposed to be *the* way to scale. Satoshi stated it explicitly (see below). The only reason to artificially cap the block size is if you don't want anyone to use Bitcoin.

5/7 - That objection mattered, because micropayments were a pillar of early Bitcoin advocacy: pay per article, pay per search, pay per page view. Gavin held the line anyway: "I don't think Bitcoin should try to solve too many very hard problems all at once."

➥ crypto wallet IP-exposure scorecard my main wallet GOT DRAINED yesterday, so i spent hours checking safer wallets to move on the Open Source Press recently analyzed the network traffic of popular Web3 wallets to identify how much info leaves your device before you even create a wallet the setup was intentionally simple: - clean Android device - no SIM card - fresh APK installation - VPN enabled - every packet logged from the moment the wallet was opened the user never created a wallet, imported a seed phrase & connected an account the only thing measured was what each wallet sent to the internet immediately after launch how the privacy score works? - the score ranges from 0 - 100 - a higher score means less network exposure the ranking is based on 2 simple metrics: → number of unique IP addresses contacted → number of unique domains contacted fewer outbound connections = fewer parties learning your IP address + device info before you even own a wallet privacy ranking post-filtered: [1] Top Tier (90-100) @cakewallet @stack_wallet @zodl_app @Trezor @vultisig @unstoppablebyhs @ZeusLN @phantom @tetherwallet @bluewalletio @zano_project [2] Middle Tier (70-89) @exodus @AtomicWallet @Thorwallet @keplrwallet @TrustWallet @safe @Rabby_io @rainbowdotme @Backpack @EdgeWallet [3] Lower Tier (<70) @Ledger @MetaMask @base wallet @solflare @Cryptocom wallet @Tangem @wallet @SafePal the differences are significant as bellow - Cake Wallet generated 0 outbound packets, 0 DNS requests, contacted 0 domains before user interaction - Zodl contacted just 1 endpoint - Unstoppable contacted only 2 endpoints - Phantom routed third-party services through its own infra, reducing direct exposure to external vendors at the other end: - SafePal contacted 26 domains across 41 IP addresses immediately after launch - OKX Wallet initialized AppsFlyer, Amplitude, OneSignal, ThreatMetrix fingerprinting, Alibaba endpoints, and other services before a wallet even existed many mainstream wallets also initialize analytics, attribution, crash reporting or messaging platforms such as Firebase, AppsFlyer, Segment, Braze, Customerio, Sentry, Crashlytics, Amplitude during cold start that doesn't automatically make them insecure these services help teams improve products, diagnose crashes, and measure usage but they also mean your IP address + device can be visible to multiple third parties before you generate your first private key for anyone who values network privacy, that's an important distinction onchain privacy starts with the wallet you choose but network privacy starts the moment you open the app s/o to @r4nk0X for the great insights

The original vision of crypto was better money. Along the way, we got distracted by social, jpegs, creator coins: noise Money that moves seamlessly, globally, for everyone. That's it. That's the industry. Everything else is a detour. That's the bet I'll live and die by.

Midnight is awesome, and the security looks amazing. But this reminds me of@VitalikButerin's talk at @EthCC 2024: your smart contract is online, few hundred lines of code, formally verified, 10 top auditors from 5 continents... perfect. Yet, the frontend is replaceable by just hacking the server. Wondering when @Morpho and other protocols will start tackling this. Solutions exist, like @okcontract.

What's all this talk about "Big Bitcoin"? I ran a node on a Raspberry Pi 4 and an old laptop for years. I heated my house for 4 years with several Antminer S9s and now I use a BitAxe as a hobby miner. None of these things are very big.

Did you know the Internet reserved error code 402, “Payment Required,” in 1997 and left it empty for a quarter century because the internet had no native money? It does now with Bitcoin.

A bit of a bitcoin to message a stranger, refunded when they reply, would end spam on the Internet.

In the 1990s, cypherpunks built remailers. You could send a message through them and the person receiving it never learned who you were. Anonymous mail, working, years before anyone called it privacy tech. Then the spam came. Anonymous systems are easy to flood, and there is no return address to block. Adam Back's answer, in 1997, was Hashcash. Before your message went through, your computer had to solve a small puzzle. Trivial for one honest email. Expensive for a million. He announced it to around two thousand people on the Cypherpunks mailing list. Years later the same mechanism showed up in the Bitcoin whitepaper, and proof of work (PoW) became famous as the thing that mints coins. That was never its first job. PoW was built to keep anonymous communication alive.

The open internet is dying. We don't like it. Nobody does. But why is it happening? Do you just need to have a better nginx configuration? Put more @Cloudflare service workers in front of your site? Just give up and put your content onto your @facebook page and let @Meta scrape your data and sell it to advertisers instead? That is certainly one way to do it. But it's a bandaid on a sucking chest wound. Or, to be more gracious, it's another layer of complexity on top of the ever growing ball of mud that is networked software. "How is this still legal?" as @EddCoates asks is a veiled request: "Make this illegal." Even if you wanted to, what would you do? Track down the IPs making the requests, get the ISP in another country to give you the info of their customer, and then try to get a foreign government to open a case against them? Then wait a few years for said case to work its way through the court system? Good luck, have fun. Even if that was the path you wanted, how many layers of registration, KYC, and legalease would this add on top of your digital life, joining the cookie warnings and mass surveillance that already pervades your journey through cyberspace? No. Of course you don't want that. What you want is simple. Or at least it should be simple. You want a personal server. A place to put your data and share it with your network. A digital space that is yours, and that distributes your content and applications, but where spammers and scrapers are unwelcome. That's Urbit. We've seen this future coming for over 20 years. It is carved in the foundations of the current networked computing stack. Woven into the duct tape and superglue creation that bundles and patches all manner of software and protocols into what we know as "The Internet". That is why we went all the way down the stack, throwing out everything but UDP and ASCII, and rewrote the entire networked computing stack. A uber-RISC low level instruction set with only 12 opcodes, Nock. A typed, functional systems programming language for building a clean slate OS: Hoon. A pure operating function, or 'solid state interpreter', that is an entire operating system in less than 100k lines of code: Arvo. A decentralized public key infrastructure where users cryptographically own their own identities: Azimuth. A content addressable p2p networking protocol, e2ee and transport agnostic: Ames. All designed and built as a cohesive whole, specifically to solve the problems that have arisen over the last 40 years of networked computing. Spam and bad faith actors being at the top of that list. Try it out today 👇🏻