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

> function pool_ assets(sender_ blockchain_ rid: byte_ array, sender_ id: byte_ array, recipient_ id: byte_ array, asset: asset , amount: big_ integer) This 

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

FUNCTION

# pool\_assets

```signature
function pool_assets(sender_blockchain_rid: byte_array, sender_id: byte_array, recipient_id: byte_array, asset: asset, amount: big_integer)
```

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

This method ensures that a rule exists for the transfer defined by the parameters passed,
and creates an `account_creation_transfer` entity representing that transfer.

This function does not check that the account does not exist, assuming it has been checked
before calling this.

This function does not allow multiple transfers of the same asset to be transferred to the
same account, regardless of sender.

Can only be called from an operation.

Throws `"TRANSFER NOT ALLOWED"` if no rule allows that transfer

**Parameters**

* **sender\_blockchain\_rid** — the ID of the blockchain where the transfer came from
* **sender\_id** — the sender account ID
* **recipient\_id** — the non-existing account that is being registered
* **asset** — the asset that was transferred
* **amount** — the amount of the asset that was transferred

**See Also**

* [module\_args\_list\_element](https://docs.chromia.com/pages/ft4-rell/-f-t4-library/lib.ft4.core.accounts.strategies.transfer/module_args_list_element/) — for a description of rules

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