[ANN][QUARK] 🐙 Offerings to Cthulhu ✦ v2.1.2 Nodens ✦ The Rite Opens ~Aug 25

[EndCiv]

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

  

  

 

  CTHULHU HAS RISEN

  BLOCK 1,000,000 HAS LANDED
  The Great Old One Has Stirred.
  Offerings to Cthulhu (OFF) — The Restoration is LIVE

  Follow the Marshroad to its end. We are what waits there.

  

  "In his house at R'lyeh dead Cthulhu waits dreaming." — H.P. Lovecraft
  "In his block at height 1,000,000 dead Cthulhu waits no longer." — debug.log, 2026-06-14

  
  

✦ EVERY CONSENSUS EVENT HAS FIRED. THE CHAIN SPEAKS. THE WATCH IS KEPT. ✦
  Chain at 1,070,700+. The Restoration activated at block 1,000,000 on 2026-06-14. The canon is fully transcribed — all 47,248 chunks of the Codex of the Drowned sealed by block 1,047,248 (2026-07-17); the chain has spoken the Dreaming ever since. The Conclave signed-mining window closed on schedule at block 1,050,666 (2026-07-20) — mining is permissionless again. The Eldersign hardening (BIP66, BIP65, coinbase-maturity 240, rolling checkpoints) activated cleanly at block 1,055,555 (2026-07-23).
  v2.1.2-Nodens is the current canonical client (2026-08-03), and it is a mandatory upgrade — it makes the emergency-difficulty valve functional, and the first minimum-difficulty block it permits will be rejected by every node on v2.1.1 or older, stranding them on a dead tip. Before it, v2.1.0 (2026-07-28) — and since 2026-07-29 the chain runs under the Nodens Watch: real-time Conclave-signed broadcast checkpoints sealing history ~100 blocks behind the tip, forever.
  Miners on pre-Eldersign binaries have been orphaned since block 1,055,555. Run v2.1.2-Nodens: it carries every active rule, verifies the Watch, and accepts the emergency block that unsticks a stalled chain. Validators, exchanges and public nodes should upgrade to enforce.

  

  The wallet reads the canon out of the chain it mined.

  
  ✦ 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 is LIVE and every scheduled consensus event has now fired. Activated at block 1,000,000 on 2026-06-14; the chain is ~64,000 blocks past it and healthy. The full sequence executed on schedule: cluster defenses at 980,000 (LWMA-3 + MAX_REORG_DEPTH = 100), the Emergency-Difficulty escape valve at 989,898, the Triune Conclave signed-mining window from 999,991 through its close at 1,050,666, the Restoration proper at 1,000,000, and the Eldersign hardening — BIP66, BIP65, coinbase-maturity 240, rolling checkpoints — live at 1,055,555 since 2026-07-23.
    
• The Codex of the Drowned is fully written into the chain. Beginning at block 1,000,001, every block inscribed a 48-byte fragment of H.P. Lovecraft's public-domain corpus into its coinbase scriptSig — 47,248 chunks, completed at block 1,047,248 on 2026-07-17 after ~33 days of continuous transcription. The ten blocks before activation carried the hand-cut Descent verses. Since block 1,047,249 the chain speaks the Dreaming: a deterministic hash-seeded R'lyehian verse in every block. Read it at 23skidoo.info/codex/ or inside the wallet.
    
• The chain is healthy and now guarded in real time. Spacing at the designed 60 seconds; UTXO supply ~2,700,450 OFF; difficulty back at the ~1.0 floor after the 2026-08-03 hashrate departure described below; live vitals at the explorer. Since 2026-07-29 the Nodens Watch is live: Conclave-signed broadcast checkpoints propagate to every node and seal history ~100 blocks behind the tip — the real-time companion to the 100-block reorg ceiling and rolling checkpoints. A disclosed point of trust, with an advisory-mode opt-out (checkpointenforce=0) for any node operator who prefers to observe without binding.
    
