Wallet & Address Management

Stobox DID supports a multi-wallet identity architecture, allowing a single verified identity (DID) to control one or many blockchain addresses. This capability is essential in real-world financial environments where users may operate:

  • multiple personal wallets

  • institutional or custodial wallets

  • role-based operational wallets

  • cold and hot storage addresses

  • separate governance, treasury, and trading accounts

Wallet & Address Management ensures that regulatory compliance and identity integrity are upheld, regardless of which address a user interacts with.


Why Multi-Wallet Identity Matters

In traditional finance, a person or organization may operate several accounts under one legal identity. Tokenized finance must offer the same flexibility — without compromising compliance.

Multi-wallet identity enables:

Operational Flexibility

Users can:

  • separate investment wallets from governance wallets

  • use new wallets without redoing KYC/KYB

  • rotate wallets for security reasons

  • operate multiple wallets across departments or subsidiaries

Institutional Compliance

Organizations often require:

  • restricted-role wallets (e.g., “treasury,” “operations,” “custody”)

  • department-level permissions

  • multi-operator control

  • risk segmentation

Security and Risk Management

If one wallet is compromised, it can be deactivated without affecting the DID or other linked wallets.

Regulatory Consistency

Each wallet inherits the DID’s identity attributes, ensuring:

  • uniform compliance

  • deterministic validation

  • transparent tracking

Wallets cannot operate outside the identity and compliance framework.


Linking a Wallet Address to a DID

A verified identity can link multiple addresses to itself. This process includes:

  1. Address declaration

  2. Ownership verification (e.g., signature-based confirmation)

  3. Linking the address to the DID record

  4. Activation of the wallet

Once linked, the wallet becomes a valid representation of the DID and may interact with STV3 assets according to the DID’s attributes.

On-chain event emitted:

  • AddressLinked


Activating and Deactivating Wallets

Wallets may be activated or deactivated at any point.

When wallets are activated:

  • a new wallet is added

  • a previously deactivated wallet is restored

  • identity checks or permissions are updated

When wallets are deactivated:

  • wallet is lost or compromised

  • regulatory compliance requires temporary suspension

  • internal policy changes

  • corporate restructuring

  • fraud suspicion or sanctions trigger

Deactivation prevents the wallet from performing any protocol-level actions, but the DID remains active.

Events emitted:

  • AddressActivated

  • AddressDeactivated


Removing a Linked Address

A DID can unlink a wallet entirely. Removal is used when:

  • a wallet is permanently abandoned

  • organizational roles change

  • custody providers rotate keys

  • a wallet must be isolated permanently

Unlinked addresses lose all permissions and can no longer interact with STV3 assets.

Event emitted:

  • AddressRemoved


Address-Based Permissioning

Although attributes belong to the DID, wallet-specific states may also control behavior:

  • an active wallet inherits all identity permissions

  • a deactivated wallet cannot execute any actions

  • different addresses may be used for different authorized roles (e.g., governance vs. transactions)

This allows complex enterprise scenarios, including:

  • role-separated operational accounts

  • department-level asset management

  • multi-signature workflows

  • treasury segmentation


Effects of DID Status on All Wallets

Because wallets derive their permissions from the DID, DID-level changes affect all linked wallets:

DID Status Change
Effect on Linked Wallets

Blocking

All wallets become unable to transfer, redeem, or receive assets

Attribute Revocation

Wallets lose eligibility for certain actions

KYC/KYB Expiration

Wallets are suspended until renewed

Jurisdiction Update

Wallets may gain or lose permissions

DID Revocation

All linked wallets become permanently disabled

This ensures consistent compliance enforcement across all wallet addresses.


Wallet Usage Scenarios

Individual Users

  • multiple personal wallets

  • hot wallet for operations, cold wallet for storage

  • separate governance wallet

Enterprises & Institutions

  • separate wallets for departments (finance, operations, treasury)

  • multisig or role-locked wallets for governance

  • custodian-controlled wallets for investor accounts

Custody Providers

  • assign wallets per client or per asset

  • rotate keys without breaking identity links

  • activate/deactivate wallets based on custody events

Marketplaces & Platforms

  • internal wallets for automated settlement

  • role-based service wallets for liquidity and treasury operations


Wallet Security Considerations

Stobox DID enhances wallet security by providing:

  • DID-level emergency blocking

  • wallet-level deactivation

  • ability to remove compromised addresses

  • attribute-based restrictions that limit wallet permissions

If a wallet is compromised:

  1. The administrator deactivates or removes the address.

  2. The DID continues functioning with other linked wallets.

  3. The compromised wallet cannot access or move assets.

This approach reduces risk while maintaining identity continuity.


Summary

Wallet & Address Management allows Stobox DID to represent real-world identities accurately and flexibly within a decentralized environment. By supporting multi-wallet architectures, activation/deactivation controls, and DID-level permissions, Stobox ensures that identities remain secure, compliant, and operationally adaptable.

This system mirrors how individuals and organizations manage multiple financial accounts — but with deterministic on-chain enforcement, cryptographic security, and institutional-grade governance.


Last updated

Was this helpful?