Infrastructure Boundaries

Husher's infrastructure is deliberately minimal, with no hot wallets, no balances, and no custody layer

Husher's infrastructure is intentionally minimal to reduce attack surface. The platform consists of a user interface (web and Telegram) and backend routing logic. There is no custody layer, no internal balance sheet, and no platform-held wallets that could be targeted.

What Husher operates without

No hot wallets

Husher holds no platform wallets. Deposit addresses are generated and controlled by ESPs.

No internal user balances

There is no Husher account balance for any user. Funds are never credited to a platform account.

No custodial accounts

Husher does not hold funds on behalf of users at any stage of execution.

No persistent personal data storage

The platform does not store personal data beyond what users voluntarily provide for optional account features.

No long-term trading history storage

Individual trading history is not retained in a persistent Husher-controlled store.

No ability to reverse completed swaps

Once a swap is completed on-chain, Husher cannot intervene, reverse, or redirect the output.

Why minimal infrastructure matters

Each component that exists in a platform's infrastructure is a potential attack surface. By eliminating hot wallets, internal balances, and custodial accounts entirely, Husher removes the categories of target that account for the majority of platform-level security incidents in the crypto industry.

The absence of these components is not a limitation. It is a deliberate security design choice that aligns with the non-custodial model: if Husher never holds funds, there is nothing for a platform-level compromise to drain.