Skip to content

[Bug]: Lite names become real subnames with #288 — CLI and truapi read paths still hash them flat #299

Description

@filip-parity

Component

Other

Priority

P2

What happened?

#288 changes how a lite name lives on chain: alice.01 is now a real subname — alice under the container 01, node namehash(namehash(tld, "01"), "alice") — instead of one flat label. The CLI (and truapi's read path) still hash a lite name as a single label, which is correct for every deployment running pre-#288 contracts and wrong the moment #288 ships.

Once a deployment carries #288, every lite lookup/read in the CLI misses again — same failure shape as #291. The fix on the CLI side is small: drop the isLitePersonLabel single-label special case in deriveDomainNode (the per-label fold already computes the right node). truapi's is_lite_label/store-label handling needs the equivalent look.

Expected behavior

Lite names resolve on both pre- and post-#288 deployments during the transition, and the single-label special case is removed once the old deployments are gone.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Tetiary Prioritydotns-sdkRelated to the DotNS SDKtype: bugBug report

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions