The trade has a dependency chain
Wallet software, RPC providers, smart contracts, oracles, bridges, chains, and execution services can each affect availability or settlement. Self-custody does not remove these dependencies.
Availability and solvency are different
A sequencer outage may delay transactions without creating a loss, while a contract exploit or bridge deficit can impair assets. The correct response depends on the failure mode.
Plan for degraded operation
Know the canonical status pages and withdrawal path before an incident. Avoid repeated blind signing when a transaction appears stuck.
- Verify chain and destination
- Review bridge finality assumptions
- Keep recovery assets outside one dependency chain
Map control as well as code
Published code does not by itself reveal who can change it. Upgradeable contracts may use an administrator, multisignature account, governance vote, or timelock. Each arrangement changes the balance between fast incident response and protection from unilateral changes.1
The transaction path can also depend on a wallet, RPC endpoint, chain sequencer, bridge, oracle, automation network, execution service, and settlement contract. A failure in one layer may stop trading without stopping liquidations or may stop withdrawals while positions continue to accrue costs.3
Prepare a dependency-specific response
Before depositing, record the canonical status pages, supported withdrawal route, contract addresses, approval-revocation method, and whether direct contract interaction is documented. During an incident, identify the failed layer before retrying signatures or bridging more funds.23