User Story

To be able to see the history of the channels (anonymized though), we need a bot that will listen in to a set of public channels and writes their content in a DB. We also need a full-text search in the archive in the same bot.

Imagine http://offsite.chat/html, but on steroids.

https://github.com/status-im/sta

GetVerboseBlockInfo uses NBitcoin's SendCommandAsync, which parses the returned JSON with Newtonsoft.

Then our RpcParser parses it again with Newtonsoft.

There're 2 opportunities to improve the performance significantly:

• Don't parse the JSON twice.
• Parse the JSON with System.Text.JSON instead.

The performance gain was about 80% when I messed around with it (https://github.

See https://github.com/lexansoft/ethcracker/tree/master/src/accounts/keystore/testdata

Reviving LedgerHQ/ledger-live-desktop#1468 we need to revisit all the ctas and make sure they are consistent. At this point I don't know if a cta is supposed to use pointer or not. It's pretty bad right now:

• Accounts screen, cards use pointer
• Portfolio screen, rows use arrow
• Settings button, arrow
• Dismiss a banner?, pointer
• Sidemenu items, arrow
• Extern

We avoid using cgo anywhere in the codebase since it causes problems with cross compilation. However, cgo would be advantageous in some cases (e.g. can use certain optimized libraries, can use libsecp256k1 bindings)

Investigate the viability of using xgo to do this. Test it on linux/osx/windows.

• https://github.com/karalabe/xgo
• https://github.com/ethereum/go-ethereum/wiki/Cross-compili

1. Start wallet from scratch
2. Go to Receive tab
3. Assuming Receiving address that got showed up first had no label, button would be Add Label
4. When you click on a Receiving address that is already labeled, button will change to Edit Label, and when you select again an address without label, button will stay Edit Label instead of Add Label.

![addLabelBug1](https://user-images

this is the natural behavior of node-hid but we should backport this behavior to all other transports.

basically it's a failsafe for race conditions.

if you open() a transport, you are responsible to close() it in a finally, if an open() happens during that time it should throw if it concerns the same device (e.g. by path id / by uuid, ... depending on the transport)