DNNS explorer acceptance record

• Workstream: MX-04

• Environment: Makalu explorer reading the Kamet DNNS registry

• Status: COMPLETE — deployed, documented, live-verified, and accepted

• Last verified: 2026-09-25 00:46:16 UTC

This record separates facts verified from deployed contracts and source-controlled deployment metadata from the final owner and client acceptance evidence. Every MX-04 acceptance item is complete.

Verified deployed v0 baseline

The deployed v0 custom contract source and public deployment manifests are now published in DNNS/. DNNS/PROVENANCE.md records their origin at contracts/dnns/ commit b6669f2aca38f3cb8680e8086920d244c260eeae; that former KaJ Labs repository is no longer publicly available. The Makalu explorer performs read-only resolution against the Kamet deployment because the same EVM address can be used across Lithosphere chains.

Field	Verified value
Network	Kamet
EVM chain ID	900523
RPC	https://rpc-3.litho.ai
TLD	.litho
Supported name form	One second-level label only (2LD)
Registry	0x316dc15bF377F7187e5BE38BA19e673Ca823d1ab
Base registrar	0xB3D1a8e92FFAD73Ab8a07BF37A8E1374df8B3722
Controller	0xb042145B0Fd44b53691b59E98bE8F9F9EB0365c5
Original resolver	0xc0F0849e09Df12E54fe4345ab4535B1F521f2190
Wrapper-aware resolver	0x54639d978418766ccaD25ffb22C58fd5A5Df8C09
Reverse registrar	0xDeFae50866342C8f72bd03292FFeAeb53eC781C2
Reverse default resolver	Not configured in the latest deployment record; the accepted fixture selects the original resolver

The deployed portal rules normalize labels to lowercase and require at least three characters, using only a-z, 0-9, and internal hyphens. Leading/trailing hyphens and subdomains are rejected. The explorer now applies the same rules before making an RPC request.

DNNS owner confirmation — 2026-09-24

The DNNS owner confirmed that the Kamet v0 deployment in the table above remains the supported explorer interface, including RPC, TLD, registry, original resolver, wrapper-aware resolver, reverse registrar, and normalization rules. The owner initially nominated kamet.litho <-> 0xE9267bDf7084815B0754545049AE45FE744Aefa8, then replaced that fixture because the original wallet was unavailable for the required forward and reverse updates. The final accepted fixture is kamet-validator.litho <-> 0xfF74E44E161B1d6e8ffCC4259749768F67dE2cB8. The owner also approved the explorer policy of retaining no persistent positive or negative resolution cache. Reverse names remain displayable only after successful forward verification.

Live forward-resolution evidence

On 2026-08-19, direct read-only JSON-RPC probes reconfirmed chain ID 900523, bytecode at the registry address, and the following registry/resolver results. Each name currently resolves to 0xE9267bDf7084815B0754545049AE45FE744Aefa8 through its registry-selected resolver:

Name	Result
litho.litho	PASS
kamet.litho	PASS
makalu.litho	PASS
dex.litho	PASS
treasury.litho	PASS
team.litho	PASS
faucet.litho	PASS
quantts.litho	PASS
bridge.litho	PASS

These records provide more than the two stable forward fixtures required by the acceptance gate. They do not prove reverse resolution: the reverse node for the shared address currently has no resolver.

Repeat the transaction-free live baseline with:

cd Makalu/explorer
pnpm --ignore-workspace verify:dnns-baseline

The command reads chain identity, registry bytecode, every forward fixture, the reverse node, and the public DNNS README. It does not register, update, or submit any transaction. Its 2026-08-19 result remains externally blocked: all nine forward fixtures pass, no reverse fixture is configured, and the public documentation still describes Makalu 700777 without publishing the verified Kamet registry address.

The same transaction-free command was repeated on 2026-09-20 from current main with the same result: all nine forward fixtures passed, the reverse resolver remained unset, and the public documentation still omitted Kamet 900523 and the verified registry address. No transaction was submitted.

The command was repeated again from current main on 2026-09-23 at 20:13:57 UTC. Chain ID 900523, registry bytecode, and all nine forward fixtures passed; kamet.litho resolved to the owner-nominated checksum address. The reverse node for that address still returned the zero resolver, so no reverse name could be read or forward-verified. The public KaJLabs/DNNS README still described Makalu chain ID 700777 and omitted both Kamet 900523 and the verified registry address. No transaction was submitted. One immediately preceding probe received HTTP 502; three subsequent chain-ID probes and the complete baseline succeeded, so this is retained as transient RPC evidence rather than ignored.

