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

> What the args property of an account_auth descriptor entity or auth_descriptor struct
must contain if it represents a multi-sig auth descriptor struct mult

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

STRUCT

# multi\_sig\_args

What the `args` property of an `account_auth descriptor` entity or `auth_descriptor` struct
must contain if it represents a multi-sig auth descriptor

```signature
struct multi_sig_args {
 flags: set<text>;
 signatures_required: integer;
 signers: list<byte_array>;
}
```

`flags: set<text>;`
:   Set of flags, which is used to determine if the auth descriptor can be used to
    authenticate an operation or not. In other words, it represents the level of
    control that this auth descriptor has over the account.

    **See Also**

    * [auth\_flags](https://docs.chromia.com/pages/ft4-rell/-f-t4-library/lib.ft4.core.accounts.auth_flags/) — for information on the predefined flags

`signatures_required: integer;`
:   When authorizing an operation with this auth descriptor, it should be signed by
    at least this number of signers from the `signers` field

`signers: list<byte_array>;`
:   When authorizing an operation with this auth descriptor, it should be signed by
    some or all of the public keys or EVM addresses (without `0x`) in this field.

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

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