resolver: resolve .simplex names, on smp7 and then on the preset routers

Offen
#2,011 2 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@shumvgolove arbeitet bereits daran.

Seit 03.11.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

.simplex is deployed on Ethereum mainnet (deployments.mainnet.simplex.json in simplex-chat/simplex-domains-app-v3, 475fe430). The current apps (v7.0.4 and v7.1.0-beta.10) already parse .simplex names, and so does every router since #1784. A resolver without the settings below answers every .simplex name 400 tldNotConfigured, because .simplex is unset in snrc-resolve.py (scripts/resolver/README.md, "Configuring addresses").

Apply the steps first to the resolver behind smp7.simplex.im, then to the resolvers behind the preset routers with the names role.

1. Resolver version

simplexmq master at 89c8ba9 (#1993) or later. The .simplex controller has a name policy, and its reservedNames call reverts. A resolver before #1993 reads reservations from the controller, so every .simplex lookup fails.

2. Settings

On the resolver service in scripts/resolver/docker-compose.yml:

SNRC_REGISTRY_SIMPLEX: "0xa7f6497be2f1aa41aa2db55aba8a6e0145dff0d2"
SNRC_REGISTRAR_SIMPLEX: "0x44052f7dc9c1cef20b0319a6b75288988dbb12a1"
SNRC_CONTROLLER_SIMPLEX: "0x8005011c6e966656cdb9a222e9a4792600a37219"

The controller address is the proxy (ETHRegistrarController in the deployment file), not SimplexControllerImpl.

3. Restart

docker compose up -d resolver. The resolver reads the name policy only at startup, so it is restarted again after any later setNamePolicy.

4. Checks

  • startup log line listening: name_policies=…simplex=0xf7054e2fb9ebfd49dd68caffdbe661c03a59b823
  • /health: registries.simplex is 0xa7f6497be2f1aa41aa2db55aba8a6e0145dff0d2
  • /v2/resolve/brenzi.simplex: type registered
  • /v2/resolve/simplex.simplex: type reserved, reservedReason internal
  • /v2/resolve/[<labelhash>].simplex of an unregistered label: type available, basePrice 5000, minLabelLength 6
  • an app on smp7 resolves a .simplex name that has a simplex.contact record; brenzi.simplex has none yet

Verified on 2026-11-03 with master at a0eec71 and the settings above, against mainnet:

  • the registry gives simplex to the registrar, and the registrar's baseNode is namehash("simplex")
  • the controller is a controller of the registrar; its namePolicy() is 0xf7054e2fb9ebfd49dd68caffdbe661c03a59b823 and its prices() is 0x3754fbcd143ab41204f7fa02d8c69ac86b5c0ee8
  • each check in step 4 except the app's answered as stated
Vorherrschende Sprache
Haskell
Sterne
865
Forks
125
Ø Merge
1 T. 20 Std.
Gemergte PRs (30 T.)
64

Entwicklungsumgebung

  • Enthält ein Dockerfile oder eine Docker-Compose-Datei
  • Keine Pull-Request-Vorlage
  • Beitragsleitfaden lesen

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus simplex-chat/simplexmq

Alle Issues in simplex-chat/simplexmq

Ähnliche Issues

Weitere Issues zu Haskell

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.