STRUCT

module_args

configuration used by the auth module, as defined in the chromia.yml file

struct module_args {
 evm_signatures_authorized_operations: gtv? = null;
 auth_op_blacklisted_operations: gtv? = null;
}

evm_signatures_authorized_operations: gtv? = null;

List of operations which require the evm_signatures operation. Generally, these operations will have a call to verify_signers inside.

Standard FT4 operations which require evm_signatures do not need to be added here.

If a transaction contains evm_signatures, but this operation is not used to authorize an operation in this list, the transaction will fail. This prevents users from adding a lot of signatures to make the transaction arbitrarily heavy.

Defined in the chromia.yml file as:

Plain text

  evm_signatures_authorized_operations:
    - op_1
    - op_2

The value of this field will be ["op_1", "op_2"].to_gtv()

When parsing it, it will be converted to set<text>, which means duplicate entries will make the parsing fail

auth_op_blacklisted_operations: gtv? = null;

List of operations which should never follow an auth operation. Generally, any operations which does not call authenticate and does not prevent the users from repeatedly calling by rate limiting them should be included here.

Standard operations which cannot be used with an auth operation do not need to be added here.

Defined in the chromia.yml file as:

Plain text

  evm_signatures_authorized_operations:
    - op_1
    - op_2

The value of this field will be ["op_1", "op_2"].to_gtv()

When parsing it, it will be converted to set<text>, which means duplicate entries will make the parsing fail

See Also

is_auth_op — for information on built-in auth operation

Source