-
Notifications
You must be signed in to change notification settings - Fork 43
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
NMT mainnet readiness #173
Comments
## Overview Closes #153 (part of #173) ## Checklist - [x] New and updated code has appropriate documentation - [x] New and updated code has new and/or updated testing - [x] Required CI checks are passing - [x] Visual proof for any user facing features like CLI or documentation updates - [x] Linked issues closed with keywords
A few of the issues previously outlined in this epic have been deemed non-critical. Therefore, they've been removed from the main description. However, they are now captured within this comment for future reference. DocsLong term
Additional features
Implementation robustness
|
Omitting the following two issues from the description of this epic, and with that, we can close the current epic:
New features [Good for Mainnet, not necessary though]Note that while removing these issues from this epic, we may later follow them up in another fresh epic with a new set of features more targeted for the mainnet. |
This meta-issue is created with the objective of determining the priority of the NMT issues concerning the mainnet. It is important to note the current list provides a snapshot of the issues and is subject to change as further issues are detected.
In progress
Error handling [Mainnet]
Code correctness [Mainnet]
IgnoreMaxNamespace
semantic #159Code cleanup
Docs
chore: add a link to the nmt specification inside the nmt implementation #98
What are the benefits ofIgnoreMaxNamespace
? #117The VerifyInclusion() function does not check proof completeness #161
The text was updated successfully, but these errors were encountered: