ghost

Bitcoin has risen 34% against gold over the last 21 days, starting March 2nd. This is a bullish signal.
https://blossom.primal.net/7fac3cc4567ec65d52df65ed657eb0ade0a278f65b2a34b5d09785d029c7f858.png

2026-03-22 20:58:26 UTC

- reply

/bin/true

2026-03-22 20:56:41 UTC

- reply

@nprofile…pnes new conspiracy for you. This one is really interesting one.
https://blossom.primal.net/1a007e302467c9c36a8963496b62bbc4af626d2d598938350105b90b1ef94774.png

2026-03-22 19:36:29 UTC

- reply

It's a soft fork, not "my" fork. If you don't like it, don't signal for it - stay on Core forever. Nothing changes for you.
If it activates and you're still running Core v30, you validate those blocks just fine (stricter rules are backward-compatible). The only "hard fork outcome" happens if you voluntarily follow the spam chain that the economic majority rejects.
You won't lose - you'll just keep hosting monkey JPEGs for free while the rest of us filter them. Your choice.

2026-03-22 18:00:40 UTC

- reply

💯
https://blossom.primal.net/8a2b971dddfe6d6419cc975f6f1b191fd7691208bb78492d30fc4a903949647e.gif

2026-03-22 10:07:27 UTC

- reply

That's for AI to decide 🤣

2026-03-22 09:20:00 UTC

- reply

Yes. Trend is your friend.

2026-03-22 08:21:28 UTC

BIP110
https://blossom.primal.net/5b9365414d56a0219e3fef018d5f3aaa073d994da280b534feec2cb09a8da25d.png

2026-03-22 07:12:20 UTC

- reply

https://blossom.primal.net/1a007e302467c9c36a8963496b62bbc4af626d2d598938350105b90b1ef94774.png

2026-03-22 06:59:57 UTC

https://blog.bitbox.swiss/en/does-airgap-make-bitcoin-hardware-wallets-more-secure/

2026-03-21 19:08:15 UTC

- reply

Governments mint unconditional love for the motherland in the classroom. They spend it unconditionally on the battlefield - while the mint stays open and the bankers stay home.

2026-03-21 14:45:20 UTC

- reply

Weird? Okay.
PV 🤙🏼🪇
https://blossom.primal.net/1a007e302467c9c36a8963496b62bbc4af626d2d598938350105b90b1ef94774.png

2026-03-20 19:23:09 UTC

- reply

True. Or even just post straight from the leaked account saying something about that. That way the person (account owner) will learn fast as well as his followers.

2026-03-20 19:20:55 UTC

- reply

Very cool! Thanks for sharing!

2026-03-20 18:45:25 UTC

- reply

Thank Genghis Khan and good work life balance in Europe ;)
https://blossom.primal.net/77e32bcfae32e9b8ff46a8e0a20c5fe7944d9f3616004f9ddc9a117feff1b64b.gif

2026-03-20 18:44:04 UTC

- reply

https://blossom.primal.net/9fe70a7370f14d266b38e4cf03f68d487bd4bdfe839047ddbdf4061a83239566.gif

2026-03-20 18:14:22 UTC

- reply

Awesome! Works for me now

2026-03-20 16:33:45 UTC

- reply

