Row 5989

Row ID: 5989 | Dataset Entry | Axioma AXP Content Repository

Content Data

This page contains data entry 5989 from the Axioma AXP content repository. The structured data below represents the complete record for this entry.

Hello folks, i have a quick question for all. Assuming we have the 4 shards(instead of 64) in ethereum and validators do their work validate transactions and assuming shard 3 has some problems and does not produce valid blocks, thus enter on change view protocol and stay behind from others. How can we guarantee that when the beacon chain changes the formation of all shards. Will shard 3 synchronize with the others? is there any existence of any global clock that says for example formation will be changed every one hour and all shards need to sync despite misconfiguration, or the beacon chain wait for shard 3 to catch up with other shards

FieldValue
text Hello folks, i have a quick question for all. Assuming we have the 4 shards(instead of 64) in ethereum and validators do their work validate transactions and assuming shard 3 has some problems and does not produce valid blocks, thus enter on change view protocol and stay behind from others. How can we guarantee that when the beacon chain changes the formation of all shards. Will shard 3 synchronize with the others? is there any existence of any global clock that says for example formation will b…
label r/ethereum
dataType post
communityName r/ethereum
datetime 2024-05-06
username_encoded Z0FBQUFBQm5LakwyNlJUNzBKRDVvajZnVUprQWFWOVA1cENkQ3lGc2NuSXd3V29hU205d04yVEFDUGdLdkczWHpremRtYXlzOC1TZkdYNFo3dmhUSXJJUF9jcWdZWU44aXc9PQ==
url_encoded Z0FBQUFBQm5Lak9HNVNwTVNQSzZuajRlM1ZkM1hWN0N3al9BanNhdjg4LVdzS05WRFZmOHZfem5nRDlaMlk5RDVYRWtfdE1iOUdjbmEtd1JmTUpwcGwtM1kzVURoRHRyYy1xX0VFM3NmVE1yc1lJZmI1cjJJQ0V1N3NweHBXVWNaWnV4TWU5UVNqU1Fya1VoUWZTdFR1YjFuNkROVFkyOVVwdlhlY2llNTBOOXpXeWFxdEtxN1dTWUVrWTMwMHUtV0ViRzJxeDEteWlyLXNYREExMmJaRGNSVDVJM2lrWTVVQT09

Raw Record

{
  "text": "Hello folks, i have a quick question for all. Assuming we have the 4 shards(instead of 64) in ethereum and validators do their work validate transactions and assuming shard 3 has some problems and does not produce valid blocks, thus enter on change view protocol and stay behind from others. How can we guarantee that when the beacon chain changes the formation of all shards. Will shard 3 synchronize with the others? is there any existence of any global clock that says for example formation will be changed every one hour and all shards need to sync despite misconfiguration, or the beacon chain wait for shard 3 to catch up with other shards",
  "label": "r/ethereum",
  "dataType": "post",
  "communityName": "r/ethereum",
  "datetime": "2024-05-06",
  "username_encoded": "Z0FBQUFBQm5LakwyNlJUNzBKRDVvajZnVUprQWFWOVA1cENkQ3lGc2NuSXd3V29hU205d04yVEFDUGdLdkczWHpremRtYXlzOC1TZkdYNFo3dmhUSXJJUF9jcWdZWU44aXc9PQ==",
  "url_encoded": "Z0FBQUFBQm5Lak9HNVNwTVNQSzZuajRlM1ZkM1hWN0N3al9BanNhdjg4LVdzS05WRFZmOHZfem5nRDlaMlk5RDVYRWtfdE1iOUdjbmEtd1JmTUpwcGwtM1kzVURoRHRyYy1xX0VFM3NmVE1yc1lJZmI1cjJJQ0V1N3NweHBXVWNaWnV4TWU5UVNqU1Fya1VoUWZTdFR1YjFuNkROVFkyOVVwdlhlY2llNTBOOXpXeWFxdEtxN1dTWUVrWTMwMHUtV0ViRzJxeDEteWlyLXNYREExMmJaRGNSVDVJM2lrWTVVQT09"
}
Explore Dataset Explore Row

Entry Information