NaCl Format
NaCl Format is Bittensor terminology for an encryption format used around legacy wallet files (Glossary: NaCl Format).
The term belongs to wallet-file security vocabulary. It describes a protection format around stored wallet material, not a subnet role, tokenomics concept, consensus mechanism, or network-status label.
Format Scope
NaCl Format names a file-format protection layer. Bittensor wallet documentation provides the broader wallet setting, while the NaCl glossary term narrows the subject to legacy wallet-file encryption (Bittensor wallet documentation, Glossary: NaCl Format).
That scope is narrower than wallet behavior. A wallet file can have a protection format without the format saying what balance, subnet role, or staking state is associated with the wallet.
Legacy Wallet Layer
Legacy context matters because wallet vocabulary can mix several layers: the key material, the local file, the account context, and the protection format around stored material. NaCl Format belongs to the file-protection layer (Bittensor wallet documentation, NaCl Format glossary entry).
This makes the term useful for compatibility reading. It explains how a legacy wallet file is protected at rest, while other wallet and key terms explain how the material is used or referenced.
Stored Material Boundary
NaCl Format should be read as stored-material vocabulary. It concerns the protection format around a wallet file, not every security property of the environment where that file exists (Glossary: NaCl Format, Bittensor wallet documentation).
That boundary prevents overstatement. A protected legacy file format can limit what the file itself reveals, but it does not replace private-key custody, workstation security, or source-specific wallet guidance.
Seed Phrase Boundary
NaCl Format and seed-phrase handling describe different wallet-safety layers. NaCl Format concerns the protection format around stored legacy wallet files, while seed-phrase guidance concerns the recovery words that can regenerate wallet key material (Glossary: NaCl Format, Handle your Seed Phrase/Mnemonic Securely).
That distinction keeps file-format language from sounding like a backup plan. A protected wallet file and a protected seed phrase both belong to wallet security, but they answer different recovery and storage questions.
Key Vocabulary Context
NaCl Format sits near public-key and private-key terminology because wallet files protect key material. Public keys are shareable reference material, while private keys are authorization material that must remain protected (Glossary: Public Key, Glossary: Private Key).
The NaCl term does not rename either key type. It identifies the legacy protection format around stored wallet material, while public-key and private-key vocabulary identify what the material is used for.
Local File Context
NaCl Format is most naturally read next to local wallet-file vocabulary. A local wallet describes wallet files kept on a user’s machine, while NaCl Format describes a legacy encryption-format label around protected wallet-file material (Glossary: Local Wallet, Bittensor wallet documentation).
For article use, the local-file context should stay attached. A NaCl-format statement is about the stored file format, not about a remote account database, subnet-role record, wallet balance, or runtime authorization event.
That also keeps NaCl Format separate from wallet-location vocabulary. Wallet location identifies where local wallet files are stored, while NaCl Format identifies the legacy protection format around stored material (Glossary: Wallet Location, Glossary: NaCl Format).
Key-Regeneration Boundary
NaCl Format and regenerating a key both sit near wallet recovery, but they answer different questions. NaCl Format names the legacy encryption format around stored wallet material, while regenerating a key names recreating a lost or deleted coldkey or hotkey from the associated mnemonic (Glossary: NaCl Format, Glossary: Regenerating a Key).
For readers, the format protects local wallet material at rest; the recovery operation depends on separate recovery words and current key-handling guidance. A NaCl-format file should therefore not be treated as the same thing as a mnemonic, a regenerated key, or proof that recovery material has been preserved.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For NaCl Format, that sequence mainly matters when legacy wallet-file examples are drawn from different network environments during development or testing.
In localnet, NaCl Format examples can be exercised with local wallet files in an isolated environment. Local file-protection behavior does not represent production wallet custody on live networks.
On testnet, legacy wallet files used in shared testing can demonstrate format compatibility under non-production conditions while staying separate from mainnet wallet state (Bittensor wallet documentation).
On mainnet, NaCl Format vocabulary still describes legacy wallet-file protection on the production network context where those files are used (Glossary: NaCl Format).
The Bittensor Networks reference separates mainnet, testnet, and localnet. A wallet-file example from one environment should not be read as representing production file custody in another environment.
Relationship to Yuma Consensus
NaCl Format and Yuma Consensus describe related parts of Bittensor’s incentive system. Yuma Consensus is the on-chain process that aggregates validator weight signals within a subnet into miner incentives and validator dividends, applying consensus clipping, bonding, and emission calculation (Yuma Consensus).
For readers, nacl format names a specific part of that incentive picture, while Yuma Consensus names the consensus process that turns validator weights into the resulting incentives and dividends.
Reader Boundary
NaCl Format should be used narrowly in Taopedia prose. It can support statements about legacy wallet-file protection and wallet-security terminology, but it should not be used to infer staking status, subnet participation, balance state, validator status, or wallet-tool behavior (NaCl Format glossary entry, Bittensor wallet documentation).
The stable article-level point is that NaCl Format is format vocabulary. It does not name a recovery process, wallet procedure, subnet action, address, public key, private key, or balance state.
Legacy Files Use NaCl-Style Encryption at Rest
The Glossary: NaCl Format describes NaCl Format as encryption used around legacy Bittensor wallet files. The term therefore belongs to local file-protection vocabulary rather than to on-chain roles or subnet participation labels (Bittensor wallet documentation).
Readers should keep NaCl Format on the stored-file side of wallet security. It names how some legacy wallet material is protected at rest, not what that material can do after unlock.
Format Protection Does Not Authorize Transactions
Working with Keys documentation covers how keys are used once available, while NaCl Format names only the legacy wrapper around stored wallet files. A protected file format can limit casual disclosure of file contents; it does not replace private-key handling or transaction review (Glossary: Private Key).
Authorization still follows whichever key material signs an action after the wallet is unlocked.
Mnemonic Recovery Stays a Separate Security Surface
NaCl Format concerns legacy wallet-file encryption, while Handle Seed Phrase guidance covers mnemonic recovery material. The two belong to wallet security but answer different questions: file format at rest versus regeneration after loss (Glossary: Mnemonic).
Readers should not treat a NaCl-format label as interchangeable with seed-phrase backup vocabulary.