Why agency MBS
Agency MBS is one of the largest fixed-income markets in the United States. Its pool-level data, such as factors, balances and security details, is published through the disclosure platforms of Fannie Mae, Freddie Mac and Ginnie Mae. Each platform publishes its own raw data. None reconciles against the others or offers a defined dispute path.
For a tokenized pool or a settlement that depends on that data, the stakes are practical: a stale or mismatched figure means a wrong value, a failed settlement or an audit question later. If an attestation layer works against this much nuance, it can be applied to simpler cases.
The mechanism, step by step
- 1.Source ingestion. OWNR pulls data from multiple authoritative sources. A defined hierarchy ranks them for each asset class.
- 2.Cross-validation. The sources are compared against each other. Agreement within tolerance moves a claim forward.
- 3.Dispute logic. When sources disagree, or data is stale, the claim halts and routes to a defined resolution path. Disagreement is never resolved silently.
- 4.Signing. The validated record is signed cryptographically. Post-quantum signing is in development.
- 5.Publication. A timestamped, immutable record is written onchain.
- 6.Independent verification. Any party, using a verification tool separate from the publisher, can confirm the signature and the audit trail.
How outcomes look
| Scenario | What happens |
|---|---|
| Sources agree within tolerance | The claim is validated, signed and published as an attestation |
| Sources conflict | The claim halts and routes to the defined dispute path. Nothing is published as valid |
| Data is stale | The claim is rejected, with the reason recorded |
| A third party checks a record | The verifier confirms the signature and audit trail without relying on OWNR's live system |
ScenarioSources agree within tolerance
What happensThe claim is validated, signed and published as an attestation
ScenarioSources conflict
What happensThe claim halts and routes to the defined dispute path. Nothing is published as valid
ScenarioData is stale
What happensThe claim is rejected, with the reason recorded
ScenarioA third party checks a record
What happensThe verifier confirms the signature and audit trail without relying on OWNR's live system
What the pilot demonstrates
- Multi-source validation. Pool-level data ingested from several disclosure feeds, ranked by a defined source hierarchy and cross-checked within tolerance.
- A visible rejection path. What happens when sources conflict or data is stale: the claim stops, the reason is recorded, and nothing is published as valid.
- Signed, published records. Each validated claim is signed and written as a timestamped onchain record.
- Independent verification. A separate verification interface, run apart from the publisher, confirms any record.
- Configurable rules. Source hierarchy and dispute rules are set per asset class, not hardcoded to MBS.