Summary
A sandbox with the same protocol and payloads runs on Solana Devnet at devnet.joyride.exchange.
How an RFQ works
- A taker sends a request naming its legs. Each leg is one instrument, one side, and one quantity. All legs share one underlying and one expiry.
- The venue publishes the request as an
openevent on therfq_makerchannel of the trading WebSocket. Every quoter subscribed to that channel receives it on its own connection and prices the package inside the request window. - Quoters respond with a signed package quote. A directional request asks for one side; a two-way request allows a bid, an ask, or both. The quote stays firm until the expiry the maker sets, at most one hour later. Several makers may answer a request, with one quote each inside its window.
- The taker is shown the best price per side and accepts one side of one quote for the whole package.
- The fill executes on-chain in one transaction against both parties’ collateral. Every leg lands or none does. The resulting positions settle at expiry against the settlement price.
Who quotes
Any user can request quotes. Quoting them requires the exchange’s approval: Joyride designates an approved account as a market maker by granting the quoter role and provisioning its on-chain subaccount. Once the subaccount is funded, the maker authenticates with its wallet and starts receiving requests.Timing
What is not supported
Signed quote payloads include both parties’ subaccount addresses. Quote competition does not provide on-chain identity anonymity.
Sessions authenticate with a wallet signature or an existing session token. API Connectivity covers the protocol.