> The Beacon Chain lets us randomly assign validators to different shards
This is interesting. Cross-shard attacks were a major flaw in shard designs. How is this solved exactly and who is "us" in this sentence? How can the network force a miner/validator to use a specific random shard?
There's a random number generator in the root chain (i.e. the beacon chain) and validators are assigned shortly before validation and may require validation of any random shard. The validator can validate blocks in a "stateless" manner, meaning that they don't have to validate the entire shard but can still validate a single block (which is necessary, because if validators needed data for all shards it would destroy the scaling benefits)
Is that a link to fairy tales from Vitalik?
The fact that "stateless client" is written in Ethereum 2.0 roadmap is an evidence that this project has no future.
This is interesting. Cross-shard attacks were a major flaw in shard designs. How is this solved exactly and who is "us" in this sentence? How can the network force a miner/validator to use a specific random shard?