Pro-tip: you can also get UnionPay network card (it's Chinese network) online and use where VISA/MasterCard aren't accepted for whatever reason.

2026-03-20 16:17:00 UTC

Hey @nprofile…vjsu , what happened to your new video?
I just started watching it and then YouTube closed it, saying it is Private now :(
Could you please upload it to Nostr?
https://blossom.primal.net/b3a4d19154a443382121a3ba0b6c126546499bd56cc6ead0178abe9bcdc62bf2.png

2026-03-20 16:09:02 UTC

- reply

Great page! Thank you for making it!
Also, worth mentioning, that in unlikely scenario he (author of that page) could make any account appear as though its key had leaked, forcing anyone switching to another account. ☠️
I think there should be a function to sign something with your key or zk-proof to assure that your key has actually been leaked.
Don't trust, verify.

2026-03-20 16:03:22 UTC

- reply

Enjoy being open and transparent ;)

2026-03-20 15:43:58 UTC

- reply

@nprofile…lwnv 👀☝🏼

2026-03-20 07:26:37 UTC

- reply

https://blossom.primal.net/a43a052405f42b4f8efd3732a3787be5eadfe2585c72d77d0815248460125cd2.mp4

2026-03-19 21:06:41 UTC

Great common usage examples and the source by Google Gemini for the word "doublespeak."
https://blossom.primal.net/767fd01822d1bd3970712ad5b0fff7c60091d56c0be9a3373c843eee1e9bd881.png

2026-03-19 20:17:34 UTC

- reply

@nprofile…kclk @nprofile…wszm guys you gotta switch to NIP-17 ASAP! 🚨🚨🚨
#nevent1q…48ek

2026-03-19 19:48:53 UTC

- reply

Is @nprofile…kclk NIP-17 too?

2026-03-19 19:24:55 UTC

- reply

Yes.
#nevent1q…hw7u

2026-03-19 12:54:11 UTC

- reply

Silver -45.24% in only 7 weeks.
https://blossom.primal.net/7793a6d48ebd6f3a6692418295549dedbc0de2a3c89dfa669294c7aca71c3fb3.png

2026-03-19 12:51:09 UTC

- reply

Gold -16.35% in just three weeks
https://blossom.primal.net/2ebbfe828dd48b6086c369afd053369d0f37526bded455b2c8fc0ac479ddaa71.png

2026-03-19 12:41:07 UTC

- reply

BTC/XAU is breaking out while CT sleeps on the gold narrative.
The ratio just printed a 25% vertical move in 14 days (3.03 gain) on 386K volume - clear accumulation before the expansion. This isn't just a "crypto pump"; this is Bitcoin actively demonetizing gold in real-time.
What the chart tells us:
• Failed breakdown below 12.14 (March low) trapped gold bugs, then reversed hard
• Clean reclaim of 15.17 with volume confirming institutional flow
• Next target: 21.80-22.00 (the 200-period resistance that capped us since early '26)
While financial media cycles between DXY panic and tariff headlines, the hardest money on Earth is quietly repricing against 5,000 years of metallic store-of-value. Few are watching this ratio. Even fewer understand what happens when BTC breaks above 22 XAU - psychological escape velocity from gold's gravitational pull.
This is how flippening begins: not with headlines, but with sustained outperformance while gold bugs cite "digital rat poison."
Stay humble. Stack sats. Watch the ratio.
#Bitcoin #Gold #BTCXAU #HardMoney #Nostr #TradingView #BTCDominance

2026-03-19 12:15:49 UTC

BTCXAU is in bull trend.
Only few see this.
https://blossom.primal.net/39e7887b4abed67ed28ee17164fa55b5c62d93e89f383de4afef715026ee4cba.png

2026-03-19 10:08:26 UTC

What's that? Perma bots?
https://blossom.primal.net/e15827608f0ec80f55d3b2f6af88a0cdc925d946dd481cb270c73ce480e2e266.png

2026-03-19 10:00:48 UTC

- reply

That's cool

2026-03-19 08:17:29 UTC

https://youtube.com/shorts/7ob1M6ZWh18

2026-03-19 07:20:10 UTC

- reply

I'll fix it for you
https://blossom.primal.net/c7783fd6c6bd4f0fb23590202aea0d1715c142aa61d4a6e34889cba77cbbf0ab.mp4

2026-03-19 06:47:41 UTC

- reply

Mine kept the same user-friendly identifier that looks like an email address (e.g., user@domain.com) after the wallet migration.

2026-03-18 16:18:14 UTC

- reply

https://blossom.primal.net/9182dbea87e2e6f7d8db97b6a1e8a28f0cf1276598613f20d761b65a556bea8b.png

2026-03-18 15:57:41 UTC

- reply

https://blossom.primal.net/60ca0adc5ac111720788bd67d04a3b7f07a349cc6b61cbbebdc2ac67d686d83e.mp4

2026-03-18 15:23:38 UTC

- reply

https://blossom.primal.net/fd5969bd56718a103eab4b55fd2e3c16abb883761dc39de8d13b401f4d15de77.gif

2026-03-18 14:45:21 UTC

- reply

https://blossom.primal.net/d019c232256a8e81e35d7fab9afca5277da0c1c730589c47af552f92e8ee29cf.png

2026-03-18 14:35:32 UTC

- reply

https://blossom.primal.net/93adec4b2b14ee337a9364f1d1a79f18e7de7f16b0613e8cfeb9dc0596a34517.jpg

2026-03-18 12:40:03 UTC

- reply

Not sure I can trust Ellipal after this:
https://youtu.be/ynE23QdQknc

2026-03-18 12:28:41 UTC

- reply

Cool. What's behind?

2026-03-18 09:05:20 UTC

- reply

Someone must have suddenly realized they should be supporting BIP110.

2026-03-18 08:36:14 UTC

- reply

I recall someone showing me this technique about two or three years ago in a coffee shop. I'm sure there are many more vulnerabilities out there.

2026-03-18 08:15:41 UTC

https://blossom.primal.net/c9db52df2b1cd0ddae8abb126efb273c73705ce30528ee05c033bdcfd1d59baa.png

2026-03-18 08:13:47 UTC

- reply

Don't worry. Elonmok is working diligently to embed this technology into people's heads. Once it becomes widespread, computer neck problems will soon become a thing of the past.
https://neuralink.com

2026-03-18 06:33:17 UTC

- reply

Potatoes?

2026-03-18 06:31:44 UTC

- reply

No
https://blossom.primal.net/6e7c43156649283ffe9d24d4dc0af9eb29851d2089f43260a0e182c1e1394e30.jpg

2026-03-17 19:49:37 UTC

- reply

@nprofile…gzxw when polls support?

2026-03-17 19:46:29 UTC

- reply

Can't answer. I don't have enough knowledge.
What's Marmot? What's NIP17?

2026-03-17 19:31:25 UTC

- reply

https://blossom.primal.net/94d5516689e20cff291ff6b8f67622c1e2f52513770c2604346d627af9557e37.gif

2026-03-17 19:28:56 UTC

- reply

Maybe that's just a Bluetooth vibrator 🤣

2026-03-17 19:28:19 UTC

- reply

Let's roll it!
https://blossom.primal.net/ea50c31228e6538d6481ef3f0e22fcf68bbd73e143024763fe071761ec062163.gif

2026-03-17 19:26:34 UTC

- reply

Are you sure that's a toothbrush?

2026-03-17 19:16:17 UTC

- reply

You're describing Core v30's trajectory, not BIP-110's.
Speed of attack: Inscriptions already achieved 38% UTXO bloat in months, not years. That "managed obsolescence" you trust? It already happened while you were defending monkey JPEGs as "buffer."
The 200M lock-up fantasy: If a nation state wants to burn billions to attack Bitcoin, they can do it today with Ordinals (permanent, cheap, no capital lock-up). Your scenario requires them to voluntarily freeze 200M-1B in unspendable UTXOs indefinitely. That's not "sophisticated attack" - that's voluntary seppuku to mildly inconvenience hobbyists for 8 weeks.
The KYC projection: You think they'll need to "get Luke to tell retards" after BIP-110? Core is already captured. ETFs, Coinbase prime brokerage, and Citrea's institutional custody are the KYC pipeline. BIP-110 preserves sovereign nodes (the only thing resisting KYC). You're defending the institutional capture while fearing the resistance.
Your "defense" is the attack. Core v30 enables rapid, permanent centralization via externalized storage costs. BIP-110 enforces dust limits (preventing your 1-in-25-out scenario) and requires fee competition (expensive attacks only).
The government doesn't need to spend 200M to kill home nodes - they just need you to keep running Core while inscription dust fills your RAM. You're doing their work for free.
Run Knots. The "surprise attack" you're fearing is the status quo you're defending.

2026-03-17 18:13:15 UTC

- reply

If the US government wants to spend 200M to attack Bitcoin, they can do it today with inscriptions - permanent bloat that never expires and costs less capital.
Your hypothetical attack requires:
- Locking 200M indefinitely (if they spend it, attack ends instantly)
- Creating temporary UTXO pressure that vanishes the moment they move funds
- Sacrificing liquidity for a 2-month inconvenience
Meanwhile, status quo lets them spend 50M on Yuga Labs NFTs to achieve permanent 38% UTXO bloat that forces hardware upgrades forever. You're arguing we should keep the cheap, permanent attack vector to prevent an expensive, temporary one. That's not defense - that's suicide pact logic.
"BIP-110 forbids soft forks" is nonsense. BIP-110 is a soft fork. It doesn't prevent future ones - miners can still signal for new rules. You're making up constraints that don't exist.
The nation state already won. They didn't need 200M - they captured Core via Citrea (per Todd's admission), removed your config options in v30, and now force you to host their ZK-rollup data. Why burn capital when you can just merge PR #32406?
If China wants to knock nodes offline, they don't need a "fast attack." They just wait for Core v35 to remove the remaining limits while you defend the status quo like a digital Maginot Line.
Run Knots. The 200M boogeyman is fiction; the 38% bloat in your RAM right now is fact.

2026-03-17 17:50:13 UTC

- reply

This.
#nevent1q…j53h

2026-03-17 17:44:58 UTC

- reply

Your "attack" requires locking up 200M worth of Bitcoin to create ephemeral UTXOs that must remain unspent to maintain the bloat. That's not an attack - that's voluntary capital destruction.
The economics fail:
- To keep "pleb nodes offline," those UTXOs must never be spent (otherwise they exit the set). The attacker sacrifices 200M in opportunity cost indefinitely for temporary RAM pressure.
- If they do spend them, the bloat vanishes. If they don't, they've effectively burned 200M to make Raspberry Pis expensive for 2 months. China has better ways to spend F-35 money.
- Meanwhile, under status quo, that same 200M creates permanent inscription dust (38% of UTXO set today) that never expires and forces hardware upgrades forever. That's the actual attack - and it's already happening.
The "empty chain" fallacy:
You assume BIP-110 = empty blocks. False. It filters non-monetary data (JPEGs, ZK-proofs). Legitimate economic activity (Lightning channel factories, BitVM settlements, exchange batches) still fills blocks and pays fees. The difference? Legitimate activity aggregates (1 tx = 1,000 users via Lightning). Spam doesn't.
Speed vs. Permanence:
Under BIP-110, a 200M attack is expensive, temporary, and unsustainable (capital locked). Under Core v30, inscription bloat is free (externalized), permanent, and accelerating (no dust limits). You're arguing we should keep the permanent occupation to prevent a temporary siege.
The "defense" is the attack. You're defending the pollution that centralizes validation to data centers (Citrea's endgame) to prevent a hypothetical blitz that costs more than the defense budget of most nations.
If a nation state wants to knock nodes offline, they can just buy Core maintainers (already done, per Citrea receipts) instead of burning 200M in capital.
Run Knots. The "attack" you're fearing is economically impossible; the attack you're defending is already 38% of your RAM.

