# Transaction Memos

### Overview

Transactions to MAYAChain pass user intent with the `MEMO` field on their respective chains. MAYAChain inspects the transaction object and the `MEMO` in order to process the transaction, so care must be taken to ensure the `MEMO` and the transaction are both valid. If not, MAYAChain will automatically refund the assets. All memos are listed[ here](https://gitlab.com/mayachain/mayanode/-/blob/develop/x/mayachain/memo/memo.go?ref_type=heads).

MAYAChain uses specific [Asset Notation](https://docs.mayaprotocol.com/mayachain-dev-docs/concepts/asset-notation) for all assets. Assets and functions can be abbreviated and Affiliate Addresses and asset amounts can be shortened to [reduce memo length](https://docs.mayaprotocol.com/mayachain-dev-docs/concepts/memo-length-reduction).

Guides have been created for [Swap](https://docs.mayaprotocol.com/mayachain-dev-docs/introduction/swapping-guide/quickstart-guide) and to enable quoting and the automatic construction of memos for simplicity.

### Memo Size Limits

MAYAChain has a [memo size limit of 250 bytes](https://gitlab.com/mayachain/mayanode/-/blob/develop/constants/constants.go?ref_type=heads#L32), any inbound tx sent with a larger memo will be ignored. Additionally, memos on UTXO chains are further constrained by the `OP_RETURN` size limit, which is [80 bytes](https://developer.bitcoin.org/devguide/transactions.html#null-data).

### Format

All memos follow the format: `FUNCTION:PARAM1:PARAM2:PARAM3:PARAM4`

The function is invoked by a string, which in turn calls a particular handler in the state machine. The state machine parses the memo looking for the parameters which it simply decodes from human-readable strings.

In addition, some parameters are optional. Simply leave them blank, but retain the `:` separator:

`FUNCTION:PARAM1:::PARAM4`

### Permitted Functions

The following functions can be put into a memo:

1. [**SWAP**](#swap)
2. [**ADD** **Liquidity**](#add-liquidity)
3. [**WITHDRAW** **Liquidity**](#withdraw-liquidity)
4. [**BOND**, **UNBOND** & **LEAVE**](#bond-unbond-and-leave)
5. [**DONATE** & **RESERVE**](#donate-and-reserve)
6. [**MIGRATE**](#mirgrate)
7. [**NOOP**](#noop)

### Swap

Perform a swap.

**`SWAP:ASSET:DESTADDR/REFUNDADDR:LIM/INTERVAL/QUANTITY:AFFILIATE[/AFF2...]:FEE[/FEE2...]:DEXAggregatorAddr:FinalTokenAddr:MnAmountOut`**

<table><thead><tr><th width="164.4771610766654">Parameter</th><th width="338.89853142855793">Notes</th><th>Conditions</th></tr></thead><tbody><tr><td>Payload</td><td>Send the asset to swap.</td><td>Must be an active pool on MAYAChain.</td></tr><tr><td><code>SWAP</code></td><td>The swap handler.</td><td><a href="../memo-length-reduction#mechanism-for-transaction-intent-2">Also</a>, <code>s</code>, <code>=</code></td></tr><tr><td><code>:ASSET</code></td><td>The <a href="https://gitlab.com/mayachain/docs/one-stop-shop/-/blob/main/mayachain-dev-docs/concepts/broken-reference/README.md">asset identifier.</a></td><td><del>Can be</del> <a href="../memo-length-reduction#shortened-asset-names"><del>shortened.</del></a></td></tr><tr><td><code>:DESTADDR</code></td><td>The destination address to send to.</td><td>Can use MAYAName.</td></tr><tr><td><code>/REFUNDADDR</code></td><td>Custom refund address</td><td>Optional, custom refund address</td></tr><tr><td><code>:LIM</code></td><td>The trade limit ie, set 100000000 to get a minimum of 1 full asset, else a refund.</td><td>Optional, 1e8 or <a href="../memo-length-reduction#scientific-notation">Scientific Notation</a>.</td></tr><tr><td><code>/INTERVAL</code></td><td>Swap interval in blocks.</td><td>Optional, 1 means do not stream.</td></tr><tr><td><code>/QUANTITY</code></td><td>Swap Quantity. Swap interval times every Interval blocks.</td><td>Optional, if 0, network will determine the number of swaps.</td></tr><tr><td><code>:AFFILIATE</code></td><td>The <a href="../fees#affiliate-fee">affiliate</a> MAYAName or address. CACAO is sent to Affiliate.</td><td>Optional. Must be MAYAName or MAYA Address. Up to 5 affiliates separated by "/" are allowed</td></tr><tr><td><code>:FEE</code></td><td>The affiliate fee. Limited from 0 to 500 Basis Points.</td><td>Optional. Limited from 0 to 500 Basis Points (5%). Up to 5 affiliate bps separated by "/" are allowed</td></tr><tr><td><code>:DEXAggregatorAddr</code></td><td>The whitelisted aggregator contract.</td><td>Optional. Can use the last x characters of the address to fuzz match it.</td></tr><tr><td><code>:FinalTokenAddr</code></td><td>The final token (must be on 1INCH Whitelist)</td><td>Optional. Can be shortened</td></tr><tr><td><code>:MinAmountOut</code></td><td>The parameter to pass into AmountOutMin in AMM contracts</td><td>Optional. Handled by the aggregator, so:<br>1. Can be 0 (no protection).<br>2. Can be in any decimals<br>3. Can be in % or BasisPoints, then converted to a price at the time of swap by the aggregator contract.<br><br>Mayanode accepts integers and scientific notation. Both <code>100000000</code> and <code>1e8</code> would forward <code>uint256 100000000</code> to the aggregator contract.</td></tr></tbody></table>

**Syntactic Examples:**

* **`SWAP:ASSET:DESTADDR`** simple swap
* **`SWAP:ASSET:DESTADDR:LIM`** swap with trade limit
* **`SWAP:ASSET:DESTADDR:LIM/1/1`** swap with limit, do not stream swap
* **`SWAP:ASSET:DESTADDR:LIM/3/0`** swap with limit, optimise swap amount, every 3 blocks
* **`SWAP:ASSET:DESTADDR:LIM/1/0:AFFILIATE:FEE`** swap with limit, optimised streaming, using affiliate address and fee
* **`SWAP:ASSET:DESTADDR:LIM/1/0:AFFILIATE_NAME`** swap with limit, optimised streaming, using affiliate MAYAName and default fee (set in MAYAName)
* **`SWAP:ASSET:DESTADDR:`:`AFFILIATE_NAME:FEE`** swap with affiliate MAYAName and overridden default fee
* **`SWAP:ASSET:DESTADDR::AFF1/AFF2/AFF3`** swap with three affiliate MAYANames using default basis points values
* **`SWAP:ASSET:DESTADDR::AFF1/AFF2/AFF3:/20/`** swap with three affiliate MAYANames using default basis points values for **AFF1** and **AFF3** and with overridden default fee for **AFF2**

**Actual Examples:**

* `SWAP:ETH.ETH:0xe6a30f4f3bad978910e2cbb4d97581f5b5a0ade0` - swap to Ether, send output to the specified address.
* `SWAP:ETH.ETH:0xe6a30f4f3bad978910e2cbb4d97581f5b5a0ade0:10000000,` same as above except the Ether output should be more than 0.1 Ether else refund.
* `SWAP:ETH.ETH:0xe6a30f4f3bad978910e2cbb4d97581f5b5a0ade0:10000000/1/1` - same as above except explicitly stated, do not stream the swap.
* `SWAP:ETH.ETH:0xe6a30f4f3bad978910e2cbb4d97581f5b5a0ade0:10000000/3/0` - same as above except told to allow streaming swap, mini swap every 3 blocks and MAYAChain to work out the number of swaps required to achieve optimal price efficiency.
* `SWAP:ETH.ETH:0xe6a30f4f3bad978910e2cbb4d97581f5b5a0ade0:10000000/3/0:t:10` - same as above except will send 10 basis points from the input and send it to `t` (THORSwap's [MAYAName](https://docs.mayaprotocol.com/mayachain-dev-docs/introduction/mayaname-guide)).

The above memo can be further reduced to:

`=:ETH.ETH:0xe6a30f4f3bad978910e2cbb4d97581f5b5a0ade0:1e6/3/0:t:10`

If the MAYAName `t` has A*ffiliate Basis Points* set, the memo can be reduced even further to:

`=:ETH.ETH:0xe6a30f4f3bad978910e2cbb4d97581f5b5a0ade0:1e6/3/0:t`

{% hint style="success" %}
If the affiliate MAYAName has subaffiliates set, the affiliate fee is split proportionally according to the affiliate share basis points assigned to each subaffiliate. See the [MAYAName Guide](https://docs.mayaprotocol.com/mayachain-dev-docs/introduction/mayaname-guide).
{% endhint %}

**Other examples:**

* `=:r:thor1el4ufmhll3yw7zxzszvfakrk66j7fx0tvcslym:19779138111` - swap to at least 197.79 RUNE
* `=:BNB/BUSD-BD1:thor15s4apx9ap7lazpsct42nmvf0t6am4r3w0r64f2:628197586176 -` Swap to at least 6281.9 Synthetic BUSD.
* `=:BNB.BNB:bnb108n64knfm38f0mm23nkreqqmpc7rpcw89sqqw5:544e6/2/6` - swap to at least 5.4 BNB, using streaming swaps, six swaps, every two blocks.

**Custom Refund Address**

By default, in the case of a refund the protocol will return the inbound swap to the original sender. However, in the case of protocol <> protocol interactions, many times the original sender is a smart contract, and not the user's EOA. In these cases, a custom refund address can be defined in the memo, which will ensure the user will receive the refund and not the smart contract.

**Multiple Affiliates**

Interfaces can define up to 5 valid affiliate (allowing both MAYANames and MAYA addresses) and affiliate basis points pairs in a swap memo and the network will attempt to skim an affiliate fee for each. Affiliates and affiliate basis points are separated by "/", eg. `:t1/t2/t3:10/20/15`. Alternatively, up to 5 valid affiliates with exactly one specified basis point value can be defined, in which case the network will apply the same basis points fee to each affiliate MAYA address. For affiliate MAYANames, the default basis points set in the MAYAName configuration will be used. For example, in the following affiliate section of the memo:

`:tmaya13wrmhnh2qe98rjse30pl7u6jxszjjwl4fd6gwn/tmaya1uuds8pd92qnnq0udw0rpg0szpgcslc9p8gps0z/t3:10`

the 10 basis points will apply to both addresses, while the affiliate MAYAName will use the default affiliate basis points specified in its configuration.\
\
**Subaffiliates**

All MAYANames used in the memo as affiliates can have nested subaffiliate MAYANames defined (each child MAYAName can have its own nested child MAYANames; the depth of nesting is unlimited). The affiliate fee assigned to the root affiliate MAYAName is further split among these nested subaffiliates MAYANames. Details on how to define the hierarchy of nested subaffiliates MAYANames can be found in the [MAYAName Guide](https://docs.mayaprotocol.com/mayachain-dev-docs/introduction/mayaname-guide)

**Calculating Affiliate Fee Shares**

Details on how affiliate fee shares are calculated in case of hierarchy of nested subaffiliates MAYANames can be found in the [MAYAName Guide](https://docs.mayaprotocol.com/mayachain-dev-docs/introduction/mayaname-guide) (**Calculating Affiliate Fee Shares** section)

**Multiple affiliate examples:**

* `=:r:thor1el4ufmhll3yw7zxzszvfakrk66j7fx0tvcslym::t1/t2/t3`- swap RUNE using three affiliates, with affiliate fees calculated based on the default affiliate basis points specified in each affiliate MAYAName configuration
* `=:r:thor1el4ufmhll3yw7zxzszvfakrk66j7fx0tvcslym::t1/t2/t3:10/20/30`- swap using three affiliates, with affiliate fee basis points overridden by the points specified in memo
* `=:r:thor1el4ufmhll3yw7zxzszvfakrk66j7fx0tvcslym::t1/t2/t3:/20/`- swap using three affiliates, with affiliate fees calculated based on the default affiliate basis points specified in the `t1` and `t3` affiliate MAYAName configurations, and with the affiliate fee basis points for `t2` overridden by the points specified in the memo (20 bps)
* `=:r:thor1el4ufmhll3yw7zxzszvfakrk66j7fx0tvcslym::t1/t2/t3:20`- swap using three affiliates, with affiliate fees calculated based on the default affiliate basis points specified in the `t2` and `t3` affiliate MAYAName configurations, and with the affiliate fee basis points for `t1` overridden by the points specified in the memo (20 bps)
* `=:r:thor1el4ufmhll3yw7zxzszvfakrk66j7fx0tvcslym::t1/tmaya13wrmhnh2qe98rjse30pl7u6jxszjjwl4fd6gwn/t2:20`- swap using three affiliates, with affiliate fees calculated based on the default affiliate basis points specified in the `t1` and `t2` affiliate MAYAName configurations, and with the affiliate fee basis points specified in the memo (20 bps) for `tmaya13wrmhnh2qe98rjse30pl7u6jxszjjwl4fd6gwn`address
* `=:r:thor1el4ufmhll3yw7zxzszvfakrk66j7fx0tvcslym::t1/tmaya13wrmhnh2qe98rjse30pl7u6jxszjjwl4fd6gwn/t2:20/20/`- swap using three affiliates, with the affiliate fee basis points for `t1` overridden by the points specified in the memo (20 bps), with the affiliate fee basis points specified in the memo (20 bps) for `tmaya13wrmhnh2qe98rjse30pl7u6jxszjjwl4fd6gwn`address, and with affiliate fees calculated based on the default affiliate basis points specified in the `t2` affiliate MAYAName configurations

**Invalid affiliate memo examples:**

* `=:r:thor1el4ufmhll3yw7zxzszvfakrk66j7fx0tvcslym::t1/tmaya13wrmhnh2qe98rjse30pl7u6jxszjjwl4fd6gwn`- affiliate basis points for explicit affiliate address must be provided
* `=:r:thor1el4ufmhll3yw7zxzszvfakrk66j7fx0tvcslym::t1/t2/t3:10/20`- the number of affiliate names and affiliate basis points must be equal (except when only one value of affiliate basis points is provided)

### Add Liquidity

There are rules for adding liquidity, see [the rules here](https://docs.thorchain.org/learn/getting-started#entering-and-leaving-a-pool).\
\&#xNAN;**`ADD:POOL:PAIREDADDR:AFFILIATE:FEE`**

<table><thead><tr><th width="178.1692373378876">Parameter</th><th width="319.5924083090204">Notes</th><th>Conditions</th></tr></thead><tbody><tr><td>Payload</td><td>The asset to add liquidity with.</td><td>Must be supported by THORChain.</td></tr><tr><td><code>ADD</code></td><td>The Add Liquidity handler.</td><td>also <code>a</code> <code>+</code></td></tr><tr><td><code>:POOL</code></td><td>The pool to add liquidity to.</td><td>Can be shortened.</td></tr><tr><td><code>:PAIREDADDR</code></td><td>The other address to link with. If on external chain, link to THOR address. If on THORChain, link to external address. If a paired address is found, the LP is matched and added. If none is found, the liquidity is put into pending.</td><td>Optional. If not specified, a single-sided add-liquidity action is created.</td></tr><tr><td><code>:AFFILIATE</code></td><td>The <a href="https://gitlab.com/mayachain/docs/one-stop-shop/-/blob/main/mayachain-dev-docs/concepts/broken-reference/README.md">affiliate</a> address. The affiliate is added in to the pool as an LP.</td><td>Optional. Must be THORName or THOR Address.</td></tr><tr><td><code>:FEE</code></td><td>The affiliate fee. Fee is allocated to the affiliate.</td><td>Optional. Limited from 0 to 1000 Basis Points.</td></tr></tbody></table>

**Examples:**

* **`ADD:POOL`** single-sided add liquidity. If this is a position's first add, liquidity can only be withdrawn to the same address.
* **`+:POOL:PAIREDADDR`** add on both sides.
* **`+:POOL:PAIREDADDR:AFFILIATE:FEE`** add with affiliate
* `+:BTC.BTC:`

### Withdraw Liquidity

Withdraw liquidity from a pool.\
A withdrawal can be either dual-sided (withdrawn based on pool's price) or entirely single-sided (converted to one side and sent out).

**`WD:POOL:BASISPOINTS:ASSET`**

<table><thead><tr><th width="209">Parameter</th><th width="305">Notes</th><th>Extra</th></tr></thead><tbody><tr><td>Payload</td><td>Send the dust threshold of the asset to cause the transaction to be picked up by THORChain.</td><td>Caution <a href="https://midgard.ninerealms.com/v2/thorchain/inbound_addresses">Dust Limits</a>: BTC,BCH,LTC chains 10k sats; DOGE 1m Sats; ETH 0 wei; THOR 0 RUNE.</td></tr><tr><td><code>WITHDRAW</code></td><td>The withdraw handler.</td><td>Also <code>-</code> <code>wd</code></td></tr><tr><td><code>:POOL</code></td><td>The pool to withdraw liquidity from.</td><td>Can be shortened.</td></tr><tr><td><code>:BASISPOINTS</code></td><td>Basis points (0-10000, where 10000=100%).</td><td></td></tr><tr><td><code>:ASSET</code></td><td>Single-sided withdraw to one side.</td><td>Optional. Can be shortened. Must be either RUNE or the ASSET.</td></tr></tbody></table>

**Examples:**

* **`WITHDRAW:POOL:10000`** dual-sided 100% withdraw liquidity. If a single-address position, this withdraws single-sidedly instead.
* **`-:POOL:1000`** dual-sided 10% withdraw liquidity.
* **`wd:POOL:5000:ASSET`** withdraw 50% liquidity as the asset specified while the rest stays in the pool, eg:
* `wd:BTC.BTC:5000:BTC.BTC`

### DONATE & RESERVE

Donate to a pool or the RESERVE.

**`DONATE:POOL`**

<table><thead><tr><th width="153.3006301940066">Parameter</th><th width="150">Notes</th><th>Extra</th></tr></thead><tbody><tr><td>Payload</td><td>The asset to donate to a THORChain pool.</td><td>Must be supported by THORChain. Can be RUNE or ASSET.</td></tr><tr><td><code>DONATE</code></td><td>The donate handler.</td><td>Also <code>%</code></td></tr><tr><td><code>:POOL</code></td><td>The pool to withdraw liquidity from.</td><td>Can be shortened.</td></tr></tbody></table>

**Example:** `DONATE:ETH.ETH` - Donate to the ETH pool.

**`RESERVE`**

<table><thead><tr><th width="154.85927710812584">Parameter</th><th width="187.65003293833834">Notes</th><th>Extra</th></tr></thead><tbody><tr><td>Payload</td><td>THOR.RUNE.</td><td>The RUNE to credit to the RESERVE.</td></tr><tr><td><code>RESERVE</code></td><td>The reserve handler.</td><td></td></tr></tbody></table>

### BOND, UNBOND & LEAVE

Perform node maintenance features. Also see [Pooled Nodes](https://docs.thorchain.org/thornodes/pooled-thornodes).

**`BOND:ASSET:UNITS:NODEADDR:PROVIDER:FEE`**

<table><thead><tr><th width="228.24376113012488">Parameter</th><th width="255">Notes</th><th>Extra</th></tr></thead><tbody><tr><td>Payload</td><td>The asset to bond to a Node.</td><td>Must be RUNE.</td></tr><tr><td><code>BOND</code></td><td>The bond handler.</td><td>Anytime.</td></tr><tr><td><code>:ASSET</code></td><td>The pool's asset from which to bond.</td><td>Optional.</td></tr><tr><td><code>:UNITS</code></td><td>The amount of LP units to bond.</td><td>Optional, if empty, all available LP units will be used.</td></tr><tr><td><code>:NODEADDR</code></td><td>The node to bond with.</td><td>Required</td></tr><tr><td><code>:PROVIDER</code></td><td>Whitelist in a provider.</td><td>Optional, add a provider</td></tr><tr><td><code>:FEE</code></td><td>Specify an Operator Fee in Basis Points.</td><td>Optional, default will be the mimir value (2000 Basis Points). Can be changed anytime.</td></tr></tbody></table>

**`UNBOND:NODEADDR:AMOUNT`**

<table><thead><tr><th width="153.3006301940066">Parameter</th><th width="150">Notes</th><th>Extra</th></tr></thead><tbody><tr><td>Payload</td><td>None required.</td><td>Use <code>MsgDeposit</code>.</td></tr><tr><td><code>UNBOND</code></td><td>The unbond handler.</td><td></td></tr><tr><td><code>:NODEADDR</code></td><td>The node to unbond from.</td><td>Must be in standby only.</td></tr><tr><td><code>:AMOUNT</code></td><td>The amount to unbond.</td><td>In 1e8 format. If setting more than actual bond, then capped at bond.</td></tr><tr><td><code>:PROVIDER</code></td><td>Unwhitelist a provider.</td><td>Optional, remove a provider</td></tr></tbody></table>

**`LEAVE:NODEADDR`**

<table><thead><tr><th width="153.3006301940066">Parameter</th><th width="150">Notes</th><th>Extra</th></tr></thead><tbody><tr><td>Payload</td><td>None required.</td><td>Use <code>MsgDeposit</code></td></tr><tr><td><code>LEAVE</code></td><td>The leave handler.</td><td></td></tr><tr><td><code>:NODEADDR</code></td><td>The node to force to leave.</td><td>If in Active, request a churn out to Standby for 1 churn cycle. If in Standby, forces a permanent leave.</td></tr></tbody></table>

**Examples:**

* `BOND:::maya19m4kqulyqvya339jfja84h6qp8tkjgxuxa4n4a` - Bond with all units to node address
* `BOND:BTC.BTC:1000000000:maya19m4kqulyqvya339jfja84h6qp8tkjgxuxa4n4a` - Bond 10 BTC worth of LP units
* `UNBOND::750000000000:maya1x2whgc2nt665y0kc44uywhynazvp0l8tp0vtu6` - Unbond specific amount
* `LEAVE:maya1hlhdm0ngr2j4lt8tt8wuvqxz6aus58j57nxnps` - Leave the network

### TRADE ACCOUNTS

Trade accounts allow users to deposit L1 assets into MAYAChain for more efficient trading without constant L1 transactions. This reduces fees and enables faster swaps.

**`TRADE+:ADDRESS`** - Deposit assets into a trade account **`TRADE-:ADDRESS`** - Withdraw assets from a trade account

<table><thead><tr><th width="153">Parameter</th><th width="150">Notes</th><th>Extra</th></tr></thead><tbody><tr><td>Payload</td><td>The asset being deposited/withdrawn</td><td>Use <code>MsgDeposit</code></td></tr><tr><td><code>TRADE+</code></td><td>Trade account deposit</td><td>Deposits L1 assets into MAYAChain trade account</td></tr><tr><td><code>TRADE-</code></td><td>Trade account withdrawal</td><td>Withdraws assets from trade account to L1</td></tr><tr><td><code>:ADDRESS</code></td><td>The address</td><td>For deposit: MAYAChain address. For withdrawal: L1 destination address</td></tr></tbody></table>

**Examples:**

* `TRADE+:maya1x2whgc2nt665y0kc44uywhynazvp0l8tp0vtu6` - Deposit into trade account
* `TRADE-:bc1qxyz...` - Withdraw BTC from trade account to Bitcoin address
* `TRADE-:0xabc123...` - Withdraw ETH/tokens from trade account to Ethereum address

{% hint style="info" %}
Trade accounts are currently only available from version 1.123.0+
{% endhint %}

### MIRGRATE

Internal memo type used to mark migration transactions between a retiring vault and a new Asgard vault during churn. Special MAYAChain triggered outbound tx without a related inbound tx.

**`:MIGRATE`**

| Parameter      | Notes                            | Extra                       |
| -------------- | -------------------------------- | --------------------------- |
| Payload        | Assets migrating                 |                             |
| `MIGRATE`      | The migrate Handler              |                             |
| `:BlockHeight` | MAYAChain Blockheight to migrate | Must be a valid blockheight |

Example (LINK): `MIGRATE:3494355`

### NOOP

Dev-centric functions to fix MAYAChain state. Caution: may cause loss of funds if not done exactly right at the right time.

**`NOOP`**

<table><thead><tr><th width="146.1615145988245">Parameter</th><th width="263">Notes</th><th>Extra</th></tr></thead><tbody><tr><td>Payload</td><td>The asset to credit to a vault.</td><td>Must be ASSET or RUNE.</td></tr><tr><td><code>NOOP</code></td><td>The noop handler.</td><td>Adds to the vault balance, but does not add to the pool.</td></tr><tr><td><code>:NOVAULT</code></td><td>Do not credit the vault.</td><td>Optional. Just fix the insolvency issue.</td></tr></tbody></table>

### Refunds

The following are the conditions for refunds:

| Condition                | Notes                                                                                                        |
| ------------------------ | ------------------------------------------------------------------------------------------------------------ |
| Invalid `MEMO`           | If the `MEMO` is incorrect the user will be refunded.                                                        |
| Invalid Assets           | If the asset for the transaction is incorrect (adding an asset into a wrong pool) the user will be refunded. |
| Invalid Transaction Type | If the user is performing a multi-send vs a send for a particular transaction, they are refunded.            |
| Exceeding Price Limit    | If the final value achieved in a trade differs to expected, they are refunded.                               |

Refunds cost fees to prevent Denial of Service attacks. The user will pay the correct outbound fee for that chain.

### **Other Internal Memos**

* `donate` - add funds to a pool (example:`DONATE:ETH.ETH`)
* `consolidate` - consolidate UTXO transactions
* `ragnarok` - only used to delist pools.