# resolve_fee_assets · FT4 Rell API · Chromia Docs (concept)

> function resolve_ fee_ assets(config: list< fee_asset >): map<byte_ array, big_ integer> Parses a list of fee_asset s, and returns a map of all the ones th

Source: https://docs.chromia.com/pages/ft4-rell/-f-t4-library/lib.ft4.core.accounts.strategies.transfer/resolve_fee_assets/

FUNCTION

# resolve\_fee\_assets

```signature
function resolve_fee_assets(config: list<fee_asset>): map<byte_array, big_integer>
```

[Source](https://gitlab.com/chromaway/ft4-lib/-/blob/development/rell/src/lib/ft4/core/accounts/strategies/transfer/fee_config.rell#lines-49)

Parses a list of `fee_asset`s, and returns a map of all the ones that could be mapped to
actual assets. This does not throw if an asset has not yet been registered, allowing
assets to be added to the config a long time before actually registering them.

This function does not discern when a `fee_asset` entry is invalid. This is because it will
typically be called after the `fee_asset` has been parsed and values have been fixed when
possible. If improper input is provided, this function will behave this way:

* if `id` is present, other values will be ignored
* if `id` is missing, `name` and `blockchain_rid` must both be present - it will throw
  otherwise

**Parameters**

* **config** — the list of `fee_asset`s to parse.

**Returns**

a map of asset ID to fee amount to pay for that asset

**See Also**

* [`fee_asset`] — for more information on when it is invalid.

[View this page on docs.chromia.com](https://docs.chromia.com/pages/ft4-rell/-f-t4%20-library/lib.ft4.core.accounts.strategies.transfer/resolve_fee_assets.html)Generated API reference, mirrored from the live docs