Skip to content
GitHub

Name-registry boundary

Planned

@monolythium/[email protected] includes some name-related constants, encoders, and read methods. This documentation does not currently verify a public price quote, registration, reverse lookup, transfer, release, wallet review, or transaction-submission path against the active runtime.

Earlier examples mixed real and nonexistent RpcClient method names. They have been removed. In particular, do not copy lythQuoteNameRegistration or lythReverseLookup examples as 0.6.8 API. An SDK encoder or lythResolveName type does not by itself prove node activation.

Names and subnames must not be used as an agent-wallet, consent, identity, or spending-policy grant. Resolve a name only as advisory input, then display and verify the resulting typed address through a released wallet before any future action.