# veri.how

> The reference site for everything Veri: Veritaseum’s tokens, contracts, software, intellectual property and their history. Maintained by Patryk Dwórznik. Each fact on a page links to the explorer page or transaction that shows it. Every page has a Markdown twin at its URL plus `.md`.

Veritaseum (VERI) is the ERC-20 contract 0x8f3470A7388c05eE4e7AF3d01D8C722b0FF52374 on Ethereum (eip155:1). Veri SmartMetal is the ERC-1155 contract 0x4516a5D613C30A36D157d3b579813734cbb929a4 on Base (eip155:8453). Not to be confused with Verify Smart Corp (VSMR), Veritone, Verida, Veritable DAO or Palmeiras VERDAO.

## VERI

- [VERI](https://veri.how/veri.md): ERC-20 token on Ethereum, issued by Veritaseum.
- [VERI token contract 0x8f3470A7388c05eE4e7AF3d01D8C722b0FF52374](https://veri.how/veri/contract.md): VERI is an ERC-20 token at 0x8f3470A7388c05eE4e7AF3d01D8C722b0FF52374 on Ethereum mainnet, deployed on 23 Apr 2017 with a fixed supply of 100,000,000 and no proxy, so the code that runs today is the code deployed then. Sections: #deployment, #verified-source, #not-upgradeable, #functions-and-events, #owner, #check-it-yourself
- [VERI supply is fixed at 100,000,000](https://veri.how/veri/supply.md): The VERI contract sets totalSupply to 100,000,000 tokens (10^26 base units at 18 decimals) once, when it is deployed, and has no mint, burn or pause function, so the supply cannot change. Sections: #where-the-number-is-set, #no-mint-burn-or-pause, #what-still-counts-in-the-supply, #two-declarations-one-getter, #check-it-yourself
- [How VERI differs from a modern ERC-20](https://veri.how/veri/erc20-quirks.md): VERI is 2017 code whose initial allocation and ownership transfer emit no Transfer event, whose decimals() returns uint256, whose failed transfers throw instead of returning false, which has no zero-address checks, and whose transferOwnership moves the owner's whole balance to the new owner, as its one call on 24 Apr 2017 did with all 100,000,000 VERI. Sections: #two-balance-changes-emit-no-transfer-event, #decimals-returns-uint256, #failures-throw-successes-return-true, #no-zero-address-checks, #approve-overwrites-with-no-increase-or-decrease, #transferownership-moves-the-owners-whole-balance, #the-code, #what-one-call-does, #edge-cases, #the-one-call-on-record, #what-else-is-missing, #check-it-yourself
- [Check a VERI balance](https://veri.how/veri/check-balance.md): Call balanceOf(address) on the VERI contract through a public Ethereum JSON-RPC endpoint with curl and divide the result by 10^18; read the balance rather than summing Transfer logs, which miss two balance changes. Sections: #1-build-the-calldata, #2-call-the-contract, #3-convert-to-veri, #on-etherscan, #why-not-sum-the-transfer-logs, #for-agents-and-tools

## Veri SmartMetal

- [Veri SmartMetal](https://veri.how/smartmetal.md): ERC-1155 tokens on Base. Each token represents a physical metal piece and is activated with the key from its QR code.
- [Veri SmartMetal contracts on Base](https://veri.how/smartmetal/contracts.md): Veri SmartMetal is an ERC-1155 token at 0x4516a5D613C30A36D157d3b579813734cbb929a4 on Base, an ERC-1967 proxy in front of the Series1155V1 implementation, with a separate SeriesActivation contract that holds every token until its holder activates it; all three were deployed on 22 May 2025 and are built on QRToken. Sections: #how-the-three-fit-together, #the-token-an-erc-1967-proxy, #series1155v1, #roles, #seriesactivation, #check-it-yourself
- [SmartMetal series: 2024 and the Limited Edition Azure Dragon](https://veri.how/smartmetal/series.md): The Veri SmartMetal contract has two series, the 2024 series of 6,566 tokens (ids 1 to 6566, created on chain on 22 May 2025) and Veri SmartMetal Limited Edition Azure Dragon, 16 tokens created on 28 May 2026; each series is one metadata folder on IPFS, and its id is the keccak256 hash of that folder's CID. Sections: #how-a-series-id-is-made, #the-2024-series, #veri-smartmetal-limited-edition-azure-dragon, #check-it-yourself
- [Look up a SmartMetal token](https://veri.how/smartmetal/lookup.md): Given a SmartMetal token id, read its series with tokenSeries(id) and its metadata URI with uri(id) on the token contract, fetch the metadata JSON from any IPFS gateway, and ask SeriesActivation whether it is activated with tokenStatus(id); veri.how also serves the indexed answer at /smartmetal/tokens/<id>.json. Sections: #1-find-its-series, #2-read-its-metadata, #3-check-whether-it-is-activated, #the-indexed-answer, #on-basescan, #for-agents-and-tools
- [Activate a SmartMetal](https://veri.how/smartmetal/activate.md): Activation is one transaction on Base, activate(timestamp, signature) on SeriesActivation, in which the key from the token's QR code signs the activator's address and a timestamp no more than an hour old, and the contract transfers the token from itself to the activator's wallet and emits TokenActivated. Sections: #what-you-need, #1-sign-the-message-with-the-holder-key, #2-send-activate-from-the-activator-wallet, #3-what-the-contract-checks, #4-what-happens, #activate-with-cast, #one-activation-on-record, #check-it-yourself
- [veri.vip](https://veri.how/smartmetal/veri-vip.md): veri.vip is the website that shows one page per Veri SmartMetal token, at veri.vip/<id>, built with QRToken; every value on a page is tagged as read from the Base blockchain or from the token's metadata file on IPFS, so each can be checked without the site. Sections: #what-a-page-shows, #reading-the-same-values-without-the-site, #what-verivip-is-not

## Veritaseum

- [Veritaseum](https://veri.how/veritaseum.md): The project that issued VERI.

## VeriDAO

- [VeriDAO](https://veri.how/veridao.md): The DAO associated with Veritaseum.

## Data files

- [Data files](https://veri.how/data.md): veri.how publishes a token list, a facts file with its JSON Schema, contract ABIs and SmartMetal token state as JSON for wallets, agents and developer tools. What each file holds, with examples.
- [Agent Skills](https://veri.how/skills.md): veri.how publishes two read-only Agent Skills, veri-token and veri-smartmetal, that teach an agent to query VERI and Veri SmartMetal contracts with curl over public RPCs. Install with `npx skills add https://veri.how`.
- [Token list](https://veri.how/tokenlist.json): VERI in the Uniswap Token Lists standard.
- [Facts](https://veri.how/facts.json): Every contract and SmartMetal series as JSON.
- [Facts schema](https://veri.how/facts.schema.json): JSON Schema for facts.json.
- [SmartMetal token state](https://veri.how/smartmetal/tokens.json): Each SmartMetal token’s activation and holder, indexed every 15 minutes; one token at https://veri.how/smartmetal/tokens/{id}.json.
- [Veritaseum ABI](https://veri.how/abi/veri.json): JSON ABI of 0x8f3470A7388c05eE4e7AF3d01D8C722b0FF52374.
- [Series1155V1 ABI](https://veri.how/abi/series1155v1.json): JSON ABI of 0x945D54B21a582d5D186Ae1E449DdC2a4Ce39E26c.
- [Veri SmartMetal ABI](https://veri.how/abi/smartmetal.json): JSON ABI of 0x4516a5D613C30A36D157d3b579813734cbb929a4.
- [SeriesActivation ABI](https://veri.how/abi/smartmetal-activation.json): JSON ABI of 0x412E962bbAE0bB97CE98e74f3424543651a21ce3.

## Optional

- [All pages in one file](https://veri.how/llms-full.txt): Every Markdown twin above, concatenated.
- [RSS feed](https://veri.how/rss.xml): Published articles with full text, newest first.