PFK Rewards
Introduce yourself
Hello, everyone! I'm Hayec.
Contribution
30.09.2020
1.http://keepstats.top/ This is a website that shows the geographical location of all nodes.
To get information on the location of all nodes, I modified the p2p and diagnostics modules of keep-core & keep-ecdsa, so that it could provide me with the information I needed. With Google Maps, I built this product.
You can find more details here: https://github.com/biluohc/KeepStats Btw, I created a PR on Github to add more peers information to diagnostics: https://github.com/keep-network/keep-core/pull/2104
2.Bug report:
I found a bug in the keep-client configuration, and pull a request for this: https://github.com/keep-network/keep-core/pull/2097
Description: This Ethereum address is not used in the code. If the user fills in an address that does not match the keyfile, the error will be difficult to understand, and mistakenly think that their address staking is incorrect. In addition, there is no such field in keep-common and keep-ecdsa. Compared with adding this field and judgment logic in the code, it should be the simplest to delete directly.
3.Run my random beacon&ECDSA nodes with address 0x454af708f9a304e0c9f6f41422b90506e6d2e192 since August. In the next month, I will add the feature to display specific node information, such as staking amount, collateral rate, node rank, etc. I hope it is helpful to the community.
07.09.2020
Hi, everyone! I'm Hayec. Nice to meet you! I have run my node since August.
1.http://keepstats.top/ This is a website that shows the geographical location of all nodes.
To get information on the location of all nodes, I modified the p2p and diagnostics modules of keep-core & keep-ecdsa, so that it could provide me with the information I needed. With Google Maps, I built this product.
You can find more details here: https://github.com/biluohc/KeepStats Btw, I created a PR on Github to add more peers information to diagnostics: https://github.com/keep-network/keep-core/pull/2104
2.Bug report:
I found a bug in the keep-client configuration, and pull a request for this: https://github.com/keep-network/keep-core/pull/2097
Description: This Ethereum address is not used in the code. If the user fills in an address that does not match the keyfile, the error will be difficult to understand, and mistakenly think that their address staking is incorrect. In addition, there is no such field in keep-common and keep-ecdsa. Compared with adding this field and judgment logic in the code, it should be the simplest to delete directly.
3.Run my random beacon&ECDSA nodes with address 0x454af708f9a304e0c9f6f41422b90506e6d2e192 since August. In the next month, I will add the feature to display specific node information, such as staking amount, collateral rate, node rank, etc. I hope it is helpful to the community.
07.09.2020
Hi, everyone! I'm Hayec. Nice to meet you! I have run my node since August.
Nodes
0x454af708f9a304e0c9f6f41422b90506e6d2e192
