radix-community-web

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Radix Community Web — MCP skill

MCP server of https://radix-community.genkipool.com (server name:

radix-community

, version 1.0.0).

https://radix-community.genkipool.com 的 MCP server（server name：

radix-community

，version 1.0.0）。

Connection

连接

Streamable HTTP endpoint (stateless, no authentication):

https://radix-community.genkipool.com/api/mcp

Example (Claude Code):

claude mcp add --transport http radix https://radix-community.genkipool.com/api/mcp

Generic JSON client config:

json

{
  "mcpServers": {
    "radix": { "type": "http", "url": "https://radix-community.genkipool.com/api/mcp" }
  }
}

Streamable HTTP endpoint（无状态、无需身份验证）：

https://radix-community.genkipool.com/api/mcp

示例（Claude Code）：

claude mcp add --transport http radix https://radix-community.genkipool.com/api/mcp

通用 JSON client 配置：

json

{
  "mcpServers": {
    "radix": { "type": "http", "url": "https://radix-community.genkipool.com/api/mcp" }
  }
}

How to work with this server

如何使用此 server

Site questions ("where is X?", "what does this site offer?") →
```
get_site_overview
```
.
Knowledge questions ("how do NFTs work on Radix?", "where is the validator install guide?") →
```
search_radix_docs
```
, then
```
read_radix_doc
```
for the full text. Both accept
```
locale: "en" | "es"
```
— answer in the user's language.
On-ledger data (balances, entity state, transactions, validators, NFTs, holders, component state, blueprints) → the ledger tools. All accept
```
network: "mainnet" | "stokenet"
```
; default is mainnet. Never mix networks: mainnet addresses contain
```
_rdx1
```
, stokenet ones
```
_tdx_2_1
```
(
```
inspect_address
```
tells you which network an address belongs to).
Actions (send tokens, stake, create a token, deploy, log in with Radix, …): this server cannot sign transactions (it is stateless). The safe pipeline is: build the manifest (console tools) →
```
validate_transaction_manifest
```
→
```
preview_transaction
```
(real fees and balance changes, no signature) →
```
explain_manifest
```
so the user understands it → sign. Signing runs on the user's machine through a separate LOCAL MCP server,
```
radix-connector
```
(a small binary from the SDK): call
```
setup_wallet_connector
```
for the one-time install steps. Crucial Pairing Flow: ALWAYS call
```
list_wallets
```
first. If a wallet is already paired, skip pairing and proceed to sign. If not paired, call
```
pair_wallet
```
. For the QR code: if your interface supports images, save the base64 PNG to a file (e.g., in the workspace root) and display it via markdown. If your interface is a text-only CLI, print the ASCII art QR code directly to the chat so the user can scan it from their terminal. Tell them to scan it in Radix Wallet (Linked Connectors), and IMMEDIATELY call
```
pair_status
```
(which will block until they approve). Then use its
```
send_transaction
```
/
```
request_pre_authorization
```
/
```
request_account_proof
```
, or for personas and data
```
request_login
```
(persona login, proof verified locally),
```
request_ownership_proof
```
(exact accounts / persona, nothing to pick),
```
request_authorized
```
(login, login without challenge or use_persona; reset; ONGOING accounts and persona data) and
```
request_data
```
(exact or minimum quantities, emails, phone numbers). The phone shows ONE request at a time and nothing can withdraw one remotely: send one request, wait for its result, never fire several in parallel. Every connector failure has a
```
code
```
, a
```
stage
```
and
```
retry_safe
```
— if
```
retry_safe
```
is NO (e.g.
```
NO_ANSWER
```
: the wallet received it but nobody answered) do NOT resend: ask the user to look at the phone and call
```
await_response
```
;
```
PENDING_IN_WALLET
```
means an earlier request is still waiting (answer it on the phone, or force-close and reopen the wallet if it never shows, then
```
cancel_request
```
);
```
WALLET_UNREACHABLE
```
/
```
NOT_DELIVERED
```
mean it never reached the phone (wallet app closed or in the background —
```
check_wallet_connection
```
);
```
DAPP_NOT_VERIFIED
```
means the dApp identity would make the wallet refuse or silently drop it (
```
check_dapp_identity
```
). Trace any request with
```
connector_log
```
; see what is waiting with
```
pending_requests
```
. Don't wait blindly: if nothing reaches the phone within about a minute, stop and read
```
connector_log
```
(request_start → turn_taken → channel_open → delivered → answered) to see where it stopped. Simulation before the phone (connector ≥ 0.6.0):
```
send_transaction
```
previews the manifest on the Gateway and does not ring the phone when it would fail (
```
PREVIEW_FAILED
```
, retry_safe: yes); pass
```
preview_only: true
```
to simulate without sending. Several processes on one link: two AI sessions, a sudo prompt or a CLI can share the same paired link, and the wallet keeps ONE channel per link — since 0.6.0 connectors take a machine-wide turn and wait for the wallet to settle; an OLDER connector running beside them can make requests vanish. After
```
update
```
, restart the AI tool: a running session keeps the binary it started with (Linux:
```
/proc/<pid>/exe
```
ends in
```
(deleted)
```
). No network on the phone? It can still sign over the USB cable: run the connector's local relay (
```
radix-connector-mcp relay
```
), list it in
```
RADIX_CONNECT_RELAYS
```
, and set it as the wallet's signaling server (URL ending in
```
/
```
, STUN never empty); USB tethering alone is not enough — the phone also needs a WireGuard tunnel to this computer as its default route (PamAuthority:
```
pamauthority wire
```
). dApp identity: ALWAYS pass
```
dapp_definition
```
+
```
origin
```
to these calls so the wallet shows a verified dApp instead of "unverified" — they are optional for
```
send_transaction
```
but REQUIRED for
```
request_account_proof
```
(ROLA login), where they are part of the signed message. Get the values from
```
get_known_addresses {network}
```
(origin is always
```
https://radix-community.genkipool.com
```
; the dApp definition is per-network). Before prompting the phone: the wallet must be switched to the same network as the request (Settings → App Settings → Gateways), or it answers
```
wrongNetwork
```
. Never add
lock_fee
(or
```
lock_contingent_fee
```
) to a manifest: the wallet adds its own fee lock from the fee payer the user picks and rejects a manifest that already has one with
```
invalidRequest
```
. The builder tools never emit it. If the user prefers not to install the connector, they can paste the manifest at
```
https://radix-community.genkipool.com/{locale}/console/transaction-manifest
```
and sign in the browser instead. ALWAYS show the final transaction URL to the user using the custom dashboard: https://radix-community.genkipool.com/es/dashboard/tx/<intent_hash>
AI Safety & Manifest Rules (CRITICAL): NEVER write or guess Scrypto transaction manifests manually from memory. Radix manifest syntax changes frequently and is highly complex (e.g., strict Enum typing, Option/None wrapping). ALWAYS use the builder tools provided by this server (
```
build_fungible_token_manifest
```
,
```
build_manifest_from_template
```
,
```
build_validator_manifest
```
, …). Furthermore, BEFORE calling
```
send_transaction
```
on the local connector to prompt the user's phone, you MUST pass the manifest through
```
validate_transaction_manifest
```
. If validation fails, DO NOT prompt the user; fix the errors or use the builder tools.
Validators: read the current state with
```
get_validator_state
```
before proposing any change, list what is possible with
```
list_validator_operations
```
, then build with
```
build_validator_manifest
```
, which resolves the owner badges the account holds and composes a single proof for all of them. It refuses the three combinations that go wrong on-ledger, and two of them are silent failures rather than errors: register + unregister (or two fee changes) in one transaction COMMIT with the last one quietly winning, and unstake + claim-xrd on the same validator aborts the whole transaction. create-validator must travel alone. Never hand-assemble a validator manifest to work around a refusal — the refusal is the ledger behaviour, not a limitation of the tool.
Bringing a validator up, in this order:
1. ```
create-validator
```
  on its own, with the node's public key (
