Treasury & Governance Transparency — Virdato (VIRD)

Purpose of This Page

This page explains how treasury-controlled tokens and program reserves are governed, how changes are approved, what reporting the public can expect, and how AI Vault Systems Inc. intends to minimize governance and custody risk.

• What we disclose: allocation categories, treasury/program wallets, control model, reporting cadence, and change procedures.
• What we do not promise: price support, liquidity provisioning, exchange listings, or profit.
• What can change: reward parameters and program rules (within published governance controls).

Treasury Overview

Important: Treasury allocations exist to support utility programs and operations—not exchange trading or financial yield programs.

Allocation Categories & Intended Use

The allocation model below is aligned with the Virdato tokenomics design. Each category has a defined purpose and internal controls. Exact operational use may evolve, but category intent and reporting remain consistent.

Team & Advisors vesting recommendation: 12-month cliff + 36-month linear vesting. Current custody/vesting details are disclosed below.

Treasury, Governance & Program Contracts — On-Chain Disclosure

Below are the primary on-chain addresses used for governance administration and the VIRD reward system. Important: several addresses previously described as “wallets” are in fact program contracts (smart contracts), not custody wallets. They are disclosed here with correct labels and BaseScan links for public verification.

These disclosures support transparency and auditability. They do not imply exchange support, liquidity guarantees, or profit expectations.

Control Model & Security Controls

Treasury and program wallets should be governed with controls appropriate for a public utility-token ecosystem. The model below reflects investor-grade operational discipline.

• Multi-signature custody (target state): treasury funds held in a multi-sig wallet (e.g., 3-of-5 or 4-of-7) to reduce single-key risk.
• Role separation: different signers for operations, security, and rewards administration.
• Timelock for sensitive actions (where feasible): high-impact transfers or parameter changes queued with delay (e.g., 24–72 hours).
• Least privilege: only necessary permissions granted to reward distribution services and admins.
• Key management: hardware wallets recommended; signer rotation procedures documented.
• Incident response: defined playbooks for key compromise, abnormal reward issuance, or contract risk.

If the current configuration is in transition (e.g., temporary custody before multi-sig/vesting deployment), publish milestones and target dates for upgrades.

Change Management & Parameter Governance

Virdato reward programs rely on configurable parameters (e.g., epoch cadence, eligibility thresholds, fraud filters, pool budgets). Changes are disclosed to preserve transparency and integrity.

Reporting & Public Accountability

Investor-grade transparency requires predictable reporting. The baseline reporting model below supports verifiable, on-chain review.

• Monthly transparency summary: treasury inflows/outflows by category with BaseScan links.
• Epoch reward reporting: total rewards distributed per epoch (creator + audience) and unclaimed/expired totals if applicable.
• Grant disclosures: summarized partnership distributions (purpose + category), with sensitive details redacted when necessary.
• Security reporting: disclose audits, major fixes, and responsible disclosure outcomes (without premature exploit details).
• Change log: versioned record of parameter updates and effective dates.

Reporting focuses on transparency and verifiability—not market making, liquidity provision, or investment promotion.

Legal Positioning (USA & EU)

VIRD is intended for utility within the Virdato ecosystem. It is not equity, does not provide revenue share, and is not promoted as an investment. Availability of features may vary by jurisdiction and applicable law.

Document Version & Update Policy

Continued use of the platform constitutes acceptance of updated disclosures. Always refer to the newest version and the latest whitepaper.

Contact & Transparency Requests

Questions about treasury transparency, governance controls, or reporting can be directed to your official contact channel. For security issues, use your responsible disclosure email.

1) Governance Layers (Overview)

2) Decision Flow (Diagram)

3) Treasury Control Principles

• Least privilege for operational systems
• Separation of duties (rewards vs operations vs security)
• Multi-sig custody target state
• Timelock for sensitive actions where feasible
• Public transparency through wallet disclosures and reports

4) Version

Monthly Treasury Report — Template

A) Summary

• Total rewards distributed (Creators): [X VIRD]
• Total rewards distributed (Audience): [X VIRD]
• Grants/Partnership distributions: [X VIRD]
• Security/Dev reserve usage: [X VIRD]
• Ops treasury usage: [X VIRD]

B) Material Transfers (Top Items)

List material transfers with BaseScan transaction links:

• [Category] — [Amount] — BaseScan TX — Reason: [purpose]
• [Category] — [Amount] — BaseScan TX — Reason: [purpose]

C) Reward Integrity Notes

• Fraud filters updated? [Yes/No]
• Notable abuse events? [None / Summary]
• Unclaimed rewards expired/rolled? [X VIRD] under policy version [vX.X]

D) Policy / Parameter Changes

List all reward rule changes with effective dates and links to changelog entries.

This report does not constitute financial advice and does not imply any market value support, exchange listing strategy, or profit expectation.