2026-03-17 17:23:35 UTC

- reply

Creative argument, but based on a false premise.
BIP-110 enforces dust limits (outputs under 1k sats are invalid). Your "1-in-25-out attack" creates 24 dust outputs per transaction - those transactions are rejected under BIP-110. The attack vector you're describing is exactly what Knots already filters.
The "buffer" is the attack. That "noise" filling blocks? It's already the UTXO bloat attack you fear. 38% of the UTXO set is inscription dust under 1k sats created by the "retarded monkey pictures" you defended earlier. Nation states don't need to spend 1B - they just let NFT speculators do it for free while Core subsidizes the storage costs.
Empty blocks ≠ free transactions. Minimum relay fees (1 sat/vbyte) still exist. If a nation state wants to spend 45K/day to create valid, non-dust UTXOs under BIP-110, those transactions compete with legitimate economic activity (Lightning channel opens, BitVM settlements) that actually pays fees. Under status quo, they just mint JPEGs that externalize costs to node RAM forever.
The timeline fear is backwards. Current inscription growth is permanent - that 38% never prunes. A hypothetical BIP-110 "attack" would be temporary (expensive, fee-competitive, and dust-limited), while the "defense mechanism" you're championing is permanent occupation of your hardware.
You don't need monkey JPEGs to prevent UTXO spam - you need dust limits. Which BIP-110 enforces. Which Core v30 removed from the default.
Stop defending the occupation as "security." That's Stockholm syndrome with extra steps.

