ghost43

> Generating a new one takes as much as 20 seconds How specifically are you generating a new address? What is it that you have timed to take that long,...

> electrum client (i guess it uses jsonrpc too) yes, the CLI uses jsonrpc too. Have you increased the gap limit for this wallet? If so, what value is it...

> Generating a new one takes as much as 20 seconds, whilst on electrum-ltc and electron-bch less than a second, with the same amount of addresses on the wallet. electrum-ltc...

Right... so the root cause seems to be the db writes being slow. This is unfortunately an architectural problem that is hard to fix. The wallet db is backed by...

btw, do you have wallet file encryption enabled? If you use the CLI, this is the `encrypt_file` option for the `password` command. That has a huge effect on the wallet...

> So with that in mind, I guess you could experiment with removing that line (i.e. the call to `self.save_db()` inside `wallet.set_up_to_date`) Another trick you could do, is open the...

> I think that without saving wallet file we would lose incoming transaction etc... Barring gap limit issues, on-chain state cannot really be lost. (as you would just resync the...

> we use createnewaddress as a jsonrpc call... Just because my example is not using jsonrpc, do not presume it would not work like that :P It should. > can...

> Would the online electrum's daemon recognize the incoming transactions\inputs? Barring gap limit issues, yes. That is, if the offline daemon is generating addresses faster than they are getting used,...

> Moreover, latest electrum tar.gz version (from downloads electrum website) doesn't have protobuf requirement, which was fixed in a recent commit, appended and this causes application fail. Indeed the latest...