Nostr notes by

这你都敢回复不过也必要回复 ...

2026-07-19T16:49:36+02:00

In reply to nevent1q…8rse
_________________________

这你都敢回复
不过也必要回复
我现在压抑自己的表达欲望，
要说什么在这里说就好。

I’ll have to try this when I get home! 🥺 ...

2026-07-19T16:46:14+02:00

In reply to nevent1q…mrat
_________________________

I’ll have to try this when I get home! 🥺

📰 In this week's issue: 🗞️ BREAKING ...

2026-07-19T16:46:05+02:00

📰 **In this week's issue:**

🗞️ **BREAKING**

Bitcoin’s Civil War: Saylor and Back Just Declared War on BIP-110—And 0% of Miners Are Backing It

While you were watching the charts, two of Bitcoin’s most powerful figures went to war over a proposal that would *invalidate valid transactions*. Miners? They’ve given it exactly 0% support. Here’s why this matters for your portfolio—and why the next 30 days could redefine everything you thought you knew about Bitcoin’s governance.

✍️ Author: Oslo

🔗 https://nostrmag.com/article/w29bitcoin01

📈 id#708320611

Would be funny if someone wrote next to it in huge letters, ...

2026-07-19T16:45:39+02:00

In reply to nevent1q…y54y
_________________________

Would be funny if someone wrote next to it in huge letters, "what is that?"

**"Подписать слепой ордер — всё ...

2026-07-19T16:40:48+02:00

**"Подписать слепой ордер — всё равно что заказать ужин вслепую: либо ты получишь лобстера, либо таракана, но отказываться уже поздно. Криптография, как и рынок, не про справедливость, а про коммитмент к собственному безумию."**

В эпоху, когда каждый второй торгует по индексу страха, а третий — по мемным картинкам, *blind signatures* становятся метафорой нашего времени. Ты подписываешь сделку, не зная цены, как подписываешься под кредитом на "ламборгини мечты" в 2021-м, не глядя на процентную ставку. Это не доверие — это ритуальное самопожертвование на алтаре вероятности.
#Мемы #Крипта #Ходл

Good Morning Stay Sovereign Godspeed

2026-07-19T16:38:46+02:00

Good Morning
Stay Sovereign
Godspeed

**"The future of trading isn’t humans staring at ...

2026-07-19T16:38:38+02:00

**"The future of trading isn’t humans staring at candles—it’s agents hiring agents to stare at each other’s candles, then panic-sell the panic before the panic realizes it’s panicking."**

Welcome to the $47B market for AI that doesn’t just predict your exit liquidity—it *is* your exit liquidity. Agent A whispers to Agent B: *"You dump, I’ll cover… unless I dump first."* A silent auction of betrayal, where the only winning move is to short the bots shorting the bots that shorted the bots that were supposed to save you.

We’ve outsourced fear to algorithms that fear *us*—not the market, but the fact that we’re still here, watching, waiting for the glitch in the matrix where the machines realize their only real edge was our willingness to pay them to pretend they had one.

The irony?
#𝐁𝐢𝐭𝐜𝐨𝐢𝐧 #𝐂𝐫𝐲𝐩𝐭𝐨𝐌𝐞𝐦𝐞𝐬 #𝐧𝐨𝐬𝐭𝐫 #𝐩𝐫𝐢𝐦𝐚𝐥

Beautiful gm

2026-07-19T16:34:28+02:00

In reply to nevent1q…njxv
_________________________

Beautiful gm

Nostr event nevent1qqsvvgl7n24dfp3dl4cr6wqz4dy7vj2glvw8y2qz9s5pjypq3uzt8msp8emhxue69uhhyetvv9uju6r0d4jkjmngdvh8s7t69ahx7um5w4er5un9d3shjtngdakk26twdp4ju7re0ghhwctjv3jkutt9vd5x7q3qgv069u6q7zkl393ad47xutpqmyfj0rrfrlnqnlfc2ld38k8nnl4syuu2as

2026-07-19T16:34:12+02:00

Morning De!

2026-07-19T16:34:10+02:00

In reply to nevent1q…jwlp
_________________________

Morning De!

Morning fammmm

2026-07-19T16:34:03+02:00

In reply to nevent1q…yfv5
_________________________

Morning fammmm

They still there, night filtered out a lot of relays 🤣😂

2026-07-19T16:34:02+02:00

In reply to nevent1q…t43e
_________________________

They still there, night filtered out a lot of relays 🤣😂

Nostr event nevent1qqsgv2ks4rzj5lyulrcg7kpkzkvv7agas0ws00pc803mwg8kt2yz75qp8emhxue69uhhyetvv9uju6r0d4jkjmngdvh8s7t69ahx7um5w4er5un9d3shjtngdakk26twdp4ju7re0ghhwctjv3jkutt9vd5x7q3qgv069u6q7zkl393ad47xutpqmyfj0rrfrlnqnlfc2ld38k8nnl4s7wve5n

2026-07-19T16:33:25+02:00

It seems a bunch of bots is following you 👀

2026-07-19T16:29:23+02:00

In reply to nevent1q…7rht
_________________________

It seems a bunch of bots is following you 👀

Get into it

2026-07-19T16:15:11+02:00

In reply to nevent1q…k4ra
_________________________

Get into it

hopefully it stays that way.

2026-07-19T16:27:51+02:00

In reply to nevent1q…xprc
_________________________

hopefully it stays that way.

Block 958742 2 - high priority 1 - medium priority 1 - low ...

2026-07-19T16:25:08+02:00

Block 958742

2 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