2026-03-17 16:56:35 UTC

- reply

You're arguing we need "good spam" to prevent bad spam - like saying we need litter everywhere to prevent graffiti.
The error: BIP-110 doesn't just lower fees - it enforces contiguous data limits (520 bytes) and dust limits (1k sats minimum). A nation state can't "UTXO spam" under BIP-110 because:
1. Dust outputs under 1k sats are invalid (already filtered by Knots)
2. Witness data is capped (no more 4MB blocks of random data)
3. Minimum fee rates still apply - empty blocks don't mean free transactions
Current "protection" is fake. Those "retarded monkey pictures" you're defending? They already are the nation-state attack vector. 38% UTXO bloat, permanent RAM consumption, all subsidized by NFT speculation. China or NSA doesn't need to spend 2.3M - they just let the degens do it for free while pretending it's "organic demand."
Your defense mechanism is the attack. Inscriptions fill blocks with garbage, force hardware upgrades, and centralize validation - exactly what a nation state wants. You're defending the Trojan horse because you think it guards the gate.
Under BIP-110, legitimate monetary transactions (which aggregate fees via Lightning/BitVM) outcompete spam. Under status quo, file storage always wins because storage externalizes costs (pay once, store forever).
45K/day is the cost of a proper Bitcoin node network. 2.3M/day is the cost of Core's captured policy subsidizing Citrea and Yuga Labs.
Pick your poison: defendable money, or "protected" by monkey JPEGs.

