Closed mpguerra closed 2 years ago
@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:
@dconnolly do you want to take ZIP 32 and 212? And I'll take ZIPs 207 and 214?
Do we also need to explicitly create an issue for ZIP-209? Or is that work already covered in our block validation code?
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.
Removed #1864 as this is already tracked in #1856
Removed #1334 and #1820 as these are already tracked under #1853
This epic will track the ZIPs that we will need to implement ahead of NU5 testnet activation.
A strikethrough means that we:
Our mandatory Canopy checkpoint significantly reduces the number of features that we have to implement.
2681
ZIP 250: Deployment of the Heartwood Network UpgradeNU2: BlossomZIP-208: Shorter Block Target SpacingZIP-206: Deployment of the Blossom Network UpgradeNU1: SaplingZIP-243: Transaction Signature Validation for SaplingZIP-32: Shielded Hierarchical Deterministic Wallets- #267 (wallets only, sapling and orchard only)ZIP 205: Deployment of the Sapling Network UpgradeZIP-143: Transaction Signature Validation for OverwinterZIP-202: Version 3 Transaction Format for OverwinterZIP-203: Transaction Expiry