Read irreversible application history
The Integration RPC exposes a strictly ordered Trusted transaction stream. An exchange can read after its last committed sequence and process only transactions that are already application-irreversible.
Commit credit and cursor together
The safest pattern is to store the customer credit and the new sequence cursor in the same exchange database transaction. After a restart, replay begins from the exact durable cursor.
WebSocket is a hint, not the ledger
Low-latency notifications can trigger faster polling, but the durable cursor is authoritative. Missed WebSocket messages therefore do not create missed deposits.
Download WildRoot.
Use the official GitHub Releases page for downloadable WildRoot artifacts.