Skip to main content
If you quote Deribit Block RFQs, you can keep the request-driven shape of your client: receive a package, price it, submit a quote, and process fills. Adapt authentication, price units, quote commitments, and reconciliation before trading on Joyride. The comparison here concerns Deribit Block RFQ. Its official walkthrough documents that workflow.

Quote commitments

A delivered Joyride quote cannot be cancelled, amended or replaced by any client. Joyride has no automatic market maker protection that withdraws quotes after a fill threshold or disconnect. A second response to the same request is rejected. Deribit documents private/edit_block_rfq_quote, private/cancel_block_rfq_quote, and private/cancel_all_block_rfq_quotes, plus market maker protection with a Block-RFQ trade_count_limit. Joyride provides no cancel or replace operation. A client that relies on those operations needs a different exposure policy for Joyride. The quote TTL is the only control over how long a delivered quote remains firm. Keep the quote reserved in your risk system until its outcome is resolved or it expires. Delivery and computation consume part of the request window. Measure the time left when a request arrives. The CLI requires an explicit --ttl; the runner can shorten it to the request’s ceiling.

Map the workflow

On reconnect, resume authentication, subscribe again, then page rfq.maker.poll for open requests. Session resume does not restore subscriptions. A losing quote receives a lost event. Keep local expiry timers as well because a disconnect can drop pushes. Reconcile trades through GET /api/query/rfq-fills?role=maker.

Convert prices and quantities

Deribit Block RFQ quotes carry a price per leg. Joyride quotes carry a bid and/or ask for the whole package in USDC. Convert your leg valuations into package totals using decimal arithmetic.
  • bid is the total you pay if the taker sells the package.
  • ask is the total you receive if the taker buys it.
  • A negative total reverses that cash direction.
  • Quantity signs describe the legs the taker receives or delivers when buying the package.
Money and quantities use decimal strings with at most six fractional digits. Preserve the request’s leg order when signing. Quoting RFQs defines the fields and sign conventions. A buy request asks for an ask, a sell request asks for a bid, and a two_way request allows either side or both. Directional requests expose their side to makers. Quotes fill the full requested package; partial fills are not supported.

Convert expiry units

Deribit’s request expires_at uses milliseconds since epoch. Joyride’s signed quote issued_at and expires_at use Unix seconds. Convert explicitly, or configure a TTL in seconds and let the runner derive the timestamps. These are different fields in different workflows. Do not copy a request deadline into a signed quote without checking the required lifetime and units.

Check unsupported fields

Joyride rfq.create rejects unknown fields. Rebuild the request from the Joyride schema rather than forwarding a Deribit object. Packages contain 1 to 13 option legs on one underlying and one expiry. Dealer targeting, hedge instruments, trade allocations, and a public RFQ trade tape are not provided by this interface. Quote only the instruments returned by live discovery and hedge elsewhere if your strategy requires it. Self-match prevention rejects a maker and taker using the same account. It does not prevent two accounts owned by the same entity from trading with each other. A maker can decline an unanswered request with a reason, such as size_limit or stale_data. That removes its own desk from the request; other makers can still quote. It does not revoke a delivered quote.

Connect your pricing program

The CLI’s maker runner sends an open request as JSON to your program and reads a price or decline from stdout:
Your program returns {ask} for a buy request, {bid} for a sell request, or {bid, ask} for two-way pricing. It can return a decline or leave the request unanswered. The maker client guide includes the subprocess contract and in-process TypeScript setup.

Prepare the account and reconciliation

Before sending quotes:
  1. Create a Joyride account and obtain the quoter role through maker onboarding.
  2. Fund the on-chain RFQ subaccount and verify readiness.
  3. Persist one monotonic quote-nonce sequence per account, before sending each quote.
  4. Check signed fee and collateral ceilings against the quoted sides. Read Fees and Limits.
  5. Track fills through finality and reconcile after disconnects and restarts.
A confirmed fill can later revert and be submitted under a new transaction signature. Key trade and hedge state by RFQ and quote; treat the signature as a transaction attempt. A re-land is the same economic trade. The maker client guide covers the recovery rules. Test the complete lifecycle in the sandbox before moving to Mainnet. Onboarding and integration support: support@joyride.exchange.