[PROPOSAL][ABANDONED] "Three Pillars Project" for better validator operation of Tendermint/Cosmos-SDK based blockchains

B-Harvest is working on 3 consecutive projects to strengthen the validator operation of Tendermint/Cosmos-SDK based blockchains. We want to share some progress on those projects. • Tendermint ADR 50 : Improved Trusted Peering • brief introduction : strengthening trusted, internal, persistent peers by introducing `unconditional_peer_ids` and `persistent_peers_max_dial_period` • status : spec PR accepted, implementation PR accepted • workloads : about 4 weeks • Cosmos-SDK ADR 16 : Validator Consensus Key Rotation • brief introduction : allow validators to replace their consensus key • status : spec PR in discussion, implementation on the way • workloads : about 8 weeks • Tendermint ADR 51 : Double Signing Protection with Tendermint Mode • brief introduction : prevent double signing of validators by checking recent block data to check the existence of the validator’s consensus key, and introducing “Tendermint Mode” • status : spec on the way, implementation on the way • workloads : about 8 weeks Why contribute? From validator operation experience, B-Harvest explored the most pain points of operating validators and we decided to move…

Excerpt (1193 of 2987 characters). Read the whole post on the forum ↗

Obvious question is why can’t we propose this to be like a Cosmos-dev project? Why community led, and specifically BHarvest?

I am not sure what you meant by cosmos-dev project. To give you some context, 2 of above projects have a long history in github issue. It has been requested and discussed for very long time but it was not executed because Tendermint team is very busy with many other things. You can check related discussions by checking references of each ADR. Why B-Harvest? We are one of the longest participating validator in Cosmos. We live and die with reputation. Supporting Cosmos is how we survive and promote. We have the biggest incentive to sustainably support Cosmos for very long time than any other entity. Our teamwork with Tendermint team is getting better and smoother. Both party are very happy to work together. (I believe) We can confidently ensure that we are one of the most important asset of Cosmos. Why we ask grant from community? We want full support from the community, not solely by Tendermint team or ICF. We are helping Cosmos but eventually we are a possession of delegators. Our owner is delegators, not Tendermint nor ICF. So it is the reason why we are asking community fund grant. We want to be financially independent from ICF so that we can properly, independently…

Excerpt (1194 of 1621 characters). Read the whole post on the forum ↗

We are requesting review of the governance proposal for community fund grant.
Below is our repository for the proposal and its signature from keybase identity.

b-harvest/Three-Pillars-Project

“Three Pillars Project” for better validator operation of Tendermint/Cosmos-SDK based blockchains - b-harvest/Three-Pillars-Project

All opinions, suggestions welcome and appreciated!

tks 4 your share, cố gắng lên bạn nhé

These seems like valuable additions, so I would support this!

I also think it would be healthy to see non-AIB/Tendermint developers contributing significant changes like these, that are financed from the community fund.

For Your Information, B-Harvest internally decided not to propose this grant on community fund, rather apply to ICF grant next year. Of course our work is continued nevertheless of grant confirmation.

The reason of switching plan is that we have another pipeline working on which will definitely excite the community more. And we don’t want to spam the grant governance.

Please stay tuned for the exciting grant proposal to come soon. Thank you for your support for three pillars project!