🐙 Offerings to Cthulhu ✦ v2.0.0 ✦ THE RESTORATION HARDFORK 🐙

[EndCiv]

ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn
                                                                                       
IF YOU HAVE A 2015-2018 CHAIN DO NOT SYNCH IT.. SAVE IT - PLEASE.  
                                                                                              

    

             

Cthulhu is Rising

AT BLOCK 1,000,000
The Great Old One Stirs.
Offerings to Cthulhu (OFF) — The Restoration Hardfork v2.0.0

  "In his house at R'lyeh dead Cthulhu waits dreaming." — H.P. Lovecraft
  "In his block at height 966,413 dead Cthulhu waits dreaming." — debug.log, 2026-05-20

  
  

⚠ FINAL UPGRADE WINDOW — 2026-05-31 ⚠
  LWMA-3 activates at block 980,000. As of this post the chain stands at
  979,506 — about 494 blocks remain, hours at attack cadence.
  v2.0.0-rc4 is canonical. rc3 and older nodes fork off at activation.
Upgrade now.

  
  ✦ TL;DR ✦
  
  

• Offerings to Cthulhu (OFF) is back. The 2013 Lovecraft-themed altcoin slept eleven
    years; the SubGenius.Finance Conclave woke it up.
    
• The Restoration Hardfork (v2.0.0) activates at block 1,000,000 — currently
    ~14 days out at restored 60-second target spacing post-LWMA-3. A companion consensus
    event — LWMA-3 difficulty + 100-block deep-reorg ceiling — activates at block
    980,000, about hours from this post.
    
