HANS token

HANS is a standard ERC-20 token with a deliberately small set of powers. Every capability the contract doesn't have is a design decision.

Key facts #

Why uncapped #

A hard supply cap looks reassuring but has two problems for a merger machine: it invites "fully diluted valuation" arithmetic that has nothing to do with real circulating value, and it handcuffs the society ten years out when a merger might genuinely warrant new supply. So instead of a cap, HANS has a process: new tokens can only exist after a multisig approval, a public delay, and a veto window — and every mint is permanently tied to a published document.

Minting #

The mint function has no recipient parameter. New HANS can only ever go to the treasury address. It also requires a memoHash — the hash of the published acquisition memo that justifies the mint — which is emitted on-chain, so every unit of supply expansion is publicly attributable to a specific governance document.

Only the contract owner can call it, and the owner is the timelock. In practice that means a mint takes: a 2-of-3 (later 3-of-5) Safe approval → the timelock delay → open execution by anyone → during which the guardian key can cancel. The full flow is on the Governance page.

The treasury address itself can be rotated by governance through the same timelock path, and the contract refuses to set it to itself or to the timelock (where funds would be stranded).

What HANS does not have #

No pause. No blacklist. No transfer tax. No rebase. No privileged transfers. No on-chain votes (voting weight belongs to sHANS, not HANS). These are absences by design, and because the contract is not upgradeable, they stay absent.

On the test network #

The rehearsal deployment performed one real mint of 1,000 HANS through the full ceremony, so total supply on Base Sepolia reads 1,000,001,000 — the genesis billion plus the rehearsal mint. That was the proof that the governance pipeline works end to end, including a successful guardian veto of a second queued mint.