# DID Lifecycle The DID lifecycle defines how a decentralized identity is created, maintained, updated, and eventually revoked within the Stobox ecosystem. Because DIDs act as the source of truth for identity and compliance enforcement, understanding their lifecycle is essential for issuers, compliance administrators, and developers integrating with STV3 programmable assets. Stobox DID ensures that every action in the lifecycle is secure, auditable, and compliant. Each lifecycle stage is reflected on-chain through smart contract events, enabling full transparency and regulatory audit readiness. *** ### **Stage 1: DID Creation** A DID is created when a user or organization completes identity verification through the Stobox onboarding process.\ Once approved, the administrator or verification provider triggers on-chain DID creation. Creation involves: * assigning a unique DID identifier * initializing the DID record * setting initial attributes (e.g., identity type, jurisdiction) * linking the first wallet address * marking the DID as active On-chain event emitted: **DIDCreated** The DID is now recognized as a valid identity within the Stobox ecosystem. *** ### **Stage 2: Attribute Assignment** After creation, compliance attributes are assigned to the DID. These attributes define how the identity may interact with assets and systems. Examples of attributes: * **jurisdiction** * **accredited / retail / institutional investor type** * **KYC/KYB verification status** * **sanctions screening results** * **ownership or transfer restrictions** * **expiry date for verification** Attributes can be: * added * updated * replaced * given an expiration * deactivated On-chain event emitted: **DIDAttributeAssigned** or **AttributeUpdated** Attributes are the core of compliance logic — controlling eligibility for asset transfers, governance roles, and participation rights. *** ### **Stage 3: Wallet Linking** A DID may have multiple blockchain addresses associated with it. This enables individuals, institutions, or departments to use more than one wallet while maintaining consistent identity. Wallet linking includes: * linking a new blockchain address * validating ownership of the address * assigning the address to the DID * marking the address active On-chain event emitted: **AddressLinked** This step is essential for operational flexibility, institutional custody models, and multi-role governance systems. *** ### **Stage 4: Wallet Activation / Deactivation** Linked wallets may be activated or deactivated as needed. #### **Activation occurs when:** * a new wallet is added * an existing wallet is restored * authorization is confirmed #### **Deactivation occurs when:** * the wallet is compromised * access control changes * compliance requires a pause * the wallet is no longer in use On-chain event emitted: * **AddressActivated** * **AddressDeactivated** Deactivation does not remove the DID — it simply prevents that wallet from interacting with assets until reactivated. *** ### **Stage 5: DID Updates** Throughout its lifecycle, a DID may need updates due to: * change in compliance status * investor eligibility updates * jurisdictional reclassification * new regulations * updated KYC/KYB verification * corporate restructuring Updates may affect: * attributes * linked wallets * expiration conditions * status flags On-chain event emitted: **DIDUpdated** DID updates ensure continuous compliance across assets, markets, and jurisdictions. *** ### **Stage 6: DID Blocking** A DID can be **blocked** if: * verification expires * sanctions screening fails * compliance violations occur * suspicious activity is detected * legal requirements mandate a freeze When blocked: * the DID cannot participate in transfers * assets cannot be received or redeemed * governance rights are suspended * linked wallets are effectively frozen On-chain event emitted: **DIDBlocked** A blocked DID can be **unblocked** after remediation. *** ### **Stage 7: DID Revocation** If an identity is permanently invalidated — e.g., regulatory rejection, fraud, corporate dissolution — the DID may be **revoked**. Revocation includes: * marking the DID inactive * disabling all associated wallets * deactivating all attributes * preventing future reactivation On-chain event emitted: **DIDRevoked** Revocation is final and is used only in situations requiring permanent identity invalidation. *** ### **Stage 8: Auditability Throughout the Lifecycle** Every lifecycle action emits an on-chain event, including: * DID creation * attribute updates * address linking * status changes * deactivation or revocation This ensures: * transparent regulatory reporting * easily auditable identity history * full traceability for investigators * verifiable compliance at all times Auditability is essential for financial institutions, compliance officers, and asset issuers. *** ### **Summary** The Stobox DID lifecycle is designed to provide robust identity verification, adaptable compliance controls, and complete audit transparency. Through creation, attribute assignment, updates, wallet linking, blocking, and revocation, the DID system ensures that every participant in the ecosystem is continuously validated. This lifecycle underpins the compliance automation and secure governance that programmable assets on STV3 rely on — making DID an indispensable foundation of the Stobox tokenization framework. *** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.stobox.io/did/did-lifecycle.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.