RISING SUN ADVENTURE v4.26
Copyright (C) 2026 Rising Sun Industries
Initializing system...
Memory check: 128GB OK
Loading kernel modules...
[OK] aios.kernel
[OK] zk.prover
[OK] ascii.renderer
[OK] terminal.emulator
Mounting filesystems...
/dev/portfolio mounted (24)
/dev/etch mounted (sor)
/dev/nous mounted
Starting services...
etch.daemon [RUNNING]
nous.validator [STAKED]
forecast.ensemble [RUNNING]
caffeine.monitor [CRITICAL]
System ready.
Welcome to RISING_SUN
Press any key to skip...

Password Palace: Zero-Knowledge Authentication Live On-Chain

A real Halo2 proof of a spatial memory palace was generated, verified, and accepted on-chain at block 307,678. A replay of the same attestation was rejected. This is the point where Password Palace's zero-knowledge claim became true.

┌────────────────────────────────────────────────────────────────────────────────────────────────────┐
││
└────────────────────────────────────────────────────────────────────────────────────────────────────┘

On June 10, a real zero-knowledge proof of knowledge of a memory palace was generated, verified off-chain, and accepted on-chain by the Password Palace contract. It completed the full authentication path with no stubs anywhere in the cryptography.

We'll be direct about what that means. This is the point where Password Palace's ZK claim became real. The circuit deployed before it didn't prove knowledge of the palace. The V5 circuit does, and it's now the one running.

The Transaction

FieldValue
Chainmemoria-3
Block307,678
Actionfull_auth
Proof typehalo2_v5
Resultsuccess (gas 229,340)

The room's nonce advanced from 0 to 1. A replay of the identical attestation was rejected: "attestation already used." The proof was consumed exactly once.

What the Proof Proves

  • >The circuit proves knowledge. Halo2 circuit V5 (5.2.0) builds a Poseidon Merkle tree over the user's placed objects *inside the proof*, plus a pepper commitment that binds it to the room. You can't produce a valid proof without knowing the spatial arrangement.
  • >The verifier actually verifies. A real Halo2 IPA verification runs (Pallas/Vesta, k=15) before anything is signed.
  • >The chain checks what was verified. Contract 4.2.0 checks a signed attestation that binds the proof *and its public inputs*. Attestations are single-use, carry a TTL, and advance the room nonce.

The property the product was always meant to have is now true: prove you remember your palace without revealing it.

What It Took

  • >A circuit soundness fix. Empty Merkle padding slots now go through the same Poseidon path as real ones, so every proof matches its verifying key.
  • >A contract built for a strict chain. The chain's WASM VM accepts only the MVP instruction set plus sign-extension. The build is pinned to that target and canonicalized so consensus math stays deterministic.
  • >Dead paths removed. Placeholder hash constants and an unused proof path were deleted, so they can't be wired onto the live path by accident.
  • >106 contract tests passing.

Why It Matters

Password Palace is the identity primitive under the rest of the stack. Concord derives spatial identity from it, and Trove uses the same ZK proving toolchain. "Protected by math, not promises" only holds if the math is actually checked. As of block 307,678, it is.

Try it at passwordpalace.com.