# Council Transparency

The Ledgity DAO is built around a simple principle:\
**every token, every stream, every decision must be fully visible on-chain.**

This page aggregates all information related to the DAO-controlled $LDY

If you have any questions or need clarification, feel free to contact **@metacasper** on Telegram.

Everything related to the DAO is verifiable on-chain.

#### **Council Treasury Address**

```
0x30fa557608017afb6e8e4abe8027787c00473ff0
```

#### **Sablier Vesting Streams (DAO-controlled)**

📎 <https://app.sablier.com/vesting/?t=search&c=1&r=0x30fa557608017afb6e8e4abe8027787c00473ff0>

This represents **over 20% of the total LDY supply already transparently on-chain**.

#### **Snapshot Governance**

All Council votes and proposals are available here:

📎 <https://snapshot.box/#/s:ledgitydao.eth>

Snapshot allows gasless, trustless community voting.

### **Council-Controlled LDY Streams**

#### **Vested Tokens Available**

As of today, approximately:

➡️ **\~4,000,000 LDY are already claimable**\
These tokens belong to the DAO and will be the subject of the first governance proposal.\
**2. Buyback Fees & Protocol Revenue Reserve**

A portion of protocol revenues (performance fees, buffer gains, yield spreads, etc.) is used to **automatically buy back $LDY** on the market.

All purchased tokens are accumulated in a **Buyback Reserve Address** controlled by the DAO.

### **Buyback Reserve**

* Protocol generates revenue
* Revenue is routed to the BuybackManager
* $LDY is purchased on-chain
* Purchased tokens accumulate in the Reserve

#### **What Happens Next?**

The DAO will decide — via proposal — how to use the accumulated LDY:

* Burn them (deflationary)
* Redirect to veLDY stakers
* Provide liquidity
* Treasury funding
* Grants & ecosystem incentives

Nothing will be moved without a validated Snapshot vote.

### **Governance Proposal  — What Comes Next**

#### **1️⃣ Claiming all vested LDY (\~4M)**

The DAO will claim the tokens on-chain and move them to the treasury.

#### **2️⃣ Deciding what to do with the claimed tokens**

The options submitted to community vote may include:

* **Burning a portion of the tokens**
* **Depositing into the DAO Treasury** for future ecosystem spending
* **Distributing rewards to veLDY stakers**
* **Bootstrapping liquidity**
* **Funding DAO operations or grants**

Nothing will be executed without a validated Snapshot vote.

### **Governance Process (Step-by-Step)**

To ensure full transparency, every proposal follows the same lifecycle:

#### **Step 1 — Draft**

A community member or contributor creates a proposal draft.

#### **Step 2 — Discussion**

The topic is discussed openly on Telegram, Discord or the forum.

#### **Step 3 — Snapshot Vote**

The final proposal is submitted to Snapshot:\
<https://snapshot.box/#/s:ledgitydao.eth>

#### **Step 4 — Execution**

If approved:

* The DAO executes the on-chain actions (claim, transfer, burn, etc.)
* All tx hashes are published on this page

#### **Step 5 — Post-Execution Report**

A summary including:

* Actions executed
* Updated balances
* Proofs / tx hashes
* Next steps

This ensures a permanent transparency archive.

#### *PROOF OF PROPOSAL*

#### **🟦 Proposal Title**

#### **🕒 Execution Date**

#### **📌 Actions Executed**

#### **📤 Transactions (Tx Hashes)**

#### **📊 Updated Balances**

#### **🔍 Proof Links**

\ <br>


---

# 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.ledgity.finance/governance-council/council-transparency.md?ask=<question>
```

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.