Ankh

On-chain console

The Ankh protocol

A life insurance policy is a promise measured in decades. The Ankh protocol puts that promise where no one can quietly rewrite it: policies mirrored on-chain, premiums receipted publicly, claims settled by bonded verification instead of a back-office letter.

Access

Wallet

Detecting browser wallet…

The record layer

AnkhPolicyRegistry

The registry is the on-chain mirror of every Ankh policy that opts in: an ERC-721-style record per policy, premium receipts appended as they confirm, a keccak256 hash of the beneficiary schedule, and the full claim lifecycle. Names, health data, and payout details never touch the chain — only commitments that let anyone verify a policy exists, is paid up, and settled honestly.

Protocol not yet deployed on this network

The AnkhPolicyRegistry is audited-in-progress and headed to testnet — launch soon. When it ships, this console will read your policies straight from the chain. The interface it will expose is already fixed:

Interface · IAnkhPolicyRegistry

Policy records · ERC-721-style

  • function balanceOf(address owner) external view returns (uint256)
  • function ownerOf(uint256 tokenId) external view returns (address)
  • function tokenOfOwnerByIndex(address owner, uint256 index) external view returns (uint256)

Policy mirror · only hashes land on-chain

  • function mintPolicy(address holder, bytes32 policyRef, bytes32 beneficiaryHash, uint256 faceValue, uint8 currency) external returns (uint256 tokenId)

    policyRef = keccak256 of the off-chain policy id · beneficiaryHash = keccak256 of the beneficiary schedule

  • function recordPremium(uint256 tokenId, uint256 amount, bytes32 receiptRef) external

Claim lifecycle · driven by the ClaimsCouncil

  • function openClaim(uint256 tokenId) external
  • function attest(uint256 tokenId) external
  • function dispute(uint256 tokenId) external

    requires an ANKH bond

  • function settle(uint256 tokenId) external

Events

  • event PolicyMinted(uint256 indexed tokenId, address indexed holder, bytes32 policyRef)
  • event PremiumRecorded(uint256 indexed tokenId, uint256 amount, bytes32 receiptRef)
  • event ClaimOpened(uint256 indexed tokenId, uint64 disputeEndsAt)
  • event ClaimSettled(uint256 indexed tokenId, address beneficiary, uint256 amount)

uint8 currency

USD = 0BTC = 1ETH = 2TON = 3ZEC = 4USDC = 5

The capital layer

The ANKH token

ANKH is the protocol’s capital and governance asset. It exists to make one thing true: when a valid claim arrives, the money is there — and everyone who touched the verification had skin in the game.

100,000,000

Fixed supply

ANKH is minted once at genesis. No inflation schedule — underwriting capacity grows only as staked capital and reserves grow.

Staked capital

Backs every policy

Stakers lock ANKH into the capital pool that collateralizes policy reserves. Coverage capacity is a conservative fraction of the pool's mark-to-market value.

Premium flow

Yield for stakers

A share of protocol margin on every premium streams to the capital pool each epoch. Stakers earn for bearing underwriting risk, not for emissions.

Slashing

Honesty, bonded

Claim attestors post ANKH bonds. A false attestation — or a frivolous dispute — burns the bond. Telling the truth is the only profitable strategy.

The settlement layer

How a claim resolves

Four stages, each enforced by the ClaimsCouncil contract. No adjuster’s discretion, no silent denial — every transition is a public transaction.

IHEARTBEATIIATTESTOR QUORUMIIIDISPUTE WINDOWIVPAYOUT

  1. I · Heartbeat

    A dead-man's switch: the policyholder (or their delegate) pings the ClaimsCouncil on a regular cadence. A missed heartbeat past the grace period opens a verification window — no paperwork required to start.

  2. II · Attestor quorum

    Independent, ANKH-bonded attestors verify the death against registries and evidence, then submit signed attestations on-chain. A quorum — e.g. 5 of 9 — moves the claim forward.

  3. III · Dispute window

    The claim rests in public view for a fixed window. Anyone may challenge by bonding ANKH; a challenge escalates to full council review. False claims are slashed, honest challenges rewarded.

  4. IV · Payout

    The window closes, the registry settles: face value releases to the beneficiaries committed in the policy's hash — to their wallets for crypto-denominated policies, via the carrier for USD.

Why this holds up: the heartbeat makes claims cheap to open and impossible to suppress; the bonded quorum makes false attestation ruinously expensive; the dispute window gives the world time to object; and the payout is a state transition, not a decision. The same registry record your policy carries in the dashboard is the record that pays your beneficiaries.