PFK Rewards
Round 6
@Hayec#2555
15000
15k KEEP
Introduce yourself
Hi, everyone! I'm Hayec.
Nodes
0x49a3b24bc71fc022a617f5dcbacbf46613e6cf2e
0x454af708f9a304e0c9f6f41422b90506e6d2e192
0x454af708f9a304e0c9f6f41422b90506e6d2e192
Contribution
30.10.2020
1.http://keepstats.top/ This is a website that shows the geographical location of all nodes, included total KEEP staked & total ETH staked, and the historical changes in the two amounts are shown on a curve. 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 You can click on "More" to see the details of nodes. I counted the online data of all the nodes. You can also see it here: https://keepstats.top/list
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 0x49a3b24bc71fc022a617f5dcbacbf46613e6cf2e and 0x454af708f9a304e0c9f6f41422b90506e6d2e192. I hope it is helpful to the community.
30.09.2020
September's PFK contributions:
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
Nice to meet you! I have run my node since August with address: 0x454af708f9a304e0c9f6f41422b90506e6d2e192.
1.http://keepstats.top/ This is a website that shows the geographical location of all nodes, included total KEEP staked & total ETH staked, and the historical changes in the two amounts are shown on a curve. 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 You can click on "More" to see the details of nodes. I counted the online data of all the nodes. You can also see it here: https://keepstats.top/list
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 0x49a3b24bc71fc022a617f5dcbacbf46613e6cf2e and 0x454af708f9a304e0c9f6f41422b90506e6d2e192. I hope it is helpful to the community.
30.09.2020
September's PFK contributions:
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
Nice to meet you! I have run my node since August with address: 0x454af708f9a304e0c9f6f41422b90506e6d2e192.
