Event JSON
{
"id": "4d23dbcd325fc69e3efab0df737c594a44e1b856cdfb4a463ac6b788973e36e2",
"pubkey": "df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200",
"created_at": 1742072446,
"kind": 1,
"tags": [
[
"e",
"6dc0481bf7cf27a33703ed83232701e7ce281bc0cbdc877a0a8a99ab15ffa5d2",
"",
"root"
],
[
"e",
"01567b50097c33577c1a61fa3795a96389f79fe48cab57cb0d92501fbc0c6272",
"",
"reply"
],
[
"p",
"b90c3cb71d66343e01104d5c9adf7db05d36653b17601ff9b2eebaa81be67823"
],
[
"p",
"df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200"
],
[
"client",
"Nostur",
"31990:9be0be0fc079548233231614e4e1efc9f28b0db398011efeecf05fe570e5dd33:1685868693432"
]
],
"content": "Alright … now I’m just getting familiar with frost … but it looks to me like the bifrost implementation generates a unique (group_pk) pubkey for each “group” of “shares”… and it isn’t straight forward how the “main” pubkey would be obtained by a client “signer”, signing with one of the “shares”. What do you know about this?\nhttps://github.com/FROSTR-ORG/bifrost/blob/master/src/types/group.ts#L24",
"sig": "86aa13304488139a48d6fc2edce29f5427339272ffb4a03423b845affbf44e83ee4f9872d4afb5d3a29bdc17d92665d9c0affe91a9531d5f4fcfadfa0da289b5"
}
