EA2YOU
PUBLIC PREVIEWPublic preview · No real payments · No live trades yet
EA2YOU / WORKSPACE

Binance connection guide

HOSTED ONLY / NETWORK OFF

Create a least-privilege API key and verify each layer.

EA2YOU profiles cover Spot or Futures only. Margin, Options, P2P, Earn, withdrawals and transfers are excluded.

VISUAL WALKTHROUGH

See the flow before you begin

Illustrations show location and sequence. Menus can vary by version and region.

01
API Management
  • Read
  • Spot / Futures
  • Withdraw OFF
  • Transfer OFF

Limit API permissions

Enable only what is needed

02
Trusted IP
Runner egress IP•••.•••.•••.•••Restricted ✓

Restrict Trusted IP

Use the assigned runner IP

03
EA2YOU
BOT · FUTURES 5x↔API · FUTURES 5x
MATCHED · TEST

Pair matching settings

Market + Leverage + Modes

01 / BINANCE

Prepare the API key

1. Open API management in your Binance account.
2. Create a dedicated key for EA2YOU.
3. Enable read plus only the required Spot or Futures permission.
4. Disable every withdrawal and transfer permission.
5. Restrict the key to the runner egress Trusted IP shown by the system.
6. Keep the API and secret keys private; never send them through chat.
02 / EA2YOU

Save and pair

1. Match Spot or Futures to the API permission.
2. Futures: configure leverage 1–125, Cross/Isolated and One-way/Hedge.
3. Save keys through the encrypted form.
4. Build a Binance strategy with the same configuration.
5. Pair strategy and API profile.
6. Rehearse on synthetic or uploaded CSV data.
7. Before live use, verify API, IP, symbol filters, leverage brackets, margin/position mode and read the actual values back from the exchange.

Why Trusted IP matters

Trusted IP limits trading-key use to the assigned runner. A runner migration must add and test the new IP before removing the old one. Multiple IPs must never be used to evade rate limits.

The real egress IP is shown only to the assigned member and administrators, never on public pages.