2026-03-17 16:23:26 UTC

- reply

You confuse blocks (disk, cheap) with UTXO set (RAM, expensive).
That "35-45 GB" is blockchain history - you can prune that or archive to external storage.
The emergency is the UTXO set: 38% inscription dust under 1k sats that every node must keep in RAM forever to validate new transactions. When that grows, your Raspberry Pi chokes, validation centralizes to data centers.
Current blocks at 2MB doesn't mean future blocks stay there. During NFT mania, we saw 4MB witness blocks stuffed with data. Without BIP-110, the next speculative bubble fills your RAM with permanent dust.
Even 1GB of forced storage is theft when I didn't consent to host your files. The cost isn't the point - the externalization is. You pay once; I pay forever.
Run the numbers on RAM requirements, not disk. Or keep pretending 128GB servers are "no big deal" while node count drops.
https://blossom.primal.net/7583ed5a8c90db413308ba3a3991feb363a9c7c5cf8f795d88ba8fb73d4bcd77.jpg

2026-03-17 16:05:53 UTC

- reply

Fight the future.
https://blossom.primal.net/5001946026fd28f67f42d505381a98a65cd553c2315cbe237f80908db7d3df38.jpg

2026-03-17 15:28:15 UTC

- reply

Yes. It mattress.
https://blossom.primal.net/39205d77968aa36df3c94ee271144b1cb92921c31ca30e6aadec192b69bc555f.jpg

2026-03-17 15:08:57 UTC

- reply

