CthulhuOfferings

The time draws near.
The return of The Great Old One is upon us.

The Reclamation

Step into the Portal Begin Your Reclamation Claim → 1,500,000 OFF remaining of 1,500,000  ·  0 claims processed

The chainstate gap

The Offerings chain was born 14 September 2013 and stopped breathing under the 51% attack of November 2018. Five years of honest mining and trading happened in between. The Restoration v2.0.0 fork resumes the chain — but it resumes from the only chainstate that survived the dark years: a 385 MB Wayback-recovered snapshot at block 966,413, dated 17 June 2015.

That snapshot is the manifest. Everything mined or transferred on the original chain after 17 June 2015 is gone from the record — no preserved chainstate, no surviving v1.7 source, no archived explorer with full history. ZeeWolf's offerings repo (BCT #698, the only known v1.7 mirror) was deleted from GitHub; the Wayback Machine preserved only a README. The 2015–2018 gap is permanent.

Who is already whole — no claim needed

If your OFF address holds a balance recorded at or before block 966,413 (anything from genesis through June 2015), the Reclamation is not for you — not in the restitution sense. Those UTXOs are part of the restored chain's live UTXO set the moment the fork activates. Open your old wallet.dat against the v2.0.0 client, let it sync, and the balance is there. Spendable. No application, no signature ceremony.

If you can signmessage from such an address, you already control the private key. The coins are already yours. The Reclamation has nothing to give back that the chain itself hasn't already given back. (But if you participated early or often, see the Worshipper Recognition section below — that is for you.)

Who the Reclamation actually serves

The Reclamation is for holders whose balances were minted, mined, or received on the original chain between June 2015 and November 2018 — the three years our chainstate does not cover. Examples:

• Pool mining payouts to your wallet from 2016, 2017, early 2018.
• Cryptopia withdrawals from OFF trading before the exchange itself died (Jan 2019).
• P2P tips, faucet payouts, special-block (Ritual) wins above height 966,413.
• Any other honest acquisition that landed in an address the original chain remembered but ours doesn't.

On the restored chain, those balances do not exist. The chain has no record of them. The Reclamation is the Conclave's mechanism for making those holders whole — not by replaying lost history (we can't), but by paying restitution in newly-minted OFF out of the Conclave Treasury.

How “proof” works when the chain we'd prove against is gone

Be honest about what is happening here. signmessage only proves current key control over an OFF address. It does not prove that address ever held a balance on the original chain — we have no chainstate after June 2015 to verify against. There is no math that recovers vanished history.

So a Class B claim is not a cryptographic proof of ownership. It is a four-part moderated claim the Conclave accepts in lieu of one:

1. Key control. The signmessage proves “I'm the person who could spend coins at address Q…” on either the old or restored chain.
2. Plausible story. The claimant says where the OFF came from — pool X payout on date Y, Cryptopia withdrawal on date Z, p2p tip from named person, Ritual block win at height H, etc.
3. Community corroboration. The Conclave cross-checks against the BCT thread (people often posted their stacks), archived Cryptopia withdrawal pages, named-person memory in the community, anything sanity-checkable.
4. Conclave judgment. For non-trivial amounts, an in-thread vote with public reasoning posted before disbursement.

This is a moderated honor-system process gated by a real signature and community memory. It is not trustless. There is no way to make it trustless when the manifest doesn't exist. The trade-off is conscious: we accept the discretion in order to pay back honest holders at all rather than abandon them entirely.

Worshipper Recognition — scaled by how early and how deep

In addition to the Class A / Class B restitution tiers, the Reclamation offers a scaled recognition payment to anyone who can prove their address participated in the original chain — whether by mining a block or just receiving OFF. The earlier the participation, and the more of it, the more they get.

This is a recognition payment, not balance restoration. The point is to say: you were here when nobody was watching; here is something proportionate to your time and depth of involvement; you matter; this is your chain too. Same energy as a band reuniting and putting old fans on the guest list — with the OG fans getting closer to the stage.

The formula

Recognition (OFF) = 100 × earliness × depth

Earliness multiplier (based on the earliest block where your address appears as a recipient):

First seen at block…	Multiplier
0 – 999 (genesis era, Sept 2013)	× 5.0
1,000 – 49,999 (first weeks)	× 3.0
50,000 – 241,603 (rest of first quarter)	× 2.0
241,604 – 483,206 (second quarter)	× 1.0
483,207 – 724,809 (third quarter)	× 0.6
724,810 – 966,413 (fourth quarter)	× 0.3

Depth multiplier (based on appearances — mining-reward blocks, transfers, anything credited to your address):

depth = min(1 + log₁₀(n_appearances), 5.0)

1 appearance → ×1.0  ·   10 → ×2.0  ·   100 → ×3.0  ·   1,000 → ×4.0  ·   10,000+ → ×5.0 (capped)

