Kaynak doğrulamalı araştırma: Deribit Heartbeat Cancel ON

Decision Matrix

Source Map

• Deribit API Documentation: Public API endpoints: heartbeat and cancelheartbeat (deribit-public-api)
• Deribit API Documentation: FIX API session and CancelOnDisconnect (deribit-fix-api)
• Deribit API Documentation: HTTP RPC and private cancel endpoint context (deribit-http-api)
• Deribit API Documentation: Deribit API documentation home (deribit-docs-home)
• NexuAlpha Official Source Registry: Official source registry policy for venue evidence (nexualpha-official-source-registry)

Control Notes

1. Heartbeat response

Heartbeat response is the point where public documentation must become an operating rule. In this package, it means heartbeat is an application-level liveness contract for WebSocket automation. The practical action is to test the exact response path and alert on missed test_request messages. The unresolved edge is whether a reconnect library hides missed heartbeat failures, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

2. Account default

Account default is the point where public documentation must become an operating rule. In this package, it means Deribit documentation ties cancel-on-disconnect behavior to account configuration or FIX tag selection. The practical action is to record the account default in a non-secret operations note before live orders. The unresolved edge is whether different subaccounts inherit the same default, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

3. FIX tag override

FIX tag override is the point where public documentation must become an operating rule. In this package, it means CancelOnDisconnect can be sent at FIX Logon while absent tags fall back to account default. The practical action is to test Logon settings in a controlled session before production rollout. The unresolved edge is whether FIX and WebSocket sessions should share the same rule, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

4. Graceful logout

Graceful logout is the point where public documentation must become an operating rule. In this package, it means logout, abnormal closure and heartbeat timeout are distinct session endings. The practical action is to document which closure path is expected during deployments. The unresolved edge is whether a clean shutdown accidentally leaves orders open, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

5. Explicit cancel fallback

Explicit cancel fallback is the point where public documentation must become an operating rule. In this package, it means private cancel endpoints still matter when disconnect automation is not enough. The practical action is to keep a separate manual or automated cancel route and reconcile final state. The unresolved edge is whether a lost response after explicit cancel races with disconnect cancellation, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

6. Evidence scope

Evidence scope is the point where public documentation must become an operating rule. In this package, it means liveness evidence can prove session behavior but not exchange-wide safety. The practical action is to store timestamps, session id, non-secret order id, event and final query result. The unresolved edge is whether logs expose strategy, balance or position data, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

Known Unknowns

• whether a reconnect library hides missed heartbeat failures
• whether different subaccounts inherit the same default
• whether FIX and WebSocket sessions should share the same rule
• whether a clean shutdown accidentally leaves orders open
• whether a lost response after explicit cancel races with disconnect cancellation
• whether logs expose strategy, balance or position data

Practical Takeaway

Deribit documentation makes connection liveness an order-risk control rather than a background networking detail. The public API documentation describes WebSocket heartbeat and test_request behavior, and says orders opened over a connection can be cancelled if the account is configured to cancel on disconnect and the connection fails the heartbeat flow. The FIX API documentation describes a CancelOnDisconnect tag at Logon and notes that abnormal or logout-driven session behavior can affect order cancellation depending on that setting. The readiness decision is to test heartbeat response, disconnect handling, account default, FIX tag use, graceful logout and post-disconnect order state before relying on Deribit automation. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, API key, pool route, stablecoin balance, tokenized asset or policy framework will work under every future condition.