A simple example of why we need this: Seqeucner A is a centralized sequencer. Light nodes get the validator set and the signed header over the current hash. They will compare if the hash matches the validator set. But they will not know if the validator set is correct. Someone new Sequencer X can set himself in the validator set and then compute the hash. The Light Node will not be able to verify this.
One way to verify this is for it to include a trust-minimized query to the validator set.
We do not have this functionality for now, so Sequencer A has to set the next Vlidatorset. If he wants to set X maliciously as the next validator set, then Sequencer A is malicious and can be fraud proven. This does not work without this schema because X can be malicious without people being able to slash him because he did not stake in the first place.
A simple example of why we need this: Seqeucner A is a centralized sequencer. Light nodes get the validator set and the signed header over the current hash. They will compare if the hash matches the validator set. But they will not know if the validator set is correct. Someone new Sequencer X can set himself in the validator set and then compute the hash. The Light Node will not be able to verify this.
One way to verify this is for it to include a trust-minimized query to the validator set.
We do not have this functionality for now, so Sequencer A has to set the next Vlidatorset. If he wants to set X maliciously as the next validator set, then Sequencer A is malicious and can be fraud proven. This does not work without this schema because X can be malicious without people being able to slash him because he did not stake in the first place.