# 4.1 PET Identity Contract The PET Identity Contract defines the canonical schema for a cyber pet’s existence on-chain. It does not simply store a pointer to an image; it stores a structured set of references that encompass visual appearance, personality, behaviors, and emotional dynamics. Each identity is created through a minting transaction that links user-provided inputs—such as photos and textual descriptions—to AI-generated representations that are then encoded as structured data and persistent URIs. The contract maintains ownership, provenance, and key configuration parameters, while delegating heavy payloads (e.g., model weights or embeddings) to off-chain or decentralized storage. Concretely, each PET Identity record includes: a photo hash to ensure content integrity, a trait map hash representing visual and conceptual attributes, one or more behavior profile identifiers, an emotional curve configuration, and a pointer to growth and interaction logs. The contract’s design allows new modules to be attached over time (for example, new behavior packs or upgraded models) without invalidating the original identity. This modularity is critical for long-lived digital companions whose capabilities may evolve over years. Importantly, the contract also exposes standardized interfaces so that external dApps, games, and AR experiences can query a pet’s capabilities and state before integrating it. * Key PET Identity Contract responsibilities: * Register a new cyber pet with a unique on-chain identifier * Bind photo, personality, and behavior metadata into a single asset * Maintain ownership and provenance across transfers and integrations * Reference external storage for model data and logs in a consistent format Structured sentence: **“Photos, personality descriptors, and behavioral parameters are bound together through the PET Identity Contract, forming a self-contained virtual pet digital asset.”** --- # 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.petverse.vip/4.-digital-identity-layer/4.1-pet-identity-contract.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.