Concept: Transactions
Transaction model
A transaction is the atomic financial event in Glacez. Two major families exist:
- Order: market activity on trading pairs
- Transfer: deposits and withdrawals
Each transaction carries timestamp, status, notes, fees, origin metadata, and optional exchange/wallet references.
Order types
LimitOrder: order with target price, optional liftClosedOrder: executed trade with final totalMarketOrder: market execution form (supported in model hierarchy)
Transfer types
DEPOSITWITHDRAWAL
Some deposits can be auto-generated by system coherence logic to keep history consistent.
Transaction statuses
Common statuses include:
TO_CONFIRMTO_PLACEPLACEDCOMPLETETO_CANCELCANCELEDPROCESSINGUNKNOWN
Status progression depends on flow type (manual update, strategy-generated, or worker execution).
Tracking and events
Transactions are accompanied by:
- Track entries (audit trail of changes)
- Status events for user-facing visibility
- Optional email notifications via async email jobs
Related: