> For the complete documentation index, see [llms.txt](https://docs.dappradardao.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dappradardao.com/dappradar-dao-report-2024/financial-reporting-overview/transactions-since-token-generation-event-tge.md).
# Transactions since Token Generation Event (TGE)
DappRadar DAO’s transactional trends have evolved since its inception. Up to 2023, 97% of fiat-equivalent transactions were conducted in RADAR, with the remainder denominated in RON and ETH. However, in 2024, USDC became the preferred payment currency, reflecting the DAO’s growing operational complexity and contributor onboarding.
### **Key Inflows in 2024**
* Node validator earnings: Generated 375K RON in fees and staking rewards, supporting operational costs and loan repayments.
* Affiliate marketing revenue: Introduced in December 2023, this revenue stream grew steadily in 2024 and is expected to expand in 2025.
* Market-making activities: Managed through GSR, optimizing liquidity and trading efficiency.
* Future growth projections: Validator node expansion across additional blockchains, with Chromia already operational as of Q4 2024.
### **Key Outflows in 2024**
* Market making and treasury diversification: Transitioned from Wintermute to GSR, supported by RADAR-backed loans for liquidity management.
* Loan repayments: The DAO started repaying its outstanding loan from DappRadar UAB, which covered early operational expenses between 2021 and 2023.
* DCP Workstream Expenses: The primary operational cost category, covering contractor and contributor payments, reinforcing the DAO’s commitment to decentralization and community governance.
As the DAO expands its validator operations and diversifies revenue streams, financial sustainability is expected to strengthen in 2025 and beyond.
---
# 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, and the optional `goal` query parameter:
```
GET https://docs.dappradardao.com/dappradar-dao-report-2024/financial-reporting-overview/transactions-since-token-generation-event-tge.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.