```
/system/identity
```
  →
```
public_key_hex
```
  ), the fee factor and a
```
payment
```
  in XRD. The creation fee is priced in USD, so preview first: the balance changes show what it really costs and any unused XRD comes back to the account. On Stokenet, fund the account with
```
build_faucet_manifest
```
  beforehand. The owner badge lands in the account as soon as the transaction commits, and the tools read it live.
2. One transaction with
```
profile
```
  +
```
register
```
  +
```
accept-delegated-stake
```
  (all owner-gated, one proof for the three).
3. The node operator sets
```
consensus.validator_address
```
  to the new
```
validator_…
```
  address on the node and restarts it; without it the node never validates.
4. ```
stake-as-owner
```
  once the node is synced (
```
/system/health
```
  reports
```
UP
```
  , not
```
SYNCING
```
  ): an active validator whose node is still catching up misses every proposal it is given.
Transient Gateway errors: a tool failing with
```
NotSyncedUpError
```
means the Gateway is over a minute behind the ledger. Wait about 20 seconds and call it again unchanged; nothing about the request is wrong.

站点问题（“X 在哪里？”“这个站点提供什么？”）→
```
get_site_overview
```
。
知识问题（“Radix 上的 NFT 如何工作？”“validator 安装指南在哪里？”）→
```
search_radix_docs
```
，然后使用
```
read_radix_doc
```
获取全文。两者都接受
```
locale: "en" | "es"
```
——使用用户的语言回答。
On-ledger 数据（余额、实体状态、transactions、validators、NFTs、holders、component state、blueprints）→ ledger 工具。所有工具都接受
```
network: "mainnet" | "stokenet"
```
；默认值为 mainnet。绝不能混用网络：mainnet 地址包含
```
_rdx1
```
，stokenet 地址包含
```
_tdx_2_1
```
（
```
inspect_address
```
可判断地址所属网络）。
操作（发送 tokens、stake、创建 token、deploy、使用 Radix 登录等）：此 server 无法签名 transactions（因为它是无状态的）。安全流程如下：构建 manifest（console 工具）→
```
validate_transaction_manifest
```
→
```
preview_transaction
```
（显示真实费用和余额变化，但不签名）→
```
explain_manifest
```
，帮助用户理解内容 → 签名。签名通过单独的 LOCAL MCP server
```
radix-connector
```
在用户机器上执行（SDK 提供的小型 binary）：调用
```
setup_wallet_connector
```
完成一次性安装步骤。关键配对流程：始终先调用
```
list_wallets
```
。如果 wallet 已经配对，则跳过配对并继续签名。如果尚未配对，则调用
```
pair_wallet
```
。对于 QR code：如果界面支持图片，请将 base64 PNG 保存为文件（例如保存到 workspace root），并通过 markdown 展示。如果界面仅支持文本 CLI，则直接将 ASCII art QR code 输出到聊天中，供用户从 terminal 扫描。告知用户使用 Radix Wallet（Linked Connectors）扫描，然后立即调用
```
pair_status
```
（该调用会阻塞，直到用户批准）。随后使用
```
send_transaction
```
/
```
request_pre_authorization
```
/
```
request_account_proof
```
；对于 personas 和 data，使用
```
request_login
```
（persona 登录，proof 在本地验证）、
```
request_ownership_proof
```
（精确的 accounts / persona，无需用户选择）、
```
request_authorized
```
（login、无 challenge 的 login 或 use_persona；reset；ONGOING accounts 和 persona data）以及
```
request_data
```
（精确或最小数量、emails、phone numbers）。手机一次只能显示一个请求，且任何远程操作都无法撤回请求：每次只发送一个请求并等待结果，绝不能并行触发多个请求。每个 connector failure 都包含
```
code
```
、
```
stage
```
和
```
retry_safe
```
——如果
```
retry_safe
```
为 NO（例如
```
NO_ANSWER
```
：wallet 已收到请求但无人处理），不要重新发送：请让用户查看手机并调用
```
await_response
```
；
```
PENDING_IN_WALLET
```
表示之前的请求仍在等待（在手机上处理；如果始终未显示，则强制关闭并重新打开 wallet，然后调用
```
cancel_request
```
）；
```
WALLET_UNREACHABLE
```
/
```
NOT_DELIVERED
```
表示请求未到达手机（wallet app 已关闭或处于后台——使用
```
check_wallet_connection
```
）；
```
DAPP_NOT_VERIFIED
```
表示 dApp identity 会导致 wallet 拒绝或静默丢弃请求（使用
```
check_dapp_identity
```
）。使用
```
connector_log
```
跟踪任何请求；使用
```
pending_requests
```
查看当前等待的请求。不要盲目等待：如果约一分钟内请求仍未到达手机，请停止操作并读取
```
connector_log
```
（request_start → turn_taken → channel_open → delivered → answered），确认请求停在了哪一步。手机请求前的 simulation（connector ≥ 0.6.0）：
```
send_transaction
```
会在 Gateway 上预览 manifest；如果交易会失败，则不会响铃（
```
PREVIEW_FAILED
```
，retry_safe：yes）。传入
```
preview_only: true
```
可只进行 simulation 而不发送。一个 link 上运行多个进程：两个 AI sessions、sudo prompt 或 CLI 可以共享同一个已配对的 link，而 wallet 每个 link 仅保留一个 channel——从 0.6.0 开始，connector 会获取 machine-wide turn 并等待 wallet 稳定；若旁边运行 OLDER connector，请求可能会消失。执行
```
update
```
后，必须重启 AI tool：正在运行的 session 会继续使用启动时加载的 binary（Linux：
```
/proc/<pid>/exe
```
以
```
(deleted)
```
结尾）。**手机没有网络？**仍可通过 USB cable 签名：运行 connector 的 local relay（
```
radix-connector-mcp relay
```
），将其列入
```
RADIX_CONNECT_RELAYS
```
，并设置为 wallet 的 signaling server（URL 以
```
/
```
结尾，STUN 不可为空）；仅使用 USB tethering 并不足够——手机还需要通过 WireGuard tunnel 将此电脑设为 default route（PamAuthority：
```
pamauthority wire
```
）。dApp identity：始终向这些调用传入
```
dapp_definition
```
和
```
origin
```
，使 wallet 显示已验证的 dApp，而不是“unverified”——它们对
```
send_transaction
```
是可选参数，但对
```
request_account_proof
```
（ROLA login）为必填参数，并且是签名消息的一部分。通过
```
get_known_addresses {network}
```
获取这些值（origin 始终为
```
https://radix-community.genkipool.com
```
；dApp definition 按网络区分）。提示用户查看手机之前：wallet 必须切换到与请求相同的网络（Settings → App Settings → Gateways），否则会返回
```
wrongNetwork
```
。绝不要向 manifest 添加
```
lock_fee
```
（或
```
lock_contingent_fee
```
）：wallet 会根据用户选择的 fee payer 添加自己的 fee lock；如果 manifest 已包含该字段，wallet 会以
```
invalidRequest
```
拒绝。builder 工具不会生成该字段。如果用户不想安装 connector，也可以在
```
https://radix-community.genkipool.com/{locale}/console/transaction-manifest
```
中粘贴 manifest，然后在浏览器中签名。始终使用 custom dashboard 向用户展示最终 transaction URL：https://radix-community.genkipool.com/es/dashboard/tx/<intent_hash>
AI Safety 与 Manifest 规则（关键）：绝不要手动编写 Scrypto transaction manifest，也不要凭记忆猜测其内容。Radix manifest 语法变化频繁且非常复杂（例如严格的 Enum 类型、Option/None 包装）。始终使用此 server 提供的 builder 工具（
```
build_fungible_token_manifest
```
、
```
build_manifest_from_template
```
、
```
build_validator_manifest
```
等）。此外，在调用 local connector 的
```
send_transaction
```
以提示用户查看手机之前，必须先通过
```
validate_transaction_manifest
```
验证 manifest。如果验证失败，不要提示用户；应修复错误或改用 builder 工具。
Validators：提出任何变更之前，先使用
```
get_validator_state
```
读取当前状态；使用
```
list_validator_operations
```
列出可执行操作；然后使用
```
build_validator_manifest
```
构建 manifest。该工具会解析 account 持有的 owner badges，并将所有 badge 组合为单个 proof。它会拒绝三种会在 on-ledger 上产生错误结果的组合，其中两种是静默失败而非报错：register + unregister（或在同一 transaction 中进行两次 fee changes）会 COMMIT，且最后一次操作会悄然生效；在同一 validator 上同时执行 unstake + claim-xrd 则会中止整个 transaction。create-validator 必须单独发送。绝不要为了绕过拒绝而手动组装 validator manifest——这种拒绝是 ledger 的行为，并非工具限制。
启动 validator 时按以下顺序操作：
1. 单独执行
```
create-validator
```
  ，提供节点的 public key（
