Cns

In CVM source, @convex.fungible resolves the name directly — this is the normal way to reach a library.

To inspect a name’s record (value, controller, metadata, child node), use a Convex MCP server’s resolveCNS tool if one is configured. Otherwise query it:

Register or Update a Name

The registry actor is #9, available in CVM code as *registry*. It has no cns-update function — use create for a new name and update for an existing one:

These are transactions (they change state). Notes:

• Creating requires controlling the parent namespace. (*registry*/create 'my.name ...) needs the my node to exist and to trust you — otherwise it fails with :TRUST “Forbidden to create CNS node”. Top-level names require special authority.
• create also accepts optional controller, metadata and child arguments: (*registry*/create 'my.name target controller metadata).
• Note (*registry*/register {:name "..."}) is unrelated — it registers metadata for the caller’s own account, not a CNS name.

CNS in Code

• @convex.fungible in CVM source resolves to the actor address at runtime
• Use CNS paths instead of hardcoded addresses for portable code
• (@convex.fungible/balance #TOKEN #USER) calls balance on the resolved actor

Common CNS Names

(Resolve with (*registry*/resolve 'name) to get the current address — these are network-specific.)