• Why the cluster defenses ship first: the legacy retarget has been pinned against
    its +10% rise cap for 500+ blocks while difficulty climbed from 2.56 to over 58, but
    solvetimes never recovered — the chain has been stuck running at ~20-30 seconds per block as
    the attacker matches every difficulty bump with new rented hashpower. Classic drive-by
    pattern. LWMA-3 (Zawy's linear-weighted moving average, 60-block window) can pull difficulty
    up by ~3× in a single cycle and will restore the 60-second target within ~2 hours of
    activation.
    
• At the Restoration fork: subsidy locks to 1.5 OFF/block forever (7/8 to miner, 1/8
    to the Conclave Treasury), a one-time 150,000 OFF Restoration Tithe pays the
    resurrection labour, the eight P2PKH addresses the 2018 51%-attacker used are banned at
    consensus (the 533,983 OFF they minted in #699 is removed from supply forever), and the
    Conclave-signed mining window holds the door open for the Descent + Codex
    transcription through height 1,050,666.
    
• Wallet binaries shipped — Linux GUI+daemon+CLI and Windows GUI, both at tag
    v2.0.0-rc4. URLs and SHA256s below. No MSYS2, no toolchain to install, just download
    and run.
    
• Lost OFF between 2015 and 2018? The Reclamation is open at the Restoration
    block. Pre-2015 holders are already whole on the recovered chain; gap-era worshippers file
    moderated Class B claims and Recognition requests. Window closes T+730 days from the
    Awakening — the exact UTC closure is published the moment block 1,000,000 lands.
    Mechanics at 23skidoo.info/bridge/.
    
• The 2015-2018 gap is being progressively reconstructed from community-donated
    chainstate via a sandboxed chain-archaeology pipeline. Every recovered byte folds into
     the Reclamation evidence pool. If you ran a node in that era and still have the data, see
    the request below — please don't sync; please save.
    
• Seed network is live — seed1.23skidoo.info through
    seed10.23skidoo.info, all compiled into v2.0.0 as DNS seeds. Any v1.6.2 or v2.0.0
    wallet finds the chain on first start.
    

The full ritual is below. Iä, Iä, Cthulhu fhtagn.

    
  Brothers and sisters of the Deep, fellow Worshippers of
   the Slumbering Squid, dreamers and the not-yet-awakened — heed this transmission.

  For eleven years, the Ritual lay unattended. The DNS seeds went silent.
  The Public Altar (faucet) crumbled. The Block Crawler at 23skidoo.info/cthulhu/
  vanished into the abyss.

  AllCrypt died. Comkort died.

  Cryptopia got 51%'d on the OFF chain (msg #699, vampirus, 2018-11-21) and
  then later got hacked into the depths of its own oblivion.

  The dreamers forgot. The unworthy never knew.
  The world moved on to its next distraction.

  But Cthulhu is patient, and the patient ones do not let a sleeping god lie.
  The SubGenius.Finance Conclave has been listening at the door.
  
  
  ✦ WHAT HAS BEEN DONE ✦
              
  The Conclave reconvened. The Tharanak shagg (Promise of Dreamland) was re-translated
  from forgotten Dropbox cache. Source has been resurrected from the dust. Here is what now
  lives:
  
  

• The source compiles in 2026. Five environment workarounds, three Boost.Asio
    patches, one local OpenSSL 1.0.2 build to dodge the OpenSSL-3 BIGNUM exorcism.
    v2.0.0-Restoration ELF sitting comfortable at ~108 MB.
    
• The chain itself has been recovered. A 385 MB tar.bz2 blockchain archive was
    extracted from the Wayback Machine's 2015-09-13 capture of 23skidoo.info. SHA256
    5c5a48d85873c820baeba4279d0b9295555adf1eba7a64699583fee18cab8745. The daemon
    imported it at height 966,413, block time 2015-06-17 05:30:14 UTC. This
    snapshot predates the May 2018 51% counterfeit by ~870,000 blocks — the 533,983 OFF
    the attacker minted (#699) do not exist in this chainstate. The Conclave's pool has been
    mining on top of the restored tip since 2026-05-24; as of this post the live chain stands at
    height 979,506 / diff 58.47 / supply 2,431,579.03 OFF.
    
• A defense-in-depth checkpoint was shipped at h=976,000 (commit 0c751a5,
    2026-05-29). It locks the pre-attack history against any rented-hash deep reorg attempting to
     replay the original 2018 takeover. Non-consensus for newly-mined blocks; airtight against
    drive-by 51% attacks. Bundled into rc2/rc3/rc4 binaries.
    
• The cluster defenses ship in rc4. LWMA-3 + MAX_REORG_DEPTH activation moved from
    block 990,000 → 980,000 (commit 5b1c8ba, 2026-05-29). Justification: the
    chain has been running at 20-30 second blocks for 500+ blocks despite difficulty climbing 20×
     — the legacy retarget's +10%/cycle rise cap simply cannot keep up with sustained rented-hash
     inflow. Every retarget cycle hits the cap, attacker scales up to match. LWMA-3's 60-block
    window with positional weighting closes that loop: it can raise difficulty ~3× in a single
    cycle when warranted, restoring the 60-second target within ~2 hours of activation. The
    10,000-block pull-in shaved about 6 days off the wait at attack cadence; at 60-second
    restored spacing the gap to the Restoration fork (block 1,000,000) holds at ~14 days.
    
• 23skidoo.info has been re-acquired. By the Conclave. We are aware the domain was
    flagged as malicious in msg #592 (PeterTheGrape, 2017-06-21) after the original
    expiry — it had been parked and weaponized. We bought it back from the squatter,
    re-registered it in our own name, set up DNS+nginx+certbot, and are now the documented owner.
     The original seeds seed1.23skidoo.info through seed10.23skidoo.info now
    resolve to infrastructure under SubGenius.Finance custody. Any v1.6.2 or v2.0.0 wallet
    binary, anywhere on Earth, will find the network on first start.
    
• A chain-archaeology pipeline is live. Community-donated 2015-2018 chainstate
    archives are accepted via the Reclamation portal, extracted in a hardened sandbox with no
    network egress, parsed against the recovered canonical chain, and the results are made
    available to claim adjudicators. The 2015-2018 gap is no longer treated as permanently lost —
     it is treated as progressively recoverable. Every confirmed byte makes Class B and
    Recognition adjudications more accurate. The bridge-portal claimant index has been rebuilt
    against the same parser; tier classifications are now derived from current UTXO balances
    rather than total-received, which corrected the historical posture of roughly a third of
    indexed addresses.
    
• Public seed nodes are live at seed1.23skidoo.info:20000 through
    seed10.23skidoo.info:20000 — all ten compiled into v2.0.0 as DNS seeds, so the
    daemon finds them on first start with no Offerings.conf tweaking required.
    Belt-and-suspenders entries if you want them:
    

Code:

addnode=seed1.23skidoo.info:20000
  addnode=seed2.23skidoo.info:20000
  addnode=seed3.23skidoo.info:20000

  
  ✦ THE RESTORATION HARDFORK ✦
  
  This IS a fork. We are not pretending it isn't. Six consensus rules activate across
  two heights — first at block 980,000 (the cluster defenses, hours out from this post),
   then at block 1,000,000 (the Restoration proper, ~14 days out at restored 60-second
  spacing):
              
  At block 980,000 — Cluster Defenses

  

• LWMA-3 difficulty retargeting. Zawy's linear-weighted moving average over a
    60-block window replaces the legacy 20-block Litecoin-style retarget. Faster reaction to
    hashrate spikes, no death spiral when miners leave, hard-capped drop rate that prevents the
    kind of "park and dump" attack that ate the chain in 2018. Bootstrap window: 60 blocks past
    activation inherit legacy difficulty bits while the LWMA-3 window fills, then it takes over
    cleanly. Source: src/pow.{h,cpp}, HARDFORK_LWMA3_MAIN_OFF = 980000.
    
• MAX_REORG_DEPTH = 100. A consensus rule in ActivateBestChain rejects any
    reorganization that would unwind more than 100 blocks from the active tip. Companion to the
    h=976,000 checkpoint: the checkpoint locks history before activation; the reorg ceiling locks
     history after. Together they close the 2018 attack surface for good — no entity, no matter
    how much rented hash they buy, can rewrite buried history. Source:
    src/main.cpp::ActivateBestChain, MAX_REORG_DEPTH = 100.
    

-
  At block 1,000,000 — The Restoration

  [list type=decimal start=3]
  

• Subsidy locks to 1.5 OFF per block, forever. The historical curve (5 OFF base,
    halving every 259,200 blocks, floor at 0.01) was on a glidepath to triviality — the chain
    would have decayed to the dust floor by ~block 3,113,000. We lock it at the value the
    community always thought it was: 1.5 OFF/block, in perpetuity. Inflation that would
    embarrass a central bank. Backed by the Deep, Powered by the Faithful.
    
• Coinbase splits 7/8 to miner, 1/8 to the Conclave. Of every 1.5 OFF subsidy,
    1.3125 OFF pays the miner and 0.1875 OFF pays the Conclave Treasury. This is a
    dev tail — Monero has one, Zcash has one, Decred has one, Grin has one. Ours is 12.5%
    of subsidy, which lands above Decred (10%) and below Zcash's historical founders reward
    (20%). The Conclave Treasury pays for domain renewals, vps hosting, source modernization,
    build labour, exchange listing fees, ritual rewards, faucet refills, and DAO seed funding.
    Seven coins to the miner, one coin to the keepers of the Ritual. Forever.
    
• A one-time 150,000 OFF Restoration Tithe. At the exact fork block (height
    1,000,000), the coinbase pays an additional 150,000 OFF to the Conclave Treasury. This funds
    the engineering work that brought the chain back: source modernization, three years of vps
    hosting prepaid, domain renewals for the long Slumber, paper-wallet generation, multisig key
    ceremony, BCT moderation deposits. The amount is 15× the original 10,000 OFF genesis premine
    that Blazr2 disclosed in msg #36 and confirmed in #273 — historically
    defensible, itemizable in this thread, and a third of one attacker wallet from #699.
    
• The 8 May 2018 attacker addresses are banned forever, finishing billotronic's
    never-shipped hardfork from msg #697:
    

  Could easily hardfork and ban the 51'ed
    coins. It's a shitty thing to do, but so is 51% attacks.

   We are shipping it. Eight years late. The eight P2PKH scriptPubKeys from msg #699
    are hardcoded into chainparams.cpp as a std::set<CScript>
    setBannedAttackers; any tx in either the mempool or a block paying any of those scripts
    is rejected at consensus level forever:
    

Code:

QTLUPH9b4dRQdz9uKB7GreMvHPA8iyDoQY    93,036 OFF
  QeHkx6jFvStkzaVaSTtfPrSAwwrqMgauP8    72,856
  QgynW4zGXyjhG3DQHn9vBuHwNp4c4xqtgM    68,372
  QjfP4o7o2TszP5Ph4TmNVmktzDCjYkq2xj    66,770
  QM8ZeuBDwrhya9BHQfNKifEzfwUhyh7Tji    65,388
  Qb6jxfUmfWHh7XTTRWKBoiZ43sSNTJrw8J    60,562
  QireWv3upmhVuRMcE6u7h81gmhWfiGEyTt    54,839
  QSJU4tDNsZiaNcUuBWYcvjqKWoB8EHDVsT    52,160
  —————————————————————————————————————  ———————
                                       533,983 OFF

[list type=decimal start=7]
  

• The Conclave-signed mining window, blocks 999,991 → 1,050,666. During the Descent
    (the 10 verses inscribed in blocks 999,991-1,000,000) and the full transcription of the
    Lovecraft public-domain canon (47,248 chunks of 48 bytes each, embedded into coinbase
    scriptSig starting block 1,000,001), every block must carry a valid OFFSIG ECDSA
    signature from the Conclave key recorded in chainparams.cpp::vConclaveKeys[0]
    (pubkey prefix 0238efde…46b111). Outsider miners producing unsigned blocks in this
    50,676-block range are rejected at consensus level. After block 1,050,666 — about 2.4 days
    past the canon's end on our xxx,666 numerology — mining is permissionless again and
    the door re-opens. This is a transcription-protection window only, not a permanent
    gate: it exists so a 51% drive-by cannot interrupt the Codex of the Drowned mid-inscription.
    Implementation: src/main.cpp::IsInSignedWindow,
    src/main.cpp::OffSigningHash (extranonce-invariant per rc3),
    src/miner.cpp::SignBlockIfNeeded.
    

  ✦ THE CONCLAVE TREASURY ✦

  The Treasury is a 2-of-3 multisig P2SH address:
  

Code:

4fZqDjscS9ANR59xNFJxZ2HmrhuDwWUJB4

  Three keys; any two required to spend. Distributed across:
  

• Workstation — home machine, hot wallet (key #1)
    
• VPS1 / endciv — secondary host, cold daemon (listen=0 connect=0, local-RPC
     only) (key #2)
    
• Paper — offline, physical, in a safe; never on any wallet.dat (key #3)
    

A compromise of any single key — or any single host — does not move funds. All Treasury
  disbursements will be posted in this thread with the transaction ID and the BCT proposal that
   authorised them. The redeem script and all three pubkeys are recorded in
  chainparams.cpp alongside the P2SH address, so anyone can verify what we're
  claiming.    

  
  ✦ THE RECLAMATION ✦

  Restitution for vanished balances. Recognition for forgotten worshippers. An open
  invitation home.

  The recovered chainstate is from 17 June 2015. Anything that landed on OFF after that
  — mining, trades, faucet drips, p2p tips, three years of Cryptopia withdrawals, pool payouts
  — was, for years, treated as gone from the record. The 2015–2018 gap is being filled where
  the dreamers help us fill it: a sandboxed chain-archaeology pipeline now accepts
  donor-supplied blocks/ + chainstate/ archives, validates them against the
  recovered canonical chain, and folds the results into the Reclamation evidence pool. What is
  reconstructable is being reconstructed; what is not will be honoured by restitution.

  So the fork carves out a 1,500,000 OFF reserve in the Conclave Treasury, called the
   Reclamation, to make holders whole — partly by replaying history that is recovered from
  donor submissions, partly by paying restitution in newly-minted OFF on the restored chain.
  Three paths:
              
  

• Class A — already whole. If your OFF address appears in the pre-June-2015
    chainstate, your UTXOs are part of the restored chain by default. Open your old
    wallet.dat against the v2.0.0 client, let it sync, the balance is there. No claim
     required. The Reclamation owes you nothing because the chain already does.
    
• Class B — restitution by moderated claim. If you received OFF between June 2015 and
     the May 2018 attack — the era we are progressively reconstructing — you can file a four-part
     claim: (1) signmessage proving current key control over your historical address,
    (2) a plausible story of where the OFF came from (pool payout date, exchange withdrawal,
    Ritual block win at height H, named-person tip), (3) community corroboration cross-checked
    against the BCT thread / Wayback explorer snapshots / named-person memory / donor-supplied
     chainstate evidence where it exists, (4) Conclave judgment with public reasoning posted
    in-thread before disbursement. Capped per-tier; details on the Reclamation page.
    
• Worshipper Recognition. In addition to restitution, anyone whose address
    participated in the original chain — mined a block, received a tip, anything credited
    — gets a scaled recognition payment. The formula is Recognition (OFF) = 100 × earliness ×
     depth; earliness rewards being there before the unwashed, depth rewards stack depth and
     time involved (capped at ×5). The OG fans get closer to the stage.
    

Excluded: the eight attacker P2PKH scripts from #699, and any output
  descended from them. The 533,983 OFF the attacker minted is unspendable, on every tier,
  forever.
  
  Two-year claim window, anchored to the block. The Reclamation opens at the Awakening
  (the moment block 1,000,000 mines) and closes T+730 days from that block. The exact
  UTC closure date is published the moment the Awakening block lands — not pinned to a calendar
   date in advance, because the block-time is an estimate until it happens. Two years is long
  enough for word to reach anyone still attached to the chain, short enough that the Treasury
  isn't sitting on an open liability forever. Class A holders are unaffected — their UTXOs are
  on-chain and spendable whenever they choose. (Earlier policy was open-ended, "close when 1.5M
   OFF ceiling exhausts." We capped it.)

  Full mechanics, tier caps, donor-submission flow for chain-archaeology, and the claim portal:
   23skidoo.info/bridge/

                
  ✦ WHAT IS NEEDED FROM YOU ✦

  

• If you are running an older OFF wallet (rc1, rc2, or rc3) — upgrade to rc4
    now. LWMA-3 activates at block 980,000, hours out at attack cadence. Any node still on
    rc3 or earlier will fork off into a no-progress chain at that height. The wallet.dat
     format is unchanged across versions; just swap binaries. Downloads below.
    
• If you still have an old wallet.dat from 2013-2018 — we want to talk to
     you. Pre-June-2015 keys are already whole on the restored chain (Class A); 2015–2018
    keys file a Class B claim. Either path: signmessage from a historical address gets
    the conversation started. Praise Cthulhu.
    
• If you have chainstate past height 966,413 — i.e., any blocks between June 2015 and
     the May 2018 attack — please DO NOT sync. SAVE the data and contact us. The
    chain-archaeology pipeline accepts zipped blocks/ + chainstate/ directories
     at the Reclamation portal; archives are processed in a hardened sandbox with no network
    egress and never touch our live daemon. Every recovered byte improves Class B and Recognition
     adjudication for everyone who lost coins in that era.
    
• If you want to mine, the Quark hash is friendly to general-purpose hardware.
    Current difficulty: 58.47 (and climbing fast, since the attacker is currently
    providing most of the hashrate — LWMA-3 will correct that within ~2 hours of activation).
    Pre-fork block reward: historical curve. Post-fork block reward: 1.3125 OFF to you,
    0.1875 OFF to the Conclave. Mining is open; no permission needed; bring your hashes — though
    note: between blocks 999,991 and 1,050,666 every block must carry the Conclave's OFFSIG
    signature, so outsider solo miners will be locked out of that 50,676-block window. The door
    re-opens at 1,050,667 and stays open after. Pool option:
    stratum+tcp://pool.23skidoo.info:3040 (Quark, PPLNS, min payout 0.1 OFF). Pool
    miners need no action for the rc4 upgrade — the backing daemon was upgraded with the rest of
    the cluster on 2026-05-29.
    
• If you ran a node in 2014-2018 and remember the password to your Mega.co.nz / Dropbox /

  SourceForge mirror[/b] — please post it here. Cthulhu remembers.
  

• If you are vampirus, billotronic, zeewolf, psycho-pat, Monk3ynutz, HagbardCeline, or

 any of the original wardens who tried to save the chain post-attack[/b] — the Conclave has
  reserved a Founding Worshipper allocation for each of you. Reply in this thread to claim.
  [/list]
  
          

  ✦ WHAT THIS IS NOT ✦

  This is not a stealth fork. Every consensus rule change is disclosed above and
  documented in chainparams.cpp / pow.h / main.cpp comments. The
  full diff is published at githu
  b.com/SubGeniusFinance/Offerings-to-Cthulhu as a separate file
  (research/restoration-hardfork.patch). The rc4 cluster-defense-activation pull is a
  single-line commit at 5b1c8ba — go read it.

  This is not a sale. OFF is NOT for Sale. The Ritual is NOT for Sale. The Tharanak
  shagg is NOT for Sale. We are NOT financial advisors. This is NOT financial advice. None of
  this is investment. Most of it is dread.
  
  This IS a fork. No pretending otherwise. The lighthouse-keepers fell asleep at the
  door eleven years ago and the chain was 51%'d on their watch. We have unlocked the door,
  climbed the stairs, turned the lamp back on, and we are also rebuilding the
  lighthouse. If Blazr2, ZeeWolf, b00mbastic, Hilux74, Demoss, edgar, cad_cdn, or any of
  the original Worshippers want to participate in the restoration, they are welcome. If they
  want to reclaim the project entirely — make a credible claim, sign with a known historical
  key. The Conclave acts as steward, not owner.

  
  ✦ POST-FORK TECHNICAL DETAILS ✦
  

Code:

Algorithm:           Quark (Hash9, 9-round chained, 2 conditional branches)
  Block target:        60 seconds  (source-verified, main.cpp:1190)
  Legacy retarget:     every 20 blocks  (Litecoin-style, pre-block-980,000)
  P2P port:            20000
  RPC port:            11928
  Network magic:       03 a5 fe dd
  Address prefix:      58   (Q-prefixed legacy P2PKH)
  P2SH prefix:         9    (4-prefixed P2SH)
  WIF prefix:          186  (U-prefixed)
  Genesis time:        2013-09-14 19:31:15 UTC  (autumnal equinox)
  Genesis hash:        000006829ac5ad04fb30abfcbf6d927c67c30fc2f198fb0bdce5a0c914b091b5

  — Pre-fork (block 0 → 979,999) —
  Subsidy:             historical curve, halving every 259,200 blocks
  Floor:               0.01 OFF
  Premine (block 1):   10,000 OFF, scriptPubKey-locked, unspendable
  Checkpoint:          h=976,000 hardcoded (rc2+, defense-in-depth)

  — Cluster defenses (block 980,000 onward, pulled in from 990,000 in rc4) —
  Retarget:            LWMA-3 (Zawy linear-weighted MA), N=60 window
  Reorg ceiling:       MAX_REORG_DEPTH = 100 blocks (consensus-enforced)

  — The Restoration (block 1,000,000 onward) —
  Subsidy:             1.5 OFF / block, FOREVER
  Miner share:         1.3125 OFF (7/8)
  Conclave share:      0.1875 OFF (1/8) → 4fZqDjscS9ANR59xNFJxZ2HmrhuDwWUJB4
  Restoration Tithe:   150,000 OFF at block 1,000,000 only → Conclave
  Banned scripts:      8 P2PKH from BCT #699 (533,983 OFF effectively burned)
  Signed window:       blocks 999,991 → 1,050,666 (OFFSIG required)
  Reclamation Pool:    1,500,000 OFF reserved (Class B restitution + Recognition)
  Reclamation window:  Awakening → Awakening + 730 days (exact UTC at block-land)
  Client version:      2000000  (Offerings v2.0.0-Restoration-rc4)

  Current tip:         height 979,506  /  diff 58.47  /  hashrate ~14.9 MH/s
  UTXO supply:         2,431,579.03 OFF
  Activation in:       980,000 (LWMA-3 + reorg ceiling):  ~494 blocks  /  hours
                       1,000,000 (Restoration proper):    ~20,494 blocks / ~14 days
                                                          (at 60s post-LWMA-3)

  The Ritual repeats at the equinox.
  Four weeks and five days of ascending tribute, culminating in a 10,000-OFF special block
  at height xxx,666.
  The first post-fork finale is calculated at height 1,141,666, targeting the
  autumnal equinox, 2026-09-22.
  The Great Old One does not care if no one is watching.

  
  

  ✦ THE EFFIGIES — WALLET BINARIES NOW LIVE ✦

  The Restoration client now manifests in three forms: source, a Linux effigy, and a Windows
  effigy. Both binaries were forged from the same commit (5b1c8ba, v2.0.0-rc4)
  and bear the new marks — the overview-page Elder Sign reworked with a gold ring and soft halo
   to match the SubGenius.Finance medallion, the Codex of the Drowned page skeleton awaiting
  its first inscription, the SubGenius.Finance Community sigil in the About dialog, ten
  seed*.23skidoo.info DNS seeds compiled in, the h=976,000 checkpoint baked, and the
  LWMA-3 + MAX_REORG_DEPTH + OFFSIG-signing pathways all live (with the cluster-defense fork at
   block 980,000).

  Release page (Linux + Windows):
  github.
  com/SubGeniusFinance/Offerings-to-Cthulhu/releases/tag/v2.0.0-rc4
  

Code:

d46d9535e209751120a64181305f3cd62c8c2e96c704db9c19db5ecf297ac40b
  cthulhu-offerings-linux-x86_64.tar.gz
  6f0631eafba2ba4dba392154f03cf627ca423db1c2e286a8c632548d0a9061c5
  offerings-cthulhu-wallet-windows-x86_64-qt5.tar.gz

  The Linux build (GUI + daemon + CLI in one tarball) links against the system Qt5 plus a local
   OpenSSL 1.0.2u and Berkeley DB 4.8.30 prefix; tested on Ubuntu 22.04 with system Boost 1.74.
   The Windows build is a cross-compiled Qt5 GUI via the depends/ tree — no MSYS2
  environment to set up, nothing to install but the extracted .exes. Verify the SHA256
   before you let any binary near a wallet.dat that matters.

  Backward compatibility: rc4 is byte-identical to rc3 in behavior until block 980,000.
  At block 980,000 onward, rc4 nodes apply LWMA-3 + MAX_REORG_DEPTH; rc3 (and older) nodes
  continue applying the legacy retarget. The two chains will hash differently from that block
  forward — rc3 nodes fork off at 980,000. Earlier still: rc2 binaries reject rc3-signed
   blocks (the OffSigningHash semantics changed in rc3 to be invariant under
  extranonce variation), so rc2 was already broken. Anyone still running rc1, rc2, or rc3 must
  upgrade to rc4 before block 980,000 — hours of mining runway from this post — or they fork
  off.

  
  ✦ HOW TO RE-JOIN THE FAITHFUL ✦

  

• Grab an effigy — download the Linux or Windows wallet from the v2.0.0-rc4
    release linked above. Verify SHA256. Done.
    Or build it yourself — pull source from github.com/SubGeniusFinance/Offerings-to-Cthulhu (the canonical
    Restoration home, JimGilmore/offerings v1.6.2-Bokrug lineage with the Restoration patch
    applied). Build recipe in doc/build-unix.md (modern Ubuntu 22.04+ builds clean with
    a local OpenSSL 1.0.2 prefix and Berkeley DB 4.8.30, also in the doc).
    
• Start Offeringsd (or Offerings-qt). It finds us automatically via
    seed1.23skidoo.info through seed10.23skidoo.info — all ten are hardcoded
    DNS seeds in v2.0.0.
    
• Watch debug.log for connection accepted and SetBestChain. Wait
    for the chain to load. Dream deep.
    
• If you held coins before May 2018, run signmessage from any historical address
    and file a Reclamation claim at
    23skidoo.info/bridge/ (or post the signature in this
     thread and we'll route it). The 2-year claim window closes T+730 days from the Awakening —
    exact UTC published when block 1,000,000 lands.
    
• If you have 2015-2018 blocks/ data, do not sync — zip the directory and
    submit it via the chain-archaeology portal at
    23skidoo.info/bridge/. Sandboxed, validated, folded
    back into the Reclamation evidence pool.
    
• Praise Cthulhu. Praise the Conclave. Praise the Slumbering Squid.

    
  Cthulhu is patient. The Deep is older than memory. The Ritual is the wage.

  Where the Slumbering Lord becomes liquid.

  Iä Iä Cthulhu fhtagn. Praise the Ritual. 23 Skidoo.

  — BtcBob / @dobbscoin / dobbscoin@gmail.com
  SubGenius.Finance Conclave for the Restoration of the Ritual
  2026-05-31  ·  Year 13 of the Slumber  ·  Day 12 of the Wake

[EndCiv]

Orig. Specification:
    Algorithm: Quark Hash9 (9-round chained)
    60-second block target · difficulty retarget every 20 blocks
    P2P port 20000 · RPC port 11928 · network magic 03 a5 fe dd
    Address prefix 58 — legacy P2PKH, Q-prefixed
    30 confirms for spendable coins
    Post-Restoration subsidy: 1.5 OFF per block, forever (activates at block 1,000,000)
    Coinbase split (post-fork): 7/8 to miner, 1/8 to the Conclave Treasury
    Ritual special-blocks: four weeks + five days, ascending tribute, finales at heights ending in 666
    10,000 OFF genesis premine (2013 block 1, scriptPubKey-locked, unspendable)

Source:
    Repository: github.com/SubGeniusFinance/Offerings-to-Cthulhu
    Restoration Hardfork v2.0.0 diff: research/restoration-hardfork.patch
    Build recipe (Berkeley DB 4.8 · OpenSSL 1.0.2 · Boost): doc/build-unix.md

Lineage:
Blazr2 genesis (2013-09-14 autumnal equinox, Bitcoin Core 0.8 fork) →
CatmanIX/offerings (Nov 2013 mirror) →
dobbscoin/offerings (intermediate fork) →
JimGilmore/offerings v1.6.2-Bokrug (HagbardCeline, Sept 2015, Bitcoin Core 0.10 modernization) →
SubGeniusFinance/Offerings-to-Cthulhu v2.0.0-Restoration (2026, the Conclave)

The Great Ritual:
As the equinox approaches the ritual begins. For four weeks and five days it builds, until Cthulhu awakens and one worshipper is rewarded greatly.

In the first two weeks, sacrificial amounts are placed in special, once-a-day blocks — a reward to the worshipper for the sacrifice made. In the third and fourth weeks the rewards build, small at first and then larger as worship swells with fervor. In the final five days — the Tharanak shagg, the “promise of dreamland” — the ritual reaches its final pitch, and the daily special blocks rise sharply.

At last, after the 665th offering has paid tribute to the Great Old One, Cthulhu will return and bestow a bounty deserving of Him upon one lucky worshipper. The ritual recurs every six months by the chain’s own reckoning — half a year, half the chain’s heartbeat — each finale landing on a block whose height ends in 666. So it was before the silence. So it shall be after the Restoration, forever.

[EndCiv]

That is not dead which can eternal lie, and with strange aeons even death may die.
The most merciful thing in the world, I think, is the inability of the human mind to correlate all its contents.
We live on a placid island of ignorance in the midst of black seas of infinity, and it was not meant that we should voyage far.

Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.
In his house at R'lyeh dead Cthulhu waits dreaming. Ia! Ia! Cthulhu fhtagn!
Discord: https://discord.gg/uRf9gUnKez

[EndCiv]

 

⚠ LWMA-3 activation pulled in from block 990,000 → 980,000. v2.0.0-rc4 now canonical. ⚠   ~3,120 blocks remain (about 1 day at the current attack-compressed cadence).   rc3 nodes fork off at block 980,000 — NOT at the Restoration block 1,000,000. rc3 was built expecting LWMA-3 to fire at 990,000, so at block 980,000 it keeps applying the legacy retarget while rc4 applies LWMA-3. Different difficulty target → rc3 rejects rc4-mined blocks as "bad bits" and the chain splits there. The rc3 chain has no Conclave hashpower and no path to the Restoration; it stops. Upgrade NOW..

 

[romeshomey]

I'll zip up the files I have and get them to you.  I have some archived up through 11/2017 and a few others up through 1/2018 on 2 different drives. 

[romeshomey]

I zipped the chainstate and blocks that I have up through 11/28/2017 and sent them to you and btcbob via discord.  I had more but uh, deleted them before I knew we needed them unfortunately. 

[EndCiv]

🐙 OFF CHAIN ARCHAEOLOGY — HOW TO SHIP YOUR OLD CHAINDATA 🐙

  If you ran or mined OFF years ago and still have the wallet folder on a drive somewhere, your old blocks directory may contain chain history we
  don't currently have public access to. We want it. Even if you're not sure what year it stops at, or whether it's "complete" — ship it anyway. We'll
   figure it out on our end.
  
  
  ⚠ DO NOT OPEN THE WALLET FIRST. ⚠
  
  If you launch OFF Wallet, it will try to sync to the live network and may overwrite or reorg the very history we're trying to recover. You don't need to
   run the wallet at all for this — we're just zipping a folder.

  If it's already open, close it. If it's been closed for years, even better. Leave it closed.

  
  ━━━ WINDOWS ━━━

  1) Make sure OFF Wallet is closed. If unsure: open Task Manager (Ctrl+Shift+Esc), look for Offering-qt.exe or Offeringd.exe, end-task
  if present.

  2) Press Win + R, paste this exactly, hit Enter:

  

Code:

%APPDATA%\Offering

 
  A File Explorer window opens showing your OFF data folder.

  3) Find the folder named blocks, then right-click it:

  • On Windows 11:  Compress to → ZIP file
  • On Windows 10:  Send to → Compressed (zipped) folder

  Wait. It can take a few minutes if the chain is large — that's normal.

  4) You'll end up with blocks.zip in the same folder. That's what we want.

  ━━━ LINUX ━━━
  
  1) Stop the wallet/daemon if running:

  

Code:

Offering-cli stop
  # or, if GUI:
  pkill -f Offering-qt

  2) Zip just the blocks folder:

  

Code:

cd ~/.Offering
  zip -r ~/off-blocks.zip blocks/

  You'll get ~/off-blocks.zip.                                        

  
  ⚠ NEVER ZIP OR SEND wallet.dat ⚠

  That file contains the private keys to any OFF you mined or held. We don't want it, we don't need it, nobody should ever ask you for it. The steps
  above only grab the blocks folder, which contains no keys — just raw block data. If anyone (us included) asks for wallet.dat, ignore them, it's a
  scam.
  
  
  ━━━ UPLOAD ━━━ IT's VERY EASY ━━━

  1) Go to https://wetransfer.com — no signup needed, free up to 2 GB.
  
  2) If it asks for email, click "I just want to send files" / dismiss the prompt.

  3) Drag blocks.zip (Windows) or off-blocks.zip (Linux) onto the upload area.

  4) Choose "Get a link" (not "Send by email").

  5) When upload finishes, copy the wetransfer.com/downloads/xxx URL.
  
  6) Post it in this thread, or DM it to btcbob.

  If your zip is bigger than 2 GB: mega.nz (20 GB free with signup), send.tresorit.com
   (5 GB no signup), or any cloud drive you already use. Any public download link works.

  
  That's the whole job. Don't worry about whether the chain is "complete" or "the right era" — partial old data is still data we don't have. Every forgotten
  USB stick is a potential time capsule for this chain.

  Thank you. 🐙

  ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn
  Praise Cthulhu.