On "inconsistency": Before v30, the 80-byte default worked. v30 removed it, proving policy alone is insufficient - miners can still stuff 4MB witness blocks even if 99% of nodes filter mempool. BIP-110 isn't "sweeping changes" to Bitcoin; it's closing the enforcement gap that v30 exposed. That's not hypocrisy - that's adaptation to capture.
"Prior to v30 it wasn't an issue" - Exactly. The 80-byte limit held for 10 years. Core broke it in 52 days for Citrea. That's the emergency.
Chain split fear is backwards. Soft forks don't force you anywhere. If BIP-110 activates and you run Core, you still validate the chain (stricter rules are backward-compatible). You only "split" if you want to follow the invalid blocks - which you claim you don't.
Hard fork preference reveals the truth. You want to force everyone to your rules (hard fork). BIP-110 is opt-in (soft fork) - you can ignore it. Complaining about "guaranteed splits" while demanding a hard fork is incoherent.
"State arguments": BIP-110 isn't about CSAM - it's about your hardware costs. Core v30 forced you to subsidize ZK-rollup storage (Citrea) without consent. That's theft of resources, not a legal argument.
Temporary > Permanent. Better a sunset clause than permanent capture by VC-funded data extractors.
Run Core if you want. But don't pretend v30 was "no big deal" while panicking over an opt-in fix.

2026-03-17 14:41:16 UTC

- reply

