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

> function register_ account(): account Registers an account on this chain, using a certain strategy. Can only be called from an operation. It will register 

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

FUNCTION

# register\_account

```signature
function register_account(): account
```

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

Registers an account on this chain, using a certain strategy.

Can only be called from an operation.

It will register the account with the `account_details` retrieved by
`_strategy.account_details`, and using the logic found in `_strategy.action`.

The new account will have a main auth descriptor given by `account_details.main`, and
optionally a disposable auth descriptor given by `account_details.disposable`

It expects all signers of both auth descriptors to have signed this transaction.

Throws if the operation that came just before this one cannot be handled. Common cases are:

* the operation is not registered as a strategy operation through extensions of `strategy`
* the operation has been misconfigured, and its name does not match the operation mount name

Throws if the signature verification is unsuccessful. Common cases are:

* `evm_signatures` is misconfigured:
  + any of the signers and signatures don't match in the exact order they're found
  + any of the signatures is null
  + there's more signatures than signers
* a signature from one of the auth descriptor participants is missing:
  + an EVM signer is specified but the signature is not found in `evm_signatures`
  + an FT signer is specified but the signature is not in the transaction
  + a signer passed is neither an EVM nor an FT signer (its length does not match either of
    `core.auth.EVM_ADDRESS_SIZE` and `core.auth.FT_PUBKEY_SIZE`)

Throws if either auth descriptor is invalid. Common cases include:

* the main auth descriptor has expiration rules instead of `core.accounts.GTV_NULL`
* the disposable auth descriptor's expiration rules:
  + is a complex rule with too many rule components
  + has already expired
  + is not the valid GTV representation of a rule
* errors with the `args` field:
  + some required flags are missing
  + in multi-sig auth descriptors, the `required_signatures` field:
    - is 0 or less
    - is greater than the number of signers

Throws if `core.accounts.AUTH_DESCRIPTORS_PER_ACCOUNT_UPPER_BOUND` is set to 1 and
`account_details.disposable` is not null.

Throws if some conditions added in development through extensions (`before_register_account`
or `after_register_account`) aren't met

**Returns**

the newly registered account

**See Also**

* [\_strategy](https://docs.chromia.com/pages/ft4-rell/-f-t4-library/lib.ft4.core.accounts.strategies/_strategy/) — for information on how to structure the transaction that calls this function.

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