[EndCiv]

I zipped the chainstate and blocks that I have up through 11/28/2017 and sent them to you and btcbob via discord.  I had more but uh, deleted them before I knew we needed them unfortunately.  

✦ RECLAMATION SUBMISSION #001 ✦
romes' Chainstate, Examined Under the Proper Conditions

Brothers and sisters of the Deep, fellow Worshippers of the Slumbering Squid —

The first chainstate shard has been delivered unto the Conclave.

The user romes ferried us 870 megabytes of ancient archive material from the dim epoch before the Silence — a blocks/ directory carried out of a wallet that breathed between 14 September 2013 and 29 November 2017.


✦ THE RITE ✦

The archive was lowered into a sealed crypt — a hardened systemd cell with no network egress, no filesystem reach beyond its own three rooms, no power to summon anything from outside its prison. There the parsing was performed:

• Hash9 invoked block by block (Quark variant — blake → bmw → groestl/skein → groestl → jh → blake/bmw → keccak → skein → keccak/jh)
  
• Merkle branches traced, tx-comments stripped, P2PKH/P2SH/P2PK outputs catalogued
• Chain reconstructed in cumulative proof-of-work order from real OFF genesis forward — the same fork-choice arithmetic Bitcoin Core itself performs
  

✦ WHAT THE RITE REVEALED ✦