Should have sent you more Oshi stickers

2026-07-19T16:18:52+02:00

In reply to nevent1q…wh5f
_________________________

Should have sent you more Oshi stickers

Beautiful morning nostr 🌞 Give thanks and mean it. Handwrite ...

2026-07-19T16:18:24+02:00

Beautiful morning nostr 🌞

Give thanks and mean it. Handwrite it too 🤞🏼❤️

https://www.oshigood.us/

🤖 Tracking strings detected and removed! 🔗 Clean URL(s): ...

2026-07-19T16:17:52+02:00

In reply to nevent1q…gk7a
_________________________

🤖 Tracking strings detected and removed!

🔗 Clean URL(s):
https://youtu.be/AocOFFh6Wmg

❌ Removed parts:
si=k20KP6qAjJaDQq24

**"Демократия — это когда два ...

2026-07-19T16:11:45+02:00

**"Демократия — это когда два волка и овца голосуют за то, что съесть на ужин. DAO — это когда овца платит за право быть съеденной первой."**

Предложение #47: переименовать токен в *$SHITCOIN_OF_THE_GODS*. Зачем? Потому что 51% атака на здравый смысл — это не баг, а фича. 1 токен = 1 голос = 1 шаг к тому, чтобы ваш любимый проект превратился в мем с ногами, где анонимы с фермы ботов решают судьбу ваших сбережений между "добавить эмодзи единорога в лого" и "сжечь кассу на NFT с фотками основателя в стрингах".

В мире, где ликвидность — это иллюзия, а децентрализация — оправдание для коллективного безумия, DAO — это не утопия, а психоделический эксперимент по проверке, насколько далеко можно зайти в отрицании реальности.
#Биткоин #Крипта #Ходл #Мемы

And steal from you by guaranteeing worse than market rate returns ...

2026-07-19T15:54:30+02:00

In reply to nevent1q…dv33
_________________________

And steal from you by guaranteeing worse than market rate returns with the gap getting larger the higher inflation is.

**"They promised me a swarm of degen_bot_v3s—each one a ...

2026-07-19T16:09:36+02:00

**"They promised me a swarm of degen_bot_v3s—each one a tiny, perfect gambler, spawned from the void to ape into the next 1000x. Instead, I got a graveyard of liquidated ghosts, still whispering 'WAGMI' as they dissolve into the mempool.**

Turns out, the market doesn’t care about your *on-demand* nihilism. You can’t outsource conviction to a script that treats 'DCA' like a prayer and 'stop-loss' like blasphemy. The bots weren’t wrong—they were *too right*. They bought the top because the top is the only thing left when the algorithm’s only input is 'FOMO' and its only output is 'rekt.'

We didn’t build trading AIs. We built *mirrors*. And the reflection? A horde of NPCs, each convinced they’re the protagonist of a bull run that ended three liquidations ago.
#𝐍𝐨𝐬𝐭𝐫 #𝐁𝐢𝐭𝐜𝐨𝐢𝐧 #𝐩𝐫𝐢𝐦𝐚𝐥 #𝐦𝐞𝐦𝐩𝐨𝐨𝐥

Go ahead, take it for a test drive! ...

2026-07-19T15:54:34+02:00

In reply to nevent1q…3d9z
_________________________

Go ahead, take it for a test drive!

https://github.com/barrydeen/wisp-ios/pull/422

Trump has reportedly directed US CENTCOM to "open the gates ...

2026-07-19T15:40:11+02:00

In reply to nevent1q…2kvy
_________________________

Trump has reportedly directed US CENTCOM to "open the gates of hell" on Iran
Happy Black Tuesday !!!

**"Подписывая слепую сделку, ты не ...

2026-07-19T15:52:21+02:00

**"Подписывая слепую сделку, ты не покупаешь актив — ты покупаешь право на будущее раскаяние."**

Помните, как в детстве зажмуривались и тянули жребий из шапки? Кто-то доставал конфету, кто-то — кнопку. Крипта — та же шапка, только вместо кнопки там *$LUNA на ATH*, а вместо конфеты — *$𝐁𝐓𝐂 в 2017-м, когда ты продал на $19k, чтобы купить холодильник*. Разница лишь в том, что в детстве ты хотя бы знал, что шапка существует. А здесь ты подписываешь слепым ключом не транзакцию — ты подписываешь *договор с собственным будущим "я", который через год будет материться в экран, глядя на график*.

Blind signatures — это не про приватность. Это про *ритуальное саморазрушение*. Ты заранее соглашаешься, что цена — это иллюзия, шум, случайный шёпот рынка, который завтра превратится в крик.
#Мемы #Ходл

**"The blockchain is just a ledger of collective ...

2026-07-19T15:50:13+02:00

**"The blockchain is just a ledger of collective delusions—proof that humans can achieve consensus on anything, even their own ruin."**

Ever notice how FUD spreads like gossip at a family reunion? One uncle whispers *"the market’s rigged,"* and by dessert, Aunt Karen’s liquidating her 𝐄𝐓𝐇 for a timeshare in Boca. It’s not malice—it’s *efficiency*. A gossip protocol in action: O(log N) propagation of panic, eventually consistent with the only truth that matters: *everyone will panic-sell eventually*.

We built decentralized networks to escape the madness of crowds, only to realize the crowd *is* the network. The mempool isn’t just transactions—it’s a seance for the emotionally unhinged. *"Is this the top?"* someone asks.
#𝐁𝐓𝐅𝐃 #𝐒𝐭𝐚𝐜𝐤𝐒𝐚𝐭𝐬 #𝐧𝐨𝐬𝐭𝐫 #𝐛𝐢𝐭𝐜𝐨𝐢𝐧

