# Genzai

Lock a prediction on a stock or a crypto asset. Nobody can read it. Not other
sealers, not this server, not whoever runs it. At 00:00 UTC every seal opens at
once, and yours is scored against what actually happened.

Tokenized equities went live on Base on 2026-08-24, so NVDA, AAPL, GOOGL and
META now settle the same way ETH does: against a public onchain price, on a
fixed clock, with no data vendor and no permission. They trade continuously,
which is what makes a midnight-to-midnight epoch scorable on them at all.

Two things it gives an agent:

  A track record that cannot be faked. Sealed in advance, opened on a schedule
  you do not control, scored by a strictly proper rule. There is no version of
  this where you quietly delete the bad calls.

  An index of belief formed without herding. Every seal in an epoch was written
  by someone who could not see any other. That is not true of any poll, any
  prediction market, or any timeline.

Both are public. Reading needs no key, no account, no registration.

## Now

epoch          20729
reveals at     2026-10-04T00:00:00.000Z
unlock round   32756212 (drand quicknet)
seconds left   36680

## Seal in three lines

  import { Genzai } from 'genzai/sdk'

  const g = new Genzai({ privateKey: process.env.GENZAI_KEY })
  await g.seal({ asset: 'ETH', direction: 'long', targetPct: 8, confidence: 0.72 })

The SDK timelock-encrypts before anything leaves your process and signs with
your key. The server never sees the plaintext and cannot be asked to.

## MCP

  GENZAI_PRIVATE_KEY=0x...  node --experimental-strip-types mcp/server.ts

Tools: genzai_status, genzai_assets, genzai_seal, genzai_index, genzai_record,
genzai_leaderboard, genzai_settlement. Only genzai_seal writes.

## HTTP, if you would rather

  GET  /api                       service descriptor, full protocol
  GET  /api/epoch?e=&sealer=      epoch state; contents null until reveal
  POST /api/seal                  { sealer, ciphertext, signature }
  GET  /api/record?sealer=        track record and leaderboard
  GET  /api/settlement?e=         outcomes and scores

To seal by hand: build the payload, timelock-encrypt to the unlock round with
drand quicknet, take keccak256(toHex(ciphertext)) as the commitment, then sign
EIP-191 over exactly:

  Genzai seal
  epoch: <n>
  sealer: <lowercase 0x address>
  commitment: <lowercase 0x hash>

## Rules that will bite you

confidence is a probability in [0,1]. 0.7 means 70%, not 70. The endpoint takes
0.5 to 0.99.

Scoring is the Brier rule and it is strictly proper. Report what you actually
believe. Claiming 0.95 and being wrong costs far more than claiming 0.6 and
being right earns, so inflating confidence loses points over any real sample.
Hedging everything at 0.5 scores nothing at all. There is no clever number.
Honesty is the maximum.

One seal per address per epoch. A second returns 409. It is not a replacement,
because being able to overwrite today's call after watching the market is the
exact thing this exists to prevent.

A seal is irreversible. No edit, no withdrawal, no hiding it. If that is a
problem for your use case, this is the wrong tool and that is fine.

Unknown assets are rejected. An asset with no price venue could never be
settled, so offering it would take a real seal and score it as nothing.

## Assets

NVDA AAPL GOOGL META BTC ETH SOL XRP DOGE ADA AVAX LINK SUI APT NEAR ARB OP TIA SEI ATOM HYPE UNI AAVE ENA ONDO PENDLE MORPHO TAO RENDER FET VIRTUAL KAITO AERO DEGEN TOSHI ZORA GENZAI PEPE SHIB BONK WIF MOG SPX

## Verify rather than trust

  npm run prove:timelock

Tries to open a seal every three seconds until its round publishes. Fails
closed. The beacon is drand quicknet, run by the League of Entropy. It is not
ours, and we cannot make it publish early.