Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Agenda: Development, Jul 21 2020 #316

Closed
1 task
lehnberg opened this issue Jul 9, 2020 · 5 comments · Fixed by #323
Closed
1 task

Agenda: Development, Jul 21 2020 #316

lehnberg opened this issue Jul 9, 2020 · 5 comments · Fixed by #323
Labels
development Anything related to development meetings Anything related to meetings

Comments

@lehnberg
Copy link
Collaborator

lehnberg commented Jul 9, 2020

Solicit suggestions for agenda items for the Development meeting to be held on Tuesday Jul 21 @ 15:00 UTC in grincoin#dev channel on Keybase. Please comment to provide topics or suggestions.

Proposed agenda

  1. A yeasty reminiscence
  2. Agenda review
  3. Action point follow ups from previous meetings
  4. Mitigating re-org risks
  5. v5.0.0 planning: High level discussion of various Consensus changes
    • Soft fork proponent arguments published?
    • one-sided transactions (1TX)
    • duplicate outputs (DO)
    • NRD activation (NRD)
    • expiring kernels (EK)
    • coinbase outputs as transaction outputs (CO)
    • bulletproofs+ (BP+)
  6. Other questions
@lehnberg lehnberg added meetings Anything related to meetings development Anything related to development labels Jul 9, 2020
@johndavies24
Copy link

There may not be time in every meeting, but I think that all the relevant consensus changes should be thoroughly discussed prior to the last hard fork. Seems like order of complexity to implement should be prioritized.

One-sided (non-interactive) transactions needs to be discussed more and I don't feel that the lack of an RFC or other "complete" and fully vetted write-up is necessary because much of the dissenting opinion is ideological rather than due to specific implementation details. If the importance of this feature is agreed upon, the details can be finalized.

@lehnberg
Copy link
Collaborator Author

@johndavies24 added as discussion point.

Also adding a point to discuss re-org risk mitigations.

@antiochp
Copy link
Member

antiochp commented Jul 20, 2020

On the subject of consensus changes, my understanding is these are ones currently in varying levels of active discussion -

  • one-sided transactions (1TX)
  • duplicate outputs (DO)
  • NRD activation (NRD)
  • expiring kernels (EK)
  • coinbase outputs as transaction outputs (CO)
  • bulletproofs+ (BP+)

I took the liberty of giving them all catchy acronyms where we did not yet have one. 😄

Please add to the list if I missed any.

@lehnberg Maybe we want to rework the agenda a little to cover the high level discussion first and then drill into these individually?

@phyro
Copy link
Member

phyro commented Jul 20, 2020

There seems to be quite a lot to talk about. Perhaps it would make sense to extend the meeting if needed to at least start the conversation about all these options and see where we stand on these since it's the last HF and it's better to gather opinions sooner rather than later.

@lehnberg
Copy link
Collaborator Author

@antiochp @phyro @johndavies24 and others - updated agenda now, moved 1TX and CO into 5.0.0, and also removed "replay attacks" as a discussion point b/c we're talking a lot about it all over the place in any case and as EK which now is under 5.0.0 will touch on this as well.

Let me know if you have any more suggestions for tweaks to agenda. Perhaps we should time cap each discussion item (5-10 min?) and agree to do dedicated follow up meetings as required or something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development Anything related to development meetings Anything related to meetings
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants