Ethereum Smart Contract

A deployed smart contract identity on an EVM chain.

Blockchain schema.org/EthereumSmartContract ethereum-smart-contract

Fields

2 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 deployed contract.

The canonical shape

What a Ethereum Smart Contract 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": "EthereumSmartContract",
  "chainId": 1,
  "address": "0x0000000000000000000000000000000000000000"
}

build one

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

const atomData = buildAtomData("ethereum-smart-contract", {
	chainId: "1",
	address: "…",
});

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

What a Ethereum Smart Contract 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.

Ethereum Smart Contract — implement → Defined Term proposed

Ethereum Smart Contract — governed by → Defined TermorERC-20 TokenorCompany proposed

Ethereum Smart Contract — use → any atom proposed

Enrichment

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