How it works

End to end

1. ConnectYour Cardano, Solana or Ethereum wallet signs a Builder Connect challenge. Strike issues an API wallet (an Ed25519 key pair) approved for the builder code. That key signs every order; your wallet is only needed again for deposits and withdrawals.
2. FundDeposit from the sidebar. You type the amount in normal units; the app builds the transaction, your wallet signs it, and the hash is registered with Strike. Credit appears after block confirmations, usually 2-5 minutes. See Deposits and sign-in.
3. Design and testPick a range, levels, margin and leverage in Grid Studio. Backtest it on real mainnet candles first. See Backtest and smart range.
4. DeployOne POST /v2/orders/batch places every rung as a post-only limit order with the builder fee header. Strike acknowledges each one on the user stream and the log shows "resting (engine ack)".
5. RunWhen a rung fills, the counter order is placed for the filled quantity within the same second. The Shield checks every position continuously. Close the tab and the orders stay on Strike; reopen it and the grid is rebuilt from your open orders.

Built for an asynchronous exchange

Strike answers order requests before the matching engine runs them, so 201 pending means "queued", not "placed". Vektor treats the user stream as the truth: fills and rejections arrive there with a reason code.

If no event arrives within a few seconds, a watchdog asks Strike for the order. A missing order means it was silently dropped, and the rung is freed with the reason in the log.