• 893,881 blocks of canonical OFFERINGS mainnet, rooted at the true genesis 000006829ac5ad04fb30abfcbf6d927c67c30fc2f198fb0bdce5a0c914b091b5
  
• Every single block matches our recovered chainstate byte-for-byte. No deviations. No corruption. No surprises.
  
• His record terminates on 1 May 2015 — six weeks before our own Wayback-recovered shard ends.
  

   000006829ac5ad04fb30abfcbf6d927c67c30fc2f198fb0bdce5a0c914b091b5 is the canonical OFF
    genesis hash — verified from the source itself (chainparams.cpp:33, uint256
    hashMainGenesisBlock("0x000006829ac5...")). It's the block mined September 14, 2013 with
    the coinbase scriptSig containing "ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn".
  
    There's only one OFF genesis. Every honest OFF node — yours, romes', the live daemon on
    VPS, any new wallet that syncs from scratch — starts from that exact block. The 893,881
    byte-for-byte matches between romes' archive and our recovered chainstate just confirms
    that both of you successfully traced the same chain forward from that shared starting point
     through May 1, 2015. No second genesis exists.

    (The bogus 000000124e58... we saw in the buggy first pass was not a real genesis — it was
    an orphan block whose parent happened to be missing from romes' indexed set, which made it
    look root-like to the depth-only picker. The cumulative-work fix correctly ignored it and
    walked back to the real 000006829ac5... instead.)

