Health Endpoint as Runtime Economic Truth
The Health endpoint defines the economic capability of a WAproxy node at runtime.
It is not a cosmetic status check.
It exposes execution boundaries.
Typical response fields:
status
fee_bps
enabled_coins
btc_min_send_sat
ltc_min_send_sat
doge_min_send_sat
These values represent live economic configuration.
Applications must query Health before execution.
Hardcoding limits is discouraged.
Minimum send thresholds prevent:
- dust transactions
- uneconomical broadcasts
- spam execution
- network rejection
Example:
btc_min_send_sat = 10000
ltc_min_send_sat = 100000
doge_min_send_sat = 100000000
All limits are expressed in atomic SAT units.
Health represents runtime truth.
Configuration files represent local policy.
Execution respects declared boundaries.
Before wallet_send:
- Verify coin is enabled
- Verify amount_sat >= min_send
- Apply fee logic
- Validate safety margin
WAproxy executes only within declared economic capability.
Health defines what the node can safely execute.