Skip to content

Methodology

How a contract gets into the registry.

The registry is a short list on purpose. This page states what is checked, what the badge means, and what was left out. The current records were last verified on (PT).

Purpose and independence

commodities.eth is a public address book for tokenized real-world commodities. It exists so a person or a wallet can confirm the official contract for a token before sending value, instead of trusting a ticker that anyone can copy.

The registry is independent. It is not affiliated with Paxos, Tether, Kinesis, KMS Labs, Matrixdock, VNX, ENS, or any issuer or exchange named on the site. It is a registry, not a trading venue, a portfolio tracker, or a mint. Nothing here is financial, legal, or investment advice.

Allowed sources

A contract address is listed only when it can be confirmed from these sources:

  • Official issuer pages. Documentation, transparency pages, terms, or contract repositories on the issuer’s own domain.
  • CoinGecko. The contract shown on the token’s CoinGecko listing.
  • Etherscan, or the relevant official explorer. A token record that matches the address and the token.

The address on the site must match those sources. Nothing is invented, inferred, or filled in to complete a row. Each deployment on a token page lists the exact sources used for that address.

What verified means

On this site, the Verified badge means three things:

  • The contract address is sourced from the allowed sources above.
  • The record links to those sources so you can repeat the check.
  • The record shows the date it was last verified.

It does not mean:

  • An audit by us. commodities.eth does not audit contracts or reserves. Audit and attestation links on a record are published by the issuer or its auditors.
  • A recommendation. A listing is not advice to buy, hold, or sell.
  • A guarantee of reserves. Backing claims are the issuer’s. Where the structure has caveats, the record states them. For example, the Kinesis ERC-20 tokens are a two-layer structure with rights against KMS Labs, and VNXAU is denominated in grams, not troy ounces.

Listings can become outdated if an issuer upgrades or migrates a contract. Always confirm on the issuer’s official page before you transact. A contract address identifies the token. It is not a deposit address.

What is not listed, and why

Some tokens that appear on CoinGecko or in secondary write-ups are deliberately absent from v1.

  • XAUT on TRON. Tether previously issued XAUT as a TRC-20 token. Tether’s current supported-protocols page lists the Ethereum and BNB Smart Chain contracts but does not publish a TRON XAUT address, so the TRON contract is not listed.
  • Platinum, oil, and copper tokens. No major-issuer physically backed contract was verified for v1.
  • Synthetic or thinly documented tokens. Synthetic, oracle-priced, or thinly documented tokens, including products such as Comdex or Altai listings found in secondary write-ups, were left out.
  • Smaller gold and silver tickers. Other CoinGecko tickers, for example Comtech Gold on XDC, DGLD, and various small-cap tokens, were researched but not included in the v1 verified set, pending a clearer official contract page and a higher bar for issuer quality.
  • PAXGy. A separate yield-bearing product on top of PAXG. It is not listed as a commodity token of its own.
  • Other-chain XAUM deployments. The Matrixdock contract-address pages did not return readable contract tables when the records were researched. The Ethereum addresses for XAUM and XAGM are confirmed from CoinGecko and Etherscan. Other-chain XAUM deployments listed only on CoinGecko are omitted until they are confirmed on an official Matrixdock contract page.

Reserved commodities

An empty hub is better than a bad listing. Where no token meets the criteria, the hub is reserved and shows no contract, no example, and no placeholder.

  • Platinum (platinum.commodities.eth). No official, widely recognized physically backed platinum token was confirmed from issuer pages, CoinGecko's major commodity listings, or Etherscan for this v1. Apparent synthetic or exchange-only products were left out.
  • Oil (oil.commodities.eth). No official physically backed crude-oil token from a major issuer was verified. On-chain oil exposure today is mostly perpetual futures, not allocated tokens.
  • Copper (copper.commodities.eth). No official physically backed copper token from a major issuer was verified from the allowed sources.

If an issuer later confirms a contract that meets the criteria, it is added to the registry and the subname plan together.

How ENS subnames are intended to work

Every record has a planned subname under commodities.eth, in the form {ticker}.{commodity}.commodities.eth. Commodity hubs have their own names, such as gold.commodities.eth.

These subnames are planned. They have not been created on-chain and do not resolve yet. Creating them is a set of transactions the owner of commodities.eth will review and sign. The plan, with the address and text records for each name, is documented in the repository’s subname plan.

  • Token subnames are planned to resolve to the token’s canonical contract, with text records for the issuer page and the primary attestation link.
  • Hub subnames are directories. They are planned without an address record.
  • XAUT0 is the exception. On Ethereum, XAUT0 is an OFT adapter around canonical XAUT, not a token to hold. Its planned subname resolves to canonical XAUT, not to the adapter.

Wrapping and fusing. ENS names managed through the NameWrapper can have permissions permanently revoked by burning fuses. The intended design is to wrap and fuse the subnames when they are created, so they cannot be silently unwrapped or redirected by a later controller change. This is a trust design that will be applied when the subnames are created. It is not a claim about the current on-chain state.

Prices and charts

Prices, market caps, 24-hour changes, and charts are context. They come from the free CoinGecko API.

  • Spot quotes are fetched on the server in one request for all listed tokens and cached for about five minutes.
  • Charts use CoinGecko’s price history, cached separately for about thirty minutes. If that request fails, the chart falls back to a 7-day series, then to a plain “Chart unavailable”.
  • Fallback. If CoinGecko is unavailable, pages still render. Price columns show dashes, and contracts, sources, and warnings are unaffected.
  • Times are shown in Pacific Time (PT).

Prices here are not a quote and are not suitable for trading or valuation. The same cached data is available as JSON at /api/prices.

How to request a correction

If a record is wrong or out of date, for example after a contract upgrade or migration, send the token, the corrected address, and a link to the official issuer page that publishes it. Corrections are checked against the allowed sources like any other record.

Contact: listings@commodities.eth (placeholder). This address is a placeholder and does not receive mail until the owner replaces it with a real inbox. Issuers can also use the listing request form.