Incognito chain’s code upgrade (tag: 20220408_1)

Hi Incognito validators,

We’ve just released a protocol code update for:

  • Reducing max 48 committee size threshold to 85%.
  • Improving EVM-based bridges verification.

The protocol changes are expected to be effective once 85% of validators (committee + pending nodes) update the new code. The latest code is published in 2 forms:

If you run pNodes or set up your vNodes by following our instructions , they should pull the latest docker image automatically. In case you encounter any issues with the code update, feel free to contact @support for assistance.

Thank you!

10 Likes

Nice, can you share what we’re at right now?

You may grasp some insight from https://monitor.incognito.org/red-list since it shows all nodes although its name is red-list :slight_smile:

1 Like

@duc

How close are we to the 85% threshold? The inactive list shows a lottttttttttt of nodes that are running the older code.

Now the red-list only tells us if the nodes are on the latest version, and we have 1416 nodes there. So we’re at least at 67% now. But it might be higher since the protocol change was in a version prior to the latest.

(yes, I scraped the website… :stuck_out_tongue_closed_eyes:)

Here’s the detailed version break-down

nodes version
1416 5586525bc (mainnet_20220408_1)
178 31a67a365 (april 4th commit)
486 d2967331a (mainnet_20220322_1)
2 92913dc96 (mainnet_20220228_1)
1 a9a16a913 (mainnet_20220214_1)
4 1fca4f9e0 (mainnet_20220117_1)
3 f6aebde67 (mainnet_20211228_1)
8 c0473ee4f (mainnet_20211119_1)
4 f733677fa (mainnet_20211026_1)
7 1abf36899 (mainnet_20211005_1)
1 167bbe3e7 (mainnet_20210824_1)
1 7e51a827e (mainnet_20210815_2)
1 02fc08471 (mainnet_20210810_1)
16 unknown
5 Likes

Thanks @duc for this update.

I’m so grateful to the Incognito Dev Team for making Node upgrades a breeze.

My vNodes auto-magically updated to the latest version. I’m not a techy person, but I certainly do appreciate the magical code that makes these upgrades happen behind the scenes. THANK YOU so much!

2 Likes

Lololololololol love the dedication. You’re an enthusiast for a reason :joy:

I dug a bit further and realized the version numbers were GitHub commits. So I updated the table above with the tags. It paints quite a different picture from what I thought. It looks like the vast majority is very much up to date.

Given that the committee size was changed on version d2967331a (mainnet_20220322_1) I get 1416+178+486 = 2080 nodes running the updated version. Out of the 2128 found on the redlist, that makes it around 97%. Which is just a single 1% shy of the original 98% requirement.

So why hasn’t the maxcommitteesize48 feature been enabled by the beacon nodes? I have no idea. @duc?

2 Likes

@SPAddict25, @fredlee, @Linnovations, @abduraman
The protocol change was effective, the max committee size is 48 now (that means the fixed node dominance is being reduced to 46%).
We’re monitoring the network, thanks for your support!

5 Likes

PRV NODES GO BRRRRRRRRRRRR

:prv:

5 Likes

:rofl:

2 Likes