The focused explorer suites also passed 11/11 tests (dnns-resolver.test.ts and dnns.test.tsx) on 2026-09-23, covering forward and reverse behavior, absent records, malformed names, provider/RPC failures, forward verification, and the no-persistent-result-cache boundary.

Final fixture and acceptance rerun — 2026-09-25

The replacement fixture was registered and configured on Kamet by 0xfF74E44E161B1d6e8ffCC4259749768F67dE2cB8. The registry owner and base-registrar token owner match that address. The registry-selected resolver returns the same checksum address for kamet-validator.litho, and the address's reverse node returns kamet-validator.litho. Forward-confirmed reverse resolution therefore passes. The registration expires at 2027-09-24T20:38:38Z and must be renewed before then to preserve the acceptance fixture.

Operation	Transaction hash
Commitment	0x212413568e9d9e8e1fe66b8e197c0003c1319f607e376017d503083ff59bcb8d
Registration	0xc35b85b2d5254423d30956d826891330549ca61dec3a6481f2a0b7a9d493df0d
Resolver	0x85a08e3bd88905224242a0cef84545a2a121c1970b37d7e5aad52adfff2adb7a
Forward address	0x5556a0c008df708369a3db2c2ff0fb689fdbfe7429160ccb3c03ba53e554aebd
Reverse record	0xb32741c413c8567f4d18b13e2cd119b4f7fe382fca988ca0826390fa516f473b

The final client rerun passed chain ID 900523, forward resolution, missing-name handling, reverse resolution, and forward-confirmed reverse resolution. E2E Smoke #138, test/dnns.test.tsx, and test/dnns-resolver.test.ts passed, including malformed-name rejection, RPC/provider failure handling, and no-persistent-cache behavior.

Explorer behavior and automated gates

• Forward results are checksummed before navigation.

• An unset name returns "not found" while an RPC/provider failure is reported as unavailable.

• Negative results are not cached for the life of the explorer process.

• Malformed .litho names are rejected before RPC access.

• Reverse names are displayed only after the name resolves forward to the queried address.

• Components handle reverse-provider failures without an unhandled promise rejection.

• Record the merged PR, deployment run, and live explorer release below.

Documentation/interface disposition

The public DNNS documentation links to KaJLabs/DNNS. PR #1 published the authoritative Kamet chain ID, RPC, contract addresses, normalization rules, reverse rules, and no-persistent-cache policy. PR #2, merged as fea450bdf4886ad3d1a1b6afda41141ef0a766eb, published the final replacement acceptance fixture.

Owner acceptance checklist

• DNNS owner confirms which deployed interface is supported for the Makalu explorer.

• DNNS owner corrects/publishes authoritative network IDs, contract addresses, normalization, and reverse rules.

• DNNS owner nominates one stable reverse record and supplies its expected name/address pair.

• DNNS owner configures the nominated reverse record on-chain.

• Dev Infra repeats live forward, missing-name, malformed-name, RPC-failure, and forward-verified reverse tests against the deployed explorer release.

• DNNS owner approves the no-persistent-cache policy or supplies bounded positive/negative TTL requirements.

• DNNS owner signs the acceptance fields below.

Evidence and approval

Field	Value
Explorer PR	#86
Merge commit	c5448da8c617cf06083f9c08be7e08bd1b5cb6b2
Deployment workflow/run	31826844798 — PASS
Deployed release	c5448da8c617cf06083f9c08be7e08bd1b5cb6b2
Live smoke-test artifact	Public version, home, blocks, shipped-bundle, and two forward-record probes recorded in the MX-04 handoff ledger (2026-08-14)
Owner-input record	PR #217, merged as bdf2f0a47c331845d830e7c41a18565323572d03
Public DNNS record	DNNS PR #2, merged as fea450bdf4886ad3d1a1b6afda41141ef0a766eb
Final automated evidence	E2E Smoke #138; test/dnns.test.tsx; test/dnns-resolver.test.ts — PASS
DNNS approver	Alex Kobzev, Sr Engineer
Approval date	2026-09-25 00:46:16 UTC
Approval evidence	Final client MX-04 rerun: all live, failure-path, automated, and cache-policy checks passed