"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.

  1. 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
  1. 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
  1. 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 forward for ourselves to advance the functionality of Tendermint and Cosmos-SDK, especially for validators.
We are very confident that each of above three projects will significantly improve the validator operation quality and security, hence resulting in stronger, safer and more stable network.
Soon, we want to propose community fund grants for above spec design and actual codebase implementation including full PR process with Tendermint team. Before we propose, we want to hear community’s opinions about our move.


Reasoning of grant proposal

The reasoning why we propose grants is that B-Harvest want to become a “sustainable contributor” of Cosmos Network and we simply need to cover the human resource to continue our contribution. Our knowledge, experience, and technical skill are becoming mature weeks by weeks, so we are very confident that B-Harvest will become one of the most efficient, highest quality, most sustainable contributor of Cosmos Network.


Why community grant?

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 represent the interest of delegators.


For the price calculation of our grant proposal

Our projects are usually devoted by 2 people, each of person devoting about 30%~50% of full time. As a team, we conservatively estimate 4 week contribution as $5,000, which is less than a month salary of any of our team member(it means the price is deficit for B-Harvest!). Total proposed grant is $25,000.(about 6k atoms)

7 Likes

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

2 Likes

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 represent the interest of delegators.

We have to keep in mind that Tendermint does not have eternal responsibility on Cosmos development. The responsibility should be gradually passed to the actively participating community members(validators are the one best aligned with incentives and healthy relation). Supporting B-Harvest to participate in Cosmos development is kind of preparing and nurturing such power of community.

2 Likes

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.

All opinions, suggestions welcome and appreciated!

1 Like

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

1 Like

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

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.

4 Likes

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!

4 Likes