From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Wed, 19 Nov 2025 13:46:13 -0800 Received: from mail-oo1-f63.google.com ([209.85.161.63]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1vLq0C-0003eZ-QE for bitcoindev@gnusha.org; Wed, 19 Nov 2025 13:46:13 -0800 Received: by mail-oo1-f63.google.com with SMTP id 006d021491bc7-65746235dd4sf63624eaf.3 for ; Wed, 19 Nov 2025 13:46:12 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1763588767; cv=pass; d=google.com; s=arc-20240605; b=g4bZYLC85QSa+9ImkTjFVcV4x7Wr5ERU1xR++EXf2LXiaAnizrQKfQh5M7RdWyalwh EBQfDzcCBc+gJtgr/Cg6u3EfEHyw1hZiqslDxqf/hC9Y8ADpfdfLBV6Wm8PmdpKV/AeG flCKolqp/jErXrc0eJU1H5Vx+5O8SHoNS9L7UAZR5enyXLvicS43fLRFbum7X0jRgWZ/ u44Iyj9hPI+YQIOabtgx/Ad+Uad7AeZsSouPmg0m8Ic7cPyDXjo1LNq97VLwWoXrKlH+ rb3zY3YkK9nrky8bMgDafCqSBLoXtgq7/dKEQRRjtNnHy8nYtvCu9FrCYIUftcrs2r88 uVyg== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:cc:subject:message-id:date:from :in-reply-to:references:mime-version:sender:dkim-signature :dkim-signature; bh=AwMYcgI+9bVwou5SLiRB4wROlStJqOFbAqnA8XlW7sg=; fh=V4ghO8qcxWrOnxb1caoiZSU5VcweZ121wouMWF2b6XE=; b=QDQwDjuv7ybZAb0VqPvgBiMlk1Pb8xmqzRroEZ45vZwbXMOO3uMmbf2wfylOB1n7qM tg1iV3JhHNerpCSWY2v5cfyDqdr1QPwZo46fnnA3IjRL1Tgpl2nWh8skjgAhS2gPln78 /nGM0Ke0ku6icPYtsMyehSr7wbM/KJu6sRqJJd4OUPxKm87KYRiTzMWsluCuQPHiAJXU aTb0CxGIbZ0Z7FVvm/tASaEPZuUrD3wYr9aAj/w5MEkEaCB4WLK58E1XFAGlXlYJjxjH T48PxaRq9E0doTUuZ9YsAEOG0FbgcdUcaLzJvwjWv10QkPMos7fQ3crbVSaRPiyu22F6 VIrw==; darn=gnusha.org ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=W8TcH0xx; spf=pass (google.com: domain of jose.edil@gmail.com designates 2a00:1450:4864:20::531 as permitted sender) smtp.mailfrom=jose.edil@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com; dara=pass header.i=@googlegroups.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1763588767; x=1764193567; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:cc:subject:message-id:date:from:in-reply-to :references:mime-version:sender:from:to:cc:subject:date:message-id :reply-to; bh=AwMYcgI+9bVwou5SLiRB4wROlStJqOFbAqnA8XlW7sg=; b=PJP7V2NtMsYpB9i7JtGJo+GPkgxXmrGYr31GaVOfqX92wdknkg6VP1YEIHIYaHKHM3 3Fdb2+Cxia2FSsvbUVQ+/F0Zs98myLMA3qyLYX8ZxIqmM/ctfoSc0GiWc8oKuHliv5q1 0IcvrW8KnW00Llp1e9/SNirP4Itug9W8Y8VgRMW26WiHmY/RfFJvp/9fuI9ABjMT7tGC q+aMtQdzpiW9oHfB7INKY5bTMEiACqXDBsrXdB/c0lI8MdMEksGmGzGpXx2hKhxPgWHL 4E/ZhK2A/OIR9gqbyAlBkS51r+8tflBmMp1pt5thkVRANlpDzT4MmWTfbt5kEEd+a43T Wxcw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1763588767; x=1764193567; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:cc:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to; bh=AwMYcgI+9bVwou5SLiRB4wROlStJqOFbAqnA8XlW7sg=; b=J7hqyELerbuuhwTqSO2MiFRgB4JDzbp7bskNk6NAX88mCr9RqdPRSac8Qm/mq6d1hj 4GqI8gkL7XSzhvSaan0F85ga2QxcOGzEuOl+GDzV30QOJfKGBtO71Xs+uuiE369ycBrw pImjyJ7zvZNqTObbnzjPW/7NOogkkEd/OAfgmSR4CsUEnIh8jc9mkd9Mt9j1S6jPg5Jh RA0W85fsh9RUxfQ0hZZnKIOlM3HdYIo2+TEMPK3nFAJl1asfbLCqqWiwp/4oFSCh7ktH /C2XbOM6uSFmnqKSZCQJKo1o8CytpW7OxlMrfBbp0T7GDx9UkaTnkHWQbIiwte2PlxbK qtLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763588767; x=1764193567; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:cc:subject:message-id:date:from:in-reply-to :references:mime-version:x-gm-gg:x-beenthere:x-gm-message-state :sender:from:to:cc:subject:date:message-id:reply-to; bh=AwMYcgI+9bVwou5SLiRB4wROlStJqOFbAqnA8XlW7sg=; b=h8SOge8x0qeO5Xe38gGlUIqrkialPrIGnbeGn7cpVAv8sjsXWzOmudSuz8npqAc5d7 ScF1fKL7DQzBXH7K/nX8EHUfGDZHK9nwpBmCNEc7KJbqhCy1w+cw0FQ8QH1vTubd4Czt zNHc25gf6wo8AnCgEngTSPYkBZFxYUMZkW51gUg/d7k6d57GsxYlkdLi66tvUFdjCvh/ rctzNCxYwLIRv9OrEOC2pQCqadiTKwDJ2v4qb2YJFT0OulU8lYxYjy7peHX+YhpBfEd8 HcYp/5EyDiguykiath8FCJH7kc7Mtc5l1hi/63wUWl9hB3MAkGZuztMRJtT9/jRDccg9 fL7g== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=2; AJvYcCXZHA9NU9NTHOGRNXE9Dse8LGrQeYhdx7qKnoLAQ0/rjlBU2dQ8HCCISO7BbtRZ52S7BjLfv5CyR7si@gnusha.org X-Gm-Message-State: AOJu0YxXMXqvHNTSSkQG+XpeVphFXZA1Z/CAp8LqmLQFC0U8hkWIEz7Y G4RE+3HnXvA95XqpHrAPkDB/fubuOsfG7nyDrg1ZQzzOsNRr+cck15ko X-Google-Smtp-Source: AGHT+IHNH7fvXwtBSjMNKjfKNq3KkRR0bFt9b9zCs5j75ehBA5q7rDdYQfUOZsnBmxCklIXrvt83uQ== X-Received: by 2002:a05:6808:2e4a:b0:450:d6b8:3b4 with SMTP id 5614622812f47-450ff3ca5famr437749b6e.49.1763588766634; Wed, 19 Nov 2025 13:46:06 -0800 (PST) X-BeenThere: bitcoindev@googlegroups.com; h="Ae8XA+ZQDcnKmeQdTjTmmbL7OYxuBJ7ABnE0VL2G9RErfgHQRg==" Received: by 2002:a05:6871:4147:b0:3e2:d619:f0df with SMTP id 586e51a60fabf-3ec9afdf4b5ls108742fac.0.-pod-prod-04-us; Wed, 19 Nov 2025 13:46:02 -0800 (PST) X-Received: by 2002:a05:6808:c2b9:b0:450:8933:b732 with SMTP id 5614622812f47-450ff20e5bamr358070b6e.7.1763588762828; Wed, 19 Nov 2025 13:46:02 -0800 (PST) Received: by 2002:a7b:c7d6:0:b0:477:b663:eee5 with SMTP id 5b1f17b1804b1-477b663f122ms5e9; Wed, 19 Nov 2025 09:04:52 -0800 (PST) X-Received: by 2002:a05:600c:a06:b0:475:e007:bae0 with SMTP id 5b1f17b1804b1-4778fe5ef06mr266011395e9.16.1763571889977; Wed, 19 Nov 2025 09:04:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1763571889; cv=none; d=google.com; s=arc-20240605; b=ZCz2I9llatQARZvACPbLPV3TsSczKLFmgCwXWYkwNMmutmxdfvhihSywpfOiBSuoTM kAZ4QBoK3bPkfCnJa08b2HZHFxfoaLio/0d9Ch4t77oLHLWWAV0qur/OqRLbZilBqQfP YvIac4pSzeUnzwBispBXYnyleAU/bJ6NVUHQXQ6M2KfKl3N2/qb7+VYaq6o3Evw4kpBH Novxk5LjwovVlknH7kEnm9naiWjtduMf7a5xMz4kaA3UuX9DQGn/CE31VDU8Zwd/kyOp gR8KdwtzlutKfOF5cF3NvwSqO2RIHKF83Fj6Bv9mRmi7qciqLAcNjZOB+YypNXAHDBh0 UPUw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:subject:message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=ctRkDG4tDMiBG1F9SFYxZrwpdXttjseCpHkHG3DmvpM=; fh=KToalNYOLOY5OcEN8k1qap7GE/GrsMpo+YpfFP5+Yok=; b=c5H2l2gT3Cf8Wu3V7hLDmZ9XjG2iF2umCTtCmDmBTnnLfwKju+S+z0vNzeQIdv6t0j Wau00v3RB8QzRmwmRAdrCZzoKqxt4t4yyAySTthdxZ8p4ypRk/kWX/KY0sP2aPkedFMA nJ2tHVZkOxAZeIOcYkxWtYslVybfva08rKldXOP/9V506Sez4rqfQFLIBJuZaAJFjat0 1c01qARy9sbQmr+vIUJs/8Y8P3OOdH50PiKxyJKeGnegzlrAFT5IwhvXM7RujkkwbeKa 9UxVdHozmLM/8vnHhIbu0g8gJcesfGUtS5eOpX2ZOUqeyAR8FiD4deerHQN94qFdSCBM wZcg==; dara=google.com ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=W8TcH0xx; spf=pass (google.com: domain of jose.edil@gmail.com designates 2a00:1450:4864:20::531 as permitted sender) smtp.mailfrom=jose.edil@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com; dara=pass header.i=@googlegroups.com Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com. [2a00:1450:4864:20::531]) by gmr-mx.google.com with ESMTPS id 5b1f17b1804b1-477b10136a5si290915e9.1.2025.11.19.09.04.49 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 19 Nov 2025 09:04:49 -0800 (PST) Received-SPF: pass (google.com: domain of jose.edil@gmail.com designates 2a00:1450:4864:20::531 as permitted sender) client-ip=2a00:1450:4864:20::531; Received: by mail-ed1-x531.google.com with SMTP id 4fb4d7f45d1cf-644fcafdce9so4081239a12.1 for ; Wed, 19 Nov 2025 09:04:49 -0800 (PST) X-Gm-Gg: ASbGncvoSxA6PKKmBNQ5CADtpvNQT0X/FPuD0pd+b0/PlnRUPpp6Qw619so2Jzw2dj4 tO5aHLoBDsnDi55PPRrY4FNecLFvLWw/LecMYsknVVnz7x9udt5vuBaRA2WuJmJcTdWWSDbVTiO Dp4S83S5CsjVv7FBnTos/qI5eAjpX7Gt/Q3IjnX1rr/jH3qd02lw+Y1J0kVT0Xr51UuBmSlQ2rz N+G86jxH8xR2DsSGa5XH+ksriONkfN6sf7c5SN0wlOxb+/n6FsLirwI5qU8twbmTDGqrctaXQ== X-Received: by 2002:a05:6402:34d1:b0:643:5f45:6fa5 with SMTP id 4fb4d7f45d1cf-645364870a8mr31112a12.33.1763571888908; Wed, 19 Nov 2025 09:04:48 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?Edil_Guimar=C3=A3es_de_Medeiros?= Date: Wed, 19 Nov 2025 14:04:36 -0300 X-Gm-Features: AWmQ_bnzhRlqdp7Z-z35HFPbWeNwgC1KZGxDszi-xoprLm5YGbZNiD3mfWoI4yE Message-ID: Subject: =?UTF-8?Q?Re=3A_=5Bbitcoindev=5D_Improve_Bitcoin=E2=80=99s_resilience_to_l?= =?UTF-8?Q?arge=2Dscale_power_grid_failures_and_Carrington=2Dtype_solar_sto?= =?UTF-8?Q?rms?= Cc: Bitcoin Development Mailing List Content-Type: multipart/alternative; boundary="000000000000f96ce60643f59352" X-Original-Sender: jose.edil@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=W8TcH0xx; spf=pass (google.com: domain of jose.edil@gmail.com designates 2a00:1450:4864:20::531 as permitted sender) smtp.mailfrom=jose.edil@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com; dara=pass header.i=@googlegroups.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: 0.4 (/) --000000000000f96ce60643f59352 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I don't see any specific measure that would require specific support from Bitcoin Core, maybe you can point to more specific requirements. The canonical approach is to maintain specific projects that solve specific problems using one of the node interfaces (e.g. RPC). But of course, anyone is free to contribute patches that might help handle this kind of situation. As you said, reorgs are expected to be gracefully handled already by the node implementations. Most software that is tested in testnet probably also was exposed to harsh conditions like deep reorgs and long periods without any block being mined. Having said that, the potential problem you describe is not specific to Bitcoin and having alternative critical communication mechanisms is desirable. But they probably fall under the economically not viable kind of infrastructure that humans have relied on governments to implement and maintain, which is far from an ideal approach. And by the way, this is the mailing list. Regards. Em dom., 16 de nov. de 2025 =C3=A0s 20:00, Alexandre escreveu: > Hi, > I=E2=80=99m submitting this feature request to explore how Bitcoin could = better > withstand extreme, long-lasting infrastructure failures caused by major > solar events. Before explaining the request itself, I want to provide a > brief overview of what these events are, because their scale matters. > > A large solar storm occurs when the Sun emits an intense burst of charged > particles and electromagnetic energy. When this material reaches Earth, i= t > can disturb the magnetic field and induce strong electric currents in lon= g > conductors such as power lines. In extreme cases, this can damage > transformers, overload electrical grids, interrupt satellite operations, > and disrupt long-distance communication systems. The most famous historic= al > example is the Carrington Event of 1859, the largest geomagnetic storm ev= er > recorded. It triggered worldwide telegraph failures, fires in equipment, > and intense auroras seen far from polar regions. Modern research suggests > that a Carrington-level event striking today could cause regional or > continental power grid failures lasting days to months, as well as major > internet and satellite disruptions. > > The issue for Bitcoin is that these types of events could fragment the > network into isolated regions unable to communicate for extended periods. > Each region might continue mining independently, creating separate versio= ns > of the chain. When connectivity eventually returns, deep chain splits and > long reorgs could occur. Although Bitcoin=E2=80=99s consensus rules can h= andle this > mechanically, the practical impact on users, operators, and services woul= d > be significant. > > The purpose of this feature request is not to propose consensus changes, > but to explore whether Bitcoin Core could improve resilience and > operational clarity in such extreme scenarios. Specifically: > > Degraded communication support > Consider improving documentation or optional tooling for running nodes > over degraded or intermittent communication channels such as HF/VHF radio > links, mesh networks, or intermittent satellite reception. These channels > exist today in experimental form but may benefit from more formal guidanc= e > or optional integration. > > Operator guidance > Document best practices for wallets, miners, and node operators during > extreme, high-latency, or partitioned network conditions to minimize user > disruption during future reconnection events. > > This request is simply to consider whether these improvements fall within > Bitcoin Core=E2=80=99s scope, or whether they should be handled entirely = by > external projects. If this discussion belongs on the mailing list first, > I=E2=80=99m willing to move it there. > > Thanks for your time and any feedback. > > -- > You received this message because you are subscribed to the Google Groups > "Bitcoin Development Mailing List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to bitcoindev+unsubscribe@googlegroups.com. > To view this discussion visit > https://groups.google.com/d/msgid/bitcoindev/d9f4f899-14d1-4787-8046-acd5= 9ff1ba98n%40googlegroups.com > > . > --=20 Edil --=20 You received this message because you are subscribed to the Google Groups "= Bitcoin Development Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoindev+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/= CANJiN3LnCFJxJpGxScLTqT2JF4iQNsX3hipiNiBK_OLMkkXb1g%40mail.gmail.com. --000000000000f96ce60643f59352 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I don't see any specific measure that would require sp= ecific support from Bitcoin Core, maybe you can point to more specific requ= irements.
The canonical approach is to maintain specific projects that = solve specific problems using one of the node interfaces (e.g. RPC).
<= div>But of course, anyone is free to contribute patches that might=C2=A0hel= p handle this kind of situation.

