Version 0.1 · Public Testnet · November 2026
Both halves match.
Abstract. Tally Chain is a proof-of-work ledger in which a payment is a receipt. The payer, the payee, the amount, the plain-language reason for payment, and an optional 32-byte work hash are signed together and sealed into a block. Both parties read that identical record back and verify it locally in the browser. Neither party holds a mutable copy.
1. The problem
A transfer on a general-purpose chain proves that units moved from address A to address B. It says nothing about what those units settled. In practice, the agreement lives inside a chat log, an email thread, or a screenshot—artifacts that are trivial to crop, edit, or lose. Two people, or a person and an autonomous software agent, cannot point to one self-contained cryptographic object that binds the money to the words.
2. Design
In Tally, the receipt is the transaction itself. Every pay transaction carries a mandatory single-line memo (1 to 140 UTF-8 bytes, with line breaks forbidden at the protocol layer so a second line cannot be concealed). Its notch is SHA-256(memo), recomputed client-side whenever the transaction is inspected. An optional 32-byte mark (ref) commits to an off-chain deliverable, PDF invoice, or repository state without bloating chain storage.
Amounts, senders, and recipients remain public by design. Obscuring the face of a voucher prevents the two halves from being held up side by side.
3. Keys
Each account is a 32-byte ed25519 secret seed generated in the user’s browser. Addresses encode the 32-byte public key plus a 4-byte double-SHA-256 checksum in Base58 with the human-readable prefix tally1. Because the public key is recoverable directly from the address, any client can verify a receipt signature with zero RPC trust.
4. Consensus
Blocks are sealed with SHA-256 proof of work targeting 20-second intervals. Difficulty adjusts on every block and is clamped to a maximum 4× step in either direction. Miners collect 8 tTALLY plus transaction fees, maturing after 3 subsequent blocks.
SHA-256 is used on the public testnet so Web Workers in an ordinary browser and Node.js CLI miners execute the exact same primitive. If dedicated hardware later crowds out general-purpose miners, the header hash can transition to a memory-hard function without altering tally.tx.v1 receipt semantics.
5. Supply on the testnet & $TALLY
Testnet coins (tTALLY) originate exclusively from block rewards and protocol-enforced faucet transactions (25 tTALLY per hour per address). There is no premine and no privileged treasury key. tTALLY has no market value and will not carry balances into mainnet.
$TALLY on Robinhood Chain (contract 0x7e270fbd339c5b6cbddb8db6821ec94184f902fb) is a separate token that funds engineering and audits on the road to Tally mainnet.
6. What comes next
Streams. Scheduled wages that notch every few blocks. Accrued balance vests immediately with the payee whenever a stream is stopped.
Errands. Escrowed payments locked to a task specification. The worker submits the deliverable’s 32-byte mark; the payer releases the lock, or an expiry height returns the funds.
Mainnet. Genesis once Streams, Errands, and multi-node peer replication are specified, tested, and reviewed.
7. What this paper does not claim
Tally does not hide balances or counterparties. It does not store off-chain files or guarantee their availability; it notarizes their 32-byte SHA-256 fingerprint at the moment of payment. A valid signature proves the payer signed those exact bytes; binding release of funds to counterparty delivery belongs to the Errands escrow phase.