Prepare changing a subname
update_subnamePrepare changing an existing subname for the user to sign in their own wallet: a new owner (ENSv1), resolver or later expiry, e.g. 'Point pay.alice.eth at the public resolver'. Nothing is sent. To change its records use set_records; to transfer an ENSv2 subname use transfer_name.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>",
"account": "<account>"
},
"name": "update_subname"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Full subname, e.g. pay.alice.eth | |
| owner | No | New owner (ENSv1 only) | |
| expiry | No | ||
| account | Yes | Account that will sign the transactions: an address (0x…) or an ENS name | |
| resolver | No | New resolver address, or none to remove it |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cost | Yes | ||
| plan | Yes | Handle of this plan for get_plan; pass it back unchanged | |
| calls | Yes | Unsigned calls, in order, for the account's wallet | |
| chain | Yes | ||
| steps | Yes | ||
| issues | Yes | Why a checked step would fail | |
| account | Yes | ||
| deploys | No | Contracts the plan deploys, at addresses known in advance | |
| signing | Yes | How to sign the steps, in plain words | |
| summary | Yes | ||
| warnings | Yes | ||
| willSucceed | Yes | Whether the steps that can be checked now would succeed if signed now | |
| requirements | Yes | What the account needs before signing, e.g. a token balance |