> For the complete documentation index, see [llms.txt](https://vitality-project.gitbook.io/vitality-token-project/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitality-project.gitbook.io/vitality-token-project/official-contracts-and-addresses.md). # Official Contracts & Addresses This page exists to provide a clear, transparent, and authoritative reference point for all official Vitality ecosystem contracts, treasury wallets, and supporting on-chain infrastructure. Only the contract addresses, wallet addresses, and links published on this page should be treated as official. Users, partners, and community members should always verify addresses here before interacting with any token, treasury contract, application module, liquidity pool, or ecosystem-related smart contract. ### Purpose of This Page As the Vitality ecosystem expands, multiple contracts, wallets, treasury modules, and application-layer integrations may exist across the network. This page is designed to remove confusion by clearly identifying which addresses are official, what each address is used for, and how each contract fits into the broader ecosystem. This page should be updated whenever a new official contract is deployed, an operational wallet is added, or a core infrastructure address becomes relevant to the public ecosystem. ### Verification First Before interacting with any Vitality-related address, always confirm: * the contract or wallet is listed on this page * the network is correct * the purpose of the address is clearly stated * the address matches any official Vitality announcements * any available block explorer verification links match exactly If an address is not published here, it should not be assumed to be official. ### Core Token Contract This section should list the official VTY token contract. Include: * contract name * ticker * network * contract address * token standard * block explorer link * verification status * whether the contract is immutable or controlled by any setup permissions Suggested format: **VTY Token Contract**\ Network: PulseChain\ Purpose: Core ecosystem utility token\ Address: 0x3c650A6C6fd6CE29225364529425C188025Db625\ Explorer: [Pulse Scan](https://scan.mypinata.cloud/ipfs/bafybeienxyoyrhn5tswclvd3gdjy5mtkkwmu37aqtml6onbf7xnb3o22pe/#/address/0x3c650A6C6fd6CE29225364529425C188025Db625)\ Status: Immutable Official Contracts\ ├── Network\ ├── Official Build Batch 1 Contracts\ ├── VTYToken\ ├── BurnSink\ ├── ProtocolRegistry\ ├── Custody Summary\ ├── Verification Status\ ├── Verification Guidance For Users\ └── Safety / No-Expectation Notice VTYToken:\ 0x3c650A6C6fd6CE29225364529425C188025Db625 BurnSink:\ 0xa2eE6B55e477342caA422558448e478ac9133A69 ProtocolRegistry:\ 0xe067aE8877812F5B3dB8f985831ae1008377017A Genesis Supply Safe:\ 0x976520057Fe307FAd16B153E7095a227B2593b28 Protocol Admin Safe:\ 0xE9D46209a813Ed2E3861279d8f7dA2780dfF25A1 | Contract | Address | Purpose | Status | | ---------------- | -------------------------------------------- | ----------------------------------- | -------- | | VTYToken | `0x3c650A6C6fd6CE29225364529425C188025Db625` | Fixed-supply Vitality token | Deployed | | BurnSink | `0xa2eE6B55e477342caA422558448e478ac9133A69` | Immutable sink address | Deployed | | ProtocolRegistry | `0xe067aE8877812F5B3dB8f985831ae1008377017A` | Official Vitality contract registry | Deployed | ### Verification Status Sourcify verification: **Complete / exact match** | Contract | Sourcify Result | | ---------------- | --------------- | | BurnSink | exact\_match | | VTYToken | exact\_match | | ProtocolRegistry | exact\_match | PulseScan / Blockscout source display: **Pending / Blockscout fetch issue** Vitality Build Batch 1 contracts are verified on Sourcify with exact source matches. PulseScan source display is pending explorer processing. ### Treasury & Reserve Infrastructure This section should list all treasury-related infrastructure that forms part of the official Vitality reserve and operational treasury architecture. This may include: * treasury reserve contracts * treasury control contracts * treasury multisig wallets * treasury execution wallets * reserve lock contracts * approved treasury module contracts Suggested format: **Treasury Reserve Contract / Wallet**\ Purpose: Holds or manages designated treasury reserve assets\ Address: \[insert official address]\ Explorer: \[insert explorer link]\ Notes: \[brief description] **Treasury Operations Wallet / Contract**\ Purpose: Executes approved treasury operations under defined governance and security controls\ Address: \[insert official address]\ Explorer: \[insert explorer link]\ Notes: \[brief description] ### Staking & Reward Infrastructure As Vitality expands, dedicated contracts may be used for staking, reward distribution, campaign mechanics, ecosystem incentives, or other participation systems. This section should list any official contracts related to: * staking * reward distribution * application reward modules * incentive settlement * referral systems * partner reward infrastructure * future ecosystem distribution contracts Suggested format: **Staking Contract**\ Purpose: Supports approved staking participation mechanics\ Address: \[insert official address]\ Explorer: \[insert explorer link]\ Notes: \[brief description] **Rewards Distributor Contract**\ Purpose: Handles approved reward allocations and distribution logic\ Address: \[insert official address]\ Explorer: \[insert explorer link]\ Notes: \[brief description] ### Application & Integration Contracts Vitality is designed as a broader ecosystem rather than a single isolated application. As a result, future applications, modules, and integrations may have their own official contracts. This section should be used to publish any approved: * application contracts * settlement modules * ecosystem registries * NFT contracts * access-control contracts * integration infrastructure * partner deployment contracts Each listing should clearly explain whether the contract is: * a core Vitality contract * an official first-party application contract * an approved integration contract * a future ecosystem module ### Operational Wallets Some Vitality ecosystem functions may involve operational wallets or administrative safes rather than purely autonomous contracts. Where relevant, this page should publish official operational wallet addresses for transparency, including wallets related to: * deployment * treasury operations * ecosystem administration * multisig governance * security management * future ecosystem functions Every operational wallet listed should include a clear description so the community understands its purpose. ### Transparency Standard Vitality is intended to operate with a high standard of public clarity around official on-chain infrastructure. Whenever possible, every published contract or wallet should include: * plain-language purpose * address * network * verification link * control status * relationship to the wider ecosystem This makes the ecosystem easier to understand, easier to verify, and safer for users, partners, and community participants. ### Important Notice Only interact with addresses published through official Vitality channels. Always verify: * official GitBook listings * official website references * official social announcements * official block explorer records Never rely on screenshots, copied messages, or third-party posts as the sole source of truth for contract verification. ### Future Expansion As the Vitality ecosystem grows, this page may expand to include additional official infrastructure for new applications, staking systems, reward modules, NFTs, integrations, partner deployments, and community-facing tools. The purpose of this page is to ensure that as the network becomes more sophisticated, public verification remains simple, consistent, and trustworthy. *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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://vitality-project.gitbook.io/vitality-token-project/official-contracts-and-addresses.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.