After clicking "Register Timestamp" it is not obvious to the user that the process is finished. The only option is to click "Reset" to start another run, which is irritating at best.

cleanup old unused code.

The revokes column should show the number of revoking votes and the total number of votes needed to end the voting. This is based on the admin-consensus-mine setting of the chain parameters.

More decimal places are shown on mouse over but this is non-obvious to the user. We should find a better way to show exact numbers without cluttering the interface to much.

We should include a first minimal demo application besides the wallet & community panels with the first public release. Document time stamping would be a low hanging fruit.

We do not make expensive sync rpc api calls during blockchain sync anymore. This prevents the address of the freshly installed node to be updated/shown in the UI during initial sync.

Transaction list balance / "My balance" mismatch:

C:\Users[user]\AppData\Local\Content-Blockchain\coblo still exists after uninstall.

which could make sense in some cases to prevent loosing important data after uninstall, but user should have the option or at least should be warned that his wallet still exists on the computer after uninstall

Changing the alias, registering a timestamp or even voting causes transaction costs. These should be explicitly confirmed by the user before these transactions are sent out. We might offer an option for users to silence these confirmation dialogs.

On the community page in the Validator and Guardians tabs there are buttons to apply for those skills (only shown if you do not already have those skills). They don´t do anything currently. We could show some info popup on how to apply (via telegram or so) before we offer users to apply via stream publishing

Wallet | Alias field shows a non-blinking cursor after the user name (Win 10).

Currently the candidates table shows all ongoing votes. Votes that assign a skill that a user already has are confusing and should be filtered out.

With a fresh installation of the application the newly generated address does not have any native balance. To be able to do any transactions the user needs one or multiple options to get some initial native currency.
We should consider creating a first time use wizard that guides the user through a setup kind of experience ... details to be planned.

In either case, the change is accepted if a sufficiently privileged user signed any input with the signature type SIGHASH_ALL, or if they signed the input with the same index as that output with SIGHASH_SINGLE.
https://www.multichain.com/developers/permissions-management/

We only consider SIGHASH_SINGLE in function getblock() in sync.py.

The revoke actions Validators/Guardians tables in the community panel need to actually trigger the revoking transactions. We should also find a way to track if the user has already sent a revoke for somebody so he cannot send multiple revokes for the same entry. While multiple revokes for the same entry have no effect on the vote they do produce transaction costs.

Currently all sync functions hammer the nodes rpc-api in rotation. We should find a more sane way that only polls for block/transaction updates in rotation and triggers more involved sync function if there actually is a new block/transaction.

Grant button in candidates.py already acts like this

Clicking the send button when there is no form data opens a message box with a raw Decimal conversion exception.

When the multichain node connects to the network for the first time automatically creates a wallet with a random address. Users should be able to backup the private keys of that address. It should also be possible for users to initialize a node with an existing address/private key.

The transaction type recorded in the comment field of the table. This collides with any custom transaction comments a user might want to do. We should create a separate column for the transaction type with a label like output.

On a fresh installation with 0 balance I can set my alias. There is no error message and the gui shows my newly set alias. Setting or changing the alias should give information about the fact that the alias change has been requested. The new alias should only be shown if it is confirmed on the blockchain. A solution would be to show something like "'New alias registration in progress" and only update the alias by the background synching process

Write in documentation for manually managed remote nodes. Users should subscribe to streams "alias" and "timestamp".

The balance reported by the nodes rpc-api does not match up with the balance calculated by the transaction history. In most cases the rpc reported balance is laging behind by 6 blocks.

This problem exists with all the table views currently implemented (transaction history, validators, guardians). Where we have sorting it is not retained after an update and a selected row is unselected after an update.

The community candidates table needs to be implemented.

Addresses are inconvenient. Users need a way to give their address an alias or change an existing alias.

Instead of "Last Active" use more explicit headers "Last Mined" and "Last Voted".

We currently read the votes from the blockchain, but we want to read them from the database.

see: https://github.com/coblo/gui-demo/blob/develop/app/widgets/candidates.py#L52

To be able to detect fraud/cheating we should show the number of blocks mined by a validator in the last 24 hours.