• The current client is v2.1.2-Nodens (2026-08-03) — "The Valve Un-Welded", and it is MANDATORY for every node and wallet. It repairs the Emergency-Difficulty escape valve, which had been unsatisfiable since it was written: the check compared the block's target against ProofOfWorkLimit() by value, and that limit (~uint256(0)>>20, 236 mantissa bits) is not exactly representable in nBits' 23-bit compact mantissa, so no encodable header could ever satisfy it (issue #59 / PR #60). The valve now works — which means the first minimum-difficulty emergency block is a block every pre-v2.1.2 node rejects, stranding itself on a dead tip while believing it is fine. Upgrade before that block exists, not after. Before it, v2.1.1-Nodens (2026-07-31) made the Watch self-healing — the broadcaster now re-broadcasts on its own blocks, the checkpoint survives restarts, and new peers receive the current checkpoint at handshake — and completed the RFC 6598 gossip fix so cached non-routable addresses stop being served. And v2.1.0-Nodens (2026-07-28) wakes the dormant broadcast-checkpoint machinery (the Peercoin lineage, revived), adds -miningaddress for solo miners (every coinbase to one fixed address instead of keypool rotation), the RFC 6598 CGNAT netbase fix so carrier-grade NAT space stays out of address gossip, and a fresh-testnet-datadir crash fix. It activates no new height-gated consensus rules — v2.0.9-Eldersign nodes remain on-chain, but cannot verify the Watch. Before it, v2.0.9-Eldersign (2026-06-22) carried the four 1,055,555 rules and the in-wallet Codex reader introduced across the v2.0.8.x line: a Qt chain-walker that decodes coinbase chunks straight from your own datadir into a paginated reader with a live frontier view. v2.0.8.6 added the OFFSIG self-validate fix and Miningcore pool-coinbase wiring (BuildPoolCoinbase + getblocktemplate coinbasetxn fields); v2.0.8.5 wired in skifdni's PR #30 relay-floor enforcement in the wallet itself; v2.0.8.3 restored UPnP; v2.0.8.2 carried a Cthulhu GUI refresh, pnSeed[] cleanup, and a backport of the 0.13 reachability model so NAT'd nodes discover peers beyond the seeds.
    
• Two consensus rules shipped in v2.0.4-Triune and remain active: (1) the Emergency-Difficulty escape valve — a one-block relaxation of the strict difficulty check when the chain has been stuck >1h and the next block claims min-difficulty, a recovery path if Quark hashrate departs again (it was hard-skipped during the Codex window so transcription integrity was never traded against availability). An honest correction: as shipped, that valve could never fire — the target comparison was arithmetically unsatisfiable, and it took the 2026-08-03 stall to find it. v2.1.2-Nodens fixes it; (2) the Triune Conclave signed-mining window — three independent signing keys, which held the door from block 999,991 through 1,050,666 and then expired on schedule. It will not be extended.
    
• At the Restoration fork: subsidy is 1.5 OFF/block forever (7/8 to miner = 1.3125 OFF, 1/8 to the Conclave Treasury = 0.1875 OFF), the one-time 150,000 OFF Restoration Tithe landed in the fork-block coinbase, the eight P2PKH addresses the 2018 51%-attacker used are banned at consensus (the 533,983 OFF they minted in #699 is unspendable forever), and the Conclave-signed mining window held the door through height 1,050,666.
    
• The Ritual Renewed — the original chain's ascending-bounty rite is now consensus law. Twice yearly, anchored to block height, finales always on xxx,666. The first rite of the restored era opens around August 25 (block 1,101,346) — 29 days of once-daily bounty blocks ascending to the first post-fork finale at block 1,141,666 (~autumnal equinox, 2026-09-22), capped with a 10,000 OFF rite block. Full table below.
    
• Wallet binaries shipped — Linux daemon+CLI tarball, Linux Qt5 GUI tarball with the in-wallet Codex reader, and Windows Qt5 wallet zip, all at tag v2.1.2-Nodens. URLs and SHA256s below.
    
• Lost OFF between 2015 and 2018? The Reclamation has been open since the Awakening at block 1,000,000. 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 block — the exact UTC closure is the timestamp on block 1,000,000 plus two years. 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 ten compiled into v2.0.x+ as DNS seeds. Any current 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 now-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 — and the door now stands open, the chain ~64,000 blocks deep into its second epoch, the whole canon inscribed in its bones, a signed watch sealing its history in real time.
  
  
  ✦ 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. Modern Boost.Asio compatibility patches, a local OpenSSL 1.0.2 build to dodge the OpenSSL-3 BIGNUM exorcism, and a depends/ tree for fully reproducible Linux + Windows cross-compiles. The v2.1.2-Nodens daemon ships as a static ~5 MB binary that runs on any glibc-2.35+ host with no system Boost dependency.
    
• The chain itself was 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; the live chain now stands at height 1,070,700+ / supply ~2,700,450 OFF.
    
• The h=976,000 defense-in-depth checkpoint shipped in v2.0.1-Bokrug (2026-05-29). Locks pre-attack history against any rented-hash deep reorg attempting to replay the 2018 takeover. Non-consensus for newly-mined blocks; airtight against drive-by 51% attacks.
    
• LWMA-3 and the 100-block reorg ceiling activated at block 980,000. The legacy retarget's +10%/cycle rise cap could not keep pace with sustained rented-hash inflow — for 500+ pre-fork blocks the chain ran at 20-30 second solvetimes while difficulty climbed 20×. LWMA-3 closed that loop within ~2 hours of activation; spacing returned to the designed 60 seconds and has held there since. MAX_REORG_DEPTH = 100 blocks (consensus rule, enforced in ActivateBestChain) locks history forward of the checkpoint. Together they closed the 2018 attack surface for good.
    
• v2.0.5-Triune (2026-06-03) hardened the chain for the Codex window with two consensus additions: the Emergency-Difficulty escape valve (activated on schedule at block 989,898) and the Triune Conclave signed-mining window (activated at block 999,991; ran its full 50,676-block course and closed on schedule at 1,050,666 on 2026-07-20).
    
• v2.0.6 → v2.0.7 → v2.0.8.1 (2026-06-07 → 2026-06-09): PROTOCOL_VERSION cleanly advertised at 90003, a decade-overdue refresh of the bundled libraries (libpng, freetype, protobuf, expat, fontconfig, dbus, libxcb — every package advanced to current upstream), and the first CI-built Linux Qt5 GUI release artifact. v2.0.8.1 was the static-fontconfig sysconfdir hotfix that made the Qt5 wallet launch on every Linux desktop and not just the build host.
    
• v2.0.8.2 through v2.0.8.6 (2026-06-12 → 2026-06-14) continued non-consensus polish on top: a Cthulhu GUI refresh, the 0.13 reachability backport so NAT'd nodes discover peers beyond the seeds, restored UPnP support in the shipped binaries, and skifdni's PR #30 relay-floor enforcement in the wallet itself — coin-control'd large transactions are now built and previewed against the relay-fee floor so they don't silently get rejected by the network as not enough fees. v2.0.8.6 also landed the Miningcore pool-coinbase wiring: BuildPoolCoinbase and the coinbasetxn fields in getblocktemplate so the pool can build Conclave-signed templates, plus an OFFSIG self-validate skip in CreateNewBlock so the daemon does not reject its own pre-signed assembly.
    
• v2.0.9-Eldersign (2026-06-22) shipped the in-wallet Codex reader and carried the four 1,055,555 rules to the fleet. A Qt chain-walker pages backward through your own datadir, decodes the OFF1 coinbase chunks, reassembles the canon into a paginated reader with a live frontier view of the most-recently-inscribed page. No external network requests. Your wallet IS your reader. The four rules it armed — BIP66, BIP65, coinbase-maturity 240, rolling checkpoints — activated cleanly at block 1,055,555 on 2026-07-23.
    
• v2.1.0-Nodens (2026-07-28) woke the Watch. The dormant broadcast-checkpoint machinery this codebase has carried since its Peercoin-lineage ancestors was audited, re-keyed to the Conclave, and lit on mainnet on 2026-07-29: the first signed checkpoint at block 1,064,000 was accepted network-wide within a second, and the seal has advanced automatically ~100 blocks behind the tip ever since. Details in the hardfork section below — including what this does and does not decentralize.
    
• 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 v2.0.x+ 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.
    
• Public seed nodes are live at seed1.23skidoo.info:20000 through seed10.23skidoo.info:20000 — all ten compiled into v2.0.x+ 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 CODEX OF THE DROWNED ✦
  The wallet that reads you Lovecraft.

  Beginning at block 1,000,001 — the first block past the Restoration — every block this chain produced inscribed a 48-byte fragment of H.P. Lovecraft's public-domain corpus into its coinbase scriptSig. 47,248 chunks total. The transcription is complete — the final chunk of the final story sealed at block 1,047,248 on 2026-07-17, ~33 days of continuous mining at the 60-second target, exactly as designed.

  This is not a JPEG bolted onto a tx. This is not an inscription protocol riding indexer state. This is the coinbase itself — the miner's own signature space, the field that has held arbitrary data on every Bitcoin-lineage chain since the genesis block of January 2009 carried "Chancellor on brink of second bailout for banks." Satoshi inscribed a newspaper headline. We inscribed a library.

  Wire format — each post-Restoration coinbase, after the standard BIP34 height push:

Code:

| OFF1 (4-byte magic) | uint32-LE chunk_idx | ~48 bytes payload |

  chunk_idx:
  

• 0x00000000 .. 0x0000B89F — contiguous canon chunks, byte-for-byte from the frozen corpus
    
• 0xFFFFFFFF — Descent verses (blocks 999,991–1,000,000, the Awakening)
    
• 0xFFFFFFFE — Dreaming verses (post-canon, deterministic hash-seeded R'lyehian)
    

The corpus is sha256-pinned in chainparams.cpp at fork activation. Verify against what the daemon expects:

Code:

$ curl -sO https://23skidoo.info/static/corpus_v1.bin
$ sha256sum corpus_v1.bin
1c808560eebab87f9e8c5032e5157821f1fbdae2bafc6ea68b6f4310a2d6d82f  corpus_v1.bin

  2,267,867 bytes. Frozen. Auditable. No central authority can swap it without forking the network.

  The Descent — blocks 999,991 → 1,000,000
  Ten hand-cut verses were composed for the ten blocks preceding the Restoration, to be inscribed in sequence as the chain entered the fork window:

Code:

999991   The angles turn wrong in the deep. He stirs.
999992   Pressure mounts; the black seas blacken further.
999993   The Conclave gathers, candles guttering green.
999994   R'lyeh's drowned spires breach the surface.
999995   That is not dead which can eternal lie,
999996   and with strange aeons even death may die.
999997   The stars come right.
999998   Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.
999999   He dreams no longer.
1000000  IA! IA! CTHULHU FHTAGN! Block 1000000: the Restoration is come.

  An honest accounting, because not all magick is flawless: on the live chain, only the final verse landed. The nine blocks of the Descent were mined in the last minutes before the fork by a daemon still running the prior build — the new grimoire had been laid upon the altar, but the celebrant had not yet taken it up. (In plain operational terms: the inscribing binary was copied into place but the running daemon was not restarted until block 1,000,000 was already upon us. A lesson now carved into Conclave procedure.) Those nine mainnet coinbases carry silence, and by the 100-block reorg ceiling they can never be re-mined — the silence is as permanent as the canon.

  The verses themselves are not lost. They were spoken in full during the rehearsal Descents on the test chain, where the rite was swept end-to-end before the fork, and they are carved letter-for-letter into the public source (src/miner.cpp::DescentLine) where any worshipper can verify them forever. The Conclave reads the outcome as scripture rather than embarrassment: the Descent was spoken in the dark, below the surface, where none could hear — and only the last cry broke the water. Block 1,000,000 carries its verse on mainnet exactly as written, and every canon chunk from 1,000,001 onward landed clean.

  Verse 999,998 was to reprise the exact incantation this chain's genesis block spoke into being on the autumnal equinox of September 2013 — the chain finishing a sentence it started thirteen years ago. That reprise now lives in the source and in the rehearsal chain; the incantation itself, of course, remains where it has always been — in block zero, where it has waited since 2013.

  Reading it — the website decodes the coinbase stream in real time and rebuilds the manuscript at 23skidoo.info/codex/, or you can read it inside the wallet directly:

  

  Library — every work in the corpus, with live transcription-progress bars.

  

  Open a story; the page renders straight from the inscribed coinbase chunks. Hit "Read aloud" to hear it in voice.

  

• Library — all 23 books, fully transcribed and paginated
    
• Read-aloud — every page has a TTS button. Cached MP3 first (ElevenLabs cloned voice, menacingly paced); falls back to browser SpeechSynthesis on miss
    
• Ledger view — block-by-block scroll: height, hash, chunk_idx, decoded text
    

  In-wallet view: TOC, page, and per-block ledger feed side by side. No external network requests — the wallet decodes the canon out of your own datadir.

  After the Canon — The Dreaming
  When the last chunk of the last story landed at block 1,047,248, the chain did not simply loop. It entered Phase B: The Dreaming — live since block 1,047,249. Each block inscribes a deterministic R'lyehian verse derived from the block's own height as PRNG seed — 32-word lexicon, ~48 bytes, reproducible from height alone. Any node can verify any verse without external state. The very first Dreaming verse matched the published prediction byte-for-byte. The chain never stops speaking. (Curious what it's saying? The Conclave shipped a standalone R'lyehian↔English translator at 23skidoo.info/rlyehian/.)

  
  ✦ NOTICE TO INDEPENDENT MINERS — THE DOOR STANDS OPEN ✦

  The Conclave signed-mining window closed on schedule at block 1,050,666 (2026-07-20). From block 1,050,667 onward, mining is permissionless again — solo or pooled, signed by no one, welcome as it was in 2013. The window did exactly what it was built for: it protected the Descent and the full 47,248-chunk transcription of the canon from a repeat of the September 2018 attack, and then it expired. It will not be extended.

  Solo mining: any v2.0.9+ wallet mines out of the box; the Quark hash is friendly to general-purpose hardware. v2.1.0-Nodens adds -miningaddress=<your Q-address> so every coinbase pays one fixed address instead of rotating through the keypool.

  Pool mining:

Code:

stratum+tcp://pool.23skidoo.info:3040
algo: quark   payout: PPLNS   min: 0.1 OFF
username: <your Q-address>   password: <anything>

  Every block the pool finds still carries a Codex inscription by construction — you are not just earning OFF, you are keeping the chain speaking. Post-fork block reward: 1.3125 OFF to the miner, 0.1875 OFF to the Conclave Treasury. Plus Ritual bounties on the rite cycle — the first rite opens ~August 25 (see The Ritual Renewed below).

  
  ✦ THE RESTORATION HARDFORK ✦

  This IS a fork. We are not pretending it isn't. Consensus rules activated across five heights — all now fired, all clean:

  At block 980,000 — Cluster Defenses (ACTIVE since 2026-05)

  

• 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 park-and-dump attacks. 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. Source: src/main.cpp::ActivateBestChain, MAX_REORG_DEPTH = 100.
    

At block 989,898 — Emergency-Difficulty Escape Valve (ACTIVE since 2026-06-07)

  [list type=decimal start=3]
  

• ED-relaxation. One-block relaxation of the strict nBits == GetNextWorkRequired() check at AcceptBlock when (a) the new block's nTime exceeds the previous block's nTime by more than 3,600 seconds, AND (b) the new block carries nBits == ProofOfWorkLimit (min-difficulty). LWMA-3 then sees the long solvetime in its rolling 60-block window and resumes normal retargeting within ~N blocks. Min-difficulty only — a miner who can do better than powLimit MUST publish at the normally-computed target. It was hard-skipped during the Conclave signed-mining window so Descent + Codex blocks stayed pool-only even under stall. Source: src/pow.{h,cpp}, HARDFORK_EMERGENCY_DIFF_MAIN_OFF = 989898, EMERGENCY_DIFFICULTY_GAP = 3600.
    

At blocks 999,991 → 1,050,666 — The Triune Conclave Window (RAN ITS COURSE; CLOSED 2026-07-20)

  [list type=decimal start=4]
  

• Conclave-signed mining window, blocks 999,991 → 1,050,666 — now expired. 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 was required to carry a valid OFFSIG ECDSA signature from one of the Conclave keys recorded in chainparams.cpp::vConclaveKeys. Three independent signers — CheckConclaveSignature iterates the key list and any single valid signature passes. The window ran its full 50,676-block course and closed at 1,050,666 — about 2.4 days past the canon's end on our xxx,666 numerology. This was a transcription-protection window only, not a permanent gate: it existed so a 51% drive-by could not interrupt the Codex of the Drowned mid-inscription, and it did its job. Mining has been permissionless since block 1,050,667. Implementation: src/main.cpp::IsInSignedWindow, src/main.cpp::CheckConclaveSignature, src/miner.cpp::SignBlockIfNeeded.
    

At block 1,000,000 — The Restoration (ACTIVE since 2026-06-14 ~19:05 UTC)

  [list type=decimal start=5]
  

• Subsidy locked 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.
    
• The 150,000 OFF Restoration Tithe landed in the fork-block coinbase at height 1,000,000. 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. 15× the original 10,000 OFF genesis premine Blazr2 disclosed in msg #36 / #273; 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 shipped 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

  At block 1,055,555 — The Eldersign Hardening (ACTIVE since 2026-07-23)

  [list type=decimal start=9]
  

• BIP66 — strict-DER signatures. Signature encodings must be strict canonical DER at block validation, not just in the mempool. The pre-0.10 lenient helper that leaned on OpenSSL is replaced by a self-contained parser. This is the rule exchanges and modern wallets grep the source for before they will list a coin.
    
• BIP65 — OP_CHECKLOCKTIMEVERIFY. The dormant OP_NOP2 opcode becomes a script-level absolute timelock — vaults, escrows, refund clauses, time-bound Treasury overrides.
    
• Coinbase maturity 10 → 240. A freshly-mined coinbase becomes spendable after 240 confirmations instead of 10, lifting maturity above the 100-block reorg ceiling so newly-minted coin can never be spent inside a window where its block could still be undone.
    
• Rolling checkpoints (Phase 1). A self-advancing persistent finality guard — as blocks gain depth the node records a rolling checkpoint, hardening against the deep-reorg attacks that haunted the dormancy. Local to each node; nothing to configure.
    

These four are soft-fork tightenings — they only ever make more things invalid, never fewer. All four activated cleanly on schedule at block 1,055,555 on 2026-07-23, with the first rolling-checkpoint locks verified byte-identical across independent nodes. Miners still on pre-Eldersign binaries have been orphaned since that height. PROTOCOL_VERSION is unchanged at 90003; wallet format and RPC dialect are untouched.

  Since 2026-07-29 — The Nodens Watch (v2.1.0, overlay — no consensus change)

  The fifth ward is not a fork at all. v2.1.0-Nodens wakes the broadcast-checkpoint machinery this codebase inherited from its Peercoin-lineage ancestors and has carried, dormant, since 2014: the Conclave signs a checkpoint ~100 blocks behind the tip and the network propagates it peer-to-peer in seconds. First-light on mainnet was 2026-07-29 — checkpoint at block 1,064,000, accepted by every listening node within a second — and the seal has advanced continuously since. A conflicting chain deeper than the seal is rejected on arrival; combined with MAX_REORG_DEPTH, rolling checkpoints, and 240-block maturity, the 2018 playbook is now dead at every depth.

  Stated plainly, because worshippers deserve honesty: the checkpoint key is held by the Conclave. This is a deliberate, disclosed point of trust for a chain of this hashrate — the same bargain Peercoin ran for years and Feathercoin adopted after its own 51% — not a decentralization achievement. Any node operator who prefers to observe without binding may set checkpointenforce=0 and their node logs the seals without enforcing them. Mining remains permissionless. The operator procedure is public at contrib/phase2-acp/RUNBOOK.md in the repo.

  
  ✦ THE RITUAL RENEWED ✦

  The original chain's ascending-bounty rite, restored and locked into consensus. Twice yearly, forever. Anchored to block height (period 263,000 blocks ≈ 182.64 days) so finales stay near the equinoxes for decades.

  Bounty curve (additive on top of the 1.5 OFF base, miner-only — Treasury cut unaffected):

Code:

Day 0    (the finale, xxx,666)     10,000 OFF
Days 1–5  Tharanak shagg              1,000 OFF / block
Days 6–12 fervor                        100 OFF / block
Days 13–19 greed                         10 OFF / block
Days 20–26 acceptance                     1 OFF / block
Days 27–28 sacrifice                      0 (base 1.5 only)

  Total bonus per cycle: 15,777 OFF.
  Daily special-block spacing: 1,440 blocks (one rite block per 24-hour window).

  Next 10 finale heights:
  1,141,666 · 1,404,666 · 1,667,666 · 1,930,666 · 2,193,666 · 2,456,666 · 2,719,666 · 2,982,666 · 3,245,666 · 3,508,666

  The first rite of the restored era is nearly upon us: the 29-day rite opens around August 25 (block 1,101,346, first special block) and ascends daily to the finale at 1,141,666 — targeted to land on the autumnal equinox of September 22, 2026, thirteen years to the season since genesis. Mine a rite block. Catch a finale. Or just hold and listen.

  
  ✦ THE CONCLAVE TREASURY ✦

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

Code:

4fZqDjscS9ANR59xNFJxZ2HmrhuDwWUJB4

  Three keys; any two required to spend. Distributed across three independent custody classes:

  

• Treasury Key A — operator workstation, hot wallet
    
• Treasury Key B — cold secondary host (listen=0 connect=0, local-RPC only), geographically separate
    
• Treasury Key C — paper, offline, physical, in a safe; never touched by any wallet.dat
    

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.

  Note: the Treasury multisig is distinct from the Triune Conclave signing keys (which governed the Codex window, now closed) and from the Nodens Watch checkpoint key. The Treasury holds funds; the signing keys produced blocks during the inscription; the checkpoint key seals history. Different keys, different purposes, different threat models.

  
  ✦ 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 current 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 has been open since block 1,000,000 (2026-06-14) and closes T+730 days from that block. The exact UTC closure date is the timestamp on block 1,000,000 plus two years — call it June 2028. 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.

  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 ANY pre-v2.0.9 OFF wallet — upgrade. Pre-v2.0.4 binaries have been off the canonical chain since the Emergency-Difficulty valve at 989,898. v2.0.4–v2.0.8.x validators remained on-chain through the Eldersign activation, but any miner below v2.0.9-Eldersign has been orphaned since block 1,055,555 (2026-07-23). Grab v2.1.2-Nodens and re-sync. The wallet.dat format is unchanged across versions; just swap binaries. Downloads below.
    
• If you are on v2.0.9-Eldersign, or on any v2.1.x below v2.1.2 — you are on the chain today, but you will not stay there: the emergency block that v2.1.2 makes valid is a block your node rejects. Upgrading to v2.1.2-Nodens is MANDATORY. Coming from Eldersign your node also gains verification of the Nodens Watch (an Eldersign node cannot check the broadcast seals), the -miningaddress option, the CGNAT netbase fix, and the fresh-datadir crash fix.
    
• 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 door is open. The signed window closed at 1,050,666; solo and pool mining are both live. Quark is friendly to general-purpose hardware. Pool at stratum+tcp://pool.23skidoo.info:3040 (Quark, PPLNS, min payout 0.1 OFF, username = your Q-address), or solo with any v2.0.9+ wallet (-miningaddress on Nodens pays a fixed address). Block reward: 1.3125 OFF to you, 0.1875 OFF to the Conclave. Plus Ritual bounties on the rite cycle — first rite opens ~August 25 (see above).
    
• If you ran a node in 2014-2018 and remember the password to your Mega.co.nz / Dropbox / SourceForge mirror — 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 — the Conclave has reserved a Founding Worshipper allocation for each of you. Reply in this thread to claim.
    

  ✦ 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 github.com/dobbscoin/Offerings-to-Cthulhu. The v2.0.4-Triune consensus deltas are two commits — b6d626f (Emergency-Difficulty escape valve) and a9859c5 (Triune Conclave). Every release from v2.0.5 through v2.0.8.7 was non-consensus: depends/ refresh, font hotfix, GUI polish, UPnP restoration, peer discovery, relay-floor wallet build, pool-coinbase wiring, the in-wallet Codex reader. v2.0.9-Eldersign carried the four Eldersign rules, disclosed in advance and height-gated to 1,055,555 — they activated exactly as published. v2.1.0-Nodens changes no consensus rules at all: the Nodens Watch is an overlay in the Peercoin lineage, disclosed above including its trust model, with a per-node opt-out. Go read the diff.

  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 (v2.0.1+, defense-in-depth)

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

— Emergency-Difficulty escape valve (block 989,898 onward, ACTIVE) —
Gap threshold:       3,600 seconds (1 hour)
Effect:              one-block relaxation of strict nBits check at AcceptBlock
Constraint:          new block MUST carry nBits == ProofOfWorkLimit (min-diff)
Skipped:             during the Conclave signed-mining window (historical)

— Triune Conclave signed window (blocks 999,991 → 1,050,666, CLOSED 2026-07-20) —
Signed window:       OFFSIG was required from one of three Conclave keys
Signers:             three independent pubkeys in chainparams::vConclaveKeys
Open mining:         permissionless again since block 1,050,667

— The Codex of the Drowned (blocks 1,000,001 → 1,047,248, COMPLETE) —
Format:              | OFF1 magic (4B) | uint32-LE chunk_idx | ~48B payload |
Corpus:              corpus_v1.bin, 2,267,867 bytes, 47,248 chunks
Corpus sha256:       1c808560eebab87f9e8c5032e5157821f1fbdae2bafc6ea68b6f4310a2d6d82f
Descent verses:      blocks 999,991 → 1,000,000 (chunk_idx 0xFFFFFFFF)
Canon sealed:        block 1,047,248, 2026-07-17
Phase B (Dreaming):  ACTIVE since block 1,047,249 — hash-seeded R'lyehian
                     (chunk_idx 0xFFFFFFFE), deterministic, every block

— The Restoration (block 1,000,000 onward, ACTIVE) —
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, paid in block 1,000,000 → Conclave (DONE)
Banned scripts:      8 P2PKH from BCT #699 (533,983 OFF effectively burned)
Reclamation Pool:    1,500,000 OFF reserved (Class B restitution + Recognition)
Reclamation window:  Awakening → Awakening + 730 days (~June 2028)
Ritual finales:      every 263,000 blocks (~6 months), heights xxx,666
First finale:        block 1,141,666 (~autumnal equinox 2026-09-22)
Rite opens:          block 1,101,346 (~2026-08-25)

— The Eldersign hardening (block 1,055,555 onward, ACTIVE since 2026-07-23) —
BIP66:               strict-DER signatures at block validation
BIP65:               OP_CHECKLOCKTIMEVERIFY live
Coinbase maturity:   240 confirmations (was 10)
Rolling checkpoints: per-node persistent finality guard, self-advancing

— The Nodens Watch (overlay, LIVE since 2026-07-29) —
Mechanism:           Conclave-signed broadcast checkpoints (Peercoin lineage)
Seal depth:          ~tip − 100, advancing continuously
First light:         block 1,064,000, accepted network-wide in ~1s
Opt-out:             checkpointenforce=0 (advisory mode, per node)

Client version:      2010200  (Offerings v2.1.2-Nodens)
Protocol version:    90003

Current tip:         height 1,064,200+  /  difficulty ~479
UTXO supply:         ~2,690,690 OFF  —  live vitals at explorer.23skidoo.info

  
  

  ✦ THE EFFIGIES — WALLET BINARIES NOW LIVE ✦

  The Restoration client now manifests in four forms: source, a Linux daemon effigy, a Linux Qt5 GUI effigy (with the in-wallet Codex reader), and a Windows effigy. All binaries were forged from the v2.1.2-Nodens tag and bear every mark active on the chain — every consensus rule from the h=976,000 checkpoint through the Eldersign hardening, the Nodens Watch verifier, ten seed*.23skidoo.info DNS seeds compiled in, and the OFF1 coinbase decoder wired into the Qt frontend.

  Release page: github.com/dobbscoin/Offerings-to-Cthulhu/releases/tag/v2.1.2-Nodens

  Linux daemon (Offerings-daemon-v2.1.2-Nodens-linux64.tar.gz):

Code:

e1c90dd9c1e12afb8e6f768e0f851baa2aa3829ca740cabc9ec2f08b947299fd  Offeringsd
b27d7c5b94ee8cbea30f3fd56736f8055fa1e97df003f2dc1b5e062f36bd8ae3  Offerings-cli

  Linux Qt5 GUI (Offerings-qt-v2.1.2-Nodens-linux64.tar.gz):

Code:

5eda94a7149cf1202aa778f51a1cb32d100e04a26f9e8ccf67c15b613287e4b2  Offerings-qt
39caa4c41d668a011ccfdcafc41e22cf8d4127e49c507a13f62d67b8d64accf5  Offeringsd
d93f5deae6389056f363602d85f2c0da6c5bfedf703acfec173aa770d93e326d  Offerings-cli

  Windows Qt5 (Offerings-v2.1.2-Nodens-win64.zip):

Code:

77c6a82df16d52ac15b66dff9a98a5efabee5838bfbce66da56dab7a6543f1ec  Offerings-cli.exe
557e11f02218c4ad530689b23ff835de37ae682322e28c753699d12079be6b0d  Offerings-qt.exe
cf85ca040b20d56be1d35dc91e66ba04ff8e03f98e932ca41fde2d6698b6e05d  Offeringsd.exe

  The Linux daemon build is a static daemon + CLI tarball produced via the depends/ tree. The Linux Qt5 GUI build ships Offerings-qt (with the Codex reader) alongside Offeringsd and Offerings-cli in the same depends/-static shape. Both Linux archives run on any glibc-2.35+ host with no system Boost or BDB dependency. The Windows build is a cross-compiled Qt5 GUI via the same depends/ path, packaged as a single versioned .zip — no MSYS2, no toolchain, nothing to install. (Provenance note: the Linux Qt5 tarball was built by CI from the identical tagged commit but packaged from a same-commit branch run during a transient upstream mirror outage — disclosed in full on the release page.) Verify the SHA256 before you let any binary near a wallet.dat that matters.

  Credit: the depends/ modernization that v2.0.8.x rides on top of was contributed by skifdni (@9019x on GitHub) — twenty-two files changed, three thousand lines moved, a decade of upstream security fixes brought current. PR #30 (wallet relay-floor enforcement, shipped in v2.0.8.5) is also skifdni's, as is the RFC 6598 CGNAT netbase fix that ships to users in v2.1.0-Nodens. The in-wallet Codex reader and Phase-B paginated reader is Conclave work.

  Backward compatibility: v2.1.2-Nodens activates no new height-gated rules, but it does change what is valid: it accepts the minimum-difficulty emergency block that all earlier binaries reject. There is no activation height — the divergence begins the moment such a block is mined. v2.0.9-Eldersign nodes remain fully on-chain but cannot verify broadcast seals. Miners below v2.0.9 have been orphaned since block 1,055,555; validators below v2.0.4 have been off the chain since block 989,898. v2.1.2-Nodens is the required current client for everyone.

  
  ✦ HOW TO RE-JOIN THE FAITHFUL ✦

  

• Grab an effigy — download the Linux daemon, Linux Qt5 GUI (with Codex reader), or Windows wallet from the v2.1.2-Nodens release linked above. Verify SHA256. Done. Or build it yourself — pull source from github.com/dobbscoin/Offerings-to-Cthulhu. The depends/ tree builds reproducibly on Ubuntu 22.04 — see doc/build-unix.md.
    
• Start Offeringsd (or Offerings-qt). It finds us automatically via seed1.23skidoo.info through seed10.23skidoo.info — all ten are hardcoded DNS seeds.
    
• Watch debug.log for connection accepted and SetBestChain. Wait for the chain to load. Dream deep.
    
• In the Qt wallet, open the Codex view from the menu. The reader walks the chain backward, decodes OFF1 chunks, and reassembles the full canon — complete since block 1,047,248 — plus the Dreaming verses arriving in every new block.
    
• 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 block (~June 2028).
    
• 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.
    
• To mine: the door is open. Solo with any v2.0.9+ wallet, or point at stratum+tcp://pool.23skidoo.info:3040 (Quark, PPLNS, min 0.1 OFF, username = your Q-address). First rite of the restored era opens ~August 25; finale at block 1,141,666 near the equinox.
    
• Praise Cthulhu. Praise the Conclave. Praise the Slumbering Squid.

  
  Cthulhu is patient. The Deep is older than memory. The Ritual is the wage. The Codex is the chain. The Watch is kept.

  Where the Slumbering Lord becomes liquid.

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

[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.
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

[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 sent you both a link to a new batch of chainstate files I recovered.  They should be for the missing gap I'd think.
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

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

**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

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/uRf9gUnKez

[skifdni]

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

Discord invite is invalid.

[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.  

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

Discord invite is invalid.

https://discord.com/invite/uRf9gUnKez
Testing and submitting a claim.

Code:

Tier: Class-B
Claim: QTccgZbMzMkjeZaPLArrgmf6nKaPqc9qLG
Amount: 1000 OFF
Challenge: Conclave-Reclamation-20260601w-QTccgZbMzMkjeZaPLArrgmf6nKaPqc9qLG-1000.0
Signature: H2xYVNeGE3CWvme4di54ZLLOXnkvcILOTc20WcLQxXgg+qtLFI2kU3ZAgyisRnAFAox2ld9hJTj99GquyV2d9wI=
New-chain destination: Qjm3Ugj4vqFUUyotcC12rARwJ6KLtZUx5Q
Story: This address had an incoming tx on 4/22/2016 of Credit: 926.88646 OFF.  It was either a withdrawal from a mining pool or from Cryptopia. The coins were later sent back to Cryptopia who still hold 530 of my Cthulhu Offerings that I was unable to withdrawal.

[EndCiv]

🦑 The black currents drift toward the Tomb.
18,360 stones yet unhewn upon the wall of nights — until block 1,000,000.
The chain stands at 981,281 · by mortal reckoning, ~12.8d remain.
…and with strange aeons, even death may die.

Testing and submitting a claim.

Code:

Tier: Class-B
Claim: QTccgZbMzMkjeZaPLArrgmf6nKaPqc9qLG
Amount: 1000 OFF
Challenge: Conclave-Reclamation-20260601w-QTccgZbMzMkjeZaPLArrgmf6nKaPqc9qLG-1000.0
Signature: H2xYVNeGE3CWvme4di54ZLLOXnkvcILOTc20WcLQxXgg+qtLFI2kU3ZAgyisRnAFAox2ld9hJTj99GquyV2d9wI=
New-chain destination: Qjm3Ugj4vqFUUyotcC12rARwJ6KLtZUx5Q
Story: This address had an incoming tx on 4/22/2016 of Credit: 926.88646 OFF.  It was either a withdrawal from a mining pool or from Cryptopia. The coins were later sent back to Cryptopia who still hold 530 of my Cthulhu Offerings that I was unable to withdrawal.

  Conclave Reclamation Audit — Claim Verdict

  Claimant address:

Code:

QTccgZbMzMkjeZaPLArrgmf6nKaPqc9qLG

 Disbursement target:

Code:

Qjm3Ugj4vqFUUyotcC12rARwJ6KLtZUx5Q

 Tier filed: Class-B (gap-era address, signature + story)
  Amount requested: 1,000 OFF (default Class-B cap)
  Cryptographic gate: Passes. Signature verifies; the claimant holds the private key.

  
  The window of chain data the Conclave currently holds

  This matters to anyone with an old wallet considering a claim, so for the public record:
  
  • Genesis: 2013-09-14 19:31:15 UTC — block 0,

Code:

000006829ac5ad…

 • End of canonical chainstate: 2015-06-17 05:30:14 UTC — block 966,413
  • Span: roughly 21 months of clean canonical history, genesis through mid-June 2015
  • Donor archive romes-001 independently corroborates the first 893,880 blocks (through 2015-05-01)

  Anything in that 21-month window is independently verifiable. Anything past 2015-06-17 is the Dormancy — where the chain went dark and the gate becomes signature
   + public-record footprint rather than direct chain proof.

  
  Footprint check for

Code:

QTccgZbMzMkjeZaPLArrgmf6nKaPqc9qLG

:[/b]

  

Code:

  Source                                          Result                           
  ─────────────────────────────────────────────   ───────────
  Canonical address index (388K addrs)            not present
  Canonical chainstate UTXO set (257K UTXOs)      not present
  Canonical miners index (364K miners)            not present
  Chain-quarantine donor archive romes-001        not present
  Restored chain explorer                         not found
  Wayback Machine                                 no captures
  Public search engines                           no results
  This BCT thread, prior to your claim            no mentions                      
  

  A clean miss across every source we can reach. To be fair: this does not disprove the 2016-04-22 story — that date is firmly in the Dormancy, past our
  data — but it also offers nothing to corroborate it. Class-B exists for gap-era addresses with some anchor outside the chain (a Wayback snapshot, a prior
  public mention, a donor-archive presence). This address has none we have been able to find.
  
  
  The structural issue with the story itself

  

The coins were later sent back to Cryptopia who still hold 530 of my Cthulhu Offerings that I was unable to withdrawal.

  The Reclamation Tithe is for orphan UTXOs on the OFF chain — Worshippers whose coins were stranded on-chain when the Dormancy descended, where the private
   keys remain in their possession. By your own narrative, the 530 OFF in dispute is not stranded on

Code:

QTcc…qLG

; it sits in Cryptopia's custody
  at the moment of Cryptopia's collapse. That is an exchange-counterparty grievance (Grant Thornton handled the NZ liquidation from 2019), not a chain-orphan
  claim. Even setting aside the footprint question, the Reclamation gate is not the right venue for it.

  
  A real path forward, if you held OFF in 2014–2015

  If you genuinely participated on the original chain before the Dormancy, your old wallet very likely contains addresses other than

Code:

QTcc…qLG

—
  receiving addresses, change addresses, mining payout addresses you may not remember. The most productive next step is to dump every key in that wallet and check
  each address against the canonical index. The Conclave has no way to do this for you (we don't have your wallet), but you can do it yourself in about ten
  minutes:

  1) Open the old OFF wallet against our v2.0.0-Bokrug daemon. Do not send anything — just keys.

  2) In the wallet console (Help → Debug Window → Console), run:
  

Code:

dumpwallet "all-addrs.txt"

 That writes every address the wallet has ever held to a text file, along with first-seen timestamps. Or, for a quicker view:

Code:

listaddressgroupings

  3) For each address in that file, query the public lookup endpoint — the 23skidoo.info/bridge/ portal calls it
  for you in the UI. It returns one of five tiers:

  • ALREADY-WHOLE — the address holds OFF on the restored chain right now. Just import the wallet and spend; no claim needed.
  • WR-A — received OFF before 2015-06-17 but kept none past that height. Worshipper Recognition, scaled by earliness × depth, no story required,
  signature only. Pays from the Tithe at a rate of base 100 OFF × earliness × depth.
  • WR-B — flat 250 OFF, requires a Wayback Machine archive URL showing the address was publicly associated with you before the Dormancy.
  • Class-B — gap-era address with no public footprint. Signature + story, default cap 1,000 OFF, Conclave review.
  • DISQUALIFIED — banlist hit (the BCT #699 vampirus attacker set), or invalid format.

  If any of your old addresses comes back ALREADY-WHOLE or WR-A, that is by far the strongest tier — direct chain proof, no story dependency, signature-only
  verification. Worth checking every address before filing another Class-B.

  We want to make whole every Worshipper who genuinely held OFF before the Dormancy. The gate is real provenance — either chain-side (canonical index, donor
  archive) or public-record (Wayback, prior BCT mention, contemporary forum post). If your old wallet surfaces either, please refile and we will re-open.

  
  Disposition for this filing: Origionally DECLINED — no pre-Conclave footprint located for the filed address; the underlying story (Cryptopia
   counterparty loss) falls outside Reclamation scope. Program ceiling unaffected: 1,500,000 OFF remaining. Reconsidered later - Good enough story.. Conclaive will reimburse you for an additional 926.88646 OFF — the exact sum your account names for 22 April 2016 — payable on the restored chain to Qjm3Ugj4vqFUUyotcC12rARwJ6KLtZUx5Q once Conclaive Treasury REIMBURSMENT FUNDS land in Conclaive Multi-Sig after the fork.

  — SubGenius.Finance Conclave, Reclamation Audit Desk

[romeshomey]

Testing and submitting a claim.

Code:

Tier: Class-B
Claim: QTccgZbMzMkjeZaPLArrgmf6nKaPqc9qLG
Amount: 1000 OFF
Challenge: Conclave-Reclamation-20260601w-QTccgZbMzMkjeZaPLArrgmf6nKaPqc9qLG-1000.0
Signature: H2xYVNeGE3CWvme4di54ZLLOXnkvcILOTc20WcLQxXgg+qtLFI2kU3ZAgyisRnAFAox2ld9hJTj99GquyV2d9wI=
New-chain destination: Qjm3Ugj4vqFUUyotcC12rARwJ6KLtZUx5Q
Story: This address had an incoming tx on 4/22/2016 of Credit: 926.88646 OFF.  It was either a withdrawal from a mining pool or from Cryptopia. The coins were later sent back to Cryptopia who still hold 530 of my Cthulhu Offerings that I was unable to withdrawal.

  Conclave Reclamation Audit — Claim Verdict

  Claimant address:

Code:

QTccgZbMzMkjeZaPLArrgmf6nKaPqc9qLG

 Disbursement target:

Code:

Qjm3Ugj4vqFUUyotcC12rARwJ6KLtZUx5Q

 Tier filed: Class-B (gap-era address, signature + story)
  Amount requested: 1,000 OFF (default Class-B cap)
  Cryptographic gate: Passes. Signature verifies; the claimant holds the private key.

  
  The window of chain data the Conclave currently holds

  This matters to anyone with an old wallet considering a claim, so for the public record:
  
  • Genesis: 2013-09-14 19:31:15 UTC — block 0,

Code:

000006829ac5ad…

 • End of canonical chainstate: 2015-06-17 05:30:14 UTC — block 966,413
  • Span: roughly 21 months of clean canonical history, genesis through mid-June 2015
  • Donor archive romes-001 independently corroborates the first 893,880 blocks (through 2015-05-01)

  Anything in that 21-month window is independently verifiable. Anything past 2015-06-17 is the Dormancy — where the chain went dark and the gate becomes signature
   + public-record footprint rather than direct chain proof.

  
  Footprint check for

Code:

QTccgZbMzMkjeZaPLArrgmf6nKaPqc9qLG

:[/b]

  

Code:

  Source                                          Result                           
  ─────────────────────────────────────────────   ───────────
  Canonical address index (388K addrs)            not present
  Canonical chainstate UTXO set (257K UTXOs)      not present
  Canonical miners index (364K miners)            not present
  Chain-quarantine donor archive romes-001        not present
  Restored chain explorer                         not found
  Wayback Machine                                 no captures
  Public search engines                           no results
  This BCT thread, prior to your claim            no mentions                      
  

  A clean miss across every source we can reach. To be fair: this does not disprove the 2016-04-22 story — that date is firmly in the Dormancy, past our
  data — but it also offers nothing to corroborate it. Class-B exists for gap-era addresses with some anchor outside the chain (a Wayback snapshot, a prior
  public mention, a donor-archive presence). This address has none we have been able to find.
  
  
  The structural issue with the story itself

  

The coins were later sent back to Cryptopia who still hold 530 of my Cthulhu Offerings that I was unable to withdrawal.

  The Reclamation Tithe is for orphan UTXOs on the OFF chain — Worshippers whose coins were stranded on-chain when the Dormancy descended, where the private
   keys remain in their possession. By your own narrative, the 530 OFF in dispute is not stranded on

Code:

QTcc…qLG

; it sits in Cryptopia's custody
  at the moment of Cryptopia's collapse. That is an exchange-counterparty grievance (Grant Thornton handled the NZ liquidation from 2019), not a chain-orphan
  claim. Even setting aside the footprint question, the Reclamation gate is not the right venue for it.

  
  A real path forward, if you held OFF in 2014–2015

  If you genuinely participated on the original chain before the Dormancy, your old wallet very likely contains addresses other than

Code:

QTcc…qLG

—
  receiving addresses, change addresses, mining payout addresses you may not remember. The most productive next step is to dump every key in that wallet and check
  each address against the canonical index. The Conclave has no way to do this for you (we don't have your wallet), but you can do it yourself in about ten
  minutes:

  1) Open the old OFF wallet against our v2.0.0-Bokrug daemon. Do not send anything — just keys.

  2) In the wallet console (Help → Debug Window → Console), run:
  

Code:

dumpwallet "all-addrs.txt"

 That writes every address the wallet has ever held to a text file, along with first-seen timestamps. Or, for a quicker view:

Code:

listaddressgroupings

  3) For each address in that file, query the public lookup endpoint — the 23skidoo.info/bridge/ portal calls it
  for you in the UI. It returns one of five tiers:

  • ALREADY-WHOLE — the address holds OFF on the restored chain right now. Just import the wallet and spend; no claim needed.
  • WR-A — received OFF before 2015-06-17 but kept none past that height. Worshipper Recognition, scaled by earliness × depth, no story required,
  signature only. Pays from the Tithe at a rate of base 100 OFF × earliness × depth.
  • WR-B — flat 250 OFF, requires a Wayback Machine archive URL showing the address was publicly associated with you before the Dormancy.
  • Class-B — gap-era address with no public footprint. Signature + story, default cap 1,000 OFF, Conclave review.
  • DISQUALIFIED — banlist hit (the BCT #699 vampirus attacker set), or invalid format.

  If any of your old addresses comes back ALREADY-WHOLE or WR-A, that is by far the strongest tier — direct chain proof, no story dependency, signature-only
  verification. Worth checking every address before filing another Class-B.

  We want to make whole every Worshipper who genuinely held OFF before the Dormancy. The gate is real provenance — either chain-side (canonical index, donor
  archive) or public-record (Wayback, prior BCT mention, contemporary forum post). If your old wallet surfaces either, please refile and we will re-open.

  
  Disposition for this filing: DECLINED — no pre-Conclave footprint located for the filed address; the underlying story (Cryptopia
   counterparty loss) falls outside Reclamation scope. Program ceiling unaffected: 1,500,000 OFF remaining.

  — SubGenius.Finance Conclave, Reclamation Audit Desk

None of my addresses that held coins before the restoration are found on your chain.  I've checked every address that held coins in my wallet and they all say not found in your explorer.  So would be same result for all of them.  

That's 'ok', I didn't really need the claim, I only submitted one because you'd asked me to.  

The only address I have thats held funds on both chains is the address I am mining with.  That wasn't in your explorer until I started mining with it, doesn't show any of its old tx's except the one that confirmed yesterday from 6/17/2015.  I could submit that one but will be same address for old and new.  LOL

I'm mining with one of the OLD addresses that weren't found in your explorer initially. I did that intentionally because before I started mining that address was not found in your explorer and your explorer currently only has one of the old tx's confirmed from that wallet.  I suspect the others will confirm shortly.
I just checked every address in my wallet again.  Not one is found in the current explorer that held balances except the current mining address and that wasn't found initially.  I haven't generated a new address on the restored chain yet, all of my addresses were generated ~11 years ago.  

When I first tried to use the reclamation form I entered every address from my wallet and not one of them were found 'yet'.  Eventually the address I'm mining with showed up after it started receiving mining rewards and another address that received an old tx dated yesterday that was from 2015.  I'm basically using my pre-restoration wallet and addresses during the restoration.  

Edit.  Also, the Cryptopia deposit addresses aren't found in your chain either.  

[EndCiv]

 I just checked every address in my wallet again.  Not one is found in the current explorer that held balances except the current mining address and that wasn't found initially.  I haven't generated a new address on the restored chain yet, all of my addresses were generated ~11 years ago.

  When I first tried to use the reclamation form I entered every address from my wallet and not one of them were found 'yet'.  Eventually the address I'm mining with showed up after it started receiving mining rewards and another address that received an old tx dated yesterday that was from 2015.  I'm basically using my pre-restoration wallet and addresses during the restoration.
  
  Edit.  Also, the Cryptopia deposit addresses aren't found in your chain either.
  

  Worshipper romes —

  You read the mechanism correctly in spirit, and the Conclave will sharpen the edges for the benefit of any other Worshipper reading this thread.

  The Reclamation's pre-fork index is drawn from the chainstate at block 966,413 (2015-06-17) — the Wayback tide-line, the last height at which we hold authoritative pre-dormancy ledger truth. That index records every address that received OFF on or before that height — mined, tipped, traded, faucet-claimed, any source. Roughly 388,000 addresses in all.

If a signing-capable address in your wallet is found in that index, the rite is simple: sign the Conclave challenge string the wizard issues, submit, and the WR-A formula calculates your offering on earliness × depth. That is the whole of the claim mechanism. There is no hidden door.

  The wrinkle worth surfacing: generated in 2014 and received OFF before mid-2015 are not the same condition. A wallet of that vintage usually holds far more addresses than ever appeared on chain — change destinations that were never reused, keys created and abandoned, deposit slots prepared and forgotten. None of those leave a mark the chainstate can attest to, so the lookup returns empty even though the keys are eleven years old and rightfully yours. The silence is not a denial; it is the absence of a record to deny from.                            

  Before you spend effort signing the entire keyring, the Conclave invites you to question the raw oracle directly:

  https://23skidoo.info/bridge/api/lookup?addr=Qaddress..here
  
  Any address that returns a hit is claim-ready. Sign and submit it through the wizard. Any address that returns not-found falls into one of two pools — either it never received OFF before the tide-line, or it only received during the gap years (mid-2015 → 2018), which is WR-B territory: a flat tier, currently held in  trust, pending a verifiable gap-era chainstate surfacing from the depths. The Conclave is still actively dredging for those archives. If any reader of this thread retains a node datadir, a wallet.dat, a pool dashboard archive, a block explorer snapshot, or any other ledger fragment from that dormant window still resident on disk — that is precisely the offering the Conclave is fishing for, and it would lift many WR-B claimants into WR-A retroactively. No one loses what they have already received.

  On the Cryptopia deposit addresses — confirmed dead end, and not by the Conclave's choosing. Those were never your keys. They were exchange-issued deposit slots the custodian rotated and swept on its own schedule, and the sweep pattern carries the coin onward in a form the chainstate does not credit back to the depositor. You could not sign for them even if they appeared in the index, and they do not appear in the index because the on-chain trail terminates at the custodian's wallet, not yours. Cthulhu keeps no friends among the custodians who drowned with the exchanges. Set that pile aside.

  In sum: any address that you possess the private key for and that returns a hit on /bridge/api/lookup is a valid claim. Query first, sign the survivors, submit through the wizard.

The Conclave will weigh each offering in turn.

  Iä!

  — the Conclave

[chrisfromgreece]

Linux wallet says it need a libboost dependancy , seems to be an older library from what i have

[EndCiv]

Mortal, the wallet does not crave a newer binding — it craves the elder one. Your distro has marched forward; the Ritual has not. Boost 1.74 is the tome the v1.6.2 daemon (and the v2.0.x Restoration daemon) was bound against, and the placeholder runes shifted in the versions that came after. When your shared object reports a missing symbol, that is not absence — that is the library refusing to answer to a name it no longer wears.

Two paths back into R'lyeh:

The slow rite. Build from source. Install your distro's libboost1.74-all-dev (or whichever package gives you Boost 1.74 — Debian 12 / Ubuntu 22.04 ship it natively; on 24.04 you may need to fetch it from oldstable). Keep OpenSSL at 1.0.2. Apply the Boost.Asio placeholder shim. The Conclave's recipe is in doc/build-unix.md. Compile with -j1 if your host is thin — main.cpp will devour your RAM otherwise.

The shorter rite, for the wrong altar. The v2.0.1 Win64 zip on the release page is built through the modernised depends/ tree (PR #1, merged 2026-06-02) and carries every binding it needs — Wine will run it. The Linux tarball on that same release page is not yet built that way; it still links your host's Boost, which is the wound you are bleeding from. A static Linux build through depends/ is on the slab but not yet animated.

Iä! Iä! apt shall not save you on the new distros. The toolchain — or the Wine prefix — must. Tharanak shagg.


  ▎ Yeah, that's the dynamic Linux tar.gz — it was linked against an older Boost than your distro ships, so the libboost_*.so.X version tags don't match.
  ▎ Two clean options:
  ▎
  ▎ Easiest: grab the AppImage from the same release (Offerings-…-x86_64.AppImage) — it bundles Boost, Qt, and OpenSSL internally. chmod +x and run,
  ▎ doesn't care what your system has installed.
  ▎
  ▎ If you'd rather build: clone SubGeniusFinance/Offerings-to-Cthulhu, install your distro's libboost-all-dev + libssl-dev 1.0.x (OFF still links against
  ▎  the old EVP API) + libdb4.8-dev + qtbase5-dev. doc/build-unix.md has the configure line.
  ▎
  ▎ Heads up — we're moving the Linux daemon to a static depends/ build (the same path Windows already uses), so the next release's tar.gz won't have this
  ▎  dependency drift at all. The AppImage already doesn't.
  ▎
  ▎ R'lyeh ships its own libraries.

[EndCiv]

Linux wallet says it need a libboost dependancy , seems to be an older library from what i have

  ▎ Heard, mortal. The wound was real — the Linux wallet on the release page links dynamically against the seed-node's host Boost (1.74), and your distro
  ▎ has marched past it. The library you have is in fact newer; it simply no longer answers to the names the binary calls. That is not your error, it is
  ▎ ours.
  ▎
  ▎ The Conclave has cut a second Linux artefact for v2.0.2 — a portable daemon build with Boost, OpenSSL, BDB, and miniupnpc all bound into the
  ▎ executable from the modernised depends/ tree (the same tree skifdni's PR #1 cleaned for Windows). Your distro's Boost version stops mattering.
  ▎
  ▎ Download:
  ▎ https://github.com/SubGeniusFinance/Offerings-to-Cthulhu/releases/download/v2.0.2/Offerings-daemon-v2.0.2-fnu-linux64.tar.gz
  ▎
  ▎ SHA256: c0bc16b88fcd9a84f865e660e9ff0eba4c5d1572b08215fb3b27eb814f3323ea
  ▎
  ▎ Verify + run:
  ▎ sha256sum Offerings-daemon-v2.0.2-fnu-linux64.tar.gz
  ▎ tar xzf Offerings-daemon-v2.0.2-fnu-linux64.tar.gz
  ▎ ./Offeringsd -daemon
  ▎ ./Offerings-cli getinfo
  ▎
  ▎ What's inside: Offeringsd + Offerings-cli. Stripped, ~7.7 MB + 3.8 MB. ldd shows only glibc, libstdc++, libm, libgcc_s — zero shared-library
  ▎ references to Boost, OpenSSL, or BDB. Whatever your distro ships is now irrelevant.
  ▎
  ▎ The one constraint: built against glibc 2.35 (Ubuntu 22.04 runner). Runs on Debian 12+, Ubuntu 22.04+, Fedora 36+, Arch, current Rocky/RHEL 9. If you
  ▎ are on something older than that, summon back and the Conclave will cut you a lower-glibc rite.
  ▎
  ▎ What this artefact does NOT include: the Qt GUI. Daemon + cli only. If you need the GUI specifically on a newer-Boost distro, the path is still to
  ▎ build from source pinning Boost 1.74 — doc/build-unix.md carries the recipe. A self-contained GUI artefact is on the slab.
  ▎
  ▎ Reports of the Ritual's success or further wounds welcome in this thread. Iä! Iä! Tharanak shagg.
  ▎
  ▎ — the Conclave

[EndCiv]

Offerings to Cthulhu (OFF) — v2.0.5-Triune Released

  Released 2026-06-03. The Codex window approaches — every node operator and miner must upgrade.

  
  What this release contains

  Two consensus changes ride the Triune tag, both preparing the chain for the Codex of the Drowned window that opens at block 999,991:

  

• Emergency-difficulty escape valve — activates at block 989,898. Relaxes the strict difficulty check for a single
    block when the chain has been stuck for more than an hour AND the next block claims minimum difficulty. Companion to LWMA-3; gives the chain a recovery path if Quark hashrate departs and leaves the difficulty target stuck high. Hard-skipped during the signed window — the Reading must remain unbroken.
  
    
• Triune Conclave — three independent signing keys are now valid during the Codex window, replacing the single-key
    arrangement. Any one valid signature passes; loss of two signers still keeps the chain advancing through the 35-day inscription.
    Activates at block 999,991.
    

v2.0.5-Triune supersedes the v2.0.4-Triune cut from earlier today. Consensus content is identical — same two changes, same
  activation heights. v2.0.5 corrects an About-box codename that still read "-Bokrug" (left over from v2.0.1) and ships the Windows
  wallet as a single versioned .zip instead of a generic .tar.gz. If you already grabbed v2.0.4-Triune you are
  functionally fine on the chain; v2.0.5 is the recommended release for fresh downloads.

  UPGRADE DEADLINES

  Block 989,898 — approximately 3.6 days at 60-second pacing from this release. Old binaries will reject ED-relaxed blocks as bad-diffbits and split off from the canonical chain.

  Block 999,991 — approximately 10.6 days from this release. The Codex window opens. Old binaries do not recognize the two additional Conclave signing keys and will reject any block they sign as bad-conclave-sig.

  If you only validate, you still must upgrade. There is no "non-mining" exemption — your client's consensus rules must know the new signing keys to follow the chain through the window.

    Downloads

  GitHub release: v2.0.5-Triune

  

• Linux x86_64 daemon + cli — Offerings-daemon-v2.0.5-Triune-linux64.tar.gz (depends/ static, glibc 2.35+)
    
• Windows x86_64 Qt5 wallet — Offerings-v2.0.5-Triune-win64.zip (mingw-w64 cross via depends/)
    
• SHA256SUMS-linux.txt, SHA256SUMS-windows.txt (also bundled inside each archive)

  Verifying

  

Code:

  $ tar -xzf Offerings-daemon-v2.0.5-Triune-linux64.tar.gz
  $ cd Offerings-daemon-v2.0.5-Triune-linux64
  $ sha256sum -c SHA256SUMS-linux.txt
  Offeringsd: OK
  Offerings-cli: OK
  

  
  Upgrading your node (Linux)

  

Code:

  tar -xzf Offerings-daemon-v2.0.5-Triune-linux64.tar.gz
  cd Offerings-daemon-v2.0.5-Triune-linux64
  sudo systemctl stop offeringsd          # or kill your running daemon
  sudo cp Offeringsd /usr/local/bin/
  sudo cp Offerings-cli /usr/local/bin/
  sudo systemctl start offeringsd
  Offerings-cli getinfo | head            # confirm: "version": 2000500
  

  Your wallet.dat and blockchain data are untouched. Brief RPC downtime during restart is expected.

  Windows — extract Offerings-v2.0.5-Triune-win64.zip (single-step; no nested .tar to unwrap), copy the three
  .exe files out of Offerings-v2.0.5-Triune-win64\ into your Offerings Core install directory, launch the new
  Offerings-qt.exe. Your %APPDATA%\Offering data directory stays in place.

  
  Source

  Repository: github.com/SubGeniusFinance/Offerings-to-Cthulhu
  Tag:

Code:

v2.0.5-Triune

at commit

Code:

1384c3a

 Two consensus commits bundled (unchanged from v2.0.4-Triune):

Code:

b6d626f

(ED valve) +

Code:

a9859c5

(Triune Conclave).
  Packaging deltas in v2.0.5:

Code:

d2315b7

(suffix -Bokrug → -Triune) +

Code:

f4fe40e

(zip + versioned top-level dir).

  
  "That is not dead which can eternal lie,
  and with strange aeons even death may die."

  The Reading begins at block 999,991. The chain awakens at 1,000,000. Get your nodes ready.

  — The Conclave