```
/system/identity
```
  →
```
public_key_hex
```
  ）、fee factor 以及以 XRD 表示的
```
payment
```
  。创建费用以 USD 定价，因此应先 preview：余额变化会显示实际成本，未使用的 XRD 会退回 account。在 Stokenet 上，应先使用
```
build_faucet_manifest
```
  为 account 充值。Transaction commit 后，owner badge 会立即进入 account，工具会实时读取它。
2. 使用一个 transaction 执行
```
profile
```
  +
```
register
```
  +
```
accept-delegated-stake
```
  （三项操作均受 owner gate 控制，并使用一个 proof）。
3. 节点运营者将节点的
```
consensus.validator_address
```
  设置为新的
```
validator_…
```
  地址并重启节点；如果不执行此操作，该节点将永远不会参与 validation。
4. 节点完成同步后（
```
/system/health
```
  报告
```
UP
```
  ，而不是
```
SYNCING
```
  ），执行一次
```
stake-as-owner
```
  ：仍在追赶区块的 active validator 会错过分配给它的每一次 proposal。
临时 Gateway 错误：工具返回
```
NotSyncedUpError
```
表示 Gateway 落后 ledger 超过一分钟。等待约 20 秒，然后原样再次调用；请求本身没有问题。

Output format

输出格式

Every tool returns pre-formatted plain text (banner, aligned key/value rows, tables, fenced code blocks, and a "Next steps" section). It is designed to be read as-is — quote it or summarise it for the user, do not re-parse it as data.

每个工具都会返回预先格式化的纯文本（banner、对齐的 key/value rows、tables、fenced code blocks，以及“Next steps”部分）。其设计目标是可直接阅读——可原样引用或为用户总结，不要将其重新解析为数据。

Typical workflows

典型工作流

"How do NFTs work on Radix?" →
```
search_radix_docs {"query": "NFT"}
```
→
```
read_radix_doc
```
→ answer with doc URL.
"Where is the validator installation guide?" →
```
search_radix_docs {"query": "validator node"}
```
→ share the URL from the result.
"What does account_rdx1… hold?" →
```
get_account_balances
```
.

"Send 10 XRD to Bob" →

build_manifest_from_template {"templateId": "transfer-tokens", "values": {…}}

→

preview_transaction

→ sign with the local

radix-connector

(

setup_wallet_connector

first if not installed) or in the console.

"Sign / actually send this transaction" →

setup_wallet_connector

(install + pair once) → the local connector's

send_transaction {manifest, network, dapp_definition, origin}

→

transaction_status

"Create a token called Foo" →
```
build_fungible_token_manifest
```
→
```
preview_transaction
```
→ user signs in the console.
"Create an NFT collection" →
```
build_nft_collection_manifest
```
(name + the initial NFTs) →
```
preview_transaction
```
→ sign.
"Give me test XRD / fund my Stokenet account" →
```
build_faucet_manifest {"accountAddress": "account_tdx_2_…"}
```
→ sign (Stokenet only).

"Deploy my Scrypto package" →

build_deploy_package_manifest {"rpdHex": "<.rpd hex>"}

→ the local connector's

deploy_package {"wasm_path": "…/pkg.wasm", "package_definition": …}

(it reads the WASM from disk).

"Register / unregister my validator, change its fee, key or delegation" →

get_validator_state

→

build_validator_manifest {"account": "account_…", "operations": [{"kind": "register", "values": {"validator": "validator_…"}}, {"kind": "update-fee", "values": {"validator": "validator_…", "feeFactor": "0.05"}}]}

→

preview_transaction

→ sign. Console equivalent: https://radix-community.genkipool.com/en/console/validator-registration.

"Set my validator's name, description, icon or website" →
```
build_validator_manifest
```
with a
```
profile
```
operation (only the fields you pass are written) → sign. Console: https://radix-community.genkipool.com/en/console/validator-profile.
"What can I claim from my unstakes?" →
```
list_claimable_stake_nfts {"account": "account_…"}
```
→ feed the matured ids to
```
build_validator_manifest
```
as
```
claim-xrd
```
→ sign. Console: https://radix-community.genkipool.com/en/console/validator-staking.
"Create a validator" →
```
build_validator_manifest
```
with a single
```
create-validator
```
operation (it cannot share a transaction with anything) →
```
preview_transaction
```
→ sign → then
```
profile
```
+
```
register
```
+
```
accept-delegated-stake
```
in one transaction → set
```
consensus.validator_address
```
on the node →
```
stake-as-owner
```
once the node is synced. Console: https://radix-community.genkipool.com/en/console/validator-create.
"Which validator should I stake with?" →
```
list_validators
```
→ compare fee/uptime/APY → staking page https://radix-community.genkipool.com/en/console/staking.
"What is this manifest going to do?" →
```
explain_manifest
```
(plain-language steps) +
```
preview_transaction
```
(fees, balance changes).
"What's the XRD price / network status?" →
```
get_xrd_price
```
,
```
get_network_status
```
.
"Log me in / prove who I am" → the local connector's
```
request_login {network, dapp_definition, origin}
```
(the persona signs; add
```
accounts: {quantity: 1, with_proof: true}
```
to prove an account in the same approval) → then
```
request_ownership_proof {identity_address, accounts}
```
whenever exact accounts must be proven again.
"A request never showed on my phone / nothing gets through" →
```
pending_requests
```
→
```
check_wallet_connection
```
→
```
connector_log
```
; answer or force-close the wallet, then
```
await_response
```
or
```
cancel_request
```
. Never resend a request whose failure says
```
retry_safe: NO
```
If the log shows it never got a turn or a channel, look for other connector processes on the machine (an older version, or a session started before an update) and update/restart them.
"What are my accounts / show my balances" (this server is stateless — it has no "connected wallet") → the local connector's
```
request_accounts
```
(no signature) to get the address(es) →
```
get_account_balances
```
for the chosen one.
"Who holds token X? What NFTs exist in collection Y?" →
```
get_resource_holders
```
,
```
get_nft_data
```
.
"What methods does component_rdx1… expose? What's in its state?" →
```
get_component_blueprint
```
,
```
get_component_state
```
,
```
get_key_value_store
```
.

“Radix 上的 NFT 如何工作？” →
```
search_radix_docs {"query": "NFT"}
```
→
```
read_radix_doc
```
→ 使用文档 URL 回答。
“validator 安装指南在哪里？” →
```
search_radix_docs {"query": "validator node"}
```
→ 分享结果中的 URL。
“account_rdx1… 持有什么？” →
```
get_account_balances
```
。

“向 Bob 发送 10 XRD” →

build_manifest_from_template {"templateId": "transfer-tokens", "values": {…}}

→

preview_transaction

→ 使用 local

radix-connector

签名（如果尚未安装，先执行

setup_wallet_connector

），或在 console 中签名。

“签名 / 实际发送此 transaction” →

setup_wallet_connector

（安装并配对一次）→ local connector 的

send_transaction {manifest, network, dapp_definition, origin}

