Verify network identity, custody and spending permissions before using a bridge or trading interface.
Start with network identity
Use Arc’s official network reference rather than a configuration copied from a reply or direct message. Mainnet and testnet have different chain IDs and assets. Verify the destination before any transfer.
Custody questions to answer before funding
- Who can sign transactions?
- How is account recovery performed?
- Can you withdraw without the current website or device?
- Does the product create or import a wallet?
- What does wallet export expose, and where will it be stored?
- Which sessions, devices and permissions remain active?
Choose a documented funding route
Use Arc Portal or a documented product bridge. Check supported source chain, asset, destination balance and total cost. Do not infer support from a matching address format. Avoid sending funds while a service labels a route disabled or pending.
Banana Gun and Maestro confirmed Arc bridging in their launch announcements. An older Bloom Manager changelog states that its Arc bridge was disabled. The trading directory therefore does not imply that every listed bot can also fund your account.
Approval versus swap versus transfer
| Request | What it authorises | Primary check |
|---|---|---|
| Token approval | A spender can move up to an allowance | Correct contract and amount. |
| Swap | Execution under specified parameters | Input, recipient and minimum output. |
| Transfer | Asset movement to a recipient | Network and full address. |
| Message signature | An application-specific statement or authorisation | Read the meaning; not all signatures are harmless. |
Keep access and allowances separate
Disconnecting a site typically removes its session connection; it does not itself cancel allowances already recorded on-chain. Review permissions using a trusted tool with confirmed Arc support or the relevant contract interface. This site does not claim that an arbitrary Ethereum approval tool supports Arc.
What security tools can and cannot tell you
The explorer provides transaction and contract evidence. A scanner provides an interpretation that can be incomplete. Neither guarantees contract safety, future liquidity or key security. Network finality is not a mechanism for reversing fraud.
If something looks wrong
- Stop signing new requests.
- Verify the URL and transaction history independently.
- Do not provide a seed phrase to someone offering recovery.
- Use the provider’s official support channel for account questions.
- Preserve the transaction hash and relevant public evidence without sharing private keys.
First-trade procedure · How evidence is classified
Frequently asked questions
Can I send funds just because the address looks EVM-compatible?
No. The receiving service must support the specific network and asset.
Does disconnecting revoke approvals?
No. Review and revoke on-chain allowances separately where appropriate.