From 2ddc62915200cf99e0cc5eef3b04e8198777ee7e Mon Sep 17 00:00:00 2001 From: Nicolas Frisby Date: Wed, 11 Jun 2025 07:51:50 -0700 Subject: [PATCH 1/4] DONOTMERGE WIP --- WIP-enrollment-CIP.md | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 WIP-enrollment-CIP.md diff --git a/WIP-enrollment-CIP.md b/WIP-enrollment-CIP.md new file mode 100644 index 0000000000..2af9ef960b --- /dev/null +++ b/WIP-enrollment-CIP.md @@ -0,0 +1,9 @@ +In my current estimation, compared to the Plutus- and Ledger-enrolling CIPs above, any CIP enrolling Consensus would be trivial. +We've simply had many less contributors and many fewer design iterations, each of which has been a massive investment. +My relevant suggestions are essentially just a few sentences. + +> The authors of any CIP that explicitly affects the Cardano consensus protocol will need to communicate early and often with some combination of the IOG Researchers and the available experts on the existing implementation. +> We suggest beginning by scheduling a discussion on the agenda of a session of INTERSECT's Consensus Technical Working Group. +> The discussion there will likely involve scheduling additional discussions with the aforementioned Researchers and experts (eg the IOE Consensus Team holds weekly office hours for this sort of communication). +> +> As the Cardano consensus protocol undergoes additional evolutions over the coming years, hopefully this CIP can be expanded to include some lessons learned that will help CIP authors usefully describe consensus changes even before entering discussions with the contemporary experts. From 98da9e588a8a8587025ea195d01c4890ada1e893 Mon Sep 17 00:00:00 2001 From: Nicolas Frisby Date: Wed, 11 Jun 2025 08:23:05 -0700 Subject: [PATCH 2/4] edits for Thomas's comments --- WIP-enrollment-CIP.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/WIP-enrollment-CIP.md b/WIP-enrollment-CIP.md index 2af9ef960b..9707577136 100644 --- a/WIP-enrollment-CIP.md +++ b/WIP-enrollment-CIP.md @@ -2,8 +2,16 @@ In my current estimation, compared to the Plutus- and Ledger-enrolling CIPs abov We've simply had many less contributors and many fewer design iterations, each of which has been a massive investment. My relevant suggestions are essentially just a few sentences. -> The authors of any CIP that explicitly affects the Cardano consensus protocol will need to communicate early and often with some combination of the IOG Researchers and the available experts on the existing implementation. +> The authors of any CIP that explicitly affects the Cardano consensus protocol will need to communicate early and often with some combination of the IOG Researchers and the available experts on the various existing implementations. > We suggest beginning by scheduling a discussion on the agenda of a session of INTERSECT's Consensus Technical Working Group. -> The discussion there will likely involve scheduling additional discussions with the aforementioned Researchers and experts (eg the IOE Consensus Team holds weekly office hours for this sort of communication). +> The discussion there will likely involve scheduling additional discussions with the aforementioned Researchers and experts (eg the IOE Consensus Team holds weekly office hours for this sort of communication, TODO does Amaru too?). > > As the Cardano consensus protocol undergoes additional evolutions over the coming years, hopefully this CIP can be expanded to include some lessons learned that will help CIP authors usefully describe consensus changes even before entering discussions with the contemporary experts. +> +> In our experience, the cognitive load of all the requirements on the consensus protocol is enormous. +> Many newcomers would bounce off of that intimidating list and a even diligent newcomer with a relatively small change would probably find most of that list to be irrelevant. +> An "open door" policy among the Cardano consensus experts, on the other hand, seems much more plausible to increase the likelihood of promising consensus CIPs being developed. +> The experts welcome newcomers' to sketch their idea and will happily offer the initial guidance of a specific subset of relevant concerns to consider. +> +> The only apparent risk to this plan is if there's an overwhelming influx of dead-end ideas. +> That doesn't seem likely at the moment, and we would adapt the scheme if it happens. From d49ab38f51f5e79d376a433647dbf64bc4d613f3 Mon Sep 17 00:00:00 2001 From: Nicolas Frisby Date: Wed, 11 Jun 2025 08:25:07 -0700 Subject: [PATCH 3/4] Arnaud clarified the Amaru office hours TODO --- WIP-enrollment-CIP.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/WIP-enrollment-CIP.md b/WIP-enrollment-CIP.md index 9707577136..e490d0633e 100644 --- a/WIP-enrollment-CIP.md +++ b/WIP-enrollment-CIP.md @@ -4,7 +4,7 @@ My relevant suggestions are essentially just a few sentences. > The authors of any CIP that explicitly affects the Cardano consensus protocol will need to communicate early and often with some combination of the IOG Researchers and the available experts on the various existing implementations. > We suggest beginning by scheduling a discussion on the agenda of a session of INTERSECT's Consensus Technical Working Group. -> The discussion there will likely involve scheduling additional discussions with the aforementioned Researchers and experts (eg the IOE Consensus Team holds weekly office hours for this sort of communication, TODO does Amaru too?). +> The discussion there will likely involve scheduling additional discussions with the aforementioned Researchers and experts (eg the IOE Consensus Team holds weekly office hours for this sort of communication; Amaru does not hold Office Hours yet, but is planning to). > > As the Cardano consensus protocol undergoes additional evolutions over the coming years, hopefully this CIP can be expanded to include some lessons learned that will help CIP authors usefully describe consensus changes even before entering discussions with the contemporary experts. > From 79ae878a3f6c4964020dd7b12fbf2afebfced277 Mon Sep 17 00:00:00 2001 From: Nicolas Frisby Date: Wed, 11 Jun 2025 08:29:24 -0700 Subject: [PATCH 4/4] typo --- WIP-enrollment-CIP.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/WIP-enrollment-CIP.md b/WIP-enrollment-CIP.md index e490d0633e..374a5162b4 100644 --- a/WIP-enrollment-CIP.md +++ b/WIP-enrollment-CIP.md @@ -11,7 +11,7 @@ My relevant suggestions are essentially just a few sentences. > In our experience, the cognitive load of all the requirements on the consensus protocol is enormous. > Many newcomers would bounce off of that intimidating list and a even diligent newcomer with a relatively small change would probably find most of that list to be irrelevant. > An "open door" policy among the Cardano consensus experts, on the other hand, seems much more plausible to increase the likelihood of promising consensus CIPs being developed. -> The experts welcome newcomers' to sketch their idea and will happily offer the initial guidance of a specific subset of relevant concerns to consider. +> The experts welcome newcomers to sketch their idea and will happily offer the initial guidance of a specific subset of relevant concerns to consider. > > The only apparent risk to this plan is if there's an overwhelming influx of dead-end ideas. > That doesn't seem likely at the moment, and we would adapt the scheme if it happens.