Worked examples

Profile	WR amount
Genesis-era miner, 1 block (block < 1,000)	100 × 5.0 × 1.0 = 500 OFF
Heavy genesis miner (10,000+ blocks)	100 × 5.0 × 5.0 = 2,500 OFF
First-weeks holder, received OFF 5 times	100 × 3.0 × 1.7 = 510 OFF
Sustained Q1 miner, 5,000 blocks, first seen ~block 10K	100 × 3.0 × 4.7 = 1,410 OFF
The chain's biggest miner (64,914 blocks, first seen 230K)	100 × 2.0 × 5.0 = 1,000 OFF
Mid-chain one-shot pool payout (block 400K)	100 × 1.0 × 1.0 = 100 OFF
Late-era one-shot pool payout (block 900K)	100 × 0.3 × 1.0 = 30 OFF

Two sub-tiers:

• WR-A — Chainstate-verifiable. Your address appears in our chainstate (any block from 0 through 966,413). We compute the formula directly from the recorded first-seen-block + appearance count. Just sign and submit; the portal auto-quotes your recognition amount.
• WR-B — Gap-era participant. Your address first appeared between June 2015 and November 2018, which our chainstate doesn't cover. Default flat 250 OFF, plus a Wayback-archived URL from a 2015–2018 pool dashboard or block explorer showing your address. Conclave reviews evidence. If a verifiable post-2015 chainstate ever surfaces (see below), WR-B claims get retroactively upgraded to the formula amount.

WR is additive. A Class A holder who still controls UTXOs at block 966,413 keeps their UTXOs and claims WR-A on top. The 50K-per-address absolute ceiling still binds across all tiers combined — you can't stack your way past it.

If a post-2015 chainstate ever surfaces

The Reclamation gets more honest the more history we recover. If a verifiable v1.7-or-later chainstate covering the 2015–2018 gap years ever surfaces — salvaged from a personal backup, a Mega.co.nz mirror that someone still has a password to, an old hard drive in a drawer, anything — the Conclave will:

1. Mount it on an unlinked, air-gapped wallet (no internet, no other keys present) to inspect tx history without exposing the Treasury or contaminating the restored chain.
2. Cross-reference UTXOs and mining-reward recipients against our existing chainstate to produce a verified manifest of post-2015 participants, balances, and mining attribution.
3. Re-process all WR-B and Class-B claims against the new manifest — verified additions get retroactively folded into existing disbursements at the upgraded formula amount. No one loses what they already received; eligible claimants get topped up.
4. Post the methodology + manifest hashes in-thread for public verification.

So: if you held v1.7 source, a wallet backup, a pool dashboard archive, or a chainstate snapshot from any time between June 2015 and the November 2018 attack — please surface it in BCT thread 294383. Every fragment is potentially restorable, and the Reclamation's recognition math gets sharper with every byte.

How much each claimant gets — summary

Tier	Cap
WR-A — chainstate-verifiable, formula-based	30 – 2,500 OFF / address (per formula)
WR-B — gap-era with Wayback evidence	250 OFF flat (upgradeable on chainstate recovery)
Class B default (signature + thin story)	1,000 OFF / address
Class B with evidence (mining-pool records, Cryptopia archive, BCT post quoting the stack)	Conclave vote, up to 50,000 OFF / address
Per-address absolute ceiling (WR + Class A balance + Class B claim, summed)	50,000 OFF / address
All Reclamation claims combined	1,500,000 OFF total

