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

High-Level Architecture

The five-step path from wallet to executed swap, with Husher acting as orchestrator but never custodian

Husher sits between your wallet and a network of third-party execution providers. It orchestrates the swap flow only; it never touches or controls your crypto.

1

Create a swap and receive a deposit address

You configure the swap on the web app or Telegram bot. Husher requests a unique, one-time deposit address from the selected Exchange Service Provider.

2

Send funds directly from your wallet

You send the input asset from your own wallet to the one-time address. This address is controlled by the ESP, not by Husher.

3

Husher monitors confirmations and execution conditions

Husher watches the deposit in real time. Execution begins as soon as network-specific confirmation thresholds are met.

4

The ESP executes the trade against CEX spot liquidity

The Exchange Service Provider performs the swap using centralized-exchange depth from providers such as Binance, Bybit, and OKX.

5

Output is withdrawn directly to your destination wallet(s)

The output asset is sent straight to the destination address you specified. No Husher hop, no intermediate custody.

The dashed line from Husher to the ESP represents monitoring only. Husher observes confirmation status and execution progress but has no ability to redirect or hold assets.

Last updated