Protocols
.gwei names resolved and registration activity decoded
rotki resolves .gwei names to and from Ethereum addresses and decodes Gwei Name Service registrations, renewals, subdomains, and record changes into readable events.
Supported features
- Forward resolution: type a .gwei name where rotki accepts an address and it is resolved on-chain.
- Reverse resolution: tracked Ethereum addresses that have a primary .gwei name are shown by name instead of by hex, resolved in batches via multicall.
- Name registrations decoded as a trade, so the ETH you paid and the name you received are paired instead of appearing as two loose transfers.
- Renewals, subdomain registrations, primary-name changes, and text-record updates decoded as informational events on the transaction.
Limitations
- Gwei Name Service is an Ethereum mainnet integration. Names are not resolved against other chains.
- Name resolution needs an on-chain call, so it depends on the Ethereum RPC endpoint you have configured being reachable.
Setup
- 1In rotki, open Blockchain Balances → Ethereum and add your address.
- 2Open History and let the transaction sync run. Registrations, renewals, and record changes are decoded automatically.
- 3Your primary .gwei name is picked up on its own; no configuration is needed to show it in place of the address.
Frequently asked questions
Can I enter a .gwei name instead of an address?
Yes. rotki resolves .gwei names on-chain wherever it accepts an address.
Why does my address still show as hex?
Reverse resolution only returns a name when the address has a valid primary .gwei name set, with the forward record pointing back at it. If either side is missing, there is no name to show.
Is the name registration treated as a purchase?
Yes. The ETH spent and the name received are decoded as a single trade, so the cost basis of the name is recorded rather than the payment appearing as an unexplained spend.