search

mimblewimble / grin-pm

Grin project management resources and docs
Apache License 2.0
75 stars 39 forks source link

Agenda: Development, Mar 17 2020 #261

Closed lehnberg closed 4 years ago

lehnberg commented 4 years ago

Solicit suggestions for agenda items for the Development meeting to be held on Tuesday Feb 18 @ 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
    • [ ] Triaging research @lehnberg
    • [ ] Status of sample project @yeastplume
  4. Basic-Auth behavior
  5. Planning
    1. Grin v4.0.0
  6. Censorship resistance for Tor-based grin tx's when Tor is blocked
  7. How to handle upgrades after 5.0.0
  8. Testing
  9. /packaging & releasing
  10. Other questions
MCM-Mike commented 4 years ago

Please add this to your general topics: Basic-Auth behavior: As of v3.1.x if basic-auth is disabled on a Grin-Node it still accepts request with a basic-auth password. Is this behavior to be changed in the near future ?

antiochp commented 4 years ago

Looks like NSKR/NRD locks are going to require "allow duplicate outputs" to be useful in any practical way.

We should discuss "allow duplicate outputs" as this would be a change to the consensus rules in itself. It may make sense to target this for 4.0.0 as a discrete change (vs. "relative kernels").

The rule is currently "we do not allow duplicate output commitments in the UTXO set". Allowing duplicates would introduce various edge cases around precedence rules (plain vs. coinbase vs. immature coinbase). We would also need to consider an adversarial scenario with millions of duplicates etc.

Is this something we want to consider? Or do we want to continue to enforce uniqueness and work around that?

Added issue here - https://github.com/mimblewimble/grin/issues/3271