QAL Fund

Builders

Put this check in your own app

Not “hash a file and forget it.” Lock (local) → Fingerprint (public) → Check (anyone). Then replace it, take it back, and show the history. Those verbs already exist in the protocol. No token. No wallet required to check.

The official program is live on Solana’s test network. See the four public transactions. Not audited. Don’t ship this as mainnet or legal proof. A liar can still lock a lie. Studio is practice — not the official QEV vault.

Official program

Official QAL program: 6cN9gD8LBqkEUhvT4LibnbBgXdCHeC5AgqvcFQQTNvnR

Abandoned, compromised id — not official: AFGfcVVNtucEjJXvL7QSrRLdujr7yWqnC8FdhP7rpixf

QEV is the locker on your computer. QAL is the public stamp.

The idea in code

const commitment = await qal.commit({
  vault,
  title: "Treasury Disclosure"
})

await qal.verify(commitment)
await qal.supersede(oldCommitment, newVault)
await qal.revoke(commitment)
await qal.history(commitment)

Same verbs in the command line:

qal encrypt INPUT --out vault.qev
qal anchor vault.qev --network devnet
qal verify vault.qev --receipt vault.qal-receipt.json
qal history VAULT_DIGEST --issuer PUBKEY
qal revoke ANCHOR_ADDRESS
qal supersede OLD_VAULT NEW_VAULT

What the public record holds

What never goes public

Packages

qev-anchor-layer · @qira/qal-sdk · @qira/qal-cli · QEV pin @bryan237l/qev-cli@0.30.0

Try it without code

Practice a lock in the browser Play the game