For a university school project I will be making some edits to your documentation which will aim to make writing more technical

Please add edits if you would like :)

Codecov Report

Merging #10574 into master will decrease coverage by 0.01%.
The diff coverage is 21.42%.

[![Impacted file tree graph](https://codecov.io/gh

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

A user asked me on slack if estimatefee returns BTC per Byte or BTC per Kilobyte... honestly I don't know and it's a bit hard to tell. I compared mainnet full nodes bcoin vs Bitcoin Core and observed a wild divergence (outputs below).

From Bitcoin Core help:

Estimates the approximate fee per kilobyte needed for a transaction to begin
confirmation within conf_target blocks if possible

Problem

currently when more than 7 coins are registered for the CoinJoin, then the error notification shows that there are not sufficient funds selected for the mix. Although this is correct, it is misleading the user as it does not tell about the too many coins.

Solution

Add a notification that is thrown when more than 7 coins are registered, and that says

Error!
You can o

The app's required node version (8.x or whatever our version of electron supports) should be documented in the README.

Team, I see a lots of broken links and in-correct or outdated documentation..

1. dotnet run doesn't work any more. Instead it should be dotnet

https://academy.stratisplatform.com/Developer%20Resources/SmartContracts/Tutorial2-HelloWorld/deploying-hello-world-contract.html

2. Operational guide github repo is missing

https://github.com/stratisproject/StratisCore/releases/tag/1.4.0.0-hac

If I want to change the settings (for example to use the Dogecoin Mainnet), I need to manually enter #settings in the URL.

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

Some examples:

• It's unclear if the Receiving Address changes/updates when funds are received (i.e to automatically prevent address re-use).
• What do the responses for all the HD requests look like?

It seems that any new applications should be making use of the HD wallet + account features, as that is the future, but currently it's creating more work for developers to have to debug and reverse-

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

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

Describe the bug
Please see issues in the Voting Tab of page rendering and asset pool.
Rendering seems to affect local only where the voting toggle runs off of the page.

To Reproduce
Steps to reproduce the behavior:

1. Go to the Hamburger Menu
2. Click on Voting
3. Click on each:Worker - Proposed, Active, BSIPs, Expired, Legacy Proposals enabled VS disabled.
4. See rendering e

Bounty

Scope

• The existing Burner Wallet uses a number of special URL schemes for taking users directly to certain features, such as loading a private key or loading a recipient address.
• However, these URL patterns are not documented and are implemented in confusing sections of code

Deliverables

• A document, either in the repo or in the Wiki, outlining the specification f

The messaging right now is pretty confusing when it states the transaction has not been broadcast.

Technically this is true, but it's leading users to believe the transaction wasn't broadcast at all. It. is however, it's just being done by anchor-link.

It's unclear weither or not Electron supports Bluetooth out of the box, there is this discussion here electron/electron#7367 but it's not clearly stated and I can't find any documentation in Electron itself. Electron often have a degraded support of Chromium features, don't implement it all so it's worth trying if hw-transport-web-ble works from the renderer thread.