docs/setup/static-ip-setup.md

Rama main · réplica de lectura del repositorio original.

# Static IP Setup

Many Indian broker APIs require an allow-listed static public IP before live
orders are accepted. FlintTrade does not apply for this on your behalf; you do
it directly in your broker's developer console.

## Checklist

1. Get a static public IP from your ISP, cloud VM, VPN provider, or office
   network.
2. Confirm the IP from the exact machine or network that will run FlintTrade.
3. Add that IP in the broker developer console.
4. Wait for the broker's activation window to complete.
5. Test with example data and Practice first, then unlock Live only after the broker
   dashboard shows the IP as active.

## Broker Notes

| Broker | Where to configure | Notes |
|---|---|---|
| Dhan | DhanHQ / profile API settings | Dhan API access is typically tied to an API token and IP allow-list. Re-check the broker UI after token rotation. |
| Upstox | Upstox developer console | Verify whether the app is in sandbox or production before enabling Live mode. |
| Kotak Neo | Kotak developer console / Neo API onboarding | Follow the broker's current onboarding email or console instructions. Neo has no sandbox — live read / API smoke only until funded unlock. |
| IndMoney | Broker/API onboarding channel | Confirm production access and IP rules directly with the broker. |

## Native Dhan + Kotak Neo Connected (read) / API smoke

The locked path is **native** Dhan + Kotak Neo on a static-IP host
whose public IP is allow-listed at both brokers. Smoke uses **non-funded**
accounts and live REST API reads (quotes / depth / hist / chain where the
SDK allows). That historical evidence is REST API smoke, not proof of the
now-wired v3 async SFeed/order-feed lifecycle and not funded Live unlock. The
stream lifecycle has local synthetic coverage only; live-account,
market-hours, funded-order, Live-promotion, and cross-platform proof remain
outstanding.

## FlintTrade Boundary

FlintTrade stores no personal public IP in committed docs or examples. Keep IPs
in your broker console and local `.env` or deployment configuration only.
Changing networks without updating the broker allow-list should make live
orders fail closed.