Incognito initiatives in Q3

[Devenus]

I have a question about slashing v2. Sometimes we (pnode and vnode owners) encounter same problem - if there is not enough time for shard data sync or beacon sync after chain data wipe, we’ll get zero votes count. Check bellow:

What should we do then? Pnode owner will be slashed?

[abduraman]

Hey @Devenus,

Doesn’t this answer your question?

@duc

In staking flow v3, we introduce a new phase for staking flow called Sync pool. A node will get into the pool and wait in there until finishing sync prior to entering a pending committee queue, this will help mitigate for the node from slashing by missing votes because its data is not up to date.

[duc]

Hi @Devenus, Staking flow v3’s sync pool will be a perfect solution for not enough sync time problem but it’s in a longer term.

The problem happened sometimes due to unbalanced nodes number among shards, I mean when a node was assigned to a shard with a short pending list, it unlikely has enough time for data sync so that it couldn’t vote/contribute to the network. That’s why we postponed enabling Slashing for a while and fixed unbalancing issue first. (You can find the fix here)

I believe the number of nodes in shards will be balanced out by the end of the month, so nodes will always have enough time for data sync (assuming total nodes is still remain as now)

[Devenus]

Thanks @duc, @abduraman. But as I understood, slashing v2 will be enabled in the early September, and staking flow v3 - late October. There is a chance for someone to be slashed during this period.

[duc]

Like I said, as long as the numbers of nodes among shards are balanced, your node will have enough time for data sync.

[duc]

Hi guys, we just created a topic for introducing Slashing V2 here and updated the link to the post above as well. Thanks @adrian and @Devenus for pointing out potential issues the network may have with Slashing. I believe we now have a better plan for Slashing’s release.

[duc]

Hello guys, we just created a topic for introducing Staking Flow V3 here and updated the link to the post above as well.

[abduraman]

For 2021 Q4 or 2022 Q1, you may examine LayerZero (https://www.binance.com/en/blog/421499824684902766/ecosystem/binance-labs-and-multicoin-capital-coled-$6m-series-a-for-layerzero) to get rid of the costs of building/maintaining bridges to the other chains. FYI.

[Jared]

Tagging @0xkraken here as she may find this interesting.

[duc]

In order to get the Q3 roadmap up-to-date, I just marked 3 initiatives delivered as shipped and updated the ship dates of pDEX v3 and Mempool v2 according to the current development progress. It seems like we can still hit all goals of Q3 as planned. cc @drusin

[abduraman]

@duc

Mempool v2 (end of Oct)

A new mempool that will help increase throughput for transactions, is one of the most important building blocks for Incognito to reduce block time. Apart from this, the team will also work on performance improvements for bottlenecks in connection, storage as well as data verification. These will be input data for the team to be able to make decisions on block time reduction in the next quarter.

Hey @duc,

Could you explain this issue further? For example, what are the bottlenecks? How will you increase the throughput? Currently does the mempool reject them if a lot of txs come? etc.

Thanks.

[Patrick_Yu]

I just want to know if pnode is not longer used anymore? I just recently popped up and found I need to stake 1750 PRV to the node. It’s fine for me to stake but if the pnode is still running ?

[SPAddict25]

Nodes that aren’t functioning properly get slashed with any staked PRV returned. There’s ways to fix your pnode to ensure it’s healthy, restake and begin to earn again.

https://we.incognito.org/t/slashing-is-live/13893

https://we.incognito.org/t/official-pnode-troubleshooting-guide/13718

[Patrick_Yu]

So right now I must stake 1850 PRV myself to run the node?

[Jared]

The short answer is, no you do not need the funds. Please read over the following guide:

Node Unstaking/Slashed? Read Me! (re-stake guide)

Node slashed? This guide will hopefully answer all of your questions and then some. The following are the most commonly asked questions via PM, email, and support inquiries. Q: My node was slashed. What does this mean? A: Refer to this post: Introducing Slashing V2 Q: My node was always online and in the app but is now slashed? A: Previously, Incognito did not require nodes to be online to generate rewards. Going forward nodes will be required to be both online and healthy. …

[Patrick_Yu]

Thanks. Eventually I stake 1750 PRV into the node.

Mind if I ask the node is healthy? I use the monitor nodes to check my node and said
Role: Syncing Shard 6
status: Online
Sync State: Beacon Stall

Are these status normal and working?

[Jared]

@Patrick_Yu

Sync State: Beacon Stall

This means it is not working correctly. If you require further assistance please message @Support.

[abduraman]

@duc

@duc

Mempool v2 (end of Oct)

A new mempool that will help increase throughput for transactions, is one of the most important building blocks for Incognito to reduce block time. Apart from this, the team will also work on performance improvements for bottlenecks in connection, storage as well as data verification. These will be input data for the team to be able to make decisions on block time reduction in the next quarter.

Hey @duc,

Could you explain this issue further? For example, what are the bottlenecks? How will you increase the throughput? Currently does the mempool reject them if a lot of txs come? etc.

Thanks.

Hey @duc,

Maybe missed. I’ll be glad if you answer them when you are available.

Thanks.