Qian Bin

> So it seems there is no big improvement in real cases. But your benchmark run shows something interesting, maybe we could get a benefit with this if we were...

It'll be better to delay this PR, since the maindb-v4 brings a lot of changes to package `trie` and `muxdb`.

> @qianbin we can mark the `trie` and `muxdb` code coverage tasks as blocked until the `maindb-v4` is merged into `main`. OK, thanks.

> Please give more details of what testing is needed 1. try sync with and without `-disable-pruner`, and record the time and disk space used. 2. test correctness of APIs

> Hi @qianbin I was playing around with your changes and wanted to share some results about the sync performance. > > That's good. How about turning on `-skip-logs`?

Hi, @shaswatsaloni. Thanks for your report. The address *0x9a1e4bf6c41f50c399a128ab588fe4e4883bd872* was the address of an authority node, and its balance was initially set as 25m, which is not shown in transfer...

@molekilla ~You must be using latest connex release v1.3.1.~ In practical, type string? is more suitable for Clause.data, and i think it's the rare case to encode a tx in...

Do you have another ledger? This error is reported when a non-matched(not previously imported) device connected.

the error message indicates the address(or say pub key) is not the one the app knows. you may re-link the device with sync app.

The xpub is already stored in the sync app. That's to say, you can see the wallet and funds without connected to ledger device.