Pure Proxies
Pure proxies are a Bittensor account-indirection concept. The official Understanding Pure Proxies documentation describes them as keyless accounts whose main use is multisignature wallet structures with swappable members. In plain terms, a pure proxy is useful when the account address should stay stable even if the person or key arrangement behind it changes.
This makes pure proxies a specialized wallet-structure tool rather than a general replacement for ordinary proxy wallets.
Reference: Understanding Pure Proxies
Why They Exist
Pure proxies solve a continuity problem. Multisig wallets are often used when several signers share responsibility for an important wallet. The official multisig wallet guide describes that model as a way to require approval from more than one signatory before an action is carried out.
A direct multisig arrangement is tied to its set of members. If membership changes, the shared wallet structure may need to change too. Pure proxies give teams a way to keep stable stand-in member accounts while changing who controls those stand-ins.
References: Understanding Pure Proxies, Secure a Coldkey with a Multisig Wallet
Not a Regular Proxy Wallet
Pure proxies are related to proxy wallets, but they solve a different problem. The official Proxies overview explains ordinary proxy wallets as a security pattern where one account acts for another account with limited authority. That pattern is useful when a valuable wallet should stay in a more protected environment.
Pure proxies are not mainly about letting a less sensitive account perform routine work for a more sensitive wallet. Their main value is stable account identity. They are best understood as durable stand-ins inside a larger wallet design, especially a multisig design.
References: Proxies overview, Understanding Pure Proxies
Multisig Continuity
The official pure-proxy documentation highlights a multisig example: if a team member leaves and a new member joins, the team may want the shared multisig address to remain the same. Pure proxies can serve as the stable members of that multisig. The visible member accounts stay in place while the human or organizational control behind one member can change.
For readers, the practical idea is continuity. A pure proxy helps separate the long-lived account structure from the people currently responsible for parts of that structure.
Reference: Understanding Pure Proxies
Security Boundaries
Keyless does not mean risk-free. A pure proxy still belongs in a carefully managed wallet design, and the accounts that control it still matter. If the surrounding control structure is careless, the pure proxy’s stable address does not eliminate operational risk.
Pure proxies should therefore be read as a specialized account-architecture concept. They are useful for stable membership patterns, but ordinary proxy wallets remain the simpler concept for day-to-day delegated wallet protection.
Rotating Members Without Changing the Multisig Address
Multisig wallets require a fixed set of signatories to approve actions, which creates a continuity problem when team membership changes. If one member leaves and another joins, a naive multisig may need a new shared address because the visible member keys changed. Pure proxies address that by serving as stable stand-in accounts inside the multisig structure.
The official Understanding Pure Proxies documentation describes this pattern for teams that want the multisig address to remain the same while control behind one member slot changes. The visible pure-proxy member stays in the multisig list; what changes is who controls the underlying account that acts as that member. For readers, pure proxy separates the long-lived wallet structure from the current people operating parts of it.
That continuity can matter for counterparties, treasury records, and subnet or validator operations that already reference one shared multisig address. Pure proxies reduce the need to re-register or reconfigure every external dependency each time one human signer rotates off the team.
References: Understanding Pure Proxies, Secure a Coldkey with a Multisig Wallet
Control Rotation Versus Keyless Safety
Keyless does not mean no one controls the pure proxy. The documentation still assumes that accounts controlling the pure proxy matter and that the broader multisig threshold protects the shared wallet. A pure proxy helps with address continuity when membership rotates; it does not remove the need for genuine signatory separation or careful approval discipline among the remaining signers.
Pure proxies are also not a substitute for ordinary proxy wallets. Regular proxies delegate limited authority from a protected wallet to a less sensitive account for day-to-day operations. Pure proxies solve identity stability inside multisig designs. Choosing between them depends on whether the problem is routine delegated access or stable shared-wallet membership.
References: Understanding Pure Proxies, Proxies overview
When Pure Proxies Fit Best
The documentation highlights multisig continuity as the primary use case: organizations, subnet teams, or validator groups that expect member changes but want external-facing wallet structure to remain stable. The trade-off is added architectural complexity. A simple two-of-three multisig without pure proxies may be easier to operate; a pure-proxy multisig may be worth the setup when membership turnover would otherwise force frequent address changes and counterpart reconfiguration.
Readers evaluating wallet design should match the tool to the failure mode: pure proxies for stable multisig slots, ordinary proxies for limiting how often a safe wallet is used directly, and multisig thresholds for ensuring no single signer can act alone. The official multisig guide still applies to the approval model itself — pure proxies change how member slots stay stable, not how many signatures are required before an action can proceed.
Reference: Understanding Pure Proxies
Reader Boundary
Pure proxies should not be read as ordinary proxy wallets, coldkey replacements, or accounts with their own spendable private keys. They name keyless stand-in accounts used mainly to keep multisig membership stable when signers rotate (Understanding Pure Proxies).
Keyless Means No Direct Signing Key, Not No Control
Pure-proxy documentation describes accounts without a private key that users hold directly. Control still flows through the accounts that manage the pure proxy inside the broader multisig approval model (Understanding Pure Proxies, Secure a Coldkey with a Multisig Wallet).
For readers, keyless describes the absence of a user-held signing key on the stand-in account itself. It does not remove threshold approval or signatory responsibility in the surrounding multisig design.
Pure Proxies Keep Multisig Addresses Stable
The pure-proxy guide highlights multisig continuity as the primary use case: member turnover can change who controls a stand-in slot without forcing the shared wallet address to change (Understanding Pure Proxies).
That separates pure proxies from ordinary proxy wallets. Ordinary proxies delegate limited authority for day-to-day operations, while pure proxies solve stable identity inside shared-control structures.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For pure proxies, that sequence changes how readers should interpret examples of keyless account setup and multisig wallet structures.
In localnet, pure proxy setup can be tested in an isolated environment. Localnet pure proxy accounts and multisig configurations reflect local chain settings and do not represent production wallet structure.
On testnet, pure proxy behavior can be observed in a shared, non-production network. Testnet pure proxy accounts are separate from mainnet wallet state.
On mainnet, pure proxies are live keyless Subtensor accounts that serve as stable stand-ins in production multisig designs. The Understanding Pure Proxies documentation describes the pure proxy mechanics that apply on the production network.
The Bittensor Networks reference separates mainnet, testnet, and localnet. A pure proxy example from one environment should not be read as representing account configuration or wallet structure in another environment.
Further Reading
- Understanding Pure Proxies
- Proxies overview
- Secure a Coldkey with a Multisig Wallet
- Introduction to Bittensor: Subnet development
- Bittensor Networks
Relationship to Proxy Wallets
Pure proxies and proxy wallets are related but different parts of Bittensor wallet architecture. Proxy wallets use delegated authority patterns where one account acts for another account with limited permissions, providing a security layer by keeping sensitive keys offline while allowing routine operations. Pure proxies are keyless stand-in accounts used primarily in multisig structures to maintain address stability when membership changes. The Proxies overview describes ordinary proxy wallets as the delegation pattern for limiting authority, while Understanding Pure Proxies describes pure proxies as keyless accounts whose main use is multisig continuity.
For readers, proxy wallets solve the problem of delegating limited authority to a less sensitive account for day-to-day operations, while pure proxies solve the problem of stable multisig membership when the people behind shared control need to change.
References: Proxies overview, Understanding Pure Proxies
Relationship to Multisig
Pure proxies and multisig are related but different parts of Bittensor wallet-security vocabulary. Multisig is the wallet pattern that requires approval from multiple signatories before an action proceeds, providing protection against single-key compromise. Pure proxies are keyless accounts used as stable stand-in members within multisig structures, allowing the shared wallet address to remain unchanged even when one signer rotates off the team and another joins. The Secure a Coldkey with a Multisig Wallet documentation describes the multisig approval threshold model, while Understanding Pure Proxies describes how pure proxies serve as stable member slots inside that multisig so membership turnover does not force address changes.
For readers, multisig names the signature-threshold security pattern, while pure proxies name the stable-identity layer that can be added inside a multisig to separate long-lived account structure from current human membership.
References: Secure a Coldkey with a Multisig Wallet, Understanding Pure Proxies