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

NU5 Tracking: Required ZIPs #1854

Closed
mpguerra opened this issue Mar 5, 2021 · 5 comments
Closed

NU5 Tracking: Required ZIPs #1854

mpguerra opened this issue Mar 5, 2021 · 5 comments
Labels
Epic Zenhub Label. Denotes a theme of work under which related issues will be grouped

Comments

@mpguerra
Copy link
Contributor

mpguerra commented Mar 5, 2021

This epic will track the ZIPs that we will need to implement ahead of NU5 testnet activation.

A strikethrough means that we:

  • have implemented that item
  • are tracking that item in another Epic, or
  • have otherwise resolved that item.

Our mandatory Canopy checkpoint significantly reduces the number of features that we have to implement.

@mpguerra mpguerra added the Epic Zenhub Label. Denotes a theme of work under which related issues will be grouped label Mar 5, 2021
@dconnolly dconnolly mentioned this issue Mar 5, 2021
53 tasks
@teor2345
Copy link
Contributor

teor2345 commented Mar 8, 2021

@mpguerra @dconnolly I've added some missing ZIPs (and one section that probably should have been a separate ZIP). I've also crossed out some ZIPs we've implemented already.

Our next task should be to split the tickets for the following ZIPs into essential validation work, and other work that's out of scope:
- ZIP 207: Funding Streams - #801 (excluding founders reward)
- ZIP 214: Consensus rules for a Zcash Development Fund - #801 (excluding founders reward)
- ZIP 212: Allow Recipient to Derive Sapling Ephemeral Secret from Note Plaintext - #785 (excluding sender)
- ZIP-32: Shielded Hierarchical Deterministic Wallets - #267 (validation only)

@dconnolly do you want to take ZIP 32 and 212? And I'll take ZIPs 207 and 214?

@mpguerra
Copy link
Contributor Author

mpguerra commented Mar 9, 2021

Do we also need to explicitly create an issue for ZIP-209? Or is that work already covered in our block validation code?

This was referenced Mar 9, 2021
@teor2345
Copy link
Contributor

teor2345 commented Mar 9, 2021

Do we also need to explicitly create an issue for ZIP-209? Or is that work already covered in our block validation code?

I think it's best that we have a separate ticket, because it needs some cached state data structure changes.

@mpguerra
Copy link
Contributor Author

Removed #1864 as this is already tracked in #1856

@mpguerra
Copy link
Contributor Author

mpguerra commented Mar 23, 2021

Removed #1334 and #1820 as these are already tracked under #1853

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic Zenhub Label. Denotes a theme of work under which related issues will be grouped
Projects
None yet
Development

No branches or pull requests

3 participants