mirror of
https://github.com/Such-Software/smirk-backend-core.git
synced 2026-10-17 07:21:32 +02:00
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.
This commit is contained in:
+4
-1
@@ -115,7 +115,10 @@ FEATURE_GRIN=true
|
|||||||
# the LWS at register/import so per-payment XMR/WOW receive addresses are
|
# the LWS at register/import so per-payment XMR/WOW receive addresses are
|
||||||
# scanned. REQUIRES your monero-lws / wownero-lws to run with
|
# scanned. REQUIRES your monero-lws / wownero-lws to run with
|
||||||
# `--max-subaddresses >= 200` (it defaults to 0, which disables subaddress
|
# `--max-subaddresses >= 200` (it defaults to 0, which disables subaddress
|
||||||
# support entirely). Check yours before enabling.
|
# support entirely). Confirm with:
|
||||||
|
# curl -s http://<lws>/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_XMR_SUBADDR_PROVISIONING=false
|
||||||
#
|
#
|
||||||
# FEATURE_UTXO_MULTI_ADDRESS: mounts the batched BTC/LTC endpoints
|
# FEATURE_UTXO_MULTI_ADDRESS: mounts the batched BTC/LTC endpoints
|
||||||
|
|||||||
Reference in New Issue
Block a user