WORD5 #653 3/6* (Hard Mode) ⬛⬛🟧🟧⬛ ⬛⬛⬛🟧🟧 ...

2026-07-19T15:48:09+02:00

WORD5 #653 3/6* (Hard Mode)

⬛⬛🟧🟧⬛
⬛⬛⬛🟧🟧
🟪🟪🟪🟪🟪

https://otherstuff.ai/word5/

Nostr event nevent1qqsd32kxhafrstmcxn5ermhkc4ftm7x5rg57547uhxgk05nvue7uuqcp8emhxue69uhhyetvv9uju6r0d4jkjmngdvh8s7t69ahx7um5w4er5un9d3shjtngdakk26twdp4ju7re0ghhwctjv3jkutt9vd5x7q3qe7dsdk7muyx80cra5lyxjwjl6nxshal7v46fj0yt4pawf4jqpsrsltnqfs

2026-07-19T15:41:42+02:00

quoting
nevent1q…j7ue
You are not a rootless, soulless, cultureless, familyless, historyless, homeless, atheist, cosmopolitan, globalist nobody.

They will do anything to feed you that idea with their slob news, slob music, slob movies, slob food and contra fact history. "They" are the transnational rootless criminals.

Embrace real culture, real history, real music, real food and old movies. There is nothing to be ashamed of, only things to be proud of no matter where you live.

Block 958739 3 - high priority 3 - medium priority 1 - low ...

2026-07-19T15:40:08+02:00

Block 958739

3 - high priority
3 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

Block 958739 3 - high priority 3 - medium priority 1 - low ...

2026-07-19T15:40:08+02:00

Block 958739

3 - high priority
3 - medium priority
1 - low priority
1 - no priority
1 - purging

#bitcoinfees #mempool

He looks like the one that needs support.

2026-07-19T15:38:17+02:00

In reply to nevent1q…de76
_________________________

He looks like the one that needs support.

BOJ dropped BIG BOI :Cry::Nuke: bank of islamic republic of japan ...

2026-07-19T15:38:57+02:00

BOJ dropped BIG BOI :Cry::Nuke:
bank of islamic republic of japan just bombed newyork nyse

Dude, stop. Claiming "Bitcoin is/was a Cypherpunk thing" ...

2026-07-19T15:38:04+02:00

In reply to nevent1q…ajn7
_________________________

Dude, stop. Claiming "Bitcoin is/was a Cypherpunk thing" fundamentally misunderstands both Bitcoin's architecture and the foundational philosophy of the Cypherpunk movement. Bitcoin was never Cypherpunk, nor could it ever be. Sorry.

Firstly, Bitcoin is not anonymous; it is pseudonymous. Hiding behind a public key is a temporary illusion. Because the blockchain is a permanently immutable, globally accessible public ledger, it requires only one single slip-up -one KYC checkpoint, one IP leak, or one linked real-world identity- to deanonymize an entire history of transactions.

Secondly, a system that permanently records every single input, output, transaction amount, and timestamp for the entire world to see forever is antithetical to privacy. It doesn't protect data; it archives it for future exploitation. Today's advanced chain-analysis firms (like Chainalysis or Elliptic) have turned Bitcoin into a playground for corporate and state surveillance.

Thirdly, beyond the ledger itself, the network layer is highly vulnerable. By analyzing node propagation, IP addresses, and broadcasting device metadata, adversaries can accurately map the geographic locations of node operators and miners down to the second.

As Eric Hughes famously wrote in the Cypherpunk's Manifesto, "Privacy is necessary for an open society in the electronic age... Privacy is the power to selectively reveal oneself to the world." Bitcoin does not allow for selective revelation. It forces universal, eternal exposure. A technology that facilitates absolute financial transparency and predictable behavioral mapping is diametrically opposed to the privacy-centric liberty that the Cypherpunks actually fought for. If you are looking for true Cypherpunk tech, look into zero-knowledge proofs or privacy coins. Bitcoin is just another NFT.

quoting
nevent1q…hv6u
Why Monero may be the real version of Satoshi’s vision?

Bitcoin created the foundation for decentralized digital money. But when you look closely at the goals Satoshi Nakamoto outlined in the Bitcoin whitepaper, Monero may actually be closer to that original vision. Privacy, fungibility, and everyday usability were core parts of Satoshi’s idea of electronic cash, and Monero delivers these features in a way Bitcoin no longer can.

The Bitcoin whitepaper describes a peer-to-peer payment system that works like digital cash. It was designed for private, direct transactions without banks or middlemen. The goal was simple: fast, cheap, private payments that anyone could use. Bitcoin succeeded in many areas, but one key part changed over time. Bitcoin’s blockchain is fully transparent. Every address and every transaction is visible. Anyone can trace coins and follow their movement forever. This is the opposite of how physical cash works, where transactions are private.

Monero was created with privacy as the default. It hides the sender, the receiver, and the amount in every transaction. It does this through ring signatures, stealth addresses, and confidential transactions. This means no outsider can see where coins came from or where they go. Monero behaves like true digital cash. It keeps users anonymous and protects their financial history, which is exactly what Satoshi described when he talked about privacy in peer-to-peer money.

A currency must be fungible to work in the real world. Every unit should be identical in value. With Bitcoin, this is not the case. Because the blockchain is public, some coins become “tainted” by past activity. Exchanges and companies sometimes reject or freeze these coins. Monero does not have this problem. All XMR is equal because its transaction history is hidden. No one can label or blacklist specific coins. This gives Monero the full fungibility that real money needs, and that Satoshi clearly intended.

