A little space.
Precisely defined.
Prepare a version-zero namespace from a short name. See how the text fits into 29 bytes, then copy the encoded result into your development workflow.
- Choose a name
- Inspect its bytes
- Take the hex
Namespace preparation
Client-side · v0 · 29 bytes1–10 UTF-8 bytes. Unicode may use several bytes per character. Spaces are preserved.
One label. Three layers.
The first byte selects version zero. Eighteen fixed zero bytes follow. The final ten bytes contain your UTF-8 text, padded with zeros on the left.
The output is 58 hexadecimal characters, without a 0x prefix. Input is neither trimmed nor normalized.
Encoded namespace · hexadecimal
Inside the namespace
Filled silver cells hold UTF-8 data. Dashed cells are left padding. Positions are zero-indexed.
Encoding is a starting point.
A generated namespace is not a reservation or proof of ownership. Different inputs can produce the same padded bytes; names that look alike can also encode differently.
Before using it in a project
Validate the namespace against your target network's rules and SDK. This instrument constructs bytes; it does not check reserved ranges, publish blobs or establish exclusive use.
Checking availability
This instrument builds the bytes, it doesn't query the chain. Search the generated hex in a Celestia explorer for your target network to see if it's already in use.