Wallets & safety
Know what you sign and keep access to your wallets.
Your wallets
Your connected wallet supplies the chosen developer-buy amount from the network shown beside it and serves as the developer wallet for its own wallet family. For the other family, connect a wallet or generate one. Connected EVM approvals proceed sequentially as the wallet switches chains. Balances and transactions remain separate on each chain.
Generated keys stay in browser memory and are excluded from the public recovery record. Export them before funding and store the backups privately. Anyone with a private key can control its wallet.
Before you sign
- Review the developer-buy amount and network, each native allocation, and its estimated initial buy.
- Check the source and receiving wallet addresses and destination chains.
- Choose creator or holder rewards where the launchpad offers them.
- Check recorded transactions before retrying or starting another batch.
Funding and launches require transaction signatures. Four.meme also uses a login signature from the selected launch wallet. Keep exported keys private and never send them in a support request.
Services and launchpads
Splits uses wallet providers, blockchain RPC services, launchpads, and Relay for cross-chain funding and native-asset conversion. An outage can delay quotes or status updates after a transaction has succeeded.
Each launchpad controls its launch and trading rules. Check token addresses and market links after confirmation. Tokens can lose value, and success on one chain does not guarantee success on another.
Existing claims
For account or email fee claims, the first payout-wallet binding relies on sign-in verification and the Splits attestation service. After binding, only the recorded payout wallet can authorize a change.