As you said, reorgs are= expected to be gracefully=C2=A0handled already by the node implementations= .
Most software that is tested in testnet probably also was expos= ed to harsh conditions=C2=A0like deep reorgs and long periods without any b= lock being mined.
Having said that, the potential problem you des= cribe is not specific to Bitcoin and having alternative critical communicat= ion=C2=A0mechanisms is desirable.
But they probably fall under th= e economically not viable kind of infrastructure=C2=A0that humans have reli= ed on governments to implement and maintain, which is far from an ideal app= roach.

And by the way, this is the mailing l= ist.

Regards.

Em dom., = 16 de nov. de 2025 =C3=A0s 20:00, Alexandre <alexandre.lg99@gmail.com> escreveu:

Hi,
I=E2=80=99m submitting this feature request to explore how Bitcoin could be= tter=20 withstand extreme, long-lasting infrastructure failures caused by major=20 solar events. Before explaining the request itself, I want to provide a=20 brief overview of what these events are, because their scale matters.

A large solar storm occurs when the Sun emits an intense=20 burst of charged particles and electromagnetic energy. When this=20 material reaches Earth, it can disturb the magnetic field and induce=20 strong electric currents in long conductors such as power lines. In=20 extreme cases, this can damage transformers, overload electrical grids,=20 interrupt satellite operations, and disrupt long-distance communication=20 systems. The most famous historical example is the Carrington Event of=20 1859, the largest geomagnetic storm ever recorded. It triggered=20 worldwide telegraph failures, fires in equipment, and intense auroras=20 seen far from polar regions. Modern research suggests that a=20 Carrington-level event striking today could cause regional or=20 continental power grid failures lasting days to months, as well as major internet and satellite disruptions.

