Chainflow Validator Updates

Transparent validator operation is one of the Chainflow's core values. This page tracks updates to the Chainflow validators.

Ready to delegate to the Chainflow validators? Learn how here.

Not ready to delegate yet? Learn more about the Chainflow validators here.

Updates 👇

21 June 2019

The Chainflow Terra validator and sentries have been upgraded to v0.2.2. See details here.

19 June 2019

I added an additional encrypted and masked backup process to the Chainflow Cosmos Validator. The same process was added to the Chainflow Iris and Terra validators. All validators are now backed-up to two geographically separate secure locations.

(Ready to delegate to the Chainflow validators? Learn how here.)

30 May 2019

I upgraded the Chainflow Cosmos Validator and all sentry nodes to v0.34.6 to address this vulnerability.

17 May 2019

Earlier this week I noticed an increase in missed blocks. This dropped the Chainflow Cosmos Validator availability from 99.99% to 99.98%. I did some investigation and believe identified the root cause. To address it, I co-located a new private sentry node with the validator and connected it into the infrastructure.

I did this without missing any blocks 😊My multi-tier, redundant setup helped make this possible. As of today, this fix seems to have addressed the issue. The Chainflow Cosmos Validator should be back on the path to 99.99% availability.

(Ready to delegate to the Chainflow Cosmos Validator? Use this link to do that.)

14 May 2019

The Chainflow Cosmos Validator voted "Yes" for Proposal #6, "Don't Burn Deposits for Rejected Governance Proposals Unless Vetoed" 👍I also made a small deposit to help activate the proposal.

22 April 2019

The Chainflow Cosmos Validator joined cosmoshub-02 at block 0. I generated the genesis file I used, rather than using the file posted by the Cosmos team.I actually vetoed proposal 3, as the upgrade felt haphazard and sloppy. In the end, it came together well and happened without a hitch!

I'm still somewhat uncomfortable with the precedent that was set by process. My hope is it becomes more conscious over time.

8 April 2019

Voted "No" on proposal #2.

4 April 2019

All Chainflow sentries and the validator have been upgraded to v0.32.2, to address a security vulnerability in v0.32.1 discovered by the Tendermint team.

The Chainflow upgrade happened fewer than 24 hours since it was first reported. Only a single block was missed in the process.

Ready to delegate to the Chainflow Cosmos Validator? Use this link to do that.

23 March 2019

I started noticing a slight dip in pre-commits. In response, I upgraded the Chainflow Cosmos Validator sentry architecture.

I added another private peering connection to a well-known and trusted validator partner later that week. These upgrades resulted in a performance improvement and reduced missed pre-commits.

Stay tuned...!

21 March 2019

The Chainflow Cosmos Validator received a 175,249 ATOM delegation from the Interchain Foundation. This established the Chainflow Cosmos Validator as a trusted Interchain Foundation validator.

I participated in this discussion organized by ChorusOne. It focused on decentralization in the Cosmos context.

16 March 2019

The Chainflow Cosmos Validator received its first major third party delegation of 100,000 ATOMS.

Ready to delegate to the Chainflow Cosmos Validator? Use this link to do that.

15 March 2019

I increased my self-bonded ATOMS to 1000, keeping 500 ATOMS in reserve.

13 March 2019

The Chainflow Cosmos Validator launched in the cosmoshub-1 genesis file. It marked the culmination of almost 18 months of preparation work.

I joined the Cosmos Validator Working Group when it formed in October of 2017. I've been validating on Cosmos since then.

I was awarded 1500 ATOMS for completing the Game of Stakes. I launched with 500 ATOMS, taking a conservative approach, due to concerns about network readiness and what felt to me like a rushed launch.

Ready to delegate to the Chainflow Cosmos Validator? Use this link to do that.

Show Comments