Minimum Send Thresholds and Economic Boundaries
WAproxy enforces minimum send thresholds per supported coin.
These limits define the lowest economically valid transfer.
Example configuration:
btc_min_send_sat = 10000
ltc_min_send_sat = 100000
doge_min_send_sat = 100000000
All values are expressed in atomic SAT units.
Execution rule:
amount_sat >= min_send_sat
If amount_sat is below threshold,
execution must be rejected.
Minimum thresholds exist to prevent:
- dust outputs
- uneconomical transactions
- mempool rejection
- execution spam
- micro-fee abuse
The minimum value reflects:
- network fee realities
- atomic precision
- protocol fee impact
- execution viability
Example:
If btc_min_send_sat = 10000
and amount_sat = 9000
Execution must stop.
Minimum thresholds are runtime-exposed via Health.
Applications must not assume static values.
These boundaries preserve:
- predictable execution cost
- stable fee behavior
- economic sustainability
WAproxy enforces economic discipline at the execution layer.