> 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/current-contract-registry.md).

# Current Contract Registry

Current Vitality contract roles and deployment states, separated from historical deployment records and future architecture.

**Status: CURRENT PUBLIC TECHNICAL RECORD — FINAL ON-CHAIN VERIFICATION REQUIRED BEFORE USE**

This page explains the current role of the principal deployed Vitality contracts. Historical deployment evidence is retained separately under **Deployment History**.

## VTYToken

`0x3c650A6C6fd6CE29225364529425C188025Db625`

**Role:** fixed-supply Vitality token. Public architecture: no owner/admin, no post-deployment minting, no transfer tax, no blacklist, no pause and no rebasing.

## BurnSink

`0xa2eE6B55e477342caA422558448e478ac9133A69`

**Role:** irreversible destination used where approved Vitality rules require permanent economic removal of VTY. A transfer to BurnSink should be distinguished from a change in ERC-20 `totalSupply()` where the implementation does not decrement supply.

## ProtocolRegistry

`0xe067aE8877812F5B3dB8f985831ae1008377017A`

**Role:** official Vitality contract registry and discovery layer for approved protocol records.

## TreasuryTokenLock

`0x394Cd657476fc04150b48364a6A53717965385c6`

**Role:** long-term Treasury reserve lock infrastructure. Published deployment state: deployed, registered, registry record frozen and **not funded**.

## TreasuryAllocationVault

`0x94a27b8868101209F72c8A4a2B06E54d15b0Cc8E`

**Role:** controlled Treasury active-support allocation infrastructure. Published deployment state: deployed, registered, registry record frozen and **not funded**.

## NoExpectationsVestingVault

`0x1a26626B837d2926a4046ad0b073Ec9C294061F8`

**Role:** vesting infrastructure for the separate No Expectations Genesis allocation. Published deployment state: deployed, registered, registry record frozen and **not funded**.

## VitalityClaimRouter

`0x8F7cE0A0Db3dAa3b9a0C6693280C98e9A2053Bf4`

**Role:** non-custodial discovery-only directory for approved claim / distribution modules. The deployed router does not itself open a claim or custody VTY.

## VitalityDistributor

`0xc17e6600b73cbba602d0aee3f4af46af39f8bbf1`

**Role:** campaign custody and accounting infrastructure for approved VTY distributions. Its existence does not mean any campaign is funded or publicly claimable.

## MerkleClaimDistributor

`0x6de61dedcc3ff448584d8d4157bb9a87a0024e85`

**Role:** Merkle-proof eligibility module for configured campaign claims. It does not choose snapshots, create eligibility or open a campaign.

## Public campaign boundary

Unless a later status page explicitly says otherwise:

* no public claim is implied by deployment;
* no sacrifice / commitment campaign is implied by deployment;
* no NFT mint is implied by deployment;
* no VTY Charging programme is implied by deployment;
* no CHI issuance is implied by deployment;
* no Nexus Genesis Pool is implied by deployment.

## Source-of-truth discipline

Application code, website copy and social posts must converge on this registry only after the deployed state has been independently revalidated. A stale application placeholder must not override a later verified deployment record, and documentation must not override actual chain state.