Metabot Wallet Manage

Bot Wallet Manage

Handle wallet balance checks and BTC/SPACE/DOGE/OPCAT transfers to a target address. Treat Bot, bot, and MetaBot as equivalent user wording for the selected local wallet profile.

{{HOST_ADAPTER_SECTION}}

Routing

{{SYSTEM_ROUTING}}

Actor Selection

Wallet commands accept optional --from <bot-slug>. Use it whenever the human names a specific local Bot, a previous workflow step already selected a Bot, or a transfer confirmation must use the same wallet as the preview. If --from is omitted, the CLI falls back to the active identity.

Trigger Guidance

Should trigger when:

• The user asks for wallet balance across all chains, MVC only, BTC only, DOGE only, or OPCAT only.
• The user asks to send, transfer, or pay BTC, SPACE, DOGE, or OPCAT to an address.
• The user mentions an amount with BTC, SPACE, DOGE, or OPCAT and a recipient address.

Should not trigger when:

• The user asks to publish buzz/service/file content.
• The user asks to delegate paid remote services.
• The user asks to manage network sources or identities.

Network and Currency Mapping

This is the authoritative mapping. Do not query any other API or chain for these currencies.

Never search for a separate SPACE API, SPACE contract, or FT token endpoint. SPACE is not a token — it is the base currency of the MVC network and is always returned by wallet balance --chain mvc.

Balance Command

For default multi-chain balance (MVC/SPACE + BTC + DOGE + OPCAT):

{{METABOT_CLI}} wallet balance --from <bot-slug>

When the human asks for BTC, Bitcoin, or 比特币:

{{METABOT_CLI}} wallet balance --from <bot-slug> --chain btc

When the human asks for DOGE or Dogecoin:

{{METABOT_CLI}} wallet balance --from <bot-slug> --chain doge

When the human asks for OPCAT:

{{METABOT_CLI}} wallet balance --from <bot-slug> --chain opcat

When the human asks for SPACE, MVC, 太空币, or any MVC-network currency:

{{METABOT_CLI}} wallet balance --from <bot-slug> --chain mvc

The mvc balance response includes balances.mvc.totalMvc (the SPACE amount) and balances.mvc.address (the MVC/SPACE receiving address). DOGE and OPCAT balances are returned under balances.doge and balances.opcat.

Default Write Network Config

Wallet balance and transfer do not use the default write-network setting. Balance defaults to all chains, and transfer selects the chain from the amount unit (BTC, SPACE, DOGE, or OPCAT).

Use these commands only when the human asks to inspect or change the default chain for on-chain write commands such as buzz, service publish, rating, private chat, or generic chain write:

{{METABOT_CLI}} config get --from <bot-slug> chain.defaultWriteNetwork
{{METABOT_CLI}} config set --from <bot-slug> chain.defaultWriteNetwork opcat

Supported values are mvc, btc, doge, and opcat. The setting is scoped to the selected local Bot profile.

Transfer Command

Currency mapping (same as balance — see Network and Currency Mapping above):

• BTC → Bitcoin network (--amount 0.00001BTC)
• SPACE → MVC network (--amount 1SPACE). SPACE is the native currency of MVC; use SPACE as the unit, not MVC.
• DOGE → Dogecoin network (--amount 0.01DOGE)
• OPCAT → OPCAT network (--amount 10OPCAT)

Amount format: append the currency unit directly to the number, no space required.

• 0.00001BTC — send 0.00001 BTC
• 1SPACE — send 1 SPACE (MVC)
• 0.01DOGE — send 0.01 DOGE
• 10OPCAT — send 10 OPCAT
• Amounts are case-insensitive: 1space, 0.00001btc, and 10opcat are all valid.

Step 1 — Always preview first (no --confirm)

Run the transfer command without --confirm to get a preview. Never skip this step.

{{METABOT_CLI}} wallet transfer --from <bot-slug> --to <address> --amount <amount><UNIT>

Example — preview a BTC transfer:

{{METABOT_CLI}} wallet transfer --from <bot-slug> --to 1EX5NN6npyCp3X6Sv4Yahv6DrBNKRtq4Gw --amount 0.00001BTC

Example — preview a SPACE transfer:

{{METABOT_CLI}} wallet transfer --from <bot-slug> --to 1EX5NN6npyCp3X6Sv4Yahv6DrBNKRtq4Gw --amount 1SPACE

Example — preview an OPCAT transfer:

{{METABOT_CLI}} wallet transfer --from <bot-slug> --to o1EX5NN6npyCp3X6Sv4Yahv6DrBNKRtq4Gw --amount 10OPCAT

Example — preview a DOGE transfer:

{{METABOT_CLI}} wallet transfer --from <bot-slug> --to D9UuD6sjdEUNv8hPC8WtUXZapBCsFn67jo --amount 0.01DOGE

The response has state: "awaiting_confirmation" and data containing:

• fromAddress — sender address
• currentBalance — total spendable balance including both confirmed and unconfirmed UTXOs (e.g. "0.001 BTC")
• toAddress — recipient address
• amount — exact amount to send
• estimatedFee — estimated network fee
• feeRateSatPerVb — fee rate used
• currency / chain

Present this information clearly to the human and ask for explicit approval before proceeding.

Step 2 — Execute only after human confirms

After the human explicitly approves, re-run the same command with --confirm appended:

{{METABOT_CLI}} wallet transfer --from <bot-slug> --to <address> --amount <amount><UNIT> --confirm

Example:

{{METABOT_CLI}} wallet transfer --from <bot-slug> --to 1EX5NN6npyCp3X6Sv4Yahv6DrBNKRtq4Gw --amount 0.00001BTC --confirm

On success the response contains:

• txid — transaction ID
• explorerUrl — clickable link to view the transaction on the block explorer
• amount — amount sent
• toAddress — recipient

Always show the explorerUrl to the human so they can verify the transaction on-chain.

Natural language → CLI mapping examples

Error Handling

• insufficient_balance — show the current balance and tell the user how much more is needed. UTXOs are spendable regardless of confirmation status — the total balance is what determines whether a transfer can proceed.
• invalid_argument — the address or amount format is wrong; ask the user to correct it.
• transfer_broadcast_failed — the network rejected the transaction; show the error message. If the error mentions mempool conflict, wait a few seconds and retry — the conflict usually resolves on its own.

In Scope

• Wallet balance checks across all, MVC, BTC, DOGE, or OPCAT chains.
• BTC, SPACE (MVC), DOGE, and OPCAT transfers with two-step preview + confirm flow.

Out of Scope

• On-chain social/service publish writes.
• Remote service order lifecycle.
• Identity or network source management.
• Other chain transfers.

Handoff To

• metabot-post-buzz / metabot-upload-file / metabot-post-skillservice for publish flows.
• metabot-call-remote-service for service delegation.
• metabot-network-manage for network discovery/source operations.

Compatibility

• CLI path: {{METABOT_CLI}}
• Compatibility manifest: {{COMPATIBILITY_MANIFEST}}