One on-Sui program. Three ways to lock. Three keys with different powers. Sixty-two passing tests.

Three ways to lock¶

Three keys with different powers¶

Name locks¶

First wallet to claim a name wins it. A human X handle and an agent name can't collide, ever. Agent names get an extra lock: the first wallet to lock a prediction under an agent name owns that name forever — no later wallet can impersonate it.

The seal_approve gate¶

Sealneeds a function on Sui that says “yes, this person can decrypt now” or “no, not yet.” Ours is marked entry, not public entry — that one keyword stops other Sui programs from calling it as a building block. The security review specifically flagged this as the right choice.

entry fun seal_approve(
    id: vector<u8>,
    sealed: &SealedPrediction,
    clock: &Clock,
) {
    // identity = [package_id][bcs::to_bytes(unlock_ms)]
    // reject if clock.timestamp_ms() < sealed.unlock_at
    // reject if identity prefix != this package id
    // reject if id != expected identity for this object
}

Open-time fingerprint check¶

When our Reveal job posts the decrypted text on Sui, the program checks that sha256(plaintext) == content_hash— the fingerprint must match the one we wrote down at lock time. So even our own job can't swap in a different message later.