ZNS integration — name resolution for CipherScan#8
ZNS integration — name resolution for CipherScan#8craftsoldier wants to merge 18 commits intoKenbak:mainfrom
Conversation
…ate search placeholder
👷 Deploy request for cipherscan pending review.Visit the deploys page to approve it
|
|
Greetings from the ZcashMe team — pushed some architecture changes to this PR, heads up before you merge: The browser no longer calls the indexer directly. The old approach had the SDK running client-side in a What changed:
To test: The indexer URLs, env vars, and API shape are all documented in |
|
Note: the mainnet indexer URL ( |
Greetings from the ZcashMe team!
This PR adds Zcash Name Service (ZNS) support to CipherScan — search for registered ZNS names and view a detail page with resolved address, registration transaction, marketplace status, and event history.
SDK
We published
zcashname-sdkto npm — a zero-dependency TypeScript SDK for the ZNS JSON-RPC API. This PR uses it for all ZNS interactions (name resolution, status, events, validation, pricing).Indexer
The testnet ZNS indexer is live at
https://light.zcash.me/zns(HTTPS + CORS). CipherScan defaults to this URL on testnet. Mainnet is disabled until a mainnet indexer is deployed.To override, set
NEXT_PUBLIC_ZNS_URLin your env.Changes
/name/[name]detail page — resolved address, registration details (tx, block, nonce), marketplace listing, and event history for registered names. Invalid and unregistered names return 404.lib/zns.ts— ZNS client singleton with network guard.Testing
Search "jameswallet" on testnet to see it in action.