Open satwikkansal opened 6 days ago
confirming this is on latest commit/release?
yes, I'm using the image available at ghcr.io/drift-labs/gateway
from the logs it looks like the txs aren't being included in blocks by Solana validators. This can happen during busy network times mostly due to competitive tx fees.
for now I recommend your script to retry the tx if it still returns 404s after atleast 15s or can retry more aggressively with something like cancelAndPlace to ensure it doesn't place multiple orders
another option is set a higher CU price per request: https://github.com/drift-labs/gateway?tab=readme-ov-file#cu-price--limits when your script encounters more 404s
also related #67
@jordy25519 every Gateway version has been doing the same since we first tried it, and we used to place orders with ridiculously high CU prices and different RPC providers too. Most order placing want a few retries, I hardly ever see orders that fly on the first attempt. What can I provide for diagnostics?
also try starting gateway with the --skip-tx-preflight
flag.
@jordy25519 every Gateway version has been doing the same since we first tried it, and we used to place orders with ridiculously high CU prices and different RPC providers too. Most order placing want a few retries, I hardly ever see orders that fly on the first attempt. What can I provide for diagnostics?
increasing chances of tx landing is a known challenge on Solana. Besides CU prices the options are basically retry the tx and sending to multiples RPC providers simultaneously, will add support for these things in next gateway update.
please see new 1.2.0 release