The comments around from_seed_slice specify that this is a dangerous method only to be used for testing, however the upper of Pair uses it without that information passed on and the client is using the same functionality to generate the tests keys for Alice, Bob, etc.

We should clarify the documentation to clearly stated under which circumstances this features is to be expected to be us

In order to get lossless presentation, and reduce the package size. (With PNG, normally multiple file is needed for different screen resolutions).

We would better to change the logos in SVG format.

Some of SVG logos could be find here: https://github.com/polkadot-js/apps/tree/master/packages/apps-config/src/ui/logos/nodes

Link for downloading Kusama SVG: https://kusama.network/assets/kusa

The contract! macro is part of the API provided to the contract developer. It should therefore be documented. Currently, there is no easy way to know that there is a env parameter to this macro that allows specifying an own EnvTypes impl.

When users get their balances, encrypted balance and pending_transfer are printed out by default. It seems messy, so add cli flags to print out these value.
https://github.com/LayerXcom/zero-chain/blob/1fc625f714442dba590d0dac95e78bf4b2a49392/zface/src/main.rs#L275-L277

ChainX桌面钱包在投票选举页面会展示各个节点logo。
在此收集各节点logo，不定期更新(每周一次)到桌面钱包到展示中，若节点不提供则会展示默认logo。
请需要展示logo的节点在本issue回复。

回复格式如下
节点名：
logo：上传大小为 80*80, 格式为 PNG 的 logo 图片, 也可以选择直接给出 logo 的 URL 地址。

ChainX desktop wallet will display a logo of each node in the staking page in the future version. The default logo will be used instead if some node doesn't provide one.

Please comment as follows:

node name

Need to comb through the app especially in governance and add helpful little question marks that give context or instructions or both to the user, as well as links to the appropriate parts of the wiki(s) where they can learn more.

Potentially also interesting is to have a floating Help tooltip that shows relevant instructions depending on the user's current location. Kind of like Paper clip guy

Motivation

According to airalab/robonomics#46 is better to dedicate node identity and store it into a file for long term usage.

Steps

• Add into identity module function to save/load peer private key from file.
• Move peer identity into Gossipsub::new() function parameter.

We should have a way to enforce uniqunesss of a property value across all entities that have this property in a given class. Implementatino similar to optionality seems like the right approach.

We have some structs that should be added to GSRPC (search TODO + GSRPC). We should also add the constants lookup function inside Connection.