> For the complete documentation index, see [llms.txt](https://solari-finance.gitbook.io/solari.finance-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solari-finance.gitbook.io/solari.finance-docs/evidence-engine-and-hedera.md).

# Evidence Engine and Hedera

How selected lifecycle events gain durable evidence references, public consensus chronology, and independent verification.

### A Continuous History of Ownership

Every important gold position has a story: how it was acquired, when it was issued, what records support it, whether it was transferred or pledged, and how it was ultimately sold, released, redeemed, or delivered. Solari's Evidence Engine keeps that story organized.

A supported event becomes part of a continuous record linking Solari, selected Hedera references, and the holder's Vault Access Packet.

The Evidence Engine receives supported lifecycle events after their applicable workflow reaches the required status. It associates each event with the relevant position, receipt, transaction, document, custody, allocation, delivery, credit, or provider record. It then creates an appropriate cryptographic reference and manages the resulting verification trail.

Initial coverage is expected to include GoldNote issuance, ownership transfer, collateral lock and release, redemption, and delivery fulfillment — the events where independent integrity, chronology, and later inspection add the most real value. Coverage is expected to expand as production integrations mature, with additions documented in Solari's evidence schema rather than decided ad hoc. Not every routine click belongs on a public ledger.

This makes evidence a platform-wide capability rather than a decorative "proof" badge. It connects what the customer sees in the account with the deeper record of what occurred.

***

***

### Independent Chronology and Continuity

The Evidence Engine gives Solari's records structure; Hedera gives selected cryptographic references an independently recorded place in time. Solari has chosen the Hedera Consensus Service (HCS) because fast finality, consensus ordering, predictable fees, energy-efficient operation, accessible historical records, and institutional network governance suit a platform built for durable ownership.

**Illustrative MVP sXAU Evidence Trail.** *Displayed references are simulated in the review environment.*

*Hedera provides independent chronology and a durable public reference for integrity verification. Trust, custody, account, and governing records remain authoritative for their respective functions.*

For selected events, the Evidence Engine creates a cryptographic representation of the relevant record and submits an evidence reference to HCS. HCS assigns that message a consensus timestamp and sequence number within its topic, creating a public, independently retrievable record of when the reference reached network consensus. Solari retains the corresponding topic ID, sequence number, consensus timestamp, evidence identifier, and other applicable transaction references needed to locate and relate that public record back to the applicable protected source record.

This distinction matters enough to state plainly: **Hedera independently establishes the existence, consensus chronology, and ordering of the submitted evidence reference. The integrity relationship to the protected source record can then be independently checked by reproducing and comparing its cryptographic reference. Hedera does not independently verify the truth of the underlying business event.** If Solari hashes an allocation record and anchors that hash, Hedera can establish that the corresponding reference existed at consensus time — it cannot establish that the referenced gold was actually sitting in a particular vault merely because Solari anchored a hash saying so. The gold's existence, weight, and location remain questions for custody, inspection, and reconciliation records, not for the ledger.

Anyone can inspect the applicable public Hedera reference independently of Solari's interface, through Hedera's own mirror-node infrastructure or explorer tools. An authorized holder, auditor, provider, or reviewer with access to the corresponding protected source record can then compare that record with its cryptographic reference — without requiring private identities, balances, agreements, or sensitive custody information to ever be published on Hedera. Hedera does not replace the Trust, custody records, physical inspection, audits, or governing documents; it gives selected evidence an independently recorded chronology and integrity layer that can survive changes in interfaces and systems.

![visual-3-independent-verification-hcs](https://content.gitbook.com/content/foyvsiE4j1HR210JM2nP/blobs/FLGLWEGddeiR6pmGY2e7/assets/visual-3-independent-verification-hcs.svg)

***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://solari-finance.gitbook.io/solari.finance-docs/evidence-engine-and-hedera.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.