# Transferring an Asset

This particular transaction type is designed for transferring a specified amount of an available asset from one sending wallet to a recipient wallet. In this context, the transaction body and payload will have the following structure:

```json
TBody = {
         "ID" : [ID],
         "From" : [From],
         "To" : [To],<
         "Timestamp" : [Timestamp],
         "Payload" : {
                       "Action":"CP_SEND",
                       "Asset":[Name of the Asset],
                       "Amount":[Amount to be transferred],
                       "Fee":[Fee]
         },
         "Nonce" : [Nonce],
         "Signature" : [Signature],
         "PublicKey" : [PublicKey],
         "Blockchain" : [Blockchain],
         "Type" : "C_TYPE_TOKEN"
    }
```

For this specific transaction type, the Payload undergoes parsing and processing to execute the intended operation, which is a CP\_SEND transfer. In this operation, the specified asset, identified by name, is moved to the "To" wallet. If the asset being transferred is the native coin "CIRX," the transaction type is labeled as C\_TYPE\_COIN. For all other tokens, it is identified as C\_TYPE\_TOKEN. For CIRX coins, the Asset name will be "Circular Coin." The amount to be transferred is represented as a double-precision floating-point number, indicating the quantity of the asset destined for the recipient wallet.

The "fee" field allows the sender to include an optional fee, signifying their willingness to expedite the transaction's inclusion in the next block. If the fee is set to zero, a nominal fee is applied, giving the transaction the lowest priority in block inclusion. It's important to note that even with an additional fee, there is no guarantee of immediate inclusion in the next block. Subsequently, the payload is converted into a string format and must be encoded in hexadecimal (Hex) without the "0x" identifier.


---

# Agent Instructions: 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:

```
GET https://circular-protocol.gitbook.io/standard-apis/api-docs/apis/transferring-an-asset.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.