Explicit scope.
Permission you can revoke.

On the dedicated hackathon deployment, URL-key permissions cover the entire resolver instance, not one name. Use separate resolver instances for independent activities. Registry references and shared record links can extend the scope; no global one-name isolation is claimed.

Read the real record

Read only · no wallet required

This reads the dedicated ETHOnline Universal Resolver, not the old deployment. The same name may be unregistered here. No previous successful result is substituted for a failed live read.

Name
relaydesk2026.eth
Resolver
Not read yet
Current url
Not read yet

No request has been made yet.

Dedicated ETHOnline deployment — September 8

Real Sepolia transactions

relaydesk2026.eth now uses resolver 0xb5Fc7c9fE83750a40F1701B68718d9fE8E53D707, verified against the dedicated factory and implementation.

  1. RegisterDirect EOA registration succeeded on the dedicated registrar; the exact MockUSDC allowance was consumed.Registration transaction ↗
  2. Grant URL-key authorityThe volunteer's root role stayed zero; the url-key TEXT role became 0x10. This scope covers the resolver instance.Grant transaction ↗
  3. Independent volunteer writesA different wallet successfully set the event URL using the DNS-name setter.Volunteer update ↗
  4. Revoke and verify denialRoot/key roles returned to zero. URL and description simulations reverted with the decoded authorization error; the dedicated Universal Resolver still returned the last URL. No registry resolver-management bypass was found for this volunteer.Revoke transaction ↗

Registration evidence · Granted-role check · Post-revocation check · Decoded transactions

These are dated checks, not a permanent guarantee. Latest independent reread. The separate two-activity comparison and final competition submission are not yet complete.

Old deployment only — not hackathon acceptance

Historical evidence · September 5, 2026
  1. Before delegationThe independent volunteer could not edit either url or description.
  2. Grant one recordThe organizer granted only the url record's TEXT role. Other record edits still reverted.Grant transaction ↗
  3. Edit from a different accountThe volunteer wrote the event link and the same ENS name resolved to the new value.Volunteer edit transaction ↗
  4. Revoke and test denialAll four volunteer role scopes returned to zero. Further edits reverted with EACUnauthorizedAccountRoles; the last published URL remained intact.Revoke transaction ↗

Final read-only check JSON ↗ · Transaction evidence JSON ↗

This is dated evidence, not a claim that live state can never change. The reproducible checker validates the current state separately.

Built for ETHOnline 2026

New application work began after kickoff. The current adapter uses the dedicated Permissioned Resolver, grantSetterRoles and revokeRoles. The older four-scope model shown in historical files is not the current model.

Codex generated the application code and automated tests; Claude reviewed technical material and implementation assumptions. The human participant directed the project, prepared accounts, and reviewed the workflow. AI assistance is disclosed in the submission materials.

Competition prototype. Sepolia test assets only. No private-key import, mainnet transactions, or automatic signing. No customers, revenue, prize awards, or final submission are implied.