Skip to content

[mkdocs] docs: add namespace concept#844

Merged
segfaultxavi merged 3 commits intoNemProject:new-docsfrom
zero4862:docs-namespace-concept
May 8, 2026
Merged

[mkdocs] docs: add namespace concept#844
segfaultxavi merged 3 commits intoNemProject:new-docsfrom
zero4862:docs-namespace-concept

Conversation

@zero4862
Copy link
Copy Markdown

@zero4862 zero4862 commented Apr 29, 2026

Adapts Namespace concept to NEM technology.

Differences with Symbol:

  • Role: Every mosaic lives under a namespace in NEM; optional alias for an account or mosaic in Symbol.
  • Mosaic lifecycle coupling: NEM mosaics become inactive when their parent namespace expires; Symbol mosaics persist independently and only the alias breaks.
  • Root name length: 16 chars on NEM vs 64 chars on Symbol. Subnamespace levels are 64 in both.
  • Duration: Fixed 525600 blocks (~1 year) on NEM vs 30 days to 5 years on Symbol.
  • Renewal window: Restricted to the last 43200 blocks before expiration on NEM; any time during the lease on Symbol.
  • Lease fee: Fixed on NEM vs duration-proportional XYM on Symbol.
  • Subnamespace cap: NEM has no explicit cap beyond the 3-level depth limit; Symbol caps at 256 subnamespaces per root.
  • Metadata: NEM does not not support metadata.

Comment thread mkdocs/pages/en/textbook/namespaces.md
Comment thread mkdocs/pages/en/textbook/namespaces.md Outdated
Comment thread mkdocs/pages/en/textbook/namespaces.md
Comment thread mkdocs/pages/en/textbook/namespaces.md
Comment thread mkdocs/pages/en/textbook/namespaces.md
@zero4862 zero4862 force-pushed the docs-namespace-concept branch from 4b2e104 to c33a002 Compare April 29, 2026 15:28
@zero4862 zero4862 marked this pull request as ready for review April 29, 2026 15:36
@segfaultxavi segfaultxavi self-requested a review April 30, 2026 10:04
Copy link
Copy Markdown
Contributor

@segfaultxavi segfaultxavi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor changes only.

Comment thread mkdocs/pages/en/textbook/namespaces.md Outdated
Comment thread mkdocs/pages/en/textbook/namespaces.md Outdated
Comment thread mkdocs/pages/en/textbook/namespaces.md
Comment thread mkdocs/pages/en/textbook/namespaces.md Outdated

`nem`, `user`, `account`, `org`, `com`, `biz`, `net`, `edu`, `mil`, `gov`, `info`.

The `nem` namespace, in particular, is used by the system to host the native currency `nem:xem`.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a colon to separate namespaces here, but previously you said it was periods. Which one is it?

Copy link
Copy Markdown
Author

@zero4862 zero4862 Apr 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NEM namespaces are not used to name mosaics (like in Symbol), but to organize them. Mosaics have their own name. In nem:xem, nem is the namespace name and xem is the mosaic name, separated by a colon.

Subnamespaces are separated by a dot. Example: company.tokens:gold, where company is the namespace, tokens the subnamespace and gold the mosaic name.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it. I had not idea.
Then definitely you cannot use this example here without explaining what the colon means.
I understand you will probably explain it in the Mosaics page, but you need to provide at least a minimal explanation here and a link to where the colon is fully explained.

Something like:

Suggested change
The `nem` namespace, in particular, is used by the system to host the native currency `nem:xem`.
The `nem` namespace, in particular, is used by the system to host the native currency `nem:xem`
(note that the colon separates the namespace from the [currency name](./mosaics.md#fully-qualified-name)).

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

Comment thread mkdocs/pages/en/textbook/namespaces.md
Comment thread mkdocs/pages/en/textbook/namespaces.md
Comment thread mkdocs/pages/en/textbook/namespaces.md Outdated
@zero4862 zero4862 force-pushed the docs-namespace-concept branch from 12f78fe to 765f950 Compare April 30, 2026 11:40
@zero4862 zero4862 requested a review from segfaultxavi April 30, 2026 11:41
Comment thread mkdocs/pages/en/textbook/namespaces.md Outdated

`nem`, `user`, `account`, `org`, `com`, `biz`, `net`, `edu`, `mil`, `gov`, `info`.

The `nem` namespace, in particular, is used by the system to host the native currency `nem:xem`.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it. I had not idea.
Then definitely you cannot use this example here without explaining what the colon means.
I understand you will probably explain it in the Mosaics page, but you need to provide at least a minimal explanation here and a link to where the colon is fully explained.

Something like:

Suggested change
The `nem` namespace, in particular, is used by the system to host the native currency `nem:xem`.
The `nem` namespace, in particular, is used by the system to host the native currency `nem:xem`
(note that the colon separates the namespace from the [currency name](./mosaics.md#fully-qualified-name)).

@zero4862 zero4862 requested a review from segfaultxavi April 30, 2026 16:28
Copy link
Copy Markdown
Contributor

@segfaultxavi segfaultxavi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@segfaultxavi segfaultxavi merged commit 806215c into NemProject:new-docs May 8, 2026
18 checks passed
segfaultxavi pushed a commit to zero4862/nem that referenced this pull request May 8, 2026
* [mkdocs] docs: add namespace concept
* [mkdocs] docs: apply comments
* [mkdocs] docs: apply comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants