Wallet Migration Guide
Allocrypt now uses the Safe L2 singleton on every supported destination chain. That keeps your Smart Wallet address deterministic across Monad and Ethereum. If a temporary L1-derived Safe received tokens, transfer them into your canonical Safe here.
What Happened
Safe smart wallets come in two variants: L1 (designed for Ethereum mainnet) and L2 (designed for L2 chains and alt-L1s like Monad). Allocrypt briefly used the L1-derived Safe for Ethereum while Monad used the L2-derived Safe. We now use the L2 derivation everywhere so one connected wallet maps to one canonical Smart Wallet address.
Because the singleton address is part of the CREATE2 derivation, the L1-derived Safe has a different address than the canonical L2-derived Safe. Both wallets are fully controlled by your same connected wallet — you own both.
Manual Migration Steps
If you prefer to transfer tokens manually or the bulk transfer above is not available, repeat these steps for each chain with a legacy balance:
Find your old and new Safe addresses
Open Allocrypt and connect your wallet. The migration tool shows the old L1-derived Safe address and the canonical L2-derived Safe address for the selected chain.
Choose the chain with a legacy balance
Use the chain selector in the migration tool. If you are using the Safe app manually, open the old Safe on that same network.
Safe URLs use the network prefix, for example app.safe.global/home?safe=eth:<old-safe> or app.safe.global/home?safe=monad:<old-safe>.
Send each supported token to your canonical Safe
In the Safe app, click "New transaction" then "Send tokens." Select each supported payment token, vault share, or underlying token with a balance and send the full balance to your canonical Safe address.
You are the sole owner of both Safes, so there is no multisig approval needed. Each transaction requires one signature from your connected wallet.
Verify in Allocrypt
Return to Allocrypt and refresh the page. Your portfolio should now reflect the transferred positions. Repeat the migration for any other supported chain with legacy balances.
Supported Tokens to Transfer
The bulk transfer checks supported payment tokens, vault shares, and vault underlying tokens for the selected chain. Transfer any that show a balance in your old Safe.
FAQ
Are my funds safe?
Yes. Both your old and new Safe wallets are controlled by the same connected wallet. Only you can sign transactions on either Safe. Your vault share tokens are standard ERC-20 tokens sitting in a wallet you fully own.
Why did the address change?
Safe uses CREATE2 deterministic deployment, and the singleton address is an input to the address derivation. Using the L1 singleton on Ethereum and the L2 singleton on Monad produced two deterministic addresses. Allocrypt now uses the L2 singleton everywhere to preserve one canonical address across supported chains.
Do I need native gas?
The Allocrypt bulk transfer uses the same Safe UserOperation path as the app. Manual transfers in the Safe app may require native gas on the selected chain.
What if I ignore this?
Your tokens remain safe in your old wallet. However, Allocrypt now reads and manages positions from the canonical L2-derived Safe address. To manage those positions through Allocrypt, move supported token balances into the canonical Safe.
Can I just keep using the old Safe?
New Allocrypt deposits and withdrawals use the canonical Safe address. You can still interact with an old Safe directly through the Safe app, but the app will not treat it as the active portfolio wallet.