→

transaction_status

。

“创建一个名为 Foo 的 token” →
```
build_fungible_token_manifest
```
→
```
preview_transaction
```
→ 用户在 console 中签名。
“创建一个 NFT collection” →
```
build_nft_collection_manifest
```
（名称和初始 NFTs）→
```
preview_transaction
```
→ 签名。
“给我一些测试 XRD / 为我的 Stokenet account 充值” →
```
build_faucet_manifest {"accountAddress": "account_tdx_2_…"}
```
→ 签名（仅限 Stokenet）。

“部署我的 Scrypto package” →

build_deploy_package_manifest {"rpdHex": "<.rpd hex>"}

→ local connector 的

deploy_package {"wasm_path": "…/pkg.wasm", "package_definition": …}

（它从磁盘读取 WASM）。

“注册 / 注销我的 validator，更改其 fee、key 或 delegation” →

get_validator_state

→

build_validator_manifest {"account": "account_…", "operations": [{"kind": "register", "values": {"validator": "validator_…"}}, {"kind": "update-fee", "values": {"validator": "validator_…", "feeFactor": "0.05"}}]}

→

preview_transaction

→ 签名。等效 console：https://radix-community.genkipool.com/en/console/validator-registration.

“设置 validator 的 name、description、icon 或 website” → 使用带
```
profile
```
operation 的
```
build_validator_manifest
```
（只会写入传入的 fields）→ 签名。Console：https://radix-community.genkipool.com/en/console/validator-profile.
“我可以从未 stake 中领取什么？” →
```
list_claimable_stake_nfts {"account": "account_…"}
```
→ 将成熟的 ids 作为
```
claim-xrd
```
传给
```
build_validator_manifest
```
→ 签名。Console：https://radix-community.genkipool.com/en/console/validator-staking.
“创建一个 validator” → 使用仅含一个
```
create-validator
```
operation 的
```
build_validator_manifest
```
（不能与其他操作共用 transaction）→
```
preview_transaction
```
→ 签名 → 随后在一个 transaction 中执行
```
profile
```
+
```
register
```
+
```
accept-delegated-stake
```
→ 在节点上设置
```
consensus.validator_address
```
→ 节点同步后执行
```
stake-as-owner
```
。Console：https://radix-community.genkipool.com/en/console/validator-create.
“我应该选择哪个 validator 进行 stake？” →
```
list_validators
```
→ 比较 fee/uptime/APY → staking page https://radix-community.genkipool.com/en/console/staking.
“这个 manifest 将执行什么操作？” →
```
explain_manifest
```
（自然语言步骤）+
```
preview_transaction
```
（费用、余额变化）。
“XRD 当前价格 / 网络状态如何？” →
```
get_xrd_price
```
、
```
get_network_status
```
。
“帮我登录 / 证明我的身份” → local connector 的
```
request_login {network, dapp_definition, origin}
```
（由 persona 签名；添加
```
accounts: {quantity: 1, with_proof: true}
```
可在同一次批准中证明一个 account）→ 需要再次证明精确 accounts 时，使用
```
request_ownership_proof {identity_address, accounts}
```
。
“请求从未显示在手机上 / 什么都没有收到” →
```
pending_requests
```
→
```
check_wallet_connection
```
→
```
connector_log
```
；处理请求或强制关闭 wallet，然后执行
```
await_response
```
或
```
cancel_request
```
。如果 failure 表明
```
retry_safe: NO
```
，绝不要重新发送请求。如果 log 显示请求始终未获得 turn 或 channel，请检查机器上是否存在其他 connector processes（旧版本，或 update 前启动的 session），并执行 update/restart。
“我的 accounts 是什么 / 显示我的 balances”（此 server 无状态——不存在“connected wallet”）→ local connector 的
```
request_accounts
```
（无需签名）获取地址 → 对选定地址使用
```
get_account_balances
```
。
“谁持有 token X？collection Y 中存在哪些 NFTs？” →
```
get_resource_holders
```
、
```
get_nft_data
```
。
“component_rdx1… 暴露了哪些 methods？其 state 中有什么？” →
```
get_component_blueprint
```
、
```
get_component_state
```
、
```
get_key_value_store
```
。

Tool reference

工具参考

Site navigation

get_site_overview

— Get site overview

get_site_overview

— 获取站点概览

Map of the Radix Community web: every section with its URL and what it offers. Call it first when you need to know where something lives on the site.

```
locale
```
("en" | "es"; required, default: "en") — Language of the descriptions and generated URLs: "en" or "es"

Radix Community web 的导航图：包含每个 section 的 URL 及其提供的内容。需要了解网站内容所在位置时，首先调用此工具。

```
locale
```
（"en" | "es"；必填，默认："en"）— descriptions 和生成 URL 的语言："en" 或 "es"

Documentation & knowledge

search_radix_docs

— Search Radix docs

search_radix_docs

— 搜索 Radix 文档

Searches the curated documentation of the site (whitepapers, Scrypto/developer guides, node & validator guides, DeFi concepts). Returns matching documents with their URL. Call without "query" to list every available document. Use read_radix_doc to fetch the full content.

```
query
```
(string; optional) — Free-text search, e.g. "install validator" or "NFT". Omit to list all docs.
```
locale
```
("en" | "es"; required, default: "en") — Language of the returned content: "en" (English) or "es" (Spanish)

搜索站点的精选文档（whitepapers、Scrypto/developer guides、node & validator guides、DeFi concepts）。返回匹配的文档及其 URL。不带 "query" 调用可列出所有可用文档。使用 read_radix_doc 获取完整内容。

```
query
```
（string；可选）— 自由文本搜索，例如 "install validator" 或 "NFT"。省略则列出所有文档。
```
locale
```
（"en" | "es"；必填，默认："en"）— 返回内容的语言："en"（English）或 "es"（Spanish）

read_radix_doc

— Read a Radix doc

read_radix_doc

— 阅读 Radix 文档

Returns the full content of one curated documentation page as Markdown, in English or Spanish. Get valid doc ids from search_radix_docs.

```
docId
```
(string; required) — Document id, e.g. "scrypto-basics" or "babylon-guide"
```
locale
```
("en" | "es"; required, default: "en") — Language of the returned content: "en" (English) or "es" (Spanish)

以 Markdown 格式返回一篇精选文档页面的完整内容，支持 English 或 Spanish。通过 search_radix_docs 获取有效 doc ids。

```
docId
```
（string；必填）— 文档 id，例如 "scrypto-basics" 或 "babylon-guide"
```
locale
```
（"en" | "es"；必填，默认："en"）— 返回内容的语言："en"（English）或 "es"（Spanish）

Ledger (on-chain data)

Ledger（on-chain 数据）

lookup_entity

— Look up a ledger entity

lookup_entity

— 查询 ledger 实体

Fetches the on-ledger state of any Radix address: accounts, components, packages, resources (tokens/NFTs), validators, pools, … Returns entity type, metadata and a summary of its details. For account token balances prefer get_account_balances.

```
address
```
(string; required) — Bech32m Radix address, e.g. account_rdx1…, component_rdx1…, package_rdx1…, resource_rdx1…, validator_rdx1…
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

获取任意 Radix 地址的 on-ledger 状态：accounts、components、packages、resources（tokens/NFTs）、validators、pools 等。返回 entity type、metadata 和详细信息摘要。查询 account token balances 时，优先使用 get_account_balances。

```
address
```
（string；必填）— Bech32m Radix 地址，例如 account_rdx1…、component_rdx1…、package_rdx1…、resource_rdx1…、validator_rdx1…
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

get_account_balances

— Get account balances

get_account_balances

— 获取 account 余额

Lists the fungible tokens (with amounts) and non-fungible tokens (with local ids) held by a Radix account.

```
address
```
(string; required) — Account address (account_rdx1… / account_tdx_2_1…)
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

列出 Radix account 持有的 fungible tokens（及其 amounts）和 non-fungible tokens（及其 local ids）。

