Resolution Metadata

Resolution metadata is the structured data returned when a blockchain naming system, such as the Ethereum Name Service (ENS) or Unstoppable Domains, resolves a human-readable domain name (e.g., alice.eth) to its underlying resource. This data extends beyond a simple address lookup, providing a rich set of attributes that define what the identifier points to and how it should be interpreted by wallets, browsers, and decentralized applications (dApps). Core components of this metadata often include the canonical cryptocurrency addresses (for Bitcoin, Ethereum, etc.), content hashes for decentralized storage (like IPFS or Arweave), and text records for associated information such as email, website URLs, or social media handles.

The technical implementation of resolution metadata is typically governed by a set of standardized smart contract interfaces. For ENS, the primary resolver contract adheres to the EIP-137 and EIP-2304 standards, which define functions like addr(), text(), and contenthash(). When an application queries alice.eth, it first checks the ENS registry to find the assigned resolver contract, then calls the appropriate function on that resolver to retrieve the specific metadata record. This two-step process decouples the domain ownership record from the data it points to, allowing for flexible updates without transferring the domain itself.

This metadata layer is fundamental for user experience (UX) and interoperability in Web3. It allows a single, memorable name to manage a complex digital identity across multiple chains and services. For example, a .eth domain's resolution metadata can contain an EVM address for Ethereum, a Bitcoin address for receiving BTC, an IPFS hash for a hosted website, and a Discord handle for verification. Wallets and dApps consume this metadata to simplify transactions, verify identities, and display verified profile information, moving beyond the raw, inscrutable hexadecimal addresses native to blockchain protocols.

Advanced use cases leverage resolution metadata for delegation and permissions. A resolver can be programmed to return different metadata based on the querying context, such as the caller's address or the specific function invoked. This enables subdomain management, where payments.alice.eth resolves to a multi-signature wallet while blog.alice.eth points to a blog. Furthermore, cross-chain resolution protocols are emerging that allow a name registered on one blockchain (e.g., Solana's Bonfida for .sol domains) to resolve to addresses and resources on entirely separate networks, with the resolution metadata acting as the unifying layer.

The integrity and availability of resolution metadata are critical, as they represent the source of truth for a decentralized identifier. While the domain ownership record is secured on the base blockchain layer (e.g., Ethereum mainnet), the metadata itself is stored on the designated resolver contract. This introduces considerations for data permanence and upgradability. Users must trust the resolver's continued operation, and best practices often involve using well-audited, non-custodial resolver contracts or even immutable resolvers that lock records permanently on-chain to ensure long-term accessibility.

Resolution metadata is the standardized data structure returned by the Chainscore API when it resolves a blockchain identifier, such as an address or transaction hash, into its constituent human-readable components. This process, known as entity resolution, transforms raw on-chain data—like the hex string 0x...—into a structured object containing labels, categories, tags, and risk scores. The metadata acts as a universal translator, providing consistent, enriched context for any address or transaction across supported blockchains.

The core of resolution metadata is the entity object, which classifies the resolved target. Key fields include a primary label (e.g., "Uniswap V3: Router"), a category (e.g., DeFi, CEX, Wallet), and descriptive tags (e.g., router, permit2, flash_loan). For risk assessment, the metadata includes a chainscore—a probability score for malicious activity—and a risk_level (e.g., LOW, CRITICAL). This structured output allows developers to programmatically understand and act upon the nature of any on-chain interaction.

Beyond basic identification, resolution metadata provides critical contextual links. It includes the canonical identifier (the original query input), the resolved name from primary sources like ENS, and direct links to the entity's profile on explorers like Etherscan. For advanced analysis, metadata can contain nested data such as token_details for token contracts or protocol_details for DeFi applications, offering a multi-layered view of the entity's role and composition within the ecosystem.

The generation of this metadata involves querying Chainscore's proprietary Entity Graph, a continuously updated knowledge base that maps relationships between addresses, contracts, and known entities. When a resolution request is made, the system performs a lookup against this graph, aggregates data from on-chain and off-chain sources, applies classification models, and compiles the results into the unified metadata schema. This ensures the information is not just a static label but a dynamic, intelligence-rich snapshot.

For developers, integrating resolution metadata means replacing opaque addresses with actionable intelligence. Use cases are extensive: filtering transaction lists by category to isolate DeFi activity, triggering alerts based on risk_level, personalizing user interfaces with entity labels, or auditing fund flows by tracing through resolved counterparties. By returning this enriched metadata in a single API call, Chainscore turns raw blockchain data into immediately usable business logic, powering safer and more insightful applications.

Resolution metadata is the structured data payload attached to a blockchain transaction that provides the necessary information for a resolver contract to map an on-chain identifier, such as an Ethereum Name Service (ENS) domain or a Decentralized Identifier (DID), to its associated off-chain resource. This metadata typically includes the Content Hash, Text Records, and Resolver Address that define where and how the identifier's data is stored and retrieved. It acts as the programmable link between the immutable identifier on the ledger and the mutable data it represents.

The primary utility of resolution metadata is to enable human-readable addressing and dynamic data association without requiring changes to the core blockchain protocol. For example, an ENS domain's metadata can point to an IPFS hash for a website, store cryptocurrency addresses for various chains (like ETH, BTC, or SOL), or hold profile information such as an email or Twitter handle. This decouples the permanent identifier from the potentially changing resource, allowing users to update their website URL or payment addresses without altering the primary name record on-chain.

From a system architecture perspective, resolution metadata facilitates interoperability and verifiability. By standardizing the structure of this data—often through protocols like ERC-721 for NFTs or ERC-634 for on-chain storage—different applications and wallets can reliably parse and display consistent information. This creates a trust-minimized layer for identity, asset ownership, and resource discovery, as the metadata's integrity and provenance are cryptographically secured by the underlying blockchain.