Skip to content

chore(dkg): mark SIP 1 as superseded by ssv-dkg#92

Open
oleg-ssvlabs wants to merge 1 commit intomainfrom
chore/516-dkg-superseded-note
Open

chore(dkg): mark SIP 1 as superseded by ssv-dkg#92
oleg-ssvlabs wants to merge 1 commit intomainfrom
chore/516-dkg-superseded-note

Conversation

@oleg-ssvlabs
Copy link
Copy Markdown
Contributor

Closes ssvlabs/ssv-node-board#516

Summary

SIP 1 (DKG) has been open-for-discussion since 2022-06-27 and contains a long-standing // TODO - missing proof of possession for the pubkey? marker. The actual DKG implementation for SSV has lived in ssvlabs/ssv-dkg with its spec in ssvlabs/dkg-spec for some time, and the two have diverged substantially from this SIP (different transport, different signing/encryption, added Resign/Reshare operations, etc.).

The SIP lifecycle defined in SIP 0 doesn't currently include a superseded state, so the header status is left as open-for-discussion. Instead, this PR adds an in-document note pointing readers to the real implementation/spec, so nobody treats this SIP as load-bearing.

Changes

  • Add a prominent note at the top of sips/dkg.md pointing to ssvlabs/ssv-dkg and ssvlabs/dkg-spec.
  • Remove the stale // TODO - missing proof of possession for the pubkey? comment from the SignedSessionPubKey section.
  • Fix a broken Markdown link to the discussion thread ([Discussion] (...)[Discussion](...)).

Notes

  • A future PR could extend sips/sip0.md to add a superseded status and then mark DKG SIP accordingly. Intentionally out of scope here.

- Add note pointing readers to ssvlabs/ssv-dkg and ssvlabs/dkg-spec,
  where the active DKG implementation and spec live.
- Remove stale "TODO - missing proof of possession for the pubkey?"
  left in the SIP since 2022.
- Fix broken Markdown link to the discussion thread.

Closes ssvlabs/ssv-node-board#516

Co-Authored-By: Claude <noreply@anthropic.com>
Comment thread sips/dkg.md
@@ -2,7 +2,16 @@
|-------------|--------------------------------|----------|---------------------|------------|
| Alon Muroch | Generalized DKG support in SSV | Core | open-for-discussion | 2022-06-27 |
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: Header row reads open-for-discussion while the note below says the SIP is superseded. sips/qbft_sync.md:4 already uses Deprecated without any SIP 0 amendment — non-lifecycle statuses are accepted in practice.

Suggested change
| Alon Muroch | Generalized DKG support in SSV | Core | open-for-discussion | 2022-06-27 |
| Alon Muroch | Generalized DKG support in SSV | Core | Superseded | 2022-06-27 |

Comment thread sips/dkg.md
Comment on lines +7 to +14
> **Note:** This SIP is no longer actively developed. The DKG protocol for SSV
> is implemented in [`ssvlabs/ssv-dkg`](https://github.com/ssvlabs/ssv-dkg)
> with its specification maintained in
> [`ssvlabs/dkg-spec`](https://github.com/ssvlabs/dkg-spec). This document
> is kept for historical reference only; design details below do not reflect
> the current implementation. The SIP lifecycle defined in [SIP 0](./sip0.md)
> does not currently include a `superseded` state, so the header status is
> left unchanged.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note phrases ssv-dkg/dkg-spec as implementing this SIP's protocol, not as a successor with divergent design. Readers chasing the redirect to understand current DKG risk over-trusting the non-normative protocol below.

> **Note:** This SIP is no longer actively developed. DKG for SSV is now provided by
> [`ssvlabs/ssv-dkg`](https://github.com/ssvlabs/ssv-dkg) and
> [`ssvlabs/dkg-spec`](https://github.com/ssvlabs/dkg-spec), which follow a **different
> design** than the protocol described below. This document is kept for historical
> reference only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants