Skip to main content

The tally

The tally is the machine's value ledger — the record every envelope is written to. Each mint and each move is an audited transition, and the ledger's record is the machine's hash-linked, sealed audit trail — deterministic and node-local, which is exactly what makes it verifiable. You don't take a supply figure on trust; you read it and check it against the chain that produced it.

What the tally records​

Every envelope

One immutable row per charged compute — value, funding, minter, owner, and its Ed25519 signature.

Every move

Mints and transfers as Zeqond-stamped transitions, ordered on the framework's clock and sealed like every other machine event.

The running supply

Minted, held, transferred, and received counters — a public read anyone can reconcile against the record.

Reading the ledger​

GET  /api/chain/YOUR_MACHINE/tally/supply   # current supply — public read
GET  /api/chain/YOUR_MACHINE/tally/tokens   # every envelope on the machine
POST /api/chain/YOUR_MACHINE/tally/verify   # verify a tally claim
GET  /api/tally/ledger                      # the public record, anyone can read

Movements are sealed under Proof of Elapsed Zeqonds like every other machine event. Envelopes can leave a machine as bearer envelopes (/api/tally/coins/migrate-out, …/redeem) — the value travels, the histories stay put.

Try the public read right now:

curl -s https://zeqsdk.com/api/tally/ledger

What a tally is good for​

Beyond the framework's own value flow, the tally is a general auditable counter your machine's logic can use: metering an API you host on a channel, gating a contract, or simply an honest count of anything your machine decides to count — every entry sealed on the same record. The State Tally app is the reference explorer for on-machine receipts.

  • Envelopes — the value primitive the tally records.
  • Bearer envelopes — carry an envelope offline as a self-verifying file.
  • Transparency — the whole network's supply, published live.