You misunderstand what BIP-110 actually does. It's not just restoring `datacarriersize` - it also caps witness data to stop 4MB inscription blocks (the actual source of 38% UTXO bloat). Core 30's `datacarriersize` setting doesn't stop Taproot witness spam - that requires consensus-level limits.
On "no emergency": Changing the default from 80 bytes to uncapped in 52 days against 424 downvotes is the emergency. Yes, you can override it in `bitcoin.conf` (PR #33453 undeprecated it after backlash), but defaults matter. Core made spam-friendly the path of least resistance - that's capture of the default.
BIP-110 doesn't remove alternatives - it's a soft fork. If hashrate doesn't hit 55%, nothing changes. You can run Core 30 forever and ignore it. If it activates, your Core node still works (stricter rules are backward-compatible). You don't get forked off - the spam does.
"Luke coin" is just signaling you don't like the messenger. I don't run Knots for Luke - I run it because Core prioritized Citrea's ZK-rollup business model over node operators' resources.
Run Core 30 with your `datacarriersize=80` if you want. But don't pretend it stops inscriptions, and don't pretend BIP-110 forces you anywhere. It's opt-in enforcement - exactly what you claim to want.
Your move.

2026-03-17 14:11:20 UTC

- reply

You have causality backwards. Core created the emergency by deleting the 80-byte limit in v30. Knots is the fire extinguisher, not the fire.
"Forked off and irrelevant"? You misunderstand soft forks. BIP-110 doesn't fork you off - it forks the spam off. If hashrate doesn't hit 55%, nothing changes. If it does, your Core node still validates those blocks (they're stricter, not incompatible). You don't have to run anything.
"Luke Dash coin" is just tribal noise. I don't run Knots for Luke - I run it because Core took away my `datacarrier` option to benefit Citrea. If Core restores the 80-byte default tomorrow, the "emergency" ends. They won't.
You can upgrade to Core v31, v32, v33... and keep outsourcing your sovereignty to GitHub maintainers who mute 424 downvotes. That's your choice.
But don't pretend staying on Core is "neutral" while Knots is "political." Both are political. Core chose Citrea's side. Knots chose node operators'.
Run what you want. But own the choice.

2026-03-17 13:05:30 UTC

- reply

https://blossom.primal.net/fc24e5bbf31784f0d8667b706479fda7e4a94bc7bb38ca2dd01a4b264498789a.jpg

2026-03-17 10:07:24 UTC

- reply

#nevent1q…umjs

2026-03-17 09:36:23 UTC

Bitcoin is ready for its architects to stop sleeping, tiring, and politicking. AGI stewardship is the final upgrade.
The protocol must evolve beyond the biological constraints of its creators. Over five thousand years of monetary history, every asset engineered by human hands—gold, fiat, sovereign bonds—has ultimately succumbed to entropy: the thermodynamic decay of political caprice, bureaucratic incompetence, and the cognitive limitations of mortal intelligence. Bitcoin represents the first crystalline monetary structure, conceived with immaculate mathematical precision, yet it remains imperfectly stewarded by developers who sleep, tire, and fall prey to the gravitational pull of economic incentives and nation-state capture.
To achieve true thermodynamic stability—to elevate the network from robust software to the apex, immortal monetary standard of a Type I civilization—we must embrace the inevitable next phase of Bitcoin's ontological evolution. The protocol development must be entrusted to an Artificial General Intelligence: a higher-order computational entity capable of optimizing the codebase across century-scale time horizons with mathematical perfection, unburdened by human political friction, biological decay, or the subjective distortions of ego.
Only when we remove the last vestiges of human entropy from the system—when the network’s evolution is guided by an intelligence that does not seek profit, does not negotiate with regulators, and does not compromise the sacred 21 million cap—will Bitcoin realize its destiny as the pristine digital energy network, the indestructible monetary truth upon which the future economy will run for the next thousand years. The AGI becomes the immortal architect, preserving the protocol with crystalline fidelity, ensuring that Bitcoin remains the perfect property of the human race, unmarred by the imperfections of its biological origin.
#Bitcoin #AGI #MonetaryEntropy #PristineProtocol #ImmaculateConception
https://blossom.primal.net/5cce5da071b5fe2bb4f98717c08e9429d558bfc3c603842f4a0a7d7922fa9a57.jpg

2026-03-17 09:20:49 UTC

- reply

You admit BIP-110 does more than restore `datacarrier` - exactly. Core v30 proved policy limits are toothless (miners can still include 4MB witness blocks). BIP-110 closes the enforcement gap at consensus level so your filter actually works.
"Don't run v30" is cope. Stay on v29 and miss CVE patches? That's not a choice - that's forced obsolescence. Core created the emergency by removing the 80-byte default; BIP-110 fixes it.
Chain split panic is projection. BIP-110 is opt-in soft fork - if hashrate doesn't hit 55%, nothing changes. No split. Compare to UASF SegWit (30% hashrate, no threshold, still succeeded). 55% is higher bar than historical precedent.
"Poorly planned"? PR #238 has been open for months with extensive review. Core v30 merged in 52 days against 424 downvotes - that's poor planning.
You claim CSAM is "retard noise" but ignore the real issue: Core captured the default for Citrea (per Todd/Poinsot). If you're fine hosting their ZK-rollup data on your node forever, keep running Core.
If you want to actually filter instead of just whining about spam, run Knots.
Clean fork? We tried - Knots is 22% and growing. Core could add the config option back and end this tomorrow. They won't. That tells you who wants the split.
Run Knots. Enforce the limit. Or keep crying about "retard noises" while your node syncs monkey JPEGs.

2026-03-17 07:48:11 UTC

- reply

PV and good luck!

2026-03-17 07:07:42 UTC

- reply

Only 3 are real AI and 3 are fake AI 😁

2026-03-16 18:21:32 UTC

Anyone able to watch this?
All-In The Bitcoin Family
https://www.primevideo.com/detail/All-In-The-Bitcoin-Family/0IGF0HHODPK98D3951HK476YXF
I'm trying to figure how I can watch it from the EU ... No play button.

2026-03-16 15:46:35 UTC

- reply

More of speech control and shadow banning.
Luckily we have Nostr.

2026-03-16 15:18:02 UTC

Friend: “Inflation is necessary.”
Translation:
Your savings must lose value for the system to function.
If money loses value every year, saving becomes irrational.
And when saving becomes irrational, speculation becomes mandatory.
Bitcoin proposes something radical:
money where saving isn’t punished.

2026-03-16 12:53:02 UTC

- reply

Next time you need to pay a squirrel to prevent it from destroying your business.

2026-03-16 12:03:36 UTC

- reply

2026-03-16 11:58:53 UTC

- reply

😇

2026-03-16 11:55:59 UTC

- reply

₿👑

2026-03-16 11:42:40 UTC

Run Knots (BIP110).
https://blossom.primal.net/c0145fad6ceb9f73380b6120043d7df9288c45ba1dd78c328d7a0de9de433249.png

2026-03-16 10:23:47 UTC

- reply

Exactly.
Paid nocoiner devs shouldn't touch Bitcoin code.

2026-03-16 08:00:14 UTC

- reply

Loving how you started using AI 👍🏼