|
|
@ -44,14 +44,17 @@ in ElectrumX are very cheap - they consume about 100 bytes of memory |
|
|
|
each and are processed efficiently. I feel the defaults are low and |
|
|
|
encourage you to raise them. |
|
|
|
|
|
|
|
MAX_HIST - maximum number of historical transactions to serve for an |
|
|
|
address. The current Electrum protocol requires |
|
|
|
MAX_HIST - maximum number of historical transactions to serve for |
|
|
|
a single address. The current Electrum protocol requires |
|
|
|
address histories be served en-masse or not at all, |
|
|
|
an obvious avenue for abuse. This limit is a stop-gap |
|
|
|
until the protocol is improved to admit incremental |
|
|
|
history requests. The default value is 2,000 which is |
|
|
|
I feel is low. Increasing to around 10,000 is probably |
|
|
|
fine but beyond that experimental. |
|
|
|
an obvious avenue for abuse. This limit is a |
|
|
|
stop-gap until the protocol is improved to admit |
|
|
|
incremental history requests. The default value is |
|
|
|
2,000 which should be ample for most legitimate |
|
|
|
users. Increasing to around 10,000 is likely fine |
|
|
|
but bear in mind one client can request multiple |
|
|
|
addresses. I welcome your experiences and suggestions |
|
|
|
for an appropriate value. |
|
|
|
MAX_SUBS - maximum number of address subscriptions across all |
|
|
|
sessions. Defaults to 250,000. |
|
|
|
MAX_SESSION_SUBS - maximum number of address subscriptions permitted to a |
|
|
|