You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the outcome of #118, we can consider incorporating the description of partial absence proof into the NMT specifications. This issue primarily aims to reach a consensus on this decision. If it is determined that including the partial absence proof description is valuable, it should be added to the specifications accordingly.
The text was updated successfully, but these errors were encountered:
staheri14
changed the title
chore: incorporating the description of partial absence proof in the NMT specs
doc: incorporating the description of partial absence proof in the NMT specs
Jun 23, 2023
## Overview
Closes#205
Additionally, in line with
[this](#206), to ensure
consistency with how **namespace ID** and **namespace** (i.e., a
combination of namespace ID and version) are utilized in the core-app, I
have replaced all instances of words that refer to or imply **namespace
ID** with the more accurate term "**namespace**".
## 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
Based on the outcome of #118, we can consider incorporating the description of partial absence proof into the NMT specifications. This issue primarily aims to reach a consensus on this decision. If it is determined that including the partial absence proof description is valuable, it should be added to the specifications accordingly.
The text was updated successfully, but these errors were encountered: