ERC-20 Token — Classifications

Fields

5 required · 0 recommended. Every field points at its schema.org property — the definition lives in one place, so nothing drifts. The full inherited superset stays available through @0xintuition/schema-org.

Field	Type		Description
`chainId`	integer	required	The EVM chain identifier.
`address`	address	required	The Ethereum address of the token contract.
`name`	string	required	The human-readable token name.
`symbol`	string	required	The token ticker symbol.
`decimals`	integer	required	The number of token decimal places.

The canonical shape

What a ERC-20 Token atom's data looks like. These exact bytes are what calculateAtomId hashes — shared shape is shared identity.

atom data · canonical JSON-LD

{
  "@context": "https://schema.intuition.systems/v1/ethereum.jsonld",
  "@type": "EthereumERC20",
  "chainId": 1,
  "address": "0x0000000000000000000000000000000000000000",
  "name": "Ether",
  "symbol": "ETH",
  "decimals": 1
}

build one

import { buildAtomData } from "@0xintuition/classifications";
import { calculateAtomId } from "@0xintuition/ids";

const atomData = buildAtomData("ethereum-erc20", {
	chainId: "1",
	address: "…",
	name: "Ether",
	symbol: "ETH",
	decimals: "18",
});

// deterministic — same bytes, same ID, offchain and on
const atomId = calculateAtomId(atomData);

What a ERC-20 Token can say

The recommended triple vocabulary for this classification — each row is a claim shape the graph already understands, with the kind of atom expected on the other end.

ERC-20 Token — listed on → CompanyorSoftwareorSoftware Application proposed

ERC-20 Token — priced in → ERC-20 TokenorDefined Term proposed

ERC-20 Token — backed by → ERC-20 TokenorDefined Term proposed

Enrichment

Paste a bare reference and the enrichment engine fills a ERC-20 Token in from its sources (default pipeline: ethereum-smart-contract) — titles, canonical sameAs URLs, and the fields above, merged onto the same deterministic atom.