Page cover
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Security

How Husher's non-custodial design creates security through structural separation, not policy promises

Husher is built on a non-custodial foundation. Security begins with the structural fact that Husher never holds, controls, or has access to user funds at any point in a standard swap. There is no internal balance, no hot wallet, and no custody layer for an attacker to compromise.

In a standard swap, the security model works through clear separation: users control their own keys, Exchange Service Providers handle execution briefly, and Husher acts solely as a routing and orchestration interface between them.

Security in this model comes from structural boundaries, not promises. Understanding where each party's control begins and ends is the starting point for using Husher safely.

Security model at a glance

Area
Who controls it
Husher's exposure

Private keys and wallets (standard swaps)

You

None

Deposit address generation

Exchange Service Provider

None

Trade execution and settlement

Exchange Service Provider

None

Routing and orchestration

Husher

No custody taken

Delivery to destination wallet

Exchange Service Provider

None

Explore the security section

Last updated