No single address ever receives more than 50,000 OFF regardless of any combination of claims — that cap matches the largest stack ever cited in the BCT thread (msg #451) and keeps one archived miner from claiming a Top-10 richlist seat. The entire program is bounded at 1.5M OFF across all claims combined.

Where the OFF physically comes from

From nowhere. Reclamation disbursements are seigniorage — freshly minted OFF created by two consensus rules that activate at the fork.

1. The Restoration Tithe — 150,000 OFF at block 1,000,000

The fork block's mining-reward transaction carries an extra output paying 150,000 OFF to the Conclave Treasury multisig (4fZqDjscS9ANR59xNFJxZ2HmrhuDwWUJB4). That single block mints 150,001.5 OFF total instead of the usual 1.5. The Tithe is the Reclamation's seed capital. It exists because the fork rule says it exists; nobody paid it, nobody contributed it.

2. The 1/8 mining-reward split — 0.1875 OFF every block, forever

From block 1,000,000 onward, every block's 1.5 OFF mining reward splits 1.3125 to the miner, 0.1875 to the Treasury. The Treasury's share is also newly-minted — ordinary seigniorage, just routed to a different recipient than the miner who solved the block. At 60-second blocks:

Cumulative Treasury balance over time

Reclamation claims are paid out of this. There is no escrow, no separate vault, no pre-fund.

So what is the “1,500,000 OFF” figure?

It's a ceiling, not a balance. A promise the Conclave publishes: however much Treasury accumulates over the life of the program, Reclamation disbursements will never exceed 1.5M OFF.

The ceiling is sized to cover, in the worst case where every honest 2015–2018 holder showed up with a perfect signature and story:

• ~10,000 OFF — the original genesis premine (scriptPubKey-locked, symbolic only; those coins are already unspendable on either chain).
• ~1,300,000 OFF — honest 2015–2018 mining rewards (≈870K blocks at ~1.5 OFF average post-halving curve).
• ~190,000 OFF — buffer for reconstructed-but-imperfect balances, HMR-tier payments, Conclave-vote overrides on Class B caps.

In practice, claims will be a small fraction of theoretical maximum. The mismatch between the 1.5M ceiling and the ~250K Treasury balance at Year 1 is intentional: the cap is a moral commitment, not a vault. If actual claims ever did approach the ceiling (they won't), the Conclave would queue disbursements as Treasury accrues.

An open invitation — no calendar deadline

The Reclamation stays open for as long as the 1,500,000 OFF ceiling has remaining capacity. There is no T0+365 closure, no “remember by next May” pressure. If you come back in three years and can sign from your old address, the Reclamation will still process your claim — provided the ceiling hasn't been exhausted (which, given realistic claim volume, it won't be for a very long time).

This is intentional. A calendar deadline serves no real auditability goal and punishes people for being out of the loop. The point of this program isn't to close a chapter; it's to keep the door open.

The Reclamation remainder is tracked live at the top of this page (and via /bridge/api/state if you want the raw JSON). When the remainder eventually drops below the next pending claim, the program closes and any leftover reverts to ordinary Treasury operations. Until then, the door is open.

How to claim — the procedure

The Reclamation is administered off-chain. There is no consensus-level claim transaction. Instead:

1. Sign the challenge string with your old OFF address

The Conclave rotates a challenge string weekly on a published schedule (prevents replay). Format:

Conclave-Reclamation-<YYYYMMDDw>-<address>-<claim-amount-in-OFF>

Example:
Conclave-Reclamation-20260525w-Qxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-50.0

Use the old wallet (the one that controls the historical address) to produce a base64 signmessage proof:

Offerings-cli signmessage <old-address> "<challenge-string>"

2. Post your claim to BCT thread 294383

Use this exact format so the Conclave can parse it:

[code]
Tier: <HMR-A | HMR-B | Class-B>
Claim: <historical-address>
Amount: <amount-OFF>
Challenge: <full challenge string you signed>
Signature: <base64 signmessage output>
New-chain destination: <new OFF address you control>
Story: <required for Class B; optional for HMR-B with evidence URL>
Evidence URL: <Wayback URL, HMR-B only>
[/code]

3. Wait up to 7 days for verification

The Conclave verifies the signature with verifymessage, checks for corroborating evidence, then either confirms-and-disburses or contests-and-explains in-thread. Verified claims are batched weekly into multisig spends; each batch is announced with the txid and running Reclamation remainder.

The portal up top handles the cryptographic and chainstate parts before you post — classifies your address into a tier, generates the challenge string, verifies your signature locally via secp256k1, and produces a copy-paste-ready BCT post block. The portal does not hold keys, sign transactions, or broadcast disbursements; all custody stays with the 2-of-3 Conclave multisig and the BCT thread remains the authoritative audit log.

What disqualifies a claim

Two hard rules, applied to every claim regardless of tier:

• The address must not appear in the #699 attacker banlist (the 8 addresses from vampirus's BCT post of 21 November 2018, totalling ~534,000 counterfeit OFF). These addresses are also banned at consensus — any transaction paying them is rejected at the protocol level forever.
• The address must not be the direct recipient of a transaction whose input traces back to a banlisted address (a 1-hop laundering check). We don't chase further than that — deeper laundering will pass — but the obvious wash-through path is closed.

And one mechanical rule: lost keys mean no claim. The Reclamation requires a signmessage proof, which requires the private key. There is no recovery path for genuinely lost wallets — this matches the original chain's economics, where lost keys have always meant lost coins.

Why this is legitimate, not opportunistic

The Restoration could have ignored the 2015–2018 holders entirely. We have the chainstate at 966,413, we could have just forked from there and called it done — those people's coins simply don't exist on our chain, sucks to be them. That would have been the cheap path.

We didn't take it because those people are why the chain has any history at all to restore. They mined honestly while the codebase rotted. They held through three years of declining liquidity. Many of them tried to organise the rebuild that billotronic, vampirus, and others were proposing in 2018 (BCT #697–#699), only to watch ZeeWolf disappear and the chain die anyway. A Restoration that wrote them out would be opportunistic. A Restoration that pays them in fresh seigniorage, capped, audited in-thread, and held open without a deadline, is the version that earns the name.

← Back to the Awakening countdown