The issue for Bitcoin is that these types of events could= =20 fragment the network into isolated regions unable to communicate for=20 extended periods. Each region might continue mining independently,=20 creating separate versions of the chain. When connectivity eventually=20 returns, deep chain splits and long reorgs could occur. Although=20 Bitcoin=E2=80=99s consensus rules can handle this mechanically, the practic= al=20 impact on users, operators, and services would be significant.

The purpose of this feature request is not to propose=20 consensus changes, but to explore whether Bitcoin Core could improve=20 resilience and operational clarity in such extreme scenarios.=20 Specifically:

Degraded communication support
Consider improving documentation or optional tooling for running nodes=20 over degraded or intermittent communication channels such as HF/VHF=20 radio links, mesh networks, or intermittent satellite reception. These=20 channels exist today in experimental form but may benefit from more=20 formal guidance or optional integration.

Operator guidan= ce
Document best practices for wallets, miners, and node operators during=20 extreme, high-latency, or partitioned network conditions to minimize=20 user disruption during future reconnection events.

This = request is simply to consider whether these=20 improvements fall within Bitcoin Core=E2=80=99s scope, or whether they shou= ld be handled entirely by external projects. If this discussion belongs on=20 the mailing list first, I=E2=80=99m willing to move it there.

Thanks for your time and any feedback.


--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.googl= e.com/d/msgid/bitcoindev/d9f4f899-14d1-4787-8046-acd59ff1ba98n%40googlegrou= ps.com.


--
Edil

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/ms= gid/bitcoindev/CANJiN3LnCFJxJpGxScLTqT2JF4iQNsX3hipiNiBK_OLMkkXb1g%40mail.g= mail.com.
--000000000000f96ce60643f59352--