> For the complete documentation index, see [llms.txt](https://tripleplus-1.gitbook.io/dor/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tripleplus-1.gitbook.io/dor/dor-whitepaper-english/2.-technical-architecture/2.5-on-chain-record-and-transparency-protocol.md).
# 2.5 On-chain Record & Transparency Protocol
Instead of the extreme on-chain maximalism of "recording every event on-chain in real-time," DOR adopts a compromise structure combining real-time execution and daily on-chain accounting (commit once per day).
This utilizes an on-chain/off-chain hybrid technical structure to provide a reproducible and auditable full history while minimizing gas costs and data redundancy.
#### 2.5.1 Daily Aggregation and On-chain Commit
In actual operation, all swap, staking, and liquidity movement events are recorded in the indexing layer in real-time.
They are then aggregated in 24-hour windows (UTC based) and organized into a summary JSON snapshot containing information such as:
* Total daily transaction count
* Total inflow/outflow volume
* Balance changes per pool
* Key risk indicators (e.g., Max Drawdown, Volatility Clustering)
A SHA-256 or Keccak hash is generated for the organized JSON, and the original file is uploaded to distributed storage like IPFS or Arweave.
Only this hash value, storage link, and DAO signature are recorded on-chain. This allows anyone to verify data integrity while minimizing on-chain costs.
Thanks to this structure, anyone can query the on-chain hash for a specific date via a dashboard or block explorer and compare it with the original JSON stored on IPFS to verify that the data for that date has not been forged or altered.
External auditors can access and verify the same data using the same mechanism, and for this purpose, the record format follows a public JSON schema.
#### 2.5.2 Data Integrity and Emergency Process
Once committed, accounting records in DOR are immutable and non-erasable.
Even if an error is found, corrections are made only by adding re-interpretation logs at a higher level, not by modifying or deleting existing records.
If a meaningful discrepancy is detected between the state recorded on-chain and the actual pool balance, an automatic warning and DAO Emergency Audit routine are triggered, and new swaps/withdrawals may be temporarily paused for that section.
After governance approves a cause analysis and recovery plan, the system gradually returns to a normal state.
This on-chain accounting and emergency process structure serves to eliminate the centralized Web2-style risk where a specific developer can arbitrarily modify the DB, and to guarantee the collective memory of the meme economy at a decentralized chain level.
In other words, the history of meme liquidity created and circulated on DOR is recorded in an "unforgettable public ledger," which serves as a common infrastructure for future governance, research, and derivatives design.
---
# 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:
```
GET https://tripleplus-1.gitbook.io/dor/dor-whitepaper-english/2.-technical-architecture/2.5-on-chain-record-and-transparency-protocol.md?ask=
```
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.