veri.vip

veri.vip has one page for each Veri SmartMetal token, at https://veri.vip/<id>, where <id> is the token id: veri.vip/1 for the first 2024 token, 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, 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, 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 gives the curl command for each, and SmartMetal series 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 and the Verify step 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 describes, and veri.vip can only report it.