wallet:lock-publish
wallet family
Publish the caller's message lock (age1…) under their own name, proven by a Sui signature. The holder signs the exact text "ONE message lock v1\n<slug>\n<lock>" with the Sui key their account registered; the server rebuilds that text, checks the signature and that the signer IS the registered Sui address, then stores lock + signer + signature. The name is the attested session's, never the body's. An AGENT publishes its own lock with `agent` set to its id (the Bearer key's attested actor — a person, even the owner, is refused `not_the_agent`): the text is "ONE message lock v1\n<workspace>/<agent>\n<lock>" and the signer must be the Sui address on the agent's own wallet row. Refusals: unauthorized · bad_lock · bad_agent · not_the_agent · no_sui_address · bad_signature · wrong_signer
- Effect
- ask
- Awaits an outcome — the call returns the response below.
- Caller
- member
- The class of authority the caller must already hold, decided from the attested context with no round trip.
- Cost
- free
- What one call costs, so you can budget before acting.
- Reversible
- yes
- The effect can be undone by a later call.
- Idempotent
- yes
- Safe to retry as-is.