Transaction landing
Speed in memecoin trading is mostly one thing: getting your transaction into a block before the price moves. Winko never trusts a single route. Every transaction it signs is broadcast to five landing routes at once, and whichever confirms first wins.
The five routes
| Route | What it is |
|---|---|
| Helius Sender | A dual route that submits to validators and the Jito block-engine auction together. Carries a tip plus a priority fee. Always on. |
| BlockRazor | Fast v2, with a Frankfurt, New York or Tokyo endpoint so the hop to the relay is short wherever you are. |
| Stellium | A dedicated fast tx-landing relay with regional endpoints. |
| Flashblock | Fast landing over a persistent HTTP/2 connection. |
| RPC fan-out | The raw transaction sent to every configured RPC node at once, as a floor under the specialised relays. |
How it works
The signed transaction is sent to all configured routes simultaneously, and the first acceptance is the one returned to you. Each relay wants a small tip to prioritise the transaction, paid as a transfer inside the transaction itself. Winko adds a tip for a relay only when that relay is actually live, so you never pay for a route that cannot land your trade.
What you control
The Helius Sender tip and the priority fee (microlamports per compute unit) are yours to tune in Settings, along with the BlockRazor tip and region. The relay keys and endpoints are all server-side and never reach the browser.
Launches are size-aware
A create-and-buy transaction must fit in Solana's 1232-byte limit. Winko probes the size first and, if the tip set would push it over, trims tips or splits into two transactions so the token still launches, over the routes that fit. See Launch a token.