Skip to main content

Trade-mining timing parameters

ParameterDefault/runtime contract
TRADE_MINING_LENGTHdefaults to DEFAULT_TRADE_MINING_DURATION_IN_SETTLEMENT_EPOCHS = 3; override via TRADE_MINING_LENGTH
DEFAULT_TRADE_MINING_SETTLEMENT_MULTIPLIER1 settlement multiplier between trade-mining distributions

Reward-distribution parameters

ParameterDefault/runtime contract
TRADE_MINING_REWARD_PER_EPOCHdefaults to 35,000,000 / (3 * 10 * 365) DDX-equivalent units per epoch; override via TRADE_MINING_REWARD_PER_EPOCH
TRADE_MINING_MAKER_REWARD_PERCENTAGEdefaults to 0.2; override via TRADE_MINING_MAKER_REWARD_PERCENTAGE
TRADE_MINING_TAKER_REWARD_PERCENTAGEcomputed as 1 - maker_percentage, so the default path is 0.8
DDX_FEE_DISCOUNT0.5 when fees are paid in DDX

How to read these values

CategoryWhat it affects
duration and settlement-multiplier fieldshow often trade-mining accounting rolls and how rewards align with settlement cadence
reward-per-epoch fieldthe baseline DDX-equivalent reward budget for one epoch
maker/taker split fieldshow rewards are divided between passive and aggressive liquidity behavior
fee-discount fieldhow paying fees in DDX changes effective fee economics

Notes

Trade-mining values are release-governed operator constants. Validate against current release configuration before using them as immutable economic assumptions. Reward-per-epoch and maker/taker split are runtime-configurable. Treat the defaults above as the code-backed baseline, not a universal deployment promise.

Interpretation rules

  • Do not assume the published defaults are permanent across deployments.
  • Do not read trade-mining parameters as the whole token-economics system; they are one incentive surface.
  • Do not infer exact live payout outcomes from the defaults alone without checking the active runtime posture.
Last modified on April 13, 2026