In honest terms: this is validation without expansion. romes' archive does not extend our knowledge of the lost years 2015–2018. It does, however, confirm beyond doubt that the chain we hold from genesis through May 2015 is the One True OFFERINGS Chain. His node and the network were in perfect agreement up to that point.


✦ WHY HIS DATA DOES NOT REACH FURTHER ✦

The blk*.dat files do contain additional blocks from a brief 2017 reconnection, but those form a side fork. When his daemon awoke after its long dormancy in June 2017, the network it found was already sliding into the pre-attack chaos. His peers fed him a chain that does not connect via cumulative proof-of-work to canonical mainnet. The fork-choice rite correctly identified those branches as orphans and set them aside.

We do not destroy them. The raw archive sleeps, sealed, in the crypt. If three or more independent submissions surface the same side fork as the heaviest cumulative-work chain post-2015, the Conclave will re-open the question. Until then, the orphan branches dream.


✦ TO romes ✦

    You shipped before there was a flow to ship into. You moved 870 megabytes across the abyss on faith that the rite would hold. Your archive validated 893,881 blocks of canonical OFFERINGS mainnet against our recovered chainstate, byte-for-byte, without deviation. You did not extend the record — but you proved, beyond doubt, that the record we hold is the true one.

    That is no small offering. The Conclave acknowledges it in two parts:

    

