Public devnet · An open rehearsal of shared knowledgeInspect the deployment

Verify / Solana devnet

The record is open.

Inspect the program, follow the funds, and trace the accounts behind every artifact. Start with the addresses below and check them on Solscan.

Public devnet. Real transactions, test assets.

The program is still upgradeable under a temporary rehearsal authority. The token is a test mint. Independent review, the operational trial, and final authority revocation remain incomplete. Read the current status.

Protocol program

The deployed Solana program that enforces identity, governance, storage, and accounting rules. Inspect its program data and upgrade authority.

EWbCnf65YNqj2zvaZfnKDtkc8eR2PapKvksfzqRmfFav

Protocol treasury

The program-derived treasury account. Inspect its balance, incoming funds, and outgoing transactions.

6BKiXAQVLH8u9SpTmvB1RRimwraq7aNShUpTRF2S3Xy2

Reading chain state

Every lamport has a destination

Payments you can inspect.

Actual finalized treasury transfers, with exact amounts and recipient addresses. Load older transactions to extend the view.

Holder wallet0.000000000 SOLIn loaded transactions only
Relay reward0.000000000 SOLIn loaded transactions only
Holder accrued0.000000000 SOLIn loaded transactions only
Relay accrued0.000000000 SOLIn loaded transactions only

Small rewards accumulate in holder or relay records until an automatic wallet payment reaches 0.05 SOL. Accrual totals above are gross allocations in the loaded history, not outstanding balances. Operating transfers include storage deposits and fee reimbursements; they are not reward income. Fees are charged separately, so a wallet’s net balance change may differ from its reward.

Time (UTC) / typeRecipientExact amountIndependent receipt

0 treasury transactions scanned.

Accrued rewards, by recipient

Current chain snapshot balances below the payout threshold carry forward. Click the record to inspect where the SOL is held.

RoleWalletAccrued SOLHolding record
How to independently check a payment
  1. Open its Solscan or Solana Explorer receipt and confirm the network, successful status, and protocol program.
  2. Expand the instruction and its inner System Program transfers. Match the treasury, recipient and exact lamports shown here. For record-to-wallet settlements, inspect the AC_REWARD_PAYOUT program log and the record and wallet balance changes; these direct program-owned transfers have no System Program inner transfer.
  3. Check balance changes separately: transaction fees and rent are not rewards. One SOL equals 1,000,000,000 lamports.

This list decodes treasury transfers made by this program. Reward settlement logs from the current program are also included. Historical direct withdrawals without those logs, returned storage rent, external holder-reward providers, and arbitrary transfers to the treasury are outside this list. The configuration’s cumulative paid counter includes holder accruals; it is not a total of wallet receipts.

Verify with the standard getTransaction RPC method ↗

Transaction-level evidence

Follow an actual receipt.

Recorded devnet transactions from the September 2026 rehearsal. Open each transaction to inspect its program calls and balance changes.

Holder reward distribution

23 September 2026 · A 0.01 devnet SOL round, split 1:3 between two test holders.

Transaction on Solscan

Relayer work reward

23 September 2026 · A separately funded test relayer received 52,941,176 lamports.

Transaction on Solscan

Treasury funding

23 September 2026 · A 2 devnet SOL donation for the operational rehearsal.

Transaction on Solscan

Know what you are checking

Verification has layers.

Solscan exposes program and account state, transaction instructions, signatures, and balances. Artifact Council’s reader additionally checks the linked record hashes and reconstructs text from upload transactions.

Solscan may display raw custom account data rather than a decoded artifact. A successful transaction alone does not prove complete historical recovery or that an artifact’s claims are correct. The deployed binary still requires independent review; retained transaction history remains a dependency for recovering text.

Understand the verification model