Wallet control
SplitLayer requests signatures from your connected wallet. It does not receive your seed phrase or private key. Funds remain at the source address until a signed transaction transfers them to the contracts involved in the route.
Non-custodial access does not remove smart-contract or bridge risk. While a transfer is in progress, its contracts and operators determine the available settlement or recovery path.
Approvals are permissions
ERC-20 approval permits the specified spender to transfer an allowed amount of a token. Check the contract address and amount before signing. Existing allowance may remain after a rejected or failed transfer.
After use, review outstanding allowances with your wallet or a trusted allowance-management tool. Revoking allowance is itself an onchain transaction and requires gas. A revocation cannot reverse a transfer already executed.
The trust boundaries
| Dependency | What can go wrong | User-visible response |
|---|---|---|
| Wallet and browser | Wrong account, compromised extension, deceptive signature | Verify the wallet's transaction details |
| RPC and indexers | Stale data, outages, incomplete reads | Refresh and inspect the chain explorer |
| Routing service | Unavailable liquidity, stale quote, service limits | Request a new quote; do not fabricate a route |
| Bridge and swap contracts | Contract failure, delayed settlement, provider incident | Keep the source hash and inspect provider status |
| Stablecoin issuer | Depeg, freezing, redemption restrictions | Verify the exact asset and issuer terms |
| Destination chain | Congestion, sequencer outage, reorganization | Wait for verified destination settlement |
A transaction is not the whole transfer
A confirmed source transaction and a completed destination transfer are different events. The route may still be awaiting source confirmations, a destination transaction, or a provider refund.
LI.FI exposes both a status and a more precise substatus. DONE with PARTIAL or REFUNDED does not mean the intended token arrived in full. NOT_FOUND may mean indexing has not caught up. Check receiving transaction details before considering the intended transfer settled.
Review status of this release
Review the selected provider's contract source, deployment addresses, administrative permissions, review reports, incident procedures, and upgrade policy. Review a small transfer end to end before increasing exposure.
If a transfer needs attention
- Record the source transaction hash, chains, token contracts, route provider, and timestamp.
- Inspect the source transaction receipt and routing-provider explorer.
- Check whether the provider reports a partial delivery, refund, or pending settlement.
- Avoid sending another transfer merely because a progress indicator stopped updating.
- Use only the support channel linked by the relevant official bridge documentation. Never share a seed phrase or sign a recovery request you cannot verify.