Skip to content
Docs FAQ
For owners and power users

FAQ

Answers to the problems people actually hit while running Vektor on mainnet.

"cannot connect an account to its own builder"

Strike will not let the account that owns a builder code approve that code for itself. Sign that account in with API wallet keys (no builder fee is charged), or connect a different wallet address to trade through the builder.

Rungs show "rejected (silently_dropped)"

Strike accepted the request but the engine never created the order, and sent no event. Vektor's watchdog checks after 8 seconds and frees the rung. The usual cause was rungs below the market minimum (ADA-USD on mainnet: $10); Deploy now refuses those.

"Order price is not a multiple of tick size"

Every price must sit on the market's price grid. Vektor rounds grid and hedge prices to the tick (sells down, buys up). If you see this, report the market; it means a market's tick was missing from its rules.

Deploy says "Paused by regime guard"

The market scored EXTREME. Untick the guard in the sidebar to deploy anyway. It never cancels or closes anything.

I deposited but my balance is still $0

Strike credits after block confirmations, usually 2-5 minutes (about 12 blocks on Ethereum). The balance updates by itself. If the panel showed an error after the wallet signed, open Manual in the Deposit panel and confirm by transaction hash.

Wallet balance shows "unavailable"

Public Solana and Ethereum RPC servers (the nodes that answer balance queries) reject requests from browser pages. Vektor sends them through its own address instead: a proxy in development and a small serverless relay in production. If it still fails, the message lists each server and its reply.

I refreshed and had to sign in again

Tick "Remember on this device" when signing in. It keeps the trading key in this browser and restores the session after a refresh. Your running grid is rebuilt from your open orders either way.

My wallet asked to send on the wrong network

Cancel it. The Ethereum deposit flow now asks the wallet to switch to Ethereum mainnet first and refuses to send on any other chain.

My position shows 20x, not the leverage I chose

Older versions sized orders with your leverage but did not set it on Strike. Deploy and hedge launch now set the symbol leverage first.