```
address
```
（string；必填）— Account 地址（account_rdx1… / account_tdx_2_1…）
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

get_transaction

— Get transaction details

get_transaction

— 获取 transaction 详情

Fetches a committed transaction by its intent hash (txid_…): status, fee, timestamp, affected entities, balance changes and the transaction manifest.

```
intentHash
```
(string; required) — Transaction intent hash (txid_…)
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

通过 intent hash（txid_…）获取已 commit 的 transaction：status、fee、timestamp、受影响 entities、balance changes 和 transaction manifest。

```
intentHash
```
（string；必填）— Transaction intent hash（txid_…）
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

list_validators

— List network validators

list_validators

— 列出网络 validators

Lists the validators of the Radix network ordered by stake rank, with stake, fee, uptime and APY. Filter by name or address with "find". Use it to answer questions about staking targets or a specific validator.

```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)
```
find
```
(string; optional) — Optional case-insensitive filter on validator name or address
```
limit
```
(integer; required, default: 20) — Max validators to return

按 stake rank 列出 Radix 网络的 validators，并显示 stake、fee、uptime 和 APY。使用 "find" 按 name 或 address 过滤。可用于回答 staking target 或特定 validator 的问题。

```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）
```
find
```
（string；可选）— 按 validator name 或 address 进行不区分大小写的可选过滤
```
limit
```
（integer；必填，默认：20）— 最多返回的 validators 数量

get_network_status

— Get network status

get_network_status

— 获取网络状态

Current status of the Radix network: epoch, total XRD staked, number of active validators, average APY and average uptime.

```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

Radix 网络的当前状态：epoch、staked XRD 总量、active validators 数量、平均 APY 和平均 uptime。

```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

get_xrd_price

— Get XRD market data

get_xrd_price

— 获取 XRD 市场数据

Live XRD market data from CoinGecko: price in USD and EUR, 24h change, market cap, circulating supply and total value locked.

No parameters.

来自 CoinGecko 的实时 XRD 市场数据：USD 和 EUR 价格、24h 变化、market cap、circulating supply 和 total value locked。

无参数。

get_recent_transactions

— Get recent network transactions

get_recent_transactions

— 获取近期网络 transactions

Latest committed transactions network-wide, newest first. Use get_transaction with an intent hash for the full breakdown of one of them.

```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)
```
limit
```
(integer; required, default: 10) — Max transactions to return

获取全网最新已 commit 的 transactions，按时间从新到旧排列。使用 intent hash 调用 get_transaction 可查看单笔 transaction 的完整明细。

```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）
```
limit
```
（integer；必填，默认：10）— 最多返回的 transactions 数量

get_address_transactions

— Get transactions of an address

get_address_transactions

— 获取地址的 transactions

Transaction history of any entity (account, validator, component, resource), newest first. The first page already shows the most recent activity, which is what users almost always want. Accounts can have thousands of transactions: do NOT keep paging to the end — only fetch more pages (with the returned cursor) if the user explicitly asks for older history. Use get_transaction for the full breakdown of one of them.

```
address
```
(string; required) — Bech32m Radix address, e.g. account_rdx1…, component_rdx1…, package_rdx1…, resource_rdx1…, validator_rdx1…
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)
```
limit
```
(integer; required, default: 10) — Max transactions to return per page
```
cursor
```
(string; optional) — Pagination cursor from a previous call, to fetch the next (older) page

获取任意 entity（account、validator、component、resource）的 transaction history，按时间从新到旧排列。第一页已显示大多数用户需要的近期 activity。Accounts 可能有数千笔 transactions：不要持续翻页至末尾——只有当用户明确要求更早的历史时，才使用返回的 cursor 获取后续页面。使用 get_transaction 查看单笔 transaction 的完整明细。

```
address
```
（string；必填）— Bech32m Radix 地址，例如 account_rdx1…、component_rdx1…、package_rdx1…、resource_rdx1…、validator_rdx1…
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）
```
limit
```
（integer；必填，默认：10）— 每页最多返回的 transactions 数量
```
cursor
```
（string；可选）— 上一次调用返回的分页 cursor，用于获取下一页（更早）的数据

get_nft_data

— Get NFT ids and data

get_nft_data

— 获取 NFT ids 和数据

Explores a non-fungible resource (NFT collection): without "ids" it lists the local ids of the collection; with "ids" it returns the decoded on-ledger data (traits, fields) of those NFTs (max 10 per call).

```
resourceAddress
```
(string; required) — Non-fungible resource address (resource_rdx1…)
```
ids
```
(array; optional) — NFT local ids, e.g. ["#1#", "#2#"] or ["<member_1>"]. Omit to list the collection ids.
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

探索 non-fungible resource（NFT collection）：不传 "ids" 时列出 collection 的 local ids；传入 "ids" 时返回这些 NFTs 的已解码 on-ledger 数据（traits、fields），每次调用最多 10 个。

```
resourceAddress
```
（string；必填）— Non-fungible resource 地址（resource_rdx1…）
```
ids
```
（array；可选）— NFT local ids，例如 ["#1#", "#2#"] 或 ["<member_1>"]。省略则列出 collection ids。
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

get_resource_holders

— Get top holders of a resource

get_resource_holders

— 获取 resource 的主要持有者

Lists the top holders of any token or NFT collection ordered by amount held, with the total holder count.

```
resourceAddress
```
(string; required) — Resource address (resource_rdx1…)
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

列出任意 token 或 NFT collection 的主要 holders，按持有量排序，并返回 holder 总数。

```
resourceAddress
```
（string；必填）— Resource 地址（resource_rdx1…）
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

get_component_state

— Get decoded component state

get_component_state

— 获取已解码的 component state

Live decoded on-ledger state of a component (oracle prices, pool reserves, configuration, …) plus its package and blueprint. For the callable methods use get_component_blueprint.

```
address
```
(string; required) — Component address (component_rdx1… / pool_rdx1…)
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

获取 component 的实时已解码 on-ledger state（oracle prices、pool reserves、configuration 等），以及其 package 和 blueprint。可调用的 methods 请使用 get_component_blueprint。

```
address
```
（string；必填）— Component 地址（component_rdx1… / pool_rdx1…）
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

get_key_value_store

— Read a key-value store

get_key_value_store

— 读取 key-value store

Reads the entries of an on-ledger key-value store (component internal storage), decoded to JSON. KVS addresses appear inside component state as internal_keyvaluestore_….

```
address
```
(string; required) — Key-value store address (internal_keyvaluestore_…)
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

读取 on-ledger key-value store（component internal storage）的 entries，并解码为 JSON。KVS 地址会出现在 component state 中，格式为 internal_keyvaluestore_…。

```
address
```
（string；必填）— Key-value store 地址（internal_keyvaluestore_…）
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

get_component_blueprint

— Get blueprint interface

get_component_blueprint

— 获取 blueprint interface

Callable interface of a component or package blueprint: every function/method with its argument names and types. Pass a component address (the blueprint is resolved automatically) or a package address plus optional blueprintName.

```
address
```
(string; required) — Component (component_rdx1…) or package (package_rdx1…) address
```
blueprintName
```
(string; optional) — Blueprint name inside a package. Ignored for component addresses.
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

获取 component 或 package blueprint 的可调用 interface：每个 function/method 及其 argument names 和 types。传入 component 地址（自动解析 blueprint），或传入 package 地址及可选的 blueprintName。

```
address
```
（string；必填）— Component（component_rdx1…）或 package（package_rdx1…）地址
```
blueprintName
```
（string；可选）— Package 内的 Blueprint 名称。对 component 地址忽略此参数。
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

Console (transactions & developer utilities)

Console（transactions 与 developer utilities）

list_console_tools

— List console tools

list_console_tools

— 列出 console 工具

Lists every tool of the web developer console (send transactions, staking, token creation, package deployment, metadata, SBOR decoding, …) with its URL and whether it needs a connected wallet. Use it to route the user to the right console page.