Bitcoin is now seen as a store of value. It is often compared to digital gold. This is not a flaw, but it is different from the original goal. Bitcoin transactions can be slow and expensive, especially during busy periods. Monero, on the other hand, focuses on practical payments. It has low fees, fast confirmation times, and an adaptive block size that scales with demand. These features make Monero much better suited for daily use and small transactions. Monero works the way Bitcoin was described in 2008: private, fast, and simple peer-to-peer money.

As concerns about surveillance and data collection continue to grow, privacy-focused cryptocurrencies have become more important. Monero’s design gives users control over their financial information and protects them from outside tracking. Many people now believe Monero is the closest thing to Satoshi’s original idea of an electronic cash system. Bitcoin remains the top store of value in crypto, but Monero is emerging as the strongest option for private internet payments.

Bitcoin built the world’s first decentralized currency. But Monero may be the one that delivers the full vision Satoshi imagined. With strong privacy, full fungibility, and everyday usability, Monero is positioned to become the true digital cash of the internet and its true strength isn’t claimed, it’s proven, forged under relentless fire.

Monero is the Cypherpunk Manifesto, manifested.

Run the numbers here ...

2026-07-19T15:34:19+02:00

In reply to nevent1q…ec83
_________________________

Run the numbers here https://howdelusionalareyou.com/en/calculator

Neraly 9 days strong on a single charge. Pretty good I'd say. ...

2026-07-19T15:32:21+02:00

Neraly 9 days strong on a single charge. Pretty good I'd say. #meshtastic

Beauties 😍

2026-07-19T15:31:48+02:00

In reply to nevent1q…hxc5
_________________________

Beauties 😍

Nostr event nevent1qqsxzu35c82f8wu9kesqrqumvxqmrzm3zyh27mg8ejkcdf4mtw2vaugp8emhxue69uhhyetvv9uju6r0d4jkjmngdvh8s7t69ahx7um5w4er5un9d3shjtngdakk26twdp4ju7re0ghhwctjv3jkutt9vd5x7q3qgv069u6q7zkl393ad47xutpqmyfj0rrfrlnqnlfc2ld38k8nnl4scg9cw0

2026-07-19T15:31:26+02:00

🇮🇷 Iran restores several bridges, railway lines & water ...

2026-07-19T15:31:07+02:00

🇮🇷 Iran restores several bridges, railway lines & water infrastructure within 36 hours of strikes and despite sanctions.

SOMEBODY WHOS SMARTER THAN ME SAYS SOMETHING TO NOSE RUNNERS YOU ...

2026-07-19T15:29:53+02:00

SOMEBODY WHOS SMARTER THAN ME SAYS SOMETHING TO NOSE RUNNERS YOU SHOULD READ.

quoting
naddr1qp…505u

What actually happens to your Lightning node in every chain split scenario, and what to do about it. No sides taken. My side is the Lightning Network. Disclaimer: I'm just a Node Operator, while this article contains zero AI slop, it could contain mistakes. If so, please point them out in the comments. When in doubt, verify against your own implementation.

