You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the universe ID group key returned in the new root of the sync diff event sometimes differs from the group key I use when upserting the pre-commit output (which is taken from the issuance leaf proof). The only difference is the prefix, for example:
039bd899fe00ce28741cc81473920f918356af0656a9759f6067a84f26d4951e21
029bd899fe00ce28741cc81473920f918356af0656a9759f6067a84f26d4951e21
I do not understand why the leaves and the universe ID would have different group keys (y component differs). It is flaky, not always the case. I assume I should just use schnorr.SerializePubKey, which strips the prefix with [1:], but I do not see why that should be necessary.
I guess we should only ever store 32 byte schnorr.SerializePubKey in the db? I think that's what we do for the universe and multiverse SQL tables. But then for the new supply commit tables we store the 33 byte compressed, which doesn't seem stable to me anymore.
The y component of a secp256k1 public key can be either -y or y for the same private key. An "odd" y is messing things up somewhere.
0 commit comments