Scenario 1: Regular Account and Member of a Multisig Account

In this scenario, we'll guide you through the process of claiming tokens using a regular account that is also a member of a multisig account. Follow these steps to connect your wallets, select the appropriate multisig account, and ensure the correct signatures for a successful claim.

Steps:

1. Open the token claim page.
2. Connect your L1 wallet using WalletConnect.
3. Connect your L2 wallet.
4. Switch to the multisig claim tab.
   • If you're not a member of a multisig account, an error message will appear.
5. From the account dropdown, select the multisig account you want to sign for.
6. If a list of destination addresses exists (from previous L2 address signings), select an L2 destination from this list.
7. Sign for the connected member.
   • If there are other members on the same device, disconnect the L1 wallet and reconnect for each account before starting the signing process.
8. When the required number of signatures is reached, the submit claim button will become active.
9. If multiple members sign for different L2 accounts, ensure all members agree on the L2 account and sign the required number of signatures for the claim transaction.
10. Finally, click the submit claim button and sign on the L2.

Scenario 2: Multisig Account that is a Member of Itself

This scenario covers the steps for a multisig account that is also a member of itself. Follow these instructions to successfully claim your tokens.

Steps:

1. Open the token claim page.
2. Connect your L1 wallet using WalletConnect.
3. Connect your L2 wallet.
4. Switch to the multisig claim tab.
   • If you're not a member of a multisig account, an error message will appear.
5. From the account dropdown, select the multisig account you want to sign for.
6. If a list of destination addresses exists (from previous L2 address signings), select an L2 destination from this list.
7. Sign for the connected member.
   • If there are other members on the same device, disconnect the L1 wallet and reconnect for each account before starting the signing process.
8. When the required number of signatures is reached, the submit claim button will become active.
9. If multiple members sign for different L2 accounts, ensure all members agree on the L2 account and sign the required number of signatures for the claim transaction.
10. Finally, click the submit claim button and sign on the L2.

Scenario 3: Multisig Account that is Not a Member of Itself

In this scenario, a multisig account cannot sign its own claim because it is not a member of itself. However, members of this account can sign on its behalf.

Steps:

• Since this account is not a member of itself, it cannot sign its claim. However, members of this account can sign on its behalf.

Scenario 4: Multisig Account that is a Member of Other Multisig Accounts

This scenario involves a multisig account that is a member of other multisig accounts. Follow these steps to claim your tokens.

Steps:

1. Open the token claim page.
2. Connect your L1 wallet using WalletConnect.
3. Connect your L2 wallet.
4. Switch to the multisig claim tab.
   • If you're not a member of a multisig account, an error message will appear.
5. From the account dropdown, select the multisig account you want to sign for.
6. If a list of destination addresses exists (from previous L2 address signings), select an L2 destination from this list.
7. Sign for the connected member.
   • If there are other members on the same device, disconnect the L1 wallet and reconnect for each account before starting the signing process.
8. When the required number of signatures is reached, the submit claim button will become active.
9. If multiple members sign for different L2 accounts, ensure all members agree on the L2 account and sign the required number of signatures for the claim transaction.
10. Finally, click the submit claim button and sign on the L2.

Key Details and Best Practices

• If multiple members of a multisig account need to sign on the same device, disconnect and reconnect for each account to ensure the process works correctly.
• Ensure consensus among members when signing for different L2 accounts to avoid any conflicts or errors.