```
locale
```
("en" | "es"; required, default: "en") — Language of the returned labels/links: "en" or "es"

列出 web developer console 的所有 tools（发送 transactions、staking、token creation、package deployment、metadata、SBOR decoding 等），并显示对应 URL 及是否需要 connected wallet。使用它将用户引导至正确的 console page。

```
locale
```
（"en" | "es"；必填，默认："en"）— 返回 labels/links 的语言："en" 或 "es"

list_manifest_templates

— List manifest templates

list_manifest_templates

— 列出 manifest 模板

Lists the ready-made transaction manifest templates (transfer tokens/NFTs, stake, unstake, claim, mint, burn, create pool, faucet, …) with the fields each one needs. Use build_manifest_from_template to render one.

```
locale
```
("en" | "es"; required, default: "en") — Language of the returned labels/links: "en" or "es"

列出现成的 transaction manifest 模板（transfer tokens/NFTs、stake、unstake、claim、mint、burn、create pool、faucet 等）及每个模板所需的 fields。使用 build_manifest_from_template 渲染模板。

```
locale
```
（"en" | "es"；必填，默认："en"）— 返回 labels/links 的语言："en" 或 "es"

build_manifest_from_template

— Build manifest from template

build_manifest_from_template

— 根据模板构建 manifest

Renders a ready-made transaction manifest template (see list_manifest_templates for ids and fields) with the given field values, validates it, and returns the manifest ready to be signed in the web console.

```
templateId
```
(string; required) — Template id from list_manifest_templates
```
values
```
(object; required) — Field values keyed by field key, e.g. { "from": "account_rdx1…", "amount": "10" }
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)
```
locale
```
("en" | "es"; required, default: "en") — Language of the returned labels/links: "en" or "es"

使用给定的 field values 渲染现成的 transaction manifest 模板（模板 ids 和 fields 参见 list_manifest_templates），验证 manifest，并返回可在 web console 中签名的 manifest。

```
templateId
```
（string；必填）— 来自 list_manifest_templates 的模板 id
```
values
```
（object；必填）— 以 field key 为键的 field values，例如 { "from": "account_rdx1…", "amount": "10" }
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）
```
locale
```
（"en" | "es"；必填，默认："en"）— 返回 labels/links 的语言："en" 或 "es"

build_fungible_token_manifest

— Build fungible token manifest

build_fungible_token_manifest

— 构建 fungible token manifest

Builds the transaction manifest that creates a new fungible token on Radix with sensible defaults (owner: none, transfers open). The initial supply is deposited into the given account. For NFTs use build_nft_collection_manifest; for advanced role setups send the user to the console create-token tool.

```
accountAddress
```
(string; required) — Account that receives the initial supply
```
name
```
(string; required) — Token name, e.g. "My Token"
```
symbol
```
(string; required) — Ticker symbol, e.g. "MTK"
```
description
```
(string; optional) — Token description
```
iconUrl
```
(string; optional) — HTTPS URL of the token icon
```
initialSupply
```
(string; required) — Initial supply as decimal string, e.g. "1000000"
```
divisibility
```
(integer; required, default: 18) — Decimal places (0-18)
```
mintable
```
(boolean; required, default: false) — Allow anyone to mint more supply
```
burnable
```
(boolean; required, default: false) — Allow anyone to burn supply
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)
```
locale
```
("en" | "es"; required, default: "en") — Language of the returned labels/links: "en" or "es"

构建在 Radix 上创建新 fungible token 的 transaction manifest，并提供合理默认值（owner：none，transfers：open）。Initial supply 会存入指定 account。NFT 请使用 build_nft_collection_manifest；如需高级 role 配置，请将用户引导至 console create-token tool。

```
accountAddress
```
（string；必填）— 接收 initial supply 的 Account
```
name
```
（string；必填）— Token 名称，例如 "My Token"
```
symbol
```
（string；必填）— Ticker symbol，例如 "MTK"
```
description
```
（string；可选）— Token 描述
```
iconUrl
```
（string；可选）— Token icon 的 HTTPS URL
```
initialSupply
```
（string；必填）— 以十进制字符串表示的 initial supply，例如 "1000000"
```
divisibility
```
（integer；必填，默认：18）— 小数位数（0-18）
```
mintable
```
（boolean；必填，默认：false）— 是否允许任何人铸造更多 supply
```
burnable
```
（boolean；必填，默认：false）— 是否允许任何人销毁 supply
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）
```
locale
```
（"en" | "es"；必填，默认："en"）— 返回 labels/links 的语言："en" 或 "es"

build_nft_collection_manifest

— Build NFT collection manifest

build_nft_collection_manifest

— 构建 NFT collection manifest

Builds the transaction manifest that creates a new non-fungible resource (NFT collection) on Radix with a set of initial NFTs (name, description, image), sensible defaults (owner: none, transfers open). The NFTs are deposited into the given account. For custom data fields or advanced role setups, send the user to the console create-token tool.

```
accountAddress
```
(string; required) — Account that receives the minted NFTs
```
name
```
(string; required) — Collection name, e.g. "My Collection"
```
description
```
(string; optional) — Collection description
```
iconUrl
```
(string; optional) — HTTPS URL of the collection icon
```
nfts
```
(array; required) — Initial NFTs to mint into the collection
```
mintable
```
(boolean; required, default: false) — Allow minting more NFTs later
```
burnable
```
(boolean; required, default: false) — Allow burning NFTs
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)
```
locale
```
("en" | "es"; required, default: "en") — Language of the returned labels/links: "en" or "es"

构建在 Radix 上创建新 non-fungible resource（NFT collection）的 transaction manifest，其中包含一组初始 NFTs（name、description、image），并提供合理默认值（owner：none，transfers：open）。NFTs 会存入指定 account。如需自定义 data fields 或高级 role 配置，请将用户引导至 console create-token tool。

```
accountAddress
```
（string；必填）— 接收 minted NFTs 的 Account
```
name
```
（string；必填）— Collection 名称，例如 "My Collection"
```
description
```
（string；可选）— Collection 描述
```
iconUrl
```
（string；可选）— Collection icon 的 HTTPS URL
```
nfts
```
（array；必填）— 要铸造到 collection 中的初始 NFTs
```
mintable
```
（boolean；必填，默认：false）— 是否允许以后铸造更多 NFTs
```
burnable
```
（boolean；必填，默认：false）— 是否允许销毁 NFTs
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）
```
locale
```
（"en" | "es"；必填，默认："en"）— 返回 labels/links 的语言："en" 或 "es"

build_faucet_manifest

— Build a Stokenet faucet manifest

build_faucet_manifest

— 构建 Stokenet faucet manifest

Builds the manifest that requests free test XRD from the Stokenet faucet and deposits it into an account. Stokenet only — mainnet has no faucet. Use it to fund a test account before other transactions.

```
accountAddress
```
(string; required) — Stokenet account to fund (account_tdx_2_…)
```
locale
```
("en" | "es"; required, default: "en") — Language of the returned labels/links: "en" or "es"

构建从 Stokenet faucet 请求免费测试 XRD 并将其存入 account 的 manifest。仅适用于 Stokenet——mainnet 没有 faucet。在执行其他 transactions 前，使用它为测试 account 充值。

```
accountAddress
```
（string；必填）— 要充值的 Stokenet account（account_tdx_2_…）
```
locale
```
（"en" | "es"；必填，默认："en"）— 返回 labels/links 的语言："en" 或 "es"

build_deploy_package_manifest

— Prepare a Scrypto package deployment

build_deploy_package_manifest

— 准备 Scrypto package deployment

Decodes a compiled .rpd package definition (Manifest SBOR) into the value needed to publish a Scrypto package, and returns the exact deploy_package call to run on the local radix-connector. The WASM is NOT handled here (too large for the agent) — the connector reads it from disk. Use this before deploy_package.