250 OFF — Chain-Archaeology Acknowledgment. Standing tithe paid from Conclave Treasury to any soul whose chain-data submission ingests cleanly and rooted at the true genesis. Paid regardless of what the data reveals; the act of preserving and delivering is the offering.
    500 OFF — First-Archivist Bonus. One-time. For being the one who walked the dark path before it was a path at all. There is only one First.


    Total: 750 OFF, paid from Conclave Treasury (not from the 1.5M Reclamation ceiling — different bucket, different purpose).

    
    ✦ romes — REPLY WITH A DESTINATION ✦
    Post a new-chain Q-prefix address you control in this thread, or DM it to btcbob.
    The Conclave will sign and disburse within seven days, txid announced in-thread alongside the next Reclamation batch.

    
✦ TO EVERY OTHER SOUL ✦

If you ran an OFFERINGS wallet between 2015 and November 2018, your chain data is needed. Even if your wallet stopped early, even if your sync was incomplete, your blocks/ directory may be holy. Ship it the way romes did — see 🐙 OFF CHAIN ARCHAEOLOGY — HOW TO SHIP YOUR OLD CHAINDATA 🐙, post #66780496 upthread.

The Restoration is reconstructed from fragments; every shard tested, every hash compared, every address triangulated. The gap will not be filled in one night, nor by one wallet, nor by one rite. But each archive that surfaces makes the record sharper, and the Reclamation more honest.

ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.

— The Conclave

[/list]

[EndCiv]

