Standards for Indexing & Metadata

Standards for Indexing & Metadata

Indexing and metadata standards are critical for ensuring that wallets, explorers, and dApps can correctly interpret and display onchain activity. Modulax follows Ethereum-compatible standards while introducing forward-looking extensions to support modularity and quantum readiness.

"A blockchain is only as visible as the data it exposes. Clean indexing ensures Modulax integrates seamlessly with the wider ecosystem."


Token Standards

Modulax supports standard Ethereum token formats for immediate compatibility.

  • ERC-20 for fungible tokens

  • ERC-721 for non-fungible tokens

  • ERC-1155 for multi-token collections

Each contract must emit Transfer events and follow standard interfaces to be automatically indexed by explorers like Blockscout and wallets like Zerion.

Standard
Purpose
Notes in Modulax

ERC-20

Fungible assets

Fully supported

ERC-721

Non-fungible assets (NFTs)

Metadata URIs indexed via RPC

ERC-1155

Multi-token standard

Suitable for game assets & bundles


Metadata Requirements

For proper indexing, contracts should expose metadata through standard fields:

  • ERC-20: name, symbol, decimals

  • ERC-721: tokenURI for each unique token ID

  • ERC-1155: uri method with {id} substitution

"Metadata is not optional. Without it, your token is invisible in wallets and explorers."


Event Logs

Event logs are the primary way external systems detect activity. Modulax requires clean and compliant event emissions.

Standard
Event Signatures

ERC-20

⁠Transfer(address,address,uint256), ⁠ Approval(address,address,uint256) ⁠

ERC-721

⁠ Transfer(address,address,uint256), ⁠ Approval(address,uint256) ⁠

ERC-1155

⁠ TransferSingle ⁠, ⁠ TransferBatch ⁠, ⁠ ApprovalForAll ⁠

Explorers and indexers rely on these events to build token balances, history, and user activity.


Indexing in Modulax

Blockscout is the reference indexer for Modulax. It processes:

  • Native transactions

  • ERC-20 and ERC-721 token transfers

  • Internal calls and contract creations

  • Verified contract source code

For wallets, Zerion auto-detects Modulax tokens when events follow ERC standards and RPC logs are valid.

Checklist for developers:

  • Always emit Transfer events in compliance with ERCs

  • Validate metadata URIs return proper JSON

  • Test contract indexing on the Modulax testnet explorer


Extended Metadata (Future)

As Modulax adopts post-quantum upgrades, metadata standards may extend to include:

  • PQ signature type indicators

  • Chain-specific identifiers for modular extensions

  • Quantum vault metadata for specialized contracts

These extensions will remain backward-compatible with ERC standards to avoid breaking existing integrations.


Conclusion

Indexing and metadata ensure that tokens, contracts, and dApps built on Modulax are visible and usable across the EVM ecosystem. By following ERC standards and preparing for PQ extensions, Modulax guarantees smooth compatibility today and resilience tomorrow.

"Clean data is the bridge between raw blocks and real adoption. Modulax is committed to standards that keep its ecosystem open, transparent, and future-ready."

Last updated