ghost43
ghost43
https://github.com/spesmilo/electrum/commit/a05dab2c4dcf0ce2f69e9a4258bd3c88c818a91d should fix at least the original illegal name problem There are probably many issues here though... Going to close and then reopen; to trick TARS into sending new tracebacks...
related: https://github.com/spesmilo/electrum/issues/4058
https://github.com/spesmilo/electrum/commit/05ebd0f5b223a7e39eb1b1c0bb3ac949c061cec9 should fix the "user deleted/renamed file while running" problem There is at least one other cause: the `wallets` dir disappearing while running (e.g. file is on usb drive; user...
> fine as far as server load is concerned, but the throttling begins frequently anyway. What kind of throttling do you mean/experience?
How does your client connect to your server? What incoming IP does the server see for the client?
Could you test with disabled resource usage limits? ``` COST_SOFT_LIMIT=0 COST_HARD_LIMIT=0 ``` (see https://electrumx-spesmilo.readthedocs.io/en/latest/environment.html#resource-usage-limits for more info)
Well it already has its own section in the docs; that's what I linked to. Or do you mean specifically this `COST_SOFT_LIMIT=0; COST_HARD_LIMIT=0` should be mentioned? Btw I think maybe...
Please rebase against current master, and make sure the CI checks pass.
> I have written up an Electrum Protocol proposal which seeks to improve both: (1) Reduce RPC bandwidth requirements (compressed block headers + protobuf/CBOR (de)serialisation) (2) Reduce requirements of Clients...
> > (2) Reduce requirements of Clients making calls (removing `block_height` requirement) > > I think the blockchain.transaction.get_merkle proposal (2) could be useful and it is a relatively small change...