waxwing on Nostr: Pretty sure I agree that FROST is closer to the mark in what @fiatjaf is looking for, ...
Pretty sure I agree that FROST is closer to the mark in what @fiatjaf is looking for, but specifically the signing algorithm and not the keygen algorithm. FROST (and Pedersen DKG before it) were advancing the state of the art by allowing for no central party (or aggregator/dealer) to be in possession of the whole private key at any time, either in key generation, or in signing. Here I guess you want to reset back to the earlier SSS basic idea of having the central party know the key in advance, then construct the individual shares such that they sum to the pre-existing key x, instead of following FROST's KeyGen to generate the shares.
But the "massive caveats" I mentioned in the other post still apply; it seems unlikely you'd want to allow the possibility to collude to take your full key.
Published at
2024-10-02 04:24:39Event JSON
{
"id": "45e710db1c7045255ff6bbd89279d5cd192a3db0a4f421353c8240ae1dd65b1d",
"pubkey": "675b84fe75e216ab947c7438ee519ca7775376ddf05dadfba6278bd012e1d728",
"created_at": 1727843079,
"kind": 1,
"tags": [
[
"e",
"00000e6f8eba9304440dd5ba881931f0bd723b5cfbacaf46645f130c4584fbb7",
"",
"root"
],
[
"e",
"000090cfa4283ad843a4d81a8c5b5754fddd7dadc9d40a854ff61ae9b043c11f"
],
[
"e",
"8df666c2d5e90cd5b872796b05f9c0afb9d5330f7732f1cffa595c78004d1d87",
"",
"reply"
],
[
"p",
"675b84fe75e216ab947c7438ee519ca7775376ddf05dadfba6278bd012e1d728"
],
[
"p",
"46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"p",
"7b3f7803750746f455413a221f80965eecb69ef308f2ead1da89cc2c8912e968"
]
],
"content": "Pretty sure I agree that FROST is closer to the mark in what @fiatjaf is looking for, but specifically the signing algorithm and not the keygen algorithm. FROST (and Pedersen DKG before it) were advancing the state of the art by allowing for no central party (or aggregator/dealer) to be in possession of the whole private key at any time, either in key generation, or in signing. Here I guess you want to reset back to the earlier SSS basic idea of having the central party know the key in advance, then construct the individual shares such that they sum to the pre-existing key x, instead of following FROST's KeyGen to generate the shares.\n\nBut the \"massive caveats\" I mentioned in the other post still apply; it seems unlikely you'd want to allow the possibility to collude to take your full key.",
"sig": "c0418f4f23a992597d21d2273af60f155d77899b621026736d849998e8544eb3d8f0e218adad03e9ce9945cd093ab0ac8451d8868646d510548905e620cfcd38"
}
