Neo v3.6.0 Checklist

[superboyiii]

Now we're making the checklist of neo v3.6.0 for release preparation. Release date still need discussion due to how many PRs are included.

Mandatory issues

• Storage fails on a specific contract on Testnet t5 #2890
• Check notifications for manifest compliance #1879
• Add zkp in neo #2647
• dBFT: Recovery message triggers PrepareRequest from Primary even if the timer isn't fired yet neo-modules#799
• Missing getContractById and getContractHashes native Management APIs neo-devpack-dotnet#784
• StrictMode during contract deploy/update will break the T5 after 3.6 release #2873

Mandatory PRs

• Check ABI for notifications #2810
• .NET 7 #2836
• Native: store ID->hash mapping for native contracts too #2833
• fix NeoSystem shutdown order #2842
• update net7 neo-devpack-dotnet#774
• update copyright neo-devpack-dotnet#773
• sort modifiers neo-devpack-dotnet#775
• Support .NET Standard 2.1(Take two) neo-vm#499
• update to net7.0 neo-vm#503
• update copyright neo-vm#502
• update to net7.0 neo-node#888
• update copyright neo-node#889
• add an icon for the application neo-node#890
• update to net7.0 neo-modules#783
• update copyright neo-modules#784
• storage dumper neo-modules#790
• Add zkp - Groth16 #2691
• Payloads: implement Conflicts attribute #2818
• Optimize vote reward data #2841
• SmartContract: add FindOptions.Backwards to iterate in reverse order #2819
• Add zkp neo-devpack-dotnet#726
• Use strictMode during deploy #2849
• Add Oracle limit neo-modules#800
• dbft: don't rush to send PrepareRequest when recovery neo-modules#801
• fix trusts conflicts #2892

@neo-project/core @neo-project/developers @neo-project/ngd-seattle

[roman-khimov]

#2812 and #2818, please. #2841 after some additional tests as well. #2819 is also there, pretty easy thing that solves some real problem.

[roman-khimov]

And also an additional question about #2691, are we really planning it for 3.6? I have no objections, nice thing to have, but I'm trying to estimate when we should start playing with it in NeoGo as it'll definitely take some time.

[superboyiii]

#2812 and #2818, please. #2841 after some additional tests as well. #2819 is also there, pretty easy thing that solves some real problem.

Added

[superboyiii]

And also an additional question about #2691, are we really planning it for 3.6? I have no objections, nice thing to have, but I'm trying to estimate when we should start playing with it in NeoGo as it'll definitely take some time.

Yeah, we wish adding it to v3.6.0, how long do you think it need for NeoGo to apply it?

[roman-khimov]

#2848, please.

[AnnaShaleva]

Could you also check the neo-project/Neo.Cryptography.BLS12_381#4, please? This issue is ZKP-related.

[Jim8y]

Could you also check the neo-project/Neo.Cryptography.BLS12_381#4, please? This issue is ZKP-related.

neo-project/Neo.Cryptography.BLS12_381#4 (comment)

[AnnaShaleva]

We should probably consider fixing neo-project/neo-modules#799 before the release.

[AnnaShaleva]

And neo-project/neo-modules#800 is likely to be mandatory for the release.

[AnnaShaleva]

We should probably fix the neo-project/neo-devpack-dotnet#784 also.

[AnnaShaleva]

Could we also include #2873 in the list? Just not to forget it.

[superboyiii]

Could we also include #2873 in the list? Just not to forget it.

Done.

[superboyiii]

@neo-project/core @neo-project/developers @neo-project/ngd-seattle We will close adding more PR/issue into this checklist. These later ones will be included into next checklist. We wait too long for v3.6.0, wish it being release in 2 weeks.

[AnnaShaleva]

I know that this check-list is closed, but we probably have to consider fixing #2879 before the 3.6 release, otherwise it may badly affect the mainnet in future.

[roman-khimov]

#2890 please, not something we want to have for any network.

[roman-khimov]

Time to close this one and open 3.7 list (there is one, we know it).