Skip to main content
MFA (multi-factor authorization) validator lets you use multiple validators for a single transaction. MFA works as a layer on top of other validator modules. It works as a multiplexer for the validator modules, calling the underlying validator implementations to validate the transaction. It also lets you have multiple configurations for the same validator module. For example, you can set up an MFA validator so that the user needs to sign a transaction with both an EOA and a passkey.

Subvalidators

Subvalidators are the validator modules that are used under the hood to validate the signature. Any ERC-7579 validator module can serve as a subvalidator. Subvalidator ID is the index of the validator in the validator list. For example, if you installed the ECDSA and the passkey modules as subvalidators, the ECDSA validator will have index 0 and the passkey validator will have index 1.

Module selection

There are two MFA validator modules: the registry-free one and the legacy one, which is the SDK default. The legacy module checks the ERC-7484 registry on installation, so installing it on a new account reverts. Select the registry-free module explicitly with MULTI_FACTOR_VALIDATOR_V2_ADDRESS. The selection is not inherited from the account config, so repeat it in the explicit signer selection as well. Otherwise the signature is routed to the legacy module.

Initialization

To create an account with MFA:
You can also install the MFA module on an existing account:

Usage

Signer Selection

Management

Adding a validator

You can also use this to update the config of the existing subvalidator.

Removing a validator

Example: EOA + passkey (2-of-2)

End to end: create an account that requires both an EOA and a passkey, then approve a transaction with both factors.