VAULT · PUZZLE · 10K

Reserve

FORGING

First vault with real gold in it. Marks are scattered across this site; assemble the answer, hash it once, and the wallet opens. More marks surface as the vein deepens.

MODELPUZZLE
ASSAYSHA-256answer → key → self-check on-chain
LOOT0.0739 PAXGlive on-chain balance
KEY-ADDRESS0xAB027E25d30314031E5C29A105C655a3B548AAEbverify balance ↗

RULESET

HOW IT WORKS

The private key is the answer. SHA-256 of the one exact canonical answer equals the key to the address above. Reproduce the answer and you hold the key. Not funded yet.

WHO CAN PLAY

Anyone. No registration. Solving privately hands you the key.

WHAT COUNTS AS A WIN

Possession. Whoever moves the gold on-chain keeps it. No clawback.

HOW YOU KNOW YOU SOLVED IT

Hash your candidate to a key, derive its address, compare with the address published here. A match settles it.

THE DERIVATION

Your answer is not checked by anyone — it is the key. Run it through exactly this, and compare what falls out against the address below. A match means the vault is already yours; nothing to submit, no one to ask.

  1. Assemble the answer to its one exact canonical form. Case, order, and separators are significant; no leading or trailing whitespace, no trailing newline.
  2. Encode it as UTF-8.
  3. SHA-256 those bytes. The 32-byte digest is the private key — nothing is truncated or re-hashed.
  4. Derive the secp256k1 public key, then the Ethereum address (keccak-256 of the uncompressed key, last 20 bytes, EIP-55 checksummed).
  5. Compare to this vault's address. Equal → import the key and sweep. Not equal → keep working; nothing is recorded either way.
Check it locally, in one line: printf '%s' "your answer" | shasum -a 256 — that digest is the private key. Use printf, never echo: a stray newline changes everything. Do this offline; never paste a candidate into an online hash tool.
MUST DERIVE TO0xAB027E25d30314031E5C29A105C655a3B548AAEb

HOW TO SWEEP SAFELY

Cracking the key gives you the gold — but claiming it is where careless sweepers get robbed. Here is the honest mechanics.

The nuance that matters: a signed token transfer cannot be redirected by a front-running bot — only whoever holds this key can move the PAXG. If you are the only one who cracked this cell, the plain method below is safe. The real risk exists only where the keyspace is small enough that others may crack the same key at the same time — then it becomes a mempool race.
  1. Import the key into a fresh wallet (MetaMask, Rabby). Never reuse this key for anything else afterward.
  2. Hide your transaction from the public mempool. Add Flashbots Protect as your wallet's network RPC: https://rpc.flashbots.net/fast. Your transfer is shielded from front-running and sandwich bots and only lands if it doesn't revert.
  3. Fund a little gas, then transfer. Send a small amount of ETH into the cracked address for gas, then move the PAXG to an address you control.
BELT & SUSPENDERS

If the keyspace is small enough that you fear others cracked it too, use an EIP-7702 sponsored-recovery tool (e.g. Antidrain, codeesura/eip7702-asset-rescuer, or the allthingsweb3 migrate-wallet tool): a separate wallet pays all gas and no ETH ever enters the cracked address, so a sweeper's trigger never fires. These are third-party and unaudited — verify the tool before importing a still-valuable key.

PAXG's on-chain transfer fee is currently zero (Paxos removed it in 2024), so you receive the full balance — but that fee is an admin-changeable contract value. Read feeRate() on the PAXG contract before you count on it.

THE RULE, PLAINLY

Possession is possession — whoever moves the gold on-chain, keeps it. If a bot beats you to it, it's gone; that's the game, and it's why we tell you how to sweep privately. An on-chain move is final and we can't reverse it, so we won't pretend otherwise.

Every figure here is read from the public chain or is honestly zero. The site holds nothing. It displays, verifies, and links.