If the TMAI migration claim reaches the Solana approval step and then fails with SignatureAddressMismatch, Error Number: 6007, Custom: 6007, or custom program error: 0x1777, the Base signature was made by a different Ethereum/Base account than the eligible snapshot address.
How to fix it
Refresh the migration page.
Connect the exact eligible Base wallet shown in the eligibility lookup. The Base signature must come from that snapshot address.
Connect the Solana wallet where you want to receive the migrated TMAI.
Click Sign Base message and approve the message only from the eligible Base wallet.
If you use Phantom for both Base and Solana, switch Phantom to the Base/EVM account for the Base signature step. After the signature is captured, switch Phantom back to the Solana account before approving the Solana transaction.
Approve the Solana transaction.
Important notes
The Solana wallet needs at least 0.01 SOL for network fees and token-account rent.
If the portal says it cleared the saved Base signature, click the claim button again and re-sign from the eligible Base wallet. If the same signature keeps being reused, refresh the page and start again.
The migration allocation is based on the Base TMAI snapshot. For veTMAI/staking reimbursements paid before the snapshot, the reimbursed TMAI was already reflected in the wallet balance used for migration eligibility. There is not a second separate staking claim in the migration portal.
Token Metrics will never ask for your seed phrase or private key.
If it still fails
Send support the eligible Base address, the Solana destination address, and either the Solana transaction signature or the full error text shown by the wallet/portal.