Skip to main content
Elysium Names uses separate treasury and royalty wallets to manage protocol revenue and secondary-market royalties. These serve different purposes: the treasury receives payments generated by the protocol, while the royalty wallet is designated to receive royalties from eligible secondary-market sales.

​
1. The Treasury

The treasury is the protocol’s designated recipient for payments generated through Elysium Names. These include:
  • Name registrations: Payments made when users register names.
  • Renewals: Payments made to extend the registration period of existing names.
  • Auction proceeds: Winning bids from the single-character name auctions.
Payments are directed to the configured treasury address through the relevant protocol contracts. The treasury address is configurable, allowing the protocol to designate or update the wallet responsible for receiving these funds. The treasury is separate from referral rewards. Referral rewards are accounted for independently and are not automatically treated as withdrawable treasury revenue.

​
2. The Royalty Wallet

The royalty wallet is designated to receive royalties from secondary-market sales of .ely NFTs. When a registered name is sold or transferred through a marketplace, the marketplace can query the NFT contract for the applicable royalty information. Elysium Names implements the ERC-2981 NFT Royalty Standard, which provides a standard way for marketplaces and other integrations to retrieve royalty information. The royalty wallet is independently configurable and does not have to be the same address as the treasury wallet.

​
3. Royalty Rate

The intended royalty rate for Elysium Names is 5% of the secondary-market sale price. For example: If a .ely name is sold for 10 HYPE, a 5% royalty would amount to 0.5 HYPE. The actual royalty amount and recipient are determined by the royalty configuration returned by the deployed NFT contract. Important: ERC-2981 communicates royalty information; it does not force marketplaces to collect or pay royalties. Actual payment depends on the marketplace or integration supporting and honouring the standard.

​
4. How ERC-2981 Works

Elysium Names exposes the ERC-2981 royaltyInfo function. An integrating marketplace can call: royaltyInfo(tokenId, salePrice) The function returns two values:
  • Receiver: The configured royalty wallet.
  • Royalty amount: The royalty calculated from the sale price and the configured rate.
This allows compatible marketplaces to determine the royalty recipient and amount without needing a separate royalty calculation.

​
5. Marketplace Support

Marketplace compatibility is important for royalty collection. Kalos supports royalties for Elysium Names, allowing its marketplace to recognise the royalty information exposed by the NFT contract. Other marketplaces and integrations may also support ERC-2981, but royalty payment should not be assumed unless the marketplace honours the returned royalty information.

​
6. Treasury and Royalty Configuration

The treasury and royalty wallets are separate protocol settings. The actual wallet addresses and royalty rate should always be verified against the deployed contract configuration. Documentation of the intended settings should not be treated as proof that a particular address or rate is currently active on a live deployment.

​
7. Summary

Elysium Names separates protocol revenue from secondary-market royalties:
  • Registration, renewal and auction payments go to the treasury.
  • Secondary-market royalties are directed to the separately configured royalty wallet.
  • ERC-2981 provides royalty information to compatible marketplaces.
  • The intended royalty rate is 5%.
  • Royalty payment depends on marketplace support and enforcement.
This separation makes the protocol’s revenue flow easier to understand while allowing marketplaces to integrate with the standard NFT royalty interface.