Pilot: Agency MBS

Our first proof point: U.S. agency MBS.

Agency mortgage-backed securities pool data comes from several disclosure feeds that must reconcile before anything can safely settle. We are piloting attestation here because it is demanding, and because success carries over to other regulated assets.

Pilot in development.

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.

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.

How outcomes look

  • Scenario

    Sources agree within tolerance

    What happens

    The claim is validated, signed and published as an attestation

  • Scenario

    Sources conflict

    What happens

    The claim halts and routes to the defined dispute path. Nothing is published as valid

  • Scenario

    Data is stale

    What happens

    The claim is rejected, with the reason recorded

  • Scenario

    A third party checks a record

    What happens

    The verifier confirms the signature and audit trail without relying on OWNR's live system

From attestation to settlement

OWNR's tokenization engine and settlement layer put attested data to work. Tokenized representations of MBS can carry attested pool data into settlement, so the record behind a transaction can be checked rather than assumed. These components are designed to connect with regulated trading venues, clearing workflows and trade reporting. Specific connections will be announced as they go live.

Work with us on the pilot

We are talking with data providers, custodians, tokenization platforms and institutions that want to test attestation against real workflows.