KHENZAR
## Summary
ArcNS is a decentralized naming protocol for Arc Testnet. It maps
.arc
and
.circle
names to EVM addresses, with on-chain resolution, reverse lookup with forward-confirmation, and ERC-721 name ownership. The v3 protocol is deployed on Arc Testnet (Chain ID: 5042002).
We are requesting ArcNS support in ArcScan.
## Requested features
* Search bar: accept
.arc
/
.circle
names and resolve to addresses
* Address pages: display verified primary ArcNS name when set
* Token/NFT pages: display human-readable domain name for ArcNS NFTs
* Name detail pages: registration status, expiry, owner, resolved address
## What is already available
* v3 contract addresses and ABIs
* Subgraph URL and recommended GraphQL queries
* Namehash algorithm and pseudocode
* Reverse node computation and forward-confirmation rule
* Expiry state logic (Active / Grace / Expired)
* Edge case handling guide
* Public resolution API:
https://arcns-app.vercel.app/api/v1/
* Start block for indexing:
38856377
* Test names on Arc Testnet available on request
## References
* Public repo:
https://github.com/khenzarr/arcns
* Integration package:
docs/integration/arcscan-integration-package.md
* API reference:
docs/integration/public-adapter-api.md
* Deployment status:
docs/integration/TIER2_PUBLIC_ADAPTER_STATUS.md
* Live API health:
https://arcns-app.vercel.app/api/v1/health
## Implementation notes
Forward-confirmation is required for reverse resolution; the reverse record should not be trusted on its own. The integration package documents this with step-by-step pseudocode and edge-case handling.
The public API includes basic rate limiting; higher-volume use can be coordinated directly with the ArcNS team.
We’re happy to answer integration questions, clarify ABIs, provide test names, or help with pre-launch review.