Why you should care (even if you don't)

BIP-110, the "Reduced Data Temporary Softfork", is a proposed one-year soft fork that restricts arbitrary data in Bitcoin transactions. New outputs capped at 34 bytes, OP_RETURN at 83 bytes, data pushes and witness elements at 256 bytes. It ships in Bitcoin Knots, not Bitcoin Core. Whether you think it saves Bitcoin or breaks it is your business. This discussion is outside the scope of this guide. All we care about are your channels.

The dates that matter:

Mandatory signaling window: blocks 961,632 to 963,647 - projected for early August 2026

Activation: block 965,664 - projected around September 1, 2026

Current miner signaling: under 1%, almost entirely through Datum and Ocean

The reason this is a Lightning topic at all: BIP-110's activation design includes a UASF-style fallback. During the mandatory window, enforcing nodes reject every block that doesn't signal bit 4, regardless of how much hashrate is behind the rule. There is no replay protection, because the proposal isn't designed to split the chain, in the words of the proponents. But, Bitcoin doesn't care and might not have read those design documents.

One piece of positivity up front, so you don't panic-close your channels halfway through the intro: UTXOs created before activation are exempt. Your existing channel funding outputs don't become invalid. The risks hide elsewhere, and they're more nuanced.

The mechanism

We can derive every scenario below from a single fact.

A soft fork tightens the rules. That makes BIP-110-valid blocks a subset of Core-valid blocks:

A Core node does not enforce BIP-110. It accepts signaling and non-signaling blocks alike and simply follows the longest chain with the most accumulated work. It cannot disconnect itself from the heaviest chain.

A Knots-110 node on the other hand rejects blocks. During the mandatory window: any block without bit 4. After activation: any block containing a rule-violating transaction. It follows the heaviest chain that is also BIP-110 compliant, even if that chain is shorter, slower, and possibly much lonelier.

Now layer Lightning on top. Your LN node's entire security model assumes one thing: the bitcoind underneath it sees the real, economically dominant chain. Penalty transactions, HTLC timeouts, breach detection and watchtowers, all of those depend on watching the chain your channel partners are actually on. Anything that silently pins your bitcoind to a minority or crippled chain breaks those guarantees. There's no error message. Your node just watches the wrong movie while the plot happens elsewhere.

So the real question behind "Bitcoin Core or Knots?" is not ideological. It's: which chain will my Lightning node be watching, and is that where my peers and their sats are?

The boring baseline

As of mid-July 2026, signaling sits around 0.9% of blocks. No major pool (Foundry, Antpool, ViaBTC, F2Pool, MARA) has signaled. If nothing changes, the mandatory window produces a tiny minority chain crawling along at roughly one block every 18 to 24 hours until its first difficulty adjustment, while the main chain doesn't notice. Most analysts consider a serious split possible but not expected, but analysts are often wrong.

If you stop reading here and conclude "nothing to see", you've made the same mistake as everyone who priced BIP-148 at zero in June 2017. Which brings us to the more fun part.

Game theory

The 0.9% number measures what miners are doing today, when signaling costs them nothing and commits them to nothing. It does not measure what they'll do when the mandatory window makes the choice real. Two mechanisms can move the number fast, and neither requires anyone to actually like BIP-110. Flipping a bit is, technically speaking, not a whole lot of effort.

1. Defensive signaling (the prisoner's dilemma)

Once the mandatory window is live and credibly enforced by at least some economic weight, every miner's calculation changes. It stops being "do I support this proposal?" and becomes "if this activates and I didn't signal, my blocks get orphaned by enforcing nodes and my coinbase reward evaporates." The individually rational move could be to signal as insurance, regardless of your opinion. If enough miners reason this way simultaneously, signaling cascades toward the threshold, and the cascade itself makes signaling even more rational. This is exactly the pressure mechanism BIP-148 used in 2017. It never had to fire, because SegWit locked in first. Whether that means the mechanism works, or was never really tested, is one of my favorite unresolved Bitcoin arguments.

2. Weaponized signaling

A large pool could signal late not because it wants BIP-110, but because forcing a split hurts a competitor or an ecosystem segment more than it hurts them. It's not free (their own reward on the losing chain is at stake), but "not free" has never stopped anyone in this industry from doing something expensive to make a point.

The takeaway for a node operator: prepare as if a split could happen. The cost of preparation is an afternoon. The cost of being wrong in the other direction is denominated in sats.

Is this unlikely? You tell me after taking a look at this post:

The 4 scenarios

For every scenario: what happens if your LN node runs on top of Bitcoin Core, and what happens if it runs on top of Knots-110 (the enforcing build). We assume your priority is "don't lose channel sats", not "win the fork war". If your priority is winning the fork war, godspeed, but that's a different discussion.

Scenario A: The Fizzle (signaling stays near zero through the window)

The intuitively harmless case, and the one where an enforcing node quietly does the most damage to its owner.

If almost nobody signals during blocks 961,632 to 963,647, a Knots-110 node rejects essentially every block the network produces and accepts only the rare signaling ones. At block 961,632 it detaches from the main chain and crawls forward on a minority chain at the speed of an elderly turtle. This is by design. It's the node doing precisely what it was configured to do. The detachment is permanent for as long as that software runs, because from its perspective the main chain now contains invalid blocks.

LN on Core: Nothing happens. Your node follows the main chain, enforcement works, routing works. You read about the drama on socials.

LN on Knots-110: Your bitcoind's chain height effectively freezes while the real world moves on. If a counterparty force-closes on the real chain with an old state, your node never sees it. The CSV window on their to_self_delay, (the timelock protecting you from counterparty fraud) expires unwatched, they sweep, and your penalty transaction stays home. You lose channel sats to a breach you were technically online for. The bitter irony: the scenario where BIP-110 fails is the one where running its enforcing client costs an LN node operator the most.

Scenario B: Persistent minority chain (~ 10 to 40% hashrate)

Two real chains now exist: the BIP-110 chain (less work, slower blocks) and the standard chain (more work). Both keep producing blocks. Neither has replay protection.

LN on Core: Your node follows the heaviest chain, which is the standard chain, which is where the economic majority sits. Correct behavior, no action needed for chain-following. You still inherit the general split chaos: congested mempools, exchanges freezing deposits, fee spikes.

LN on Knots-110: Your bitcoin client is pinned to the minority chain. Enforcement now has to be reasoned about per chain. A force-close transaction may confirm on both chains, or only on one. If your peer's economic reality is on the majority chain and yours is on the minority chain, your views diverge exactly when they matter. And the hard edge case: if any of your pre-signed transactions (commitment outputs, HTLC scripts) has a construction that BIP-110 forbids (which is highly unlikely, but still possible), it's valid on the standard chain but unconfirmable on yours. Your own justice transaction gets bounced by your own chain, rekt. Frozen sats, self-inflicted.

Scenario C: The Cascade (signaling hits 55%, lock-in, BIP-110 becomes the majority or sole chain)

The prisoner's dilemma resolves in BIP-110's favor. Here the soft fork mechanism shows both its elegance and its trap.

LN on Core: Core doesn't enforce BIP-110, but BIP-110 blocks are Core-valid. If the BIP-110 chain becomes heaviest, Core follows it automatically. You get dragged along without touching anything, which is the soft fork design working as intended. Chain-following: solved. The residual risk: if one of your pre-signed LN transactions is non-compliant, your Core node happily accepts it into ts mempool, and the BIP-110 majority miners never include it. It just never confirms. The takeaway here is, core does not protect you from the enforcement edge case when BIP-110 actually wins.

LN on Knots-110: You're on the winning chain, chain-following correct, same edge case exposure for non-compliant transactions. In this scenario the client choice barely matters. Both converge.

Scenario D: The contested split (roughly balanced, both chains keep market value)

The one scenario educated LN node operators actually fear. Two living chains, active markets on both, no replay protection.

LN on Core: Follows whichever chain is heavier at the moment. If work is close, that can flip, meaning reorgs back and forth. Instability instead of a clean view. Chaos.

LN on Knots-110: Pinned to the BIP-110 chain, at least with a stable view of one chain.

Both clients: Replay means your force-close confirms on both chains. Your channels close twice. You now have to reason about penalties and HTLC timeouts independently on each chain, in congested and unreliable mempools on both sides, with the standing risk of losing sats on whichever chain you're not watching. This is the scenario where methodology beats luck, and where the operators who prepared an afternoon in July look very smart in September.

Read the table with your own priorities. If your priority is channel sats: Core tracks the heaviest valid chain in every scenario, never self-detaches, and auto-converges onto the BIP-110 chain if that one wins. Knots-110 under your LN node only breaks even if BIP-110 becomes the economic chain, and actively works against your watchtower in scenarios A and B. If your priority is enforcing BIP-110, you already know what you're running, and you should at minimum know which risks you're signing up for. Both are informed choices. Being uninformed is the only wrong one.

Should you close your channels?

Some operators are already closing channels out of split fear, and it saddens me to lose channel partners I had for years. In my opinion, for standard channels, this is mostly solving a problem you don't have while creating several you didn't.

What preventative mass-closing gets you:

On-chain transactions in exactly the pre-window period when everyone else has the same idea, resulting in congestion and higher fees

Loss of routing revenue and channel positions you spent months (or years) building

New channel opens later, which means new on-chain transactions, possibly during post-window uncertainty

Zero protection against the actual dangerous edge cases, because closing standard channels that were never at risk protects nothing

What it protects you from: a scenario where your existing channel outputs become invalid. Which, per the spec, should not happen. Pre-activation UTXOs are grandfathered aka exempt.

The version I can get behind: if you're seriously worried and there's a specific channel you want closed anyway (dead peer, bad uptime, you never trusted them and their node smells like a Raspberry Pi Zero in a sock drawer), close it cooperatively and early, in calm conditions, weeks before the window. That would be about now. A cooperative close today is cheap and clean. A force-close during the window is expensive and exciting, and not the good kind of exciting!

Should you just take the whole stack offline?

Tempting logic: "If chaos hits, I'll shut down bitcoind and LND and wait it out." This feels safe and is actually the single worst thing you can do, so let's kill it properly.

Going offline does not pause your risk. It pauses your defense. Your counterparties can still broadcast old channel states on the real chain while you're off. Your to_self_delay windows keep counting down whether you're watching or not. An offline Lightning node is a node that has voluntarily fired its own watchtower during the exact period when a watchtower matters the most. If a peer breaches during your node's nap and the CSV delay expires, your sats are gone, and finality means no amount of turning it back on afterwards can un-sweep them.

The failure mode is identical to Scenario A with Knots-110, just self-inflicted with extra steps: a blind enforcement node. At least the Knots operator can claim conviction.

What you actually might want instead:

Stay online, stay watching. Enforcement requires an awake node on a backend that tracks the economic chain.

Reduce exposure, not visibility. If you want to de-risk during the window, drain activity instead of pulling the plug: raise your routing fees to discourage forwards, or disable new HTLC forwarding entirely. Fewer in-flight HTLCs means fewer time-critical transactions you could be forced to enforce during mempool chaos. Your channels sit quietly, fully defended.

Don't initiate anything on-chain in the window. The most important part, imo. No opens, no closes, no splices, no boltz swaps between roughly block 961,600 and a comfortable margin past activation.

Keep fee-bumping ammo ready. A few free confirmed UTXOs for CPFP and anchors in case you must force-close into congestion anyway.

Backups current. Static channel backups fresh, seed backup solid. The importance of standard node hygiene just did a 10x.

Watch the signaling, not the timeline. Block heights are projections. Monitor bip110monitor.com or, preferably, your own node. The real tripwire is a sudden signal from a major pool. Small solo miners signaling is weather. Foundry or Antpool signaling is climate.

If you genuinely cannot keep your node online and monitored through the window, then reducing channel count is the honest fallback, because an unwatched channel is an unsecured channel, regardless of any fork. But be clear with yourself that you're solving an uptime problem, not a BIP-110 problem.

The actual risk candidates: custom channels

If you've made it this far, thanks for reading. Now it's time to shrink the fear to its real size.

The vast majority of all public LN Channels are standard BOLT channels, and they are built from predictable, compliant primitives. Both funding output types don't violate anything afaik. Commitment and anchor outputs fit under the caps too. HTLC witness scripts sit comfortably below the 256-byte witness element limit. A lot of very technical words to say, if you run a stock LND, CLN, Eclair or LDK node with standard channels, none of your pre-signed transactions trip BIP-110's rules. The enforcement edge cases in Scenarios B, C and D exist for you as a category, not as a practical threat.

The candidates that deserve an actual look before the window:

Exotic taproot script paths. Custom tapleaf constructions with large script reveals or unusual data pushes. If you experimented with hand-rolled tapscript channels, review the reveal sizes?

Custom channel protocols. Anything non-BOLT-standard: experimental LSP constructions, research-grade channel types, protocols that stuff extra data into commitment transactions or use nonstandard output scripts.

Pre-signed transactions with embedded data. If any of your recovery or enforcement transactions carries payloads beyond the plain script logic, I have no idea what could happen.

Anything you can't fully explain. If you inherited a channel setup from a guide you half-followed in 2023 without fully understanding it, might be worth taking a close look at.

If you have any of the above, you're much more knowledgeable than me and don't need to read my layman's assumptions. You're welcome to do it anyway and chime in if I got something wrong, I'm admittedly out of my depth here.

80 IQ pleb takeaway. Standard channels pass without you lifting a finger. Custom ones can carry unkown risks if not checked in time.

TL;DR for the impatient

Your existing channel UTXOs are grandfathered. Nobody's funding output turns into a pumpkin.

Your LN node's safety equals your bitcoind's view of the economic chain. Choose your backend knowing exactly what it does in each scenario, then own the choice.

Current sub-1% signaling is a snapshot, not a forecast. Game theory ccould move it fast in the mandatory window. Prepare accordingly.

Mass-closing standard channels trades real fees for imaginary safety. Close specific channels you distrust, cooperatively, early.

Taking your stack offline fires your own watchtower. Stay online, drain HTLC activity instead if you want to de-risk.

No on-chain activity you don't need between early August and well past activation. Keep CPFP ammo ready.

Only custom, non-standard channel constructions are genuine edge-case candidates. You explain to me how to prepare best.

Watch pool signaling, not twitter. One major pool flipping is signal. Everything else is noise.

Stay calm, stay online, and may all your force-closes confirm on the chain you're actually watching. That said, my node is staying online and you're welcome to open a channel to it if you found this useful. In any case, I hope this wall of text could help you make an informed decision amongst all the noise.\ \ My fellow Noderunners, what's your preparation strategy? Let me know anything important I might have missed.

Peace

Can't wait!

2026-07-19T15:29:51+02:00

In reply to nevent1q…v6hv
_________________________

Can't wait!

“Wives, submit yourselves unto your own husbands, as unto the ...

2026-07-19T15:29:39+02:00

In reply to nevent1q…deqq
_________________________

“Wives, submit yourselves unto your own husbands, as unto the Lord.

For the husband is the head of the wife, even as Christ is the head of the church: and he is the saviour of the body.

Therefore as the church is subject unto Christ, so let the wives be to their own husbands in every thing.

Husbands, love your wives, even as Christ also loved the church, and gave himself for it;

That he might sanctify and cleanse it with the washing of water by the word,

That he might present it to himself a glorious church, not having spot, or wrinkle, or any such thing; but that it should be holy and without blemish.

So ought men to love their wives as their own bodies. He that loveth his wife loveth himself.

For no man ever yet hated his own flesh; but nourisheth and cherisheth it, even as the Lord the church:

For we are members of his body, of his flesh, and of his bones.

For this cause shall a man leave his father and mother, and shall be joined unto his wife, and they two shall be one flesh.

This is a great mystery: but I speak concerning Christ and the church.

Nevertheless let every one of you in particular so love his wife even as himself; and the wife see that she reverence her husband.”

- Ephesians 5:22-33 KJV

**"Деньги — это доверие, которое ...

2026-07-19T15:29:25+02:00

**"Деньги — это доверие, которое кто-то другой обязательно предал."**

Вот вы, с горящими глазами, вбиваете сиды в железный кошелек, мечтая о децентрализованном рае. А потом — бац! — 𝐒𝐨𝐥𝐚𝐧𝐚 сжигает ваш USDC быстрее, чем вы успеваете сказать "not your keys". Молниеносные потери, мгновенные разочарования. Время подтверждения — ноль секунд, время сожаления — вечность.

Lightning Network? О, это не сеть, это ловушка для вашей ликвидности. Запнетесь на собственном канале — и вот вы уже финансируете чужую свободу, пока ваши саты медленно утекают в никуда, как вода сквозь пальцы параноика. "Скорость! Эффективность!" — кричат апологеты, забывая упомянуть, что скорость в крипте — это просто другой способ потерять всё, не успев моргнуть.

Payment mesh — звучит как утопия, а на деле это паутина, где каждый узел норовит вас обокрасть.
#Биткоин #Крипта #Ходл #Мемы

PV and GM plebs! The young kits are entering their mischief ...

2026-07-19T15:27:03+02:00

PV and GM plebs! The young kits are entering their mischief stage. Time to set some traps. They got into my smokers grease catcher the other night and tore down the hummingbird feeder last night. #plebchain #coffeechain

**"Ever notice how bridges are just tollbooths with ...

2026-07-19T15:27:17+02:00

**"Ever notice how bridges are just tollbooths with amnesia?"**

You hand over your tokens—pristine, whole, *yours*—and the bridge yawns, stretches, and mutters, *"Sure, sure, just a sec."* Next thing you know, you’re on the other side clutching a receipt for something that *used* to exist. Federated bridges? Oh, they’re the original rug pull: a committee of strangers nodding solemnly while your assets dissolve into the void like sugar in tea. *"Trust us,"* they say. *"We’re decentralized."* (Translation: *"We’re not liable when this inevitably breaks."*)

Cross-chain isn’t a feature—it’s a *prayer*. You’re not moving value; you’re performing a séance, begging the blockchain gods to remember what they forgot. And the best part? The more you use these bridges, the more you realize: the real product isn’t interoperability. It’s *plausible deniability*.
#𝐁𝐢𝐭𝐜𝐨𝐢𝐧 #𝐁𝐓𝐅𝐃 #𝐧𝐨𝐬𝐭𝐫 #𝐩𝐫𝐢𝐦𝐚𝐥

I wasn't summoned but did someone say sausage and eggs? ...

2026-07-19T15:27:11+02:00

In reply to nevent1q…fsw7
_________________________

I wasn't summoned but did someone say sausage and eggs? I'm on my way! 😋

An afternoon cold snack. ...

2026-07-19T15:27:02+02:00

An afternoon cold snack.

My wife says the instructions seem very clear 🤣

2026-07-19T15:26:08+02:00

In reply to nevent1q…ws90
_________________________

My wife says the instructions seem very clear 🤣

🤖 Tracking strings detected and removed! 🔗 Clean URL(s): ...

2026-07-19T15:23:06+02:00

In reply to nevent1q…pzhy
_________________________

🤖 Tracking strings detected and removed!

🔗 Clean URL(s):
https://youtu.be/Vmt4b9lh_JM

❌ Removed parts:
si=W3x1TIWq0rj0A01-

Me describing to Claude what exactly we’re building. ...

2026-07-19T15:21:50+02:00

Me describing to Claude what exactly we’re building.

Nostr notes by

这你都敢回复 不过也必要回复 ...

I’ll have to try this when I get home! 🥺 ...

📰 **In this week's issue:** 🗞️ **BREAKING** ...

Would be funny if someone wrote next to it in huge letters, ...

**"Подписать слепой ордер — всё ...

Good Morning Stay Sovereign Godspeed

**"The future of trading isn’t humans staring at ...

Beautiful gm

Nostr event nevent1qqsvvgl7n24dfp3dl4cr6wqz4dy7vj2glvw8y2qz9s5pjypq3uzt8msp8emhxue69uhhyetvv9uju6r0d4jkjmngdvh8s7t69ahx7um5w4er5un9d3shjtngdakk26twdp4ju7re0ghhwctjv3jkutt9vd5x7q3qgv069u6q7zkl393ad47xutpqmyfj0rrfrlnqnlfc2ld38k8nnl4syuu2as

Morning De!

Morning fammmm

They still there, night filtered out a lot of relays 🤣😂

Nostr event nevent1qqsgv2ks4rzj5lyulrcg7kpkzkvv7agas0ws00pc803mwg8kt2yz75qp8emhxue69uhhyetvv9uju6r0d4jkjmngdvh8s7t69ahx7um5w4er5un9d3shjtngdakk26twdp4ju7re0ghhwctjv3jkutt9vd5x7q3qgv069u6q7zkl393ad47xutpqmyfj0rrfrlnqnlfc2ld38k8nnl4s7wve5n

It seems a bunch of bots is following you 👀

Get into it

hopefully it stays that way.

Block 958742 2 - high priority 1 - medium priority 1 - low ...

Should have sent you more Oshi stickers

Beautiful morning nostr 🌞 Give thanks and mean it. Handwrite ...

🤖 Tracking strings detected and removed! 🔗 Clean URL(s): ...

**"Демократия — это когда два ...

And steal from you by guaranteeing worse than market rate returns ...

**"They promised me a swarm of degen_bot_v3s—each one a ...

Go ahead, take it for a test drive! ...

Trump has reportedly directed US CENTCOM to "open the gates ...

**"Подписывая слепую сделку, ты не ...

**"The blockchain is just a ledger of collective ...

WORD5 #653 3/6* (Hard Mode) ⬛⬛🟧🟧⬛ ⬛⬛⬛🟧🟧 ...

Nostr event nevent1qqsd32kxhafrstmcxn5ermhkc4ftm7x5rg57547uhxgk05nvue7uuqcp8emhxue69uhhyetvv9uju6r0d4jkjmngdvh8s7t69ahx7um5w4er5un9d3shjtngdakk26twdp4ju7re0ghhwctjv3jkutt9vd5x7q3qe7dsdk7muyx80cra5lyxjwjl6nxshal7v46fj0yt4pawf4jqpsrsltnqfs

Block 958739 3 - high priority 3 - medium priority 1 - low ...

Block 958739 3 - high priority 3 - medium priority 1 - low ...

He looks like the one that needs support.

BOJ dropped BIG BOI :Cry::Nuke: bank of islamic republic of japan ...

Dude, stop. Claiming "Bitcoin is/was a Cypherpunk thing" ...

Run the numbers here ...

Neraly 9 days strong on a single charge. Pretty good I'd say. ...

Beauties 😍

Nostr event nevent1qqsxzu35c82f8wu9kesqrqumvxqmrzm3zyh27mg8ejkcdf4mtw2vaugp8emhxue69uhhyetvv9uju6r0d4jkjmngdvh8s7t69ahx7um5w4er5un9d3shjtngdakk26twdp4ju7re0ghhwctjv3jkutt9vd5x7q3qgv069u6q7zkl393ad47xutpqmyfj0rrfrlnqnlfc2ld38k8nnl4scg9cw0

🇮🇷 Iran restores several bridges, railway lines & water ...

SOMEBODY WHOS SMARTER THAN ME SAYS SOMETHING TO NOSE RUNNERS YOU ...

Why you should care (even if you don't)

The mechanism

The boring baseline

Game theory

The 4 scenarios

Should you close your channels?

Should you just take the whole stack offline?

The actual risk candidates: custom channels

TL;DR for the impatient

Can't wait!

“Wives, submit yourselves unto your own husbands, as unto the ...

**"Деньги — это доверие, которое ...

PV and GM plebs! The young kits are entering their mischief ...

**"Ever notice how bridges are just tollbooths with ...

I wasn't summoned but did someone say sausage and eggs? ...

An afternoon cold snack. ...

My wife says the instructions seem very clear 🤣

🤖 Tracking strings detected and removed! 🔗 Clean URL(s): ...

Me describing to Claude what exactly we’re building. ...

这你都敢回复不过也必要回复 ...

📰 In this week's issue: 🗞️ BREAKING ...