Prop Trade Records: Public Market IDs Are Not Private Account Fills
A public trade stream and a private account execution ledger describe different scopes. Replayed events can distort either one if identity is lost. Deduplicate within the documented source and preserve the distinction between market activity and your account.
Explore this site’s existing research resource
Retain source and identifier together
Record the venue, product, symbol, identifier and event type. An ID is only meaningful within its documented scope. Do not merge unrelated events from different accounts or products because their local numeric labels happen to match.
Bybit’s public-trade documentation distinguishes event fields and trade records from other streams. That public schema is not a HashHedge integration claim. Its messages cannot establish that a particular evaluation account participated in a trade.
Audit a fictional reconnect replay
Suppose a supplied market record has T1 quantity 2,T1 quantity 2 again after reconnect, and T2 quantity 1. If the source definition establishes that both T1 rows identify the same event, the unique market quantity is 3 rather than 5.
A separate private fill named T1 must retain its account and source namespace. A matching text label alone cannot join it to the public event. Missing private execution evidence leaves account quantity unknown even when the public stream is fully deduplicated.
| Received row | Quantity | Unique-event treatment |
|---|---|---|
| T1 first receipt | 2 | Count once |
| T1 replay | 2 | No additional event |
| T2 | 1 | Different supplied event |
| Unique total /account evidence | 3 /not supplied | Market subtotal is not account quantity |
Use the right ledger for evaluation activity
The related resource preserves this site’s earlier reconnect audit. A Singapore diary should retain the original timestamps and full local dates without turning a replay received later into a new trade. Actual account costs and valuation require separate records.
The optional sponsored HashHedge link offers current programme conditions. No stream is opened or account accessed here. The example establishes a unique public-event subtotal, not a user’s executions, qualifying activity or a successful evaluation.
Sources and rule dates
- Bybit: public trade field definitions
Checked 2026-10-23. Selected published description only. Worked numbers and event records are fictional; no actual provider account, search result, live price, eligibility or payment is established. - HashHedge: challenge types
Checked 2026-10-23. Selected published description only. Worked numbers and event records are fictional; no actual provider account, search result, live price, eligibility or payment is established. - HashHedge: terms and conditions
Checked 2026-10-23. Selected published description only. Worked numbers and event records are fictional; no actual provider account, search result, live price, eligibility or payment is established.