Ecosystem
One name.
Many uses.
A name is not a profile on our site. It is a record on Arc that any application can read, so the same six characters work wherever someone bothers to look them up.
Sending USDC
Toorixa.arcresolves to 0x4B615d1b…3150
Amount120.00usdcSigning in
orixa.arcconnectedliveOn a marketplace
orixa.arc5 char · 4y left480usdcBuyWhat apps read
- addr
- 0x4B615d1b…3150
- url
- orixa.xyz
- com.twitter
- @orixa
- avatar
- set
Alsobuild,launch,govern— anything that can read a record.
Sketches of the same name in four places. The record keys and the resolution are real; the surrounding apps are drawn.
In the app
What you can do with a name today.
Five tools, all live, all paid in USDC. Nothing here needs an approval step, because USDC is the gas token on Arc rather than a token you hold alongside it.
For builders
If you already support ENS, you support this.
The resolver exposes the same function signatures ENS does. Integrating means pointing at a different contract address, not writing different code.
Forward resolution
addr(bytes32), addr(bytes32, uint256), text(bytes32, string) and contenthash(bytes32), all with ENS-identical signatures.
Reverse resolution
Names set under the standard <hexaddr>.addr.reverse node, so showing a name instead of an address is one call.
No metadata server
tokenURI renders on chain. There is no image host to go down and nothing off chain for a name to depend on.
Orixa also builds orixa.live, an NFT marketplace and launchpad on Arc, which runs on Arc testnet today. A .arc name is an ERC-721 on Arc mainnet with on-chain artwork and a 5% creator royalty, so it will be tradable there once that reaches mainnet, with nothing for you to do. Until then the market on this site is where .arc names trade. Contract addresses are on Arcscan.
