ChartaMONETARY EXPERIMENT

DON'T TRUST, VERIFY

Check Charta yourself,
straight from the chain.

Your browser reads the program, its upgrade key, the token mint and the vaults directly from Solana and compares them with what the project publishes. No server of ours is involved.

–

Checks

Not run

  1. The program is deployed and executable

    –

  2. The code on chain matches the published build

    –

  3. Who can still change the code

    –

  4. Nobody can mint or freeze CHTA at will

    –

  5. Total supply stays within 90 million

    –

  6. Vaults hold what the rules say

    –

  7. Administrator, recovery key and pause

    –

✓ passes · ! needs your attention (expected before the audit) · ✕ does not match · – not checked yet.

Without this website

Every check above can be repeated with the official Solana command-line tools. Replace the addresses with the ones shown on this page and in the GitHub repository.

Program, data length and upgrade key
solana program show <PROGRAM_ID>
Hash of the code on chain
solana-verify get-program-hash <PROGRAM_ID>
Rebuild from source and compare
solana-verify build in heli-v20-package/heli/solana-v20, then solana-verify get-executable-hash on the result
Mint authority, freeze authority and supply
spl-token display <MINT>

Latest published local build (V23, Agave 2.1.21): ELF SHA-256 ce1949d9b35ca102b4e1ca515d1f26c3808e4cf0880f3063ad5bb98c49cbbc43, 1,010,656 bytes. The program address is compiled into the code, so the deployed build gets its own hash; it is published with the deployment and used by the check above.