From 38489986af8e8f5e51606e2c428c6c7002beb2ff Mon Sep 17 00:00:00 2001 From: jwinterm Date: Sat, 1 Aug 2026 16:23:10 -0400 Subject: [PATCH] docs(env): show how to verify max_subaddresses before enabling The note said to check the LWS setting without saying how. Adds the one-liner and records that the backend probes it at provision time and refuses loudly, so a wrong setting is not a silent half-working state. --- .env.example | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.env.example b/.env.example index 7d7ac0e..8d81696 100644 --- a/.env.example +++ b/.env.example @@ -115,7 +115,10 @@ FEATURE_GRIN=true # the LWS at register/import so per-payment XMR/WOW receive addresses are # scanned. REQUIRES your monero-lws / wownero-lws to run with # `--max-subaddresses >= 200` (it defaults to 0, which disables subaddress -# support entirely). Check yours before enabling. +# support entirely). Confirm with: +# curl -s http:///get_version | grep -o '"max_subaddresses":[0-9]*' +# The backend probes this at provision time and refuses with a clear error +# rather than half-working, so a wrong setting is loud, not silent. FEATURE_XMR_SUBADDR_PROVISIONING=false # # FEATURE_UTXO_MULTI_ADDRESS: mounts the batched BTC/LTC endpoints