Closed 3xtr4t3rr3str14l closed 3 years ago
jgm: Is there something up with SyncCommittee and the latest Altair spec release? It appears that both Lodestar and Prysm changed their SyncCommittee spec tests to point to SyncAggregate for some reason (e.g. https://github.com/ChainSafe/lodestar/pull/2728/commits/10517d421fc6ab2cb258251d55743994da075e48 for Lodestar). My SyncCommittee implementation fails on the spec tests, specifically on calculating the hash tree root. Given SyncCommittee is a simple list of 512 public keys followed by a public key I'm struggling to understand why. (btw @chainsafe it would be awesome if https://simpleserialize.com/ were updated with altair types)
jgm: Is there something up with SyncCommittee and the latest Altair spec release? It appears that both Lodestar and Prysm changed their SyncCommittee spec tests to point to SyncAggregate for some reason (e.g. https://github.com/ChainSafe/lodestar/pull/2728/commits/10517d421fc6ab2cb258251d55743994da075e48 for Lodestar).
My SyncCommittee implementation fails on the spec tests, specifically on calculating the hash tree root. Given SyncCommittee is a simple list of 512 public keys followed by a public key I'm struggling to understand why.
(btw @chainsafe it would be awesome if https://simpleserialize.com/ were updated with altair types)
from: https://discord.com/channels/595666850260713488/598292067260825641/859569001209135144
from: https://discord.com/channels/595666850260713488/598292067260825641/859569001209135144