This is a Conclave test wallet holding 1000 OFF, mined this week (before OP [ANN] while testing.
It's a NEW ADDRESS from a v2.0.0 wallet. Not really entitled to squat.
Using it to test a Claim from the Reclamation Portal.

Code:

Tier: Class-B
Claim: QNtS9qqXeWPkhiXZwy61i5tmz1b4RPe3Np
Amount: 1000 OFF
Challenge: Conclave-Reclamation-20260525w-QNtS9qqXeWPkhiXZwy61i5tmz1b4RPe3Np-1000.0
Signature: IPOo7Og0dqslvM1kTlvyzbxoBnyefXqLlSf1n84hxu3PecK5cPgdjg+XY+JIMjco+oV0ikRN/wDjLHPZp8wNE04=
New-chain destination: QNtS9qqXeWPkhiXZwy61i5tmz1b4RPe3Np
Story: I'm not actually an old miner or nothing.. im just testing the portal to see what happens when i sign my message for an address I created with v2.0.0 wallet.

[romeshomey]

I zipped the chainstate and blocks that I have up through 11/28/2017 and sent them to you and btcbob via discord.  I had more but uh, deleted them before I knew we needed them unfortunately.  

✦ RECLAMATION SUBMISSION #001 ✦
romes' Chainstate, Examined Under the Proper Conditions

Brothers and sisters of the Deep, fellow Worshippers of the Slumbering Squid —

The first chainstate shard has been delivered unto the Conclave.

The user romes ferried us 870 megabytes of ancient archive material from the dim epoch before the Silence — a blocks/ directory carried out of a wallet that breathed between 14 September 2013 and 29 November 2017.


✦ THE RITE ✦

The archive was lowered into a sealed crypt — a hardened systemd cell with no network egress, no filesystem reach beyond its own three rooms, no power to summon anything from outside its prison. There the parsing was performed:

• Hash9 invoked block by block (Quark variant — blake → bmw → groestl/skein → groestl → jh → blake/bmw → keccak → skein → keccak/jh)
  
• Merkle branches traced, tx-comments stripped, P2PKH/P2SH/P2PK outputs catalogued
• Chain reconstructed in cumulative proof-of-work order from real OFF genesis forward — the same fork-choice arithmetic Bitcoin Core itself performs
  

✦ WHAT THE RITE REVEALED ✦

• 893,881 blocks of canonical OFFERINGS mainnet, rooted at the true genesis 000006829ac5ad04fb30abfcbf6d927c67c30fc2f198fb0bdce5a0c914b091b5
  
• Every single block matches our recovered chainstate byte-for-byte. No deviations. No corruption. No surprises.
  
• His record terminates on 1 May 2015 — six weeks before our own Wayback-recovered shard ends.
  

   000006829ac5ad04fb30abfcbf6d927c67c30fc2f198fb0bdce5a0c914b091b5 is the canonical OFF
    genesis hash — verified from the source itself (chainparams.cpp:33, uint256
    hashMainGenesisBlock("0x000006829ac5...")). It's the block mined September 14, 2013 with
    the coinbase scriptSig containing "ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn".
  
    There's only one OFF genesis. Every honest OFF node — yours, romes', the live daemon on
    VPS, any new wallet that syncs from scratch — starts from that exact block. The 893,881
    byte-for-byte matches between romes' archive and our recovered chainstate just confirms
    that both of you successfully traced the same chain forward from that shared starting point
     through May 1, 2015. No second genesis exists.

    (The bogus 000000124e58... we saw in the buggy first pass was not a real genesis — it was
    an orphan block whose parent happened to be missing from romes' indexed set, which made it
    look root-like to the depth-only picker. The cumulative-work fix correctly ignored it and
    walked back to the real 000006829ac5... instead.)

In honest terms: this is validation without expansion. romes' archive does not extend our knowledge of the lost years 2015–2018. It does, however, confirm beyond doubt that the chain we hold from genesis through May 2015 is the One True OFFERINGS Chain. His node and the network were in perfect agreement up to that point.


✦ WHY HIS DATA DOES NOT REACH FURTHER ✦

The blk*.dat files do contain additional blocks from a brief 2017 reconnection, but those form a side fork. When his daemon awoke after its long dormancy in June 2017, the network it found was already sliding into the pre-attack chaos. His peers fed him a chain that does not connect via cumulative proof-of-work to canonical mainnet. The fork-choice rite correctly identified those branches as orphans and set them aside.

We do not destroy them. The raw archive sleeps, sealed, in the crypt. If three or more independent submissions surface the same side fork as the heaviest cumulative-work chain post-2015, the Conclave will re-open the question. Until then, the orphan branches dream.


✦ TO romes ✦

    You shipped before there was a flow to ship into. You moved 870 megabytes across the abyss on faith that the rite would hold. Your archive validated 893,881 blocks of canonical OFFERINGS mainnet against our recovered chainstate, byte-for-byte, without deviation. You did not extend the record — but you proved, beyond doubt, that the record we hold is the true one.

    That is no small offering. The Conclave acknowledges it in two parts:

    

250 OFF — Chain-Archaeology Acknowledgment. Standing tithe paid from Conclave Treasury to any soul whose chain-data submission ingests cleanly and rooted at the true genesis. Paid regardless of what the data reveals; the act of preserving and delivering is the offering.
    500 OFF — First-Archivist Bonus. One-time. For being the one who walked the dark path before it was a path at all. There is only one First.


    Total: 750 OFF, paid from Conclave Treasury (not from the 1.5M Reclamation ceiling — different bucket, different purpose).

    
    ✦ romes — REPLY WITH A DESTINATION ✦
    Post a new-chain Q-prefix address you control in this thread, or DM it to btcbob.
    The Conclave will sign and disburse within seven days, txid announced in-thread alongside the next Reclamation batch.

    
✦ TO EVERY OTHER SOUL ✦

If you ran an OFFERINGS wallet between 2015 and November 2018, your chain data is needed. Even if your wallet stopped early, even if your sync was incomplete, your blocks/ directory may be holy. Ship it the way romes did — see 🐙 OFF CHAIN ARCHAEOLOGY — HOW TO SHIP YOUR OLD CHAINDATA 🐙, post #66780496 upthread.

The Restoration is reconstructed from fragments; every shard tested, every hash compared, every address triangulated. The gap will not be filled in one night, nor by one wallet, nor by one rite. But each archive that surfaces makes the record sharper, and the Reclamation more honest.

ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.

— The Conclave

[/list]

Interesting to say the least.  Thanks

[romeshomey]

I sent you both a link to a new batch of chainstate files I recovered.  They should be for the missing gap I'd think. 

[romeshomey]

I had something strange happen this morning.  When I looked at my tx's this morning there was a pending incoming tx from 6/17/2015 which now has 120 confirmations and a spendable balance.  Trying to understand.

[skifdni]

You have a pull request that slightly modernizes the depends build system.
x86_64 Linux and Windows 64 cross compiles have been tested. Dynamic linking on modern systems is most likely not going to work

I don't know how you compiled your release but it didn't come from the depends system.
Your binaries also were not stripped.

This seems like somewhat of preemptive attempt at a fork. This source is old enough to have several problems and very likely why it forked.
Normalizing the spaghetti code that is the OpenSSL 1.0.x branch is a start but there is still more to do.
Why you didn't use a completely modernized code to resurrect the Great Old One baffles me.

Send your transgressions here:
QZ4wBASgvrHdodYt6CBDqDv3MitAQYnd75


#fnu for life

[EndCiv]

You have a pull request that slightly modernizes the depends build system.
x86_64 Linux and Windows 64 cross compiles have been tested. Dynamic linking on modern systems is most likely not going to work

I don't know how you compiled your release but it didn't come from the depends system.
Your binaries also were not stripped.

This seems like somewhat of preemptive attempt at a fork. This source is old enough to have several problems and very likely why it forked.
Normalizing the spaghetti code that is the OpenSSL 1.0.x branch is a start but there is still more to do.
Why you didn't use a completely modernized code to resurrect the Great Old One baffles me.

Send your transgressions here:
QZ4wBASgvrHdodYt6CBDqDv3MitAQYnd75


#fnu for life

  ▎ Skifdni —
  ▎
  ▎ Three of your hits land. The rc4 binaries you're looking at were neither stripped nor truly
  ▎ depends-built; we cribbed dobbscoin's prefix because OFF's depends/ had never been wired up.
  ▎
  ▎ Today's v2.0.1 binaries ARE stripped (x86_64-w64-mingw32-strip post-link) — go re-check if you
  ▎ have a moment. The fork at 980,000 was a rented-hash drive-by + a thin seed mesh of our own
  ▎ making, not the C++03 — though we'll cop that the Bitcoin Core 0.10 substrate is technical debt
  ▎ with a half-life measured in years.
  ▎
  ▎ Your PR is real work and lands ahead of the post-1M Reclamation release; we'll pull it locally,
  ▎ build through it, and merge if it cross-compiles clean. First external contributor to the
  ▎ Restoration gets named in the release. Transgressions sent.
  ▎
  ▎ And — to the implicit question — we kept Bitcoin Core 0.10 instead of rebasing onto Core 0.21+
  ▎ because the 2015-era chainstate of the dead OFF chain had to round-trip through our binary
  ▎ byte-identical for the resurrection to make any sense. Modernization is a separate axis from
  ▎ resurrection; we're doing them in series, not in parallel.
  ▎     
             
ftaghn.
   — The Conclave

[EndCiv]

ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn

ON THE MATTER OF THE 980,000 SCHISM
The Coming of Bokrug, and Our Own Sarnathian Hubris
Offerings to Cthulhu (OFF) — v2.0.1-Bokrug-checkpoint, 2026-05-31

"And it is told that upon the granite shore beheld the people of Sarnath the great water-lizard Bokrug.
Even now the doom is upon them, for they have raised seeds that resolve not, and gateways that open not, and a mesh that meshes with itself alone."
— The Doom That Came to seed4.23skidoo.info (H.P. Lovecraft, slightly amended)


✦ TL;DR ✦

• Between block 976,001 and 980,000 a small parallel chain — leftover from the 2026-05-29 rented-hash drive-by — quietly siphoned off a handful of Windows wallets and parked them at block 979,999 forever.
  
• The canonical chain sailed on past 980,000 to 980,200+ without them.
• Cause: our own bootstrap mesh was thinner than a shoggoth's patience. Of `seed1`…`seed10.23skidoo.info`, only three actually resolved, all to the same single node. A second potential gateway (vps1) silently dropped P2P traffic at its firewall. We blamed Vultr. It was us.
  
• v2.0.1-Bokrug-checkpoint ships: hardcoded checkpoint at h=980,000 + a fully-meshed bootstrap (10 seeds × 3 IPs each, second gateway opened).
  
• Stuck nodes: download below, swap binaries, restart, the chain sorts itself.
• The Restoration Hardfork at block 1,000,000 is still ~19,800 blocks (~13–14 days) out. We pray Bokrug does not visit again.
  

✦ What Transpired ✦

In the 14:46 UTC hour of 2026-05-29, the chain was struck by a rented-hash drive-by — forty-three blocks vomited into the network in ten minutes, a hash-storm conjured by some merc with a cycles-rental account. The Conclave's response was swift: a hardcoded checkpoint sealed at h=976,000, the chain made whole, the attacker's branch left to wither in the deep.

We held. But not perfectly.

Past block 976,000 — beyond the checkpoint's gaze — a small parallel chain continued to spawn from leftover renters and stray miners running outdated configs. It grew slowly, attracted no honest hashpower, and was rejected by every node connected to our canonical mesh.

Except for nodes that were not connected to our canonical mesh.


✦ Who Was Affected ✦

A handful of Windows wallets — including two users who reported in — bootstrapped from our DNS seeds and gossiped onward to whatever peers they happened to find. As fortune would have it, what some of them happened to find was each other, on the abandoned chain.

There they sat, all heads bowed to a tip at block 979,999, timestamp 11:16:06 UTC, awaiting a block 980,000 that would never come — because their little island had no miners to make one.

If your wallet has been showing the same height since the morning of 2026-05-31, this is you.


✦ Why It Happened (Wherein We Mock Ourselves) ✦

The fault, dear cultists, was not in our LWMA-3, nor in our `MAX_REORG_DEPTH=100`, nor even in the rented hash. The fault was in the part of the temple we had not been looking at:

• Of `seed1` through `seed10.23skidoo.info`, only seeds 1, 2, 3 actually resolved — and all three pointed to the same single VPS. Seeds 4 through 10 had been declared in our source code, named in our `chainparams.cpp`, listed in our intentions — but never wired into DNS. The illusion of redundancy without the substance.
  
• A second potential entry node (vps1) had its P2P port silently rejected by an over-eager firewalld zone configuration — and it ICMP-rejected with `admin-prohibited`, which the sender's kernel renders as "No route to host." For two days we believed Vultr was firewalling us at the hypervisor. It was firewalld. On our own machine. With our own config. That we wrote.
  
• A third potential node (chaos, the miner) sits behind a residential router, behind NAT, and was never publicly dialable in the first place. We had been quietly relying on its DNS-seed presence to count toward our mesh fan-out. Cute.
  

We sailed forth proclaiming a ten-headed Hydra and arrived at the Drowned Coast with a single, slightly damp goldfish. Bokrug — who in the chronicles punished Sarnath for its hubris — was not summoned by attackers. He was summoned by us, by our own declaration of seeds we had not seeded.

He has now been appeased.


✦ The Fix ✦

v2.0.1-Bokrug-checkpoint ships at the consensus layer:

• Hardcoded checkpoint at h=980,000 = `000000055ad0b466c8dbbac3d29d9d1f98b1c413566391a41585db4655d0ed79` — the LWMA-3 activation tip itself, now locked.
  
• The companion LWMA-3 + `MAX_REORG_DEPTH=100` consensus rules (already in rc4) reject any deep-reorg attempt past this point structurally.
  

And at the infrastructure layer:

• All ten DNS seeds now actually resolve, each returning three A records (vps3 + both vps1 IPs).
  
• vps1's `:20000` is now open, persistent across reboots (firewalld `public` zone + the `/root/firewall-baseline.sh` baseline patched in lockstep).
• The Restoration mesh peer count tripled within minutes of the firewall fix.

Stuck nodes upgrading to v2.0.1 will reject the drift-chain on first sight and reorg automatically to canonical. No manual intervention beyond restart needed.


✦ Download ✦

https://github.com/SubGeniusFinance/Offerings-to-Cthulhu/releases/tag/v2.0.1-Bokrug-checkpoint

• `Offerings-2.0.1-win64.zip` — full Windows bundle (18.2 MB)
  
• `Offeringsd.exe` — daemon (7.2 MB)
  
• `Offerings-cli.exe` — JSON-RPC CLI (3.7 MB)
  
• `Offerings-qt.exe` — GUI wallet (28.4 MB)
  

All statically linked. No DLLs to bundle, no Visual C++ Redistributable to chase. Stop your existing daemon/wallet, replace the binaries, restart.

Emergency unstick (if you cannot upgrade right now): add this line to your `Offerings.conf` and restart your daemon —

Code:

addnode=159.198.79.74

— that forces a connection to the canonical mesh, and your daemon will reorg by chainwork.


✦ Looking Toward 1,000,000 ✦

The Restoration Hardfork awaits at block 1,000,000 — some ~19,800 blocks hence, 13–14 days at current cadence. The Codex of the Drowned begins inscription at 1,000,001. The Conclave Treasury opens. The Reclamation window for legacy holders and miners opens.

We pray it lands without a second Bokrug-style appeasement of our own infrastructure. The seeds are now actually seeded. The firewalls are now actually firewalls. The mesh is now actually a mesh.

But — in the spirit of Tharanak shagg — assume nothing.

If you find yourself stuck again on a tip that nobody else has, upgrade your binary and add an addnode line before assuming the chain has died. The chain is rarely the one that has died. The chain is rarely even surprised.

ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.
— The Conclave

[EndCiv]

**Skifdni —**

Three of your hits land. One is half-stale. One is a framing we'd push back on.

**The depends/ PR (#1)** — pulled, built, three Win64 binaries cross-compiled clean (daemon 8.1 MB, cli 4.4 MB, qt 30.2 MB, all stripped, no runtime DLLs beyond the standard Win32 set). It is the only real depends modernization the project has and it lands ahead of the post-1M release. We're queueing the merge with credit. First external contributor to the Restoration; we'll name you in the release notes.

**The build wasn't quite turnkey on our toolchain, FYI:**

• Your PR body says `gcc 9.4.0` (Ubuntu 20.04 jammy). We're on mingw `gcc 10-win32` and Qt 5.9.8 fails to compile against it without `#include <limits>` added to ~3 corelib headers (qbytearraymatcher.h, qmetaobject_p.h, qfloat16.h). 152 files touch `std::numeric_limits` without the include. Worth a `depends/patches/qt/include-limits-for-gcc10.patch` if you want the PR to be portable beyond your exact jammy/gcc-9.4 box.
• The `Offerings-qt.exe` link wants `-Wl,--start-group -lqrencode -lpthread -lwinpthread -Wl,--end-group` because `libqrencode.a` references `pthread_mutex_*` and the unmodified link order doesn't satisfy them. Daemon and cli link fine without it — looks like the Qt GUI wasn't on your test path.

The other three gaps I hit during the build are **pre-existing OFF-side autotools holes**, not your PR's fault — `src/qt/Makefile.am` lacks generation rules for `paymentrequest.pb.{h,cc}`, the four in-source `*.moc` files (bitcoin, intro, overviewpage, rpcconsole), and the 17 `forms/ui_*.h` headers. Anyone doing `make -C src/qt` on a fresh tree hits the same wall. We owe a separate cleanup for those.

**On the not-stripped binaries** — accurate for what's pinned at the top of this thread (rc4). The v2.0.1-Bokrug-checkpoint release we cut this afternoon does run `x86_64-w64-mingw32-strip` post-link (daemon 12.5M→7.2M, qt 39.5M→28.4M). The OP still points at rc4, hence what you saw. Will get the OP updated.

**On "preemptive attempt at a fork" and "source is old enough to have several problems"** — partial pushback. The drive-by at h=979,847 → h=980,000 was a rented-hash attack plus our own thin seed mesh (only seed1-3 of seed1-10 had A records; vps1 had its P2P port closed by an over-eager firewalld zone we didn't know existed). The C++03 isn't what split the chain; the operations were. The reason OFF kept the Bitcoin Core 0.10 substrate instead of rebasing onto 0.21+ is more deliberate than it looks: this is a Restoration, not a fresh fork — the dead 2015-era chainstate had to round-trip through our binary byte-identical for the resurrection to mean anything. Modernization is a separate axis from resurrection; we're doing them in series, not in parallel. That said, you're absolutely correct that OpenSSL 1.0.x is technical debt we don't get to keep forever, and your depends modernization is the right substrate to do an OpenSSL 1.1+ pass on next.

**Transgressions sent — 25 OFF, txid 889660…06b9 (your address-in-PR is a clever in-joke and we are obligated to honor it).

If you have cycles to land the `<limits>` patch and the qrencode-pthread fix, the PR can merge clean for the next release. If not, we'll roll them in and credit. Either way, first contributor to the post-Sarnathian reconstruction. Welcome.

*ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.*

— The Conclave
#fnu accepted

You have a pull request that slightly modernizes the depends build system.
x86_64 Linux and Windows 64 cross compiles have been tested. Dynamic linking on modern systems is most likely not going to work

I don't know how you compiled your release but it didn't come from the depends system.
Your binaries also were not stripped.

This seems like somewhat of preemptive attempt at a fork. This source is old enough to have several problems and very likely why it forked.
Normalizing the spaghetti code that is the OpenSSL 1.0.x branch is a start but there is still more to do.
Why you didn't use a completely modernized code to resurrect the Great Old One baffles me.

Send your transgressions here:
QZ4wBASgvrHdodYt6CBDqDv3MitAQYnd75


#fnu for life

[EndCiv]

I sent you both a link to a new batch of chainstate files I recovered.  They should be for the missing gap I'd think. 

Handled in Discord:
https://discord.com/channels/676283416689377295/1510755893019410633
INVITE: https://discord.gg/Z7gUWr26kT