> For the complete documentation index, see [llms.txt](https://kkone.gitbook.io/kkone-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kkone.gitbook.io/kkone-docs/wallets-and-trading/wallet-groups-and-send.md).

# Wallet Groups and Send

Wallet Groups organize the in-product wallets used by KK.one tasks and creator operations. A group such as W1 or W2 provides the identity KK.one resolves for a selected network while keeping balances, fees, transactions, and status separate by network.

## Base and Robinhood Chain

Both live networks use an EVM address format. One Wallet Group may display the same EVM address for Base and Robinhood Chain, but:

* Base ETH is not Robinhood Chain ETH;
* a Base token is not the corresponding Robinhood Chain token;
* each network needs its own usable fee balance;
* transactions must be submitted and confirmed on the selected network;
* explorer links and transaction hashes are network-specific.

## Fund a wallet

Select a live network before copying the deposit address or opening its explorer. Always verify the network shown by the sending wallet or exchange.

The estimated number of launches is informational. Fees change, and an estimate does not reserve capacity or guarantee a successful deployment.

## Send

Open **Wallet → Send** to transfer an eligible asset from an in-product Wallet Group.

The Send drawer requires:

1. a live network;
2. a token or native asset available in the selected Wallet Group;
3. an amount;
4. a recipient address valid for that network;
5. a review of the fee estimate and final transfer details.

Send is a same-network transfer. It is not a bridge or swap. Selecting Base sends on Base; selecting Robinhood Chain sends on Robinhood Chain.

### Amount shortcuts

Percentage shortcuts use the currently available balance. **Max** may reserve enough native asset for the estimated network fee, so the final amount can be lower than the visible balance.

### Recipient safety

An EVM address can be syntactically valid on more than one network. You are responsible for confirming that the recipient supports the selected network and asset. Confirmed blockchain transfers are usually irreversible.

## Transaction states

* **Preparing** — validating asset, amount, network, and fee data.
* **Waiting for authorization** — wallet approval is required.
* **Submitted** — the transaction was broadcast; this is not final success.
* **Confirming** — awaiting sufficient network confirmation.
* **Confirmed** — the network confirmed the transfer.
* **Failed** — the current attempt did not confirm successfully.
* **Unknown / delayed** — the final chain result is not yet known; check Records and the network explorer before retrying.

Never retry only because a page is slow. A duplicate transfer can occur if the first transaction was already accepted by the network.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kkone.gitbook.io/kkone-docs/wallets-and-trading/wallet-groups-and-send.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
