---
title: veri.vip
description: 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.
url: https://veri.how/smartmetal/veri-vip
area: smartmetal
kind: explainer
updated: 2026-10-15T00:00:00Z
author: Patryk Dwórznik
license: CC BY 4.0
contracts:
  - id: eip155:8453:0x4516a5d613c30a36d157d3b579813734cbb929a4
    name: Veri SmartMetal
    verified:
      date: 2026-10-13
sources:
  - title: veri.vip, token 7777
    url: https://veri.vip/7777
  - title: veri.vip, token 1
    url: https://veri.vip/1
  - title: QRToken introduction, trust model
    url: https://docs.qrtoken.xyz/introduction/#trust-model-provenance-by-source
  - title: QRToken getting started, Verify
    url: https://docs.qrtoken.xyz/getting-started/#7-verify
---

# veri.vip

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.

## Facts

| Fact | Value |
| --- | --- |
| Address | [0x4516a5D613C30A36D157d3b579813734cbb929a4](https://basescan.org/token/0x4516a5d613c30a36d157d3b579813734cbb929a4) |
| Chain | [Base (eip155:8453)](https://basescan.org) |
| Standard | [ERC-1155](https://eips.ethereum.org/EIPS/eip-1155) |
| Proxy | [ERC-1967](https://eips.ethereum.org/EIPS/eip-1967) |
| Implementation | [Series1155V1 0x945D54B21a582d5D186Ae1E449DdC2a4Ce39E26c](https://basescan.org/address/0x945d54b21a582d5d186ae1e449ddc2a4ce39e26c#code) |
| Deployed | [Block 30,569,433 · 22 May 2025](https://basescan.org/tx/0x565a24675da44a562bb5b747b81cdd9290ad0d58f86b1e635e7d888083e3c53e) |
| Source | [Verified on BaseScan](https://basescan.org/address/0x4516a5d613c30a36d157d3b579813734cbb929a4#code) |
| Transactions | [All transactions](https://basescan.org/address/0x4516a5d613c30a36d157d3b579813734cbb929a4) |
| ABI | [smartmetal.json](https://veri.how/abi/smartmetal.json) |
| Last verified | 13 Oct 2026 |

veri.vip has one page for each Veri SmartMetal token, at `https://veri.vip/<id>`, where `<id>` is the token id: [veri.vip/1](https://veri.vip/1) for the first 2024 token, [veri.vip/7777](https://veri.vip/7777) for the first Azure Dragon. The token's metadata names that page as its `external_url`, so wallets and marketplaces link to it. The site is built with [QRToken](https://docs.qrtoken.xyz), Patryk Dwórznik's framework for tokens tied to physical items, and its footer names the QRToken build it runs.

## What a page shows

The page header carries the token's name, series label as the site writes it ("2024 SERIES" or "2026 SERIES"), serial number and standard, plus links to the token on [BaseScan](https://basescan.org/token/0x4516a5d613c30a36d157d3b579813734cbb929a4?a=7777), to its raw metadata file and to its raw image on the IPFS gateway at `ipfs.veridao.io`. Below it, four tabs: Overview, Contract, Metadata and Media.

The Overview tab is a list of values, each tagged with its source:

| Value                                                 | Tag      | Where it comes from                                                                 |
| ----------------------------------------------------- | -------- | ----------------------------------------------------------------------------------- |
| Serial №                                              | ON-CHAIN | The token id on the contract, 0x4516a5D613C30A36D157d3b579813734cbb929a4            |
| Metal, Purity, Weight (oz), Year, Mint, Serial Number | METADATA | The `attributes` of the token's metadata file at `ipfs://<series CID>/<id>.json`    |
| AI Agent Access, P2P Trading, Derivatives             | METADATA | Boolean attributes of the same file, `true`; the page shows the label with no value |

"ON-CHAIN values are read straight from the Base blockchain. METADATA values come from the token's metadata file, stored on IPFS", as the page puts it. Nothing on it is the site's own statement: every row is a value you can read yourself.

## Reading the same values without the site

The page is a view of two sources that are public on their own:

- **The contract.** `uri(id)` on the token contract returns the metadata URI, and `tokenSeries(id)` the series. `tokenStatus(id)` on `SeriesActivation` says whether the token has been activated.
- **The metadata file.** `ipfs://<series CID>/<id>.json`, fetched from any IPFS gateway, holds the name, description, image and attributes the page displays.

[Look up a SmartMetal token](https://veri.how/smartmetal/lookup.md) gives the `curl` command for each, and [SmartMetal series](https://veri.how/smartmetal/series.md) the two series' CIDs and token ids. If the page and the contract ever disagree, the contract is right; the point of the tags is that you never have to take the page's word for it. The QRToken documentation describes the same check from the issuer's side, in [its trust model](https://docs.qrtoken.xyz/introduction/#trust-model-provenance-by-source) and the [Verify step](https://docs.qrtoken.xyz/getting-started/#7-verify) of its getting-started guide.

## What veri.vip is not

It is not the contract, and holds no tokens: the token lives at 0x4516a5D613C30A36D157d3b579813734cbb929a4 on Base, and the pages read it. And it does not decide a token's state: whether a SmartMetal is activated is written in `SeriesActivation` by the activation transaction, as [Activate a SmartMetal](https://veri.how/smartmetal/activate.md) describes, and veri.vip can only report it.

## Sources

1. [veri.vip, token 7777](https://veri.vip/7777)
2. [veri.vip, token 1](https://veri.vip/1)
3. [QRToken introduction, trust model](https://docs.qrtoken.xyz/introduction/#trust-model-provenance-by-source)
4. [QRToken getting started, Verify](https://docs.qrtoken.xyz/getting-started/#7-verify)

## Related

- [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.
- [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.
- [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.
- [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.
