Official Contracts
Official Vitality mainnet contract records.
This page lists official Vitality mainnet contract records, Safe-controlled addresses, registry status, verification status, and public funding boundaries for the current deployed infrastructure.
Batch 2 + Batch 3A recorded
Build Batch 2 and Build Batch 3A contracts are deployed, registered, frozen, source verified, and not funded.
Registered and frozen
Official records have been registered and frozen in ProtocolRegistry to support stable public reference.
Not funded
No VTY has been transferred into Build Batch 2 or Build Batch 3A contracts. Future funding requires separate approval and Safe transaction review.
Build Batch 3B-1
VitalityClaimRouter
VitalityClaimRouter is the official discovery-only directory for approved Vitality claim and distribution modules. It supports future frontend, app, and ecosystem integrations by providing a registered module discovery layer.
Discovery-only claim and distribution module directory
0x8F7cE0A0Db3dAa3b9a0C6693280C98e9A2053Bf4
VitalityClaimRouter is deployed on PulseChain mainnet as a discovery-only router for approved Vitality claim and distribution modules. The router does not custody VTY, does not execute claims, does not include routeClaim, and does not include funding logic.
Safe-owned VTY distribution custody and campaign accounting infrastructure
0xC17e6600B73CbBa602D0aeE3f4Af46AF39f8bbF1
- Network: PulseChain mainnet
- Status: Deployed, registered, frozen, Sourcify exact-match verified
- Registry key: VITALITY_DISTRIBUTOR
- Funding status: Unfunded, no VTY moved
Registry key bytes32
0xf9a2f055316958ead8ff918a7758fdf1483eecedd53e3635e0c2ec3f30e684e6
Owner / Protocol Admin Safe
0xE9D46209a813Ed2E3861279d8f7dA2780dfF25A1
VitalityDistributor is deployed unfunded. Any future campaign funding must be handled through a separate approved funding process with purpose, amount, source Safe, campaign ID, allocation cap, Safe review, post-transfer verification, and reconciliation record.
Protocol-owned PulseX liquidity for VTY/pDAI
0x8808a2Ae5c8B35990e32632585150436C6589B8f
- Network: PulseChain mainnet
- DEX: PulseX
- Pair: VTY/pDAI
- Status: LP-1 live and under observation
- Custody: Treasury Safe / protocol-owned liquidity
- Initial liquidity record: 500,000 VTY / 500,000 pDAI
VTY token
0x3c650A6C6fd6CE29225364529425C188025Db625
pDAI token
0x6B175474E89094C44Da98b954EedeAC495271d0F
PulseX Router
0x165C3410fC91EF562C50559f7d2289fEbed552d9
PulseX Factory
0x29eA7545DEf87022BAdc76323F373EA1e707C523
Treasury Safe
0xE9D46209a813Ed2E3861279d8f7dA2780dfF25A1
Liquidity custody
Protocol-owned liquidity
LP-1 is a protocol-owned liquidity record and is currently under observation. This public record does not announce or open a claim campaign or airdrop, and it does not imply guaranteed value, price stability, return, yield, or future eligibility. Future liquidity phases may be considered only after the observation window.
Eligibility and Merkle proof verification infrastructure
0x6de61DeDcC3fF448584D8D4157Bb9A87A0024e85
- Network: PulseChain mainnet
- Status: Deployed, registered, frozen, Sourcify exact-match verified
- Registry key: MERKLE_CLAIM_DISTRIBUTOR
- Funding status: No funding. No VTY movement
- Campaign status: No campaign root created. No public claim campaign active
- Module approval: Not approved as a claim module in VitalityDistributor
Registry key bytes32
0x5364eddd0e171043987abe80e6cb6beab1f00074e0bc33f26b20d16da77b3e2d
Owner / Protocol Admin Safe
0xE9D46209a813Ed2E3861279d8f7dA2780dfF25A1
MerkleClaimDistributor is the eligibility and Merkle proof verification module for future approved Vitality distribution campaigns. VitalityDistributor remains the VTY custody and campaign accounting layer. MerkleClaimDistributor does not custody VTY by design.
ProtocolRegistry
0xe067aE8877812F5B3dB8f985831ae1008377017A
VitalityDistributor dependency
0xC17e6600B73CbBa602D0aeE3f4Af46AF39f8bbF1
MerkleClaimDistributor is registered infrastructure only. It does not create any guaranteed return, yield, profit, investment outcome, or automatic user entitlement. A separate campaign launch process is required before any claim campaign can open.
Network
PulseChain Mainnet
The router is deployed on PulseChain mainnet and is part of the public Vitality contract record.
Registry key
Registered and frozen
0xe29124dd2eb7572482486305c9f10b1be4ba41901e79f3109d382ce10ac16735
The VitalityClaimRouter registry record is registered in ProtocolRegistry and frozen for registry integrity.
Source verification
Sourcify exact/full match
The VitalityClaimRouter source is verified through Sourcify with an exact/full match.
Custody and funding
Non-custodial and not funded
The router is non-custodial and should not receive or hold VTY. No VTY has been transferred into this router.
Operational boundary
Discovery layer only
VitalityClaimRouter provides an official discovery layer for approved claim and distribution modules. It is not a claims executor, funding vault, custody contract, or token distribution contract.
Verification Status
Current build batch summary
The following status summary is provided as a public verification checkpoint for the latest official Vitality infrastructure records.
Treasury Infrastructure
Deployed, registered, frozen, source verified, not funded.
- Registry status: Registered and frozen
- Source verification: Sourcify full/exact match confirmed
- Funding status: Not funded
Vesting Infrastructure
Deployed, registered, frozen, source verified, not funded.
- Registry status: Registered and frozen
- Source verification: Sourcify exact/full match confirmed
- Funding status: Not funded
Public records updated
Claim infrastructure records are now published in GitBook.
VitalityDistributor and MerkleClaimDistributor are deployed and verified infrastructure for future campaign-based distributions. Infrastructure does not mean a public claim is open.
- No public claim is open.
- No campaign is active.
- No sacrifice is open.
- No NFT minting is enabled.
- No snapshot has been executed.
- No transaction UI is live.
Core Protocol Contracts
Core mainnet records
These are the core official Vitality protocol records currently listed for public reference.
Vitality Token
Official VTY token contract on PulseChain mainnet.
0x3c650A6C6fd6CE29225364529425C188025Db625
Official Registry
ProtocolRegistry records official Vitality system contract addresses and frozen public references.
0xe067aE8877812F5B3dB8f985831ae1008377017A
Final ProtocolRegistry Owner
Safe-controlled administration address for ProtocolRegistry ownership.
0xE9D46209a813Ed2E3861279d8f7dA2780dfF25A1
Genesis Supply Custody
Safe-controlled address associated with initial VTY supply custody records.
0x976520057Fe307FAd16B153E7095a227B2593b28
Deployment Address
Vitality mainnet deployment address used for official deployment records.
0x1E8569CA3B0E86bFE3c777aA6FBFf823d6807e45
Treasury Infrastructure
Build Batch 2 records
Build Batch 2 created treasury infrastructure records. These contracts are deployed, registered, frozen, source verified, and not funded.
Treasury long-term reserve infrastructure
Status: Deployed, registered, frozen, source verified, not funded.
0x394Cd657476fc04150b48364a6A53717965385c6
- Registry status: Registered and frozen
- Source verification: Sourcify full/exact match confirmed
- Funding status: Not funded
No VTY has been transferred into this contract. Future funding requires separate approval, Safe transaction review, exact transfer amount approval, and post-transfer verification.
Treasury 1 active support vault infrastructure
Status: Deployed, registered, frozen, source verified, not funded.
0x94a27b8868101209F72c8A4a2B06E54d15b0Cc8E
- Registry status: Registered and frozen
- Source verification: Sourcify full/exact match confirmed
- Funding status: Not funded
No VTY has been transferred into this contract. Future funding requires separate approval, Safe transaction review, exact transfer amount approval, and post-transfer verification.
Vesting Infrastructure
Build Batch 3A records
Build Batch 3A created the No Expectations allocation vesting infrastructure. The contract is deployed, registered, frozen, source verified, and not funded.
No Expectations allocation vesting infrastructure
The NoExpectationsVestingVault is the official vesting infrastructure for the No Expectations allocation. It is configured for monthly linear vesting over 60 months to a dedicated Safe-controlled recipient address. Vested amounts become claimable over time, but VTY remains inside the vault until claimed. Claimed VTY transfers to the No Expectations Recipient Safe.
Contract address
0x1a26626B837d2926a4046ad0b073Ec9C294061F8
Deployment transaction
0x5d43fc62adb9126241df51cb2aa6f0dfc1ccd3a5e1f85ae35de82a6a6536daeb
Registry key
0x8b2d616be406742ac4c973975ce760fa666c328cb322c8b580d2e43b7c21dc27
Beneficiary
0x3786E8cDa552a5c15c37AeC98349F05Ff5292677
Beneficiary Safe type
2-of-3 multisig
Vesting start
1780272000
Vesting start date
1 June 2026, 00:00:00 UTC
Vesting model
Monthly linear vesting over 60 months
Monthly vesting amount
4,340,000 VTY
Total No Expectations allocation
260,400,000 VTY
Claim model
Claimable, not automatic
Status
Deployed, registered, frozen, source verified, not funded
- Registry status: Registered and frozen
- Source verification: Sourcify exact/full match confirmed
- Funding status: Not funded
No VTY has been transferred into this vault. Any future funding requires separate approval, Safe transaction review, exact transfer amount approval, and post-transfer verification.
Integrity Notes
Funding, source verification, and registry integrity
These notes define the current public boundary for the latest official contract records.
Build Batch 2 and Build Batch 3A are not funded
No VTY has been transferred into Build Batch 2 or Build Batch 3A contracts. Any future funding requires separate approval, Safe transaction review, exact transfer amount approval, and post-transfer verification.
Sourcify full/exact match confirmed
Build Batch 2 and Build Batch 3A contracts are source verified through Sourcify full/exact match records.
Registered and frozen
The official records have been registered and frozen in ProtocolRegistry to support durable public verification.
Verify Before Use
Use official references before interacting with public infrastructure.
Contract addresses should be checked against this page, the official GitBook record, and relevant public verification routes before use.