[General] What consensus mechanism is used for zksync hyperchains?

[namn-grg]

Environment

Testnet

Provide a brief description of the functionality you're trying to implement.

What consensus mechanism is used for zksync hyperchains? and is consensus even needed in hyperchains

I read in the FAQs that zkPorter uses POS. Why is that?

I came across this question through topic "How to avoid the fragmentation of consensus stake in a multi-rollup ecosystem" in the zkfellowship. I dont even think consensus stake is even needed for L2's. L2's security is dependent on the L1 so why stake

What is the specific issue or error you're encountering?

.

Can you share the error messages or logs you're receiving, if any?

.

Have you made any recent changes to the contract before encountering this issue?

.

Are there any external libraries or contracts that your contract interacts with?

.

Can you provide the relevant portions of your contract code where the issue is occurring?

.

Have you tried to isolate the problem, and if so, what were the results?

.

What steps have you already taken to try to resolve the issue?

.

Repo Link (Optional)

No response

Additional Details

No response

[dutterbutter]

hello 👋

Currently zkSync does not have a consensus mechanism in place but we intend to decentralize the sequencers where we will make use of a faster version of HotStuff that we call HotShot. Alex briefly discusses it in his ETHCC address which can be found here, roughly at the ~8:40 mark.

[dutterbutter]

There will be multiple flavours of hyperchains as teams determine what customizations, or application specific changes, are required to meet their needs.

[namn-grg]

Got it. This definitely solved a lot of confusion.

So is HotShot/HotStuff a type of PoS? Here its mentioned that zkPorter will work on PoS. In this its also mentioned the zksync tokens will be used to stake - so will the stake needed to be done individually to all zkPorter chains?

Also another ques - Will the security of L1 determine hyperchains security? (I think the ans is - obviously yes)

Thanks!

[dutterbutter]

I don't know too much details about our implementation, but I would assume its a type of PoS given its based off of HotStuff.

Security will be inherited by L1 (Ethereum), yes.

[namn-grg]

Ok got it!

Last thing - I had a doubt regarding a topic given in zksyncfellowship. Can I post it here or should I make a new discussion?

Question: The topic "Prover and sequencer market dynamics" what does it mean? Does it mean improving the sequencer like the concept of shared sequencing etc? Can you please throw some light on the topic?

[dutterbutter]

Definitely create a new discussion with the relevant details! Thanks for posting 🚀 🙏

[samui68400]

To make things clearer, I'd like to make a comparison with systems already in place.

If I've understood correctly, hyperchains can be configured as required, with a mix of zk rollups and zk porter.

Can we talk about modularity like celestia, which offsets the availability of off-chain data?

Are hyperchains like rollapps in the dymension ecosystem? In this case Zk Stacks could be considered as cosmos SDK that makes it easy to create hyperchains?

[bxpana]

Let's go ahead and open up a new Discussion in the ZK Stack Category and we can answer there.