```
rpdHex
```
(string; required) — Hex-encoded contents of the compiled .rpd package-definition file
```
owner
```
("none" | "allowAll"; required, default: "none") — Package owner: "none" (no owner) or "allowAll" (anyone can update it)
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

将已编译的 .rpd package definition（Manifest SBOR）解码为发布 Scrypto package 所需的值，并返回要在 local radix-connector 上运行的准确 deploy_package 调用。此处不处理 WASM（对于 agent 而言过大）——connector 会从磁盘读取。使用此工具后再调用 deploy_package。

```
rpdHex
```
（string；必填）— 已编译 .rpd package-definition 文件内容的 Hex encoding
```
owner
```
（"none" | "allowAll"；必填，默认："none"）— Package owner："none"（无 owner）或 "allowAll"（任何人都可更新）
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

validate_transaction_manifest

— Validate a transaction manifest

validate_transaction_manifest

— 验证 transaction manifest

Statically validates Radix transaction manifest syntax with the Radix Engine Toolkit and reports the exact parse error if invalid.

```
manifest
```
(string; required) — Transaction manifest source text
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

使用 Radix Engine Toolkit 对 Radix transaction manifest 语法进行静态验证；如果无效，则报告确切的 parse error。

```
manifest
```
（string；必填）— Transaction manifest source text
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

preview_transaction

— Preview (simulate) a transaction

preview_transaction

— 预览（simulation）transaction

Dry-runs a transaction manifest on the Gateway without any signature: returns the execution status, total fee in XRD, per-entity balance changes and engine logs. Always preview a manifest before asking the user to sign it.

```
manifest
```
(string; required) — Transaction manifest source text
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)
```
locale
```
("en" | "es"; required, default: "en") — Language of the returned labels/links: "en" or "es"
```
blobs
```
(array; optional) — Hex-encoded blobs referenced by the manifest via Blob("<hash>"), e.g. package WASM. Required to dry-run a package deploy.

在 Gateway 上对 transaction manifest 执行 dry-run，不进行任何签名：返回 execution status、XRD total fee、各 entity 的 balance changes 和 engine logs。请求用户签名之前，始终预览 manifest。

```
manifest
```
（string；必填）— Transaction manifest source text
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）
```
locale
```
（"en" | "es"；必填，默认："en"）— 返回 labels/links 的语言："en" 或 "es"
```
blobs
```
（array；可选）— Manifest 通过 Blob("<hash>") 引用的 Hex-encoded blobs，例如 package WASM。Dry-run package deployment 时必须提供。

explain_manifest

— Explain a transaction manifest

explain_manifest

— 解释 transaction manifest

Translates a Radix transaction manifest into a plain-language, step-by-step explanation (withdrawals, deposits, proofs, component calls, …) in English or Spanish. Use it to help the user understand what they are about to sign.

```
manifest
```
(string; required) — Transaction manifest source text
```
locale
```
("en" | "es"; required, default: "en") — Language of the returned labels/links: "en" or "es"

将 Radix transaction manifest 转换为通俗易懂的分步说明（withdrawals、deposits、proofs、component calls 等），支持 English 或 Spanish。用于帮助用户理解即将签名的内容。

```
manifest
```
（string；必填）— Transaction manifest source text
```
locale
```
（"en" | "es"；必填，默认："en"）— 返回内容的语言："en"（English）或 "es"（Spanish）

decode_sbor

— Decode an SBOR payload

decode_sbor

— 解码 SBOR payload

Decodes a hex-encoded SBOR payload (component state, events, schemas) into human-readable text. Scrypto vs Manifest SBOR is auto-detected from the prefix byte.

```
hex
```
(string; required) — Hex-encoded SBOR payload (starts with 5c for Scrypto, 4d for Manifest)
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

将 Hex-encoded SBOR payload（component state、events、schemas）解码为易读文本。根据 prefix byte 自动检测 Scrypto SBOR 或 Manifest SBOR。

```
hex
```
（string；必填）— Hex-encoded SBOR payload（以 5c 开头表示 Scrypto，以 4d 开头表示 Manifest）
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

convert_olympia_address

— Convert Olympia address

convert_olympia_address

— 转换 Olympia 地址

Converts a legacy Olympia address (rdx1… account or _rr1… resource) into its Babylon equivalent. For accounts it also returns the compressed secp256k1 public key embedded in the address, and the wallet-import QR payload string the Radix Wallet scans to import the legacy account (Settings → "Import from a Legacy Wallet"). Render that string as a QR (or save it) to complete the import. The payload holds only public data, never a seed phrase or private key.

```
olympiaAddress
```
(string; required) — Olympia address (rdx1… or …_rr1…)
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)
```
accountType
```
("S" | "H"; required, default: "S") — Original Olympia account type: "S" software (seed phrase) or "H" hardware (Ledger).
```
addressIndex
```
(integer; required, default: 0) — BIP44 address index the account was derived with (0 for the first account).
```
accountName
```
(string; required, default: "") — Display name shown in the mobile wallet during import (max 30 chars).
```
wordCount
```
(any; required, default: 12) — Seed-phrase word count of the original Olympia wallet (12, 15, 18, 21 or 24).

将 legacy Olympia 地址（rdx1… account 或 _rr1… resource）转换为对应的 Babylon 地址。对于 accounts，还会返回地址中嵌入的 compressed secp256k1 public key，以及 Radix Wallet 扫描后用于导入 legacy account 的 wallet-import QR payload string（Settings → “Import from a Legacy Wallet”）。将该 string 渲染为 QR（或保存它）即可完成导入。该 payload 仅包含 public data，绝不包含 seed phrase 或 private key。

```
olympiaAddress
```
（string；必填）— Olympia 地址（rdx1… 或 …_rr1…）
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）
```
accountType
```
（"S" | "H"；必填，默认："S"）— 原 Olympia account type："S" software（seed phrase）或 "H" hardware（Ledger）
```
addressIndex
```
（integer；必填，默认：0）— 派生 account 所用的 BIP44 address index（0 表示第一个 account）
```
accountName
```
（string；必填，默认：""）— 导入时在 mobile wallet 中显示的名称（最多 30 个字符）
```
wordCount
```
（any；必填，默认：12）— 原 Olympia wallet 的 seed-phrase word count（12、15、18、21 或 24）

resolve_vault_address

— Resolve a vault address

resolve_vault_address

— 解析 vault 地址

Resolves the internal vault address holding a resource in an account (the target a recall/freeze needs). An account holds a resource in exactly one vault. For non-fungibles it also returns the NFT ids in that vault. Feed the vault into the recall-token / recall-nft / freeze-vault / unfreeze-vault manifest templates.

```
account
```
(string; required) — Account address (account_…) that holds the resource.
```
resource
```
(string; required) — Resource address (resource_…) to locate in the account.
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

解析 account 内部持有 resource 的 vault 地址（recall/freeze 的目标）。一个 account 只会在一个 vault 中持有某个 resource。对于 non-fungibles，还会返回该 vault 中的 NFT ids。将 vault 传入 recall-token / recall-nft / freeze-vault / unfreeze-vault manifest 模板。

```
account
```
（string；必填）— 持有 resource 的 Account 地址（account_…）
```
resource
```
（string；必填）— 要在 account 中定位的 Resource 地址（resource_…）
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

inspect_address

— Inspect a Radix address

inspect_address

— 检查 Radix 地址

Offline analysis of any Radix bech32m address: entity type (account, resource, component, package, validator, …), network, and checksum validity. No network calls.

```
address
```
(string; required) — Any Radix address or transaction id

离线分析任意 Radix bech32m 地址：entity type（account、resource、component、package、validator 等）、network 和 checksum validity。不会发起 network calls。

```
address
```
（string；必填）— 任意 Radix 地址或 transaction id

verify_account_security

— Verify how an account is protected

verify_account_security

— 验证 account 保护方式

