/submit-transaction is signed by the user and sent by RAVN
as signed.
Quotes can’t be altered. The quoteToken is signed. Changing the amount, fee or route
invalidates it (QUOTE_INVALID), and /execute checks its expiry before building.
The SDK checks every execution before the wallet sees it. @ravnexchange/sdk holds what
/execute returns to what your user asked: only the contracts RAVN’s venues use, only the input
token, at most the input amount, RAVN’s fee at most 1% and only to RAVN. It ships through npm, apart
from RAVN’s servers, so on EVM chains and Bitcoin even a compromised RAVN couldn’t empty a wallet
through your integration: the most at stake is the swap amount. On Solana, give it your RPC and it
simulates each transaction too. RAVN’s server runs the same check on every answer. See
the check before the wallet.
Gasless where it counts. On RFQ and gasless venues the user signs a message and a solver pays
the gas, so they need only the token they’re selling.
GET /health reports each venue’s live status.
