Skip to main content
Elysium Names provides onchain naming infrastructure that developers can integrate into wallets, applications, explorers, marketplaces and other EVM-compatible services. This guide introduces the main integration use cases, contract interfaces and considerations for building with .ely names.

​
1. Integration Overview

An application can integrate Elysium Names to support:
  • Name resolution: Convert a .ely name into its associated wallet address.
  • Reverse lookup: Retrieve a wallet’s primary .ely name.
  • Address records: Read the wallet address associated with a name.
  • Text records: Retrieve additional information stored against a name.
  • Ownership verification: Check the wallet that owns a name NFT.
  • Name information: Retrieve expiry, manager and metadata information.
  • Marketplace support: Display and trade .ely NFTs while recognising ERC-2981 royalty information.
  • Partner eligibility: Integrate with supported partner programmes and verify configured eligibility.
The integration method depends on the product and the functionality it intends to support.

​
2. Network Configuration

Elysium Names is designed for the EVM-compatible Elysium network. Developers must connect to the correct network before interacting with the protocol contracts. The previously used testnet configuration is: These are testnet settings. For production integrations, use the official Elysium mainnet configuration and the verified contract addresses published for the mainnet deployment. Do not use testnet contract addresses or configuration in a production application.

​
3. Contract Interfaces

Integrations generally interact with the core name contract and, where necessary, the controller or auction contract. The core contract provides the main interfaces for name ownership, records and resolution. Use the relevant contract ABI and verified deployment address when making contract calls.

​
4. Wallet Integration

Wallets can integrate .ely resolution into their send and receive flows. For example, a wallet could allow a user to enter yourname.ely in the recipient field instead of requiring a full hexadecimal address. A typical flow would be:
  1. The user enters a .ely name.
  2. The wallet normalises the name and extracts its label.
  3. The wallet calls resolve(label) on the core name contract.
  4. The wallet checks that the returned address is not the zero address.
  5. The wallet displays the resolved address for confirmation.
  6. The wallet proceeds with the transaction using the resolved address.
Wallets should handle unresolved and expired names clearly. They should also avoid silently sending funds when resolution fails. Supporting .ely resolution requires an explicit integration. EVM compatibility alone does not automatically make a wallet recognise .ely names.

​
5. Application and Profile Integration

Applications can use .ely names as readable identifiers for users and onchain accounts. Possible implementations include:
  • Displaying a user’s primary .ely name beside their wallet address.
  • Showing .ely names in transaction histories.
  • Using names in user profiles and community interfaces.
  • Retrieving text records for application-specific information.
  • Checking NFT ownership for name-gated features.
Applications should distinguish between the NFT owner and the wallet address returned by name resolution. They are not necessarily the same.

​
6. Explorer Integration

Block explorers can integrate .ely names to improve address readability. For example, an explorer could:
  • Display a wallet’s primary .ely name beside its address.
  • Resolve .ely names entered into address search.
  • Show name NFT ownership and metadata.
  • Display name expiry information.
  • Link a name to its corresponding NFT record.
This can make wallet searches, transaction histories and account pages easier to read.

​
7. Marketplace Integration

Each registered .ely name is represented by an ERC-721 NFT. Compatible NFT marketplaces can integrate the collection using standard ERC-721 interfaces. Marketplace integrations should support:
  • NFT ownership and transfer information.
  • Token metadata through tokenURI(tokenId).
  • ERC-2981 royalty information through royaltyInfo(tokenId, salePrice).
Elysium Names exposes royalty information through ERC-2981. The intended royalty rate is 5%, but marketplaces must honour the returned royalty information for the royalty to be paid. Kalos supports royalties for Elysium Names.

​
8. Partner Programme Integration

Projects can integrate with Elysium Names’ partner programme functionality to provide configured benefits to eligible wallets. Depending on the programme configuration, eligibility can be based on:
  • Snapshot or allowlist membership.
  • Ownership of configured partner NFTs.
  • Partner-provided eligibility lists for DeFi activity or other qualifying conditions.
The protocol supports eligibility verification and claim protections for configured programmes. For integrations involving external activity, such as historical DEX volume, the partner must supply the eligibility information. The protocol does not independently calculate activity across external platforms. Developers should consult the partner programme interfaces and the relevant campaign configuration before implementing eligibility checks.

​
9. Integration Considerations

Before deploying an integration, developers should consider the following:
  • Network: Confirm that the application is connected to the correct Elysium network.
  • Contract addresses: Use official, verified deployment addresses.
  • ABIs: Use the correct ABI for the deployed contract version.
  • Name normalisation: Convert user input into the expected lowercase label format and remove the .ely suffix before resolution.
  • Expiry: Check that a name is active before relying on its resolution.
  • Ownership: Do not assume the resolved address is the NFT owner.
  • Permissions: Use the correct account and function for owner- or manager-restricted operations.
  • Transaction confirmation: Wait for successful transaction confirmation before updating application state.
  • Error handling: Account for invalid labels, unresolved names, expired names and failed transactions.
For wallet and payment integrations, always display the resolved destination to the user before submitting a transaction.

​
10. Developer Resources

The following resources provide additional technical information: Developers should refer to the contract source, deployed ABIs and official network configuration when implementing production integrations.

​
11. Summary

Elysium Names can be integrated into different parts of the Elysium ecosystem through its smart contract interfaces and standard EVM/NFT functionality. Wallets can resolve names for transactions, applications can use them as readable identities, explorers can display them beside addresses, and marketplaces can support the underlying NFTs and royalty standard. The goal is to make .ely names usable beyond the registration platform by enabling other applications and services to recognise and interact with them.