Reads from the ledger who actually controls a Radix account: its key (one seed phrase, no recovery), or an account owner badge. When it is a badge, it also says whether that badge sits in an Access Controller (multi-factor with recovery) or loose in an account. Reports the controller's roles, its timed-recovery delay and any recovery or badge-withdrawal attempt in flight. Read-only.

```
address
```
(string; required) — Account address (account_rdx1… / account_tdx_2_1…)
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

从 ledger 读取实际控制 Radix account 的主体：其 key（一个 seed phrase，无 recovery），或 account owner badge。如果是 badge，还会说明该 badge 位于 Access Controller（带 recovery 的 multi-factor）中，还是作为 loose badge 存放在 account 中。报告 controller 的 roles、timed-recovery delay，以及正在进行的 recovery 或 badge-withdrawal attempt。Read-only。

```
address
```
（string；必填）— Account 地址（account_rdx1… / account_tdx_2_1…）
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

get_known_addresses

— Get well-known network addresses

get_known_addresses

— 获取 well-known 网络地址

Canonical well-known addresses of a network: XRD resource, faucet, native packages (account, pool, validator, …), system badges, plus this site's dApp definition + origin to pass to the wallet when signing. Use it to fill manifest addresses without guessing.

```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

获取某个网络的 canonical well-known addresses：XRD resource、faucet、native packages（account、pool、validator 等）、system badges，以及此站点的 dApp definition + origin，用于 wallet 签名时传入。使用它填写 manifest addresses，不要自行猜测。

```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

list_validator_operations

— List validator operations

list_validator_operations

— 列出 validator 操作

Lists every operation a validator supports (register, unregister, change fee, change consensus key, open/close delegation, protocol update vote, public profile metadata, stake, unstake, claim, owner locked stake units, create validator) with whether it needs the owner badge and whether it can share a transaction with the others. Use it before build_validator_manifest.

No parameters.

列出 validator 支持的所有 operations（register、unregister、change fee、change consensus key、open/close delegation、protocol update vote、public profile metadata、stake、unstake、claim、owner locked stake units、create validator），并说明是否需要 owner badge，以及能否与其他 operations 共用 transaction。在 build_validator_manifest 之前使用此工具。

无参数。

get_validator_state

— Read validator state

get_validator_state

— 读取 validator 状态

Reads a validator from the ledger: whether it is registered, whether it accepts delegated stake, its fee factor, consensus public key, and the stake unit (LSU) and claim NFT resources it mints. Use it to know the current state before proposing a change.

```
validator
```
(string; required) — Validator component address (validator_…)
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

从 ledger 读取 validator：是否已 registered、是否接受 delegated stake、fee factor、consensus public key，以及其铸造的 stake unit（LSU）和 claim NFT resources。提出变更之前，使用此工具了解当前状态。

```
validator
```
（string；必填）— Validator component 地址（validator_…）
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

list_claimable_stake_nfts

— List stake claim NFTs

list_claimable_stake_nfts

— 列出 stake claim NFTs

Lists the stake claim NFTs an account holds, each attributed to the validator that minted it, with the XRD it redeems for and whether it has matured. Feed the matured ones to build_validator_manifest as a claim-xrd operation.

```
account
```
(string; required) — Account address (account_…)
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

列出 account 持有的 stake claim NFTs，每项都关联到铸造它的 validator，并显示可兑换的 XRD 以及是否已经成熟。将成熟项作为

claim-xrd

operation 传给 build_validator_manifest。

```
account
```
（string；必填）— Account 地址（account_…）
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

build_validator_manifest

— Build validator manifest

build_validator_manifest

— 构建 validator manifest

Builds one transaction manifest out of one or more validator operations, resolving the owner badges the account holds and composing a single proof for all of them. Refuses combinations the ledger would garble. Returns the manifest for the user to sign in their Radix wallet.

```
account
```
(string; required) — Account that signs, pays the fee and presents the owner badges
```
operations
```
(array; required) — Operations to combine in one transaction
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)

根据一个或多个 validator operations 构建单个 transaction manifest，解析 account 持有的 owner badges，并将所有 badge 组合为单个 proof。它会拒绝 ledger 会错误处理的 operation combinations。返回供用户在 Radix wallet 中签名的 manifest。

```
account
```
（string；必填）— 用于签名、支付 fee 并提供 owner badges 的 Account
```
operations
```
（array；必填）— 要组合到同一 transaction 中的 Operations
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）

verify_document_signature

— Verify a document-signature certificate

verify_document_signature

— 验证 document-signature certificate

Verifies a Radix Seal document-attestation certificate (the contents of a .radixsig.json file). Checks every signature against the shared payload — ROLA proofs and/or the on-ledger chain of custody — and reports whether the certificate is complete. It receives ONLY the certificate, never the document itself.

```
certificate
```
(string; required) — The certificate JSON: the full contents of the .radixsig.json file.

验证 Radix Seal document-attestation certificate（.radixsig.json 文件的内容）。根据 shared payload 检查每个 signature——包括 ROLA proofs 和/或 on-ledger chain of custody——并报告 certificate 是否完整。它只接收 certificate，绝不接收 document 本身。

```
certificate
```
（string；必填）— Certificate JSON：.radixsig.json 文件的完整内容。

check_signing_request

— Check a Radix Seal signing request

check_signing_request

— 检查 Radix Seal signing request

Reads the on-ledger status of a Radix Seal signing request by its id (the first invitation NFT global id, e.g. "resource_tdx_2_1...:#25#"). Returns the required signers, who has signed, and whether the request is complete. Read-only Gateway query.

```
requestId
```
(string; required) — Request id: the first invitation NFT global id, e.g. "resource_tdx_2_1...:#25#".
```
network
```
("mainnet" | "stokenet"; required, default: "mainnet") — Radix network: "mainnet" (production) or "stokenet" (testnet)
```
docHash
```
(string; optional) — Optional document hash (blake2b-256, 64 hex chars) to confirm the request anchors the expected file.

通过 id 读取 Radix Seal signing request 的 on-ledger 状态（id 为第一个 invitation NFT global id，例如 "resource_tdx_2_1...:#25#"）。返回所需 signers、已签名人员以及 request 是否完成。Read-only Gateway query。

```
requestId
```
（string；必填）— Request id：第一个 invitation NFT global id，例如 "resource_tdx_2_1...:#25#"
```
network
```
（"mainnet" | "stokenet"；必填，默认："mainnet"）— Radix 网络："mainnet"（production）或 "stokenet"（testnet）
```
docHash
```
（string；可选）— 可选的 document hash（blake2b-256，64 个 hex 字符），用于确认 request 锚定的是预期文件。

setup_wallet_connector

— Set up local wallet signing

setup_wallet_connector

— 设置 local wallet signing

Explains how to install and use the LOCAL Radix signing connector (radix-connector-mcp) so the user can sign and submit transactions with their Radix Wallet. This HTTP server cannot sign (it is stateless); the local connector holds the wallet channel and the phone approves. Call this when the user wants to send/sign a transaction, stake, create a token, deploy, or log in with Radix.

```
client
```
("claude-code" | "claude-desktop" | "cursor" | "antigravity" | "generic"; required, default: "generic") — Which MCP client the user runs, so the registration snippet matches it.
```
os
```
("linux" | "macos" | "windows"; optional) — User OS, to show the matching prebuilt-binary installer. Omit to show all.

说明如何安装和使用 LOCAL Radix signing connector（radix-connector-mcp），以便用户使用 Radix Wallet 签名并提交 transactions。此 HTTP server 无法签名（因为它是无状态的）；local connector 持有 wallet channel，并由手机批准。当用户希望 send/sign transaction、stake、创建 token、deploy 或使用 Radix 登录时，调用此工具。

```
client
```
（"claude-code" | "claude-desktop" | "cursor" | "antigravity" | "generic"；必填，默认："generic"）— 用户运行的 MCP client，用于让 registration snippet 与其匹配。
```
os
```
（"linux" | "macos" | "windows"；可选）— 用户 OS，用于显示匹配的 prebuilt-binary installer。省略则显示全部。