Risks That Remain With Non-Custodial Smart Contract Trading
Non-custodial trading does not eliminate the risk of losing funds. Smart-contract bugs, compromised keys and infrastructure failures can still affect users. Retaining authority over transactions is one protection. The reliability of the contracts, services and markets involved needs a separate assessment.
For funds and trading desks, the question extends beyond who controls the wallet: what could fail between depositing capital, opening a position and withdrawing the proceeds?
What does non-custodial trading protect against?
Non-custodial trading generally reduces reliance on a provider holding funds and moving them at its discretion. The exact protection depends on the system's signing requirements, permissions and contract rules.
It does not mean funds always remain in the original wallet. Capital may enter contracts or become trading collateral. Once that happens, access also depends on how those systems work.
Two questions help separate the risks:
- Control: Who can authorise transactions?
- Availability: Can the user access funds when needed?
Can smart-contract bugs put funds at risk?
A contract can contain a flaw even when its intended design requires user authorisation. Errors in permissions, accounting or interactions with other contracts can allow funds to be stolen or locked.
Administrative controls also matter. Where a system supports upgrades or emergency pauses, review who holds those powers and how they are protected. Ethereum's security guidance identifies access controls and compromised administrator keys as important considerations.
An institution should assess the deployed contracts and their permissions, rather than relying on the non-custodial label alone.
Does an audit remove smart-contract risk?
An audit adds independent scrutiny, but it cannot guarantee that every vulnerability has been found. Ethereum's security guidance explicitly cautions against treating audits as a complete solution.
When reviewing an audit, ask:
- Which contracts and versions were examined?
- Were significant findings resolved?
- Does the deployed system match the reviewed version?
- Which integrations or components were outside the scope?
An audit is useful evidence. Its scope determines what that evidence covers.
Can infrastructure failures delay access to funds?
A system can prevent unauthorised spending while still depending on services that process transactions, generate proofs or complete settlement.
ShieldTX provides a concrete example. Its architecture explains that withdrawals depend on a proven batch being accepted by the settlement contract. It also describes, in the current architecture, how its sequencer can delay processing or stop submitting batches required for withdrawals.
The practical question is what recovery process exists if a required service stops operating. Teams should distinguish a recovery mechanism available today from one described as a future improvement.
What risks remain outside the contract itself?
A contract may depend on information or activity elsewhere. Understanding those dependencies helps identify failures that reviewing the contract alone may miss.
| Dependency | What to check |
|---|---|
| External data or attestations | Who confirms that an event happened, and what if the confirmation is wrong? |
| Cross-chain transfers | Which services must complete the transfer before funds become usable? |
| Transaction processing | What happens if processing, proving or settlement stops? |
| Signing access | How are keys, devices and account recovery protected? |
| Trading venue | Which margin, liquidation and order rules apply after funds arrive? |
Assess the full trading workflow
Non-custodial design is an important part of evaluating a trading system. A complete assessment also considers what can break and what can delay access.
For shielded Hyperliquid trades, review ShieldTX's technical architecture and speak with the team about the controls and dependencies relevant to your trading workflow.
How to access ShieldTX
ShieldTX enables shielded Hyperliquid trades, helping traders limit the public association between their funding wallet and trading activity.
Professional traders, funds and systematic desks can request access and discuss their trading requirements, including API integration for existing workflows.
Request access to ShieldTXFrequently asked questions
Does keeping my private key prevent every loss?
A key controls authorisation, but it does not prevent losses caused by contract failures. Protecting the key and understanding the transactions it authorises are both important.
Does a zero-knowledge proof guarantee the whole system is safe?
A proof verifies specified conditions. It does not automatically establish that every dependency, external input or operational process is reliable.
What should a trading desk review before committing capital?
Map the complete deposit, trade and withdrawal flow. Identify contract permissions, external dependencies, audit coverage and recovery procedures. Then confirm how the team will monitor positions and respond to interruptions.