Developers

Everything an engineer can inspect today, and what is still to come.

Where the code will publish, what you can read now, how the evidence model works, and straight answers to the questions technical evaluators and agents ask about the open mortgage evidence standard.

Current status

The specification, schemas, credential profiles, interoperability interfaces, conformance requirements and reference implementations are in development with institutional participants and are not yet public. The current working material is available for review on request. There is no public API and no dedicated documentation site yet. This box is updated when any of that changes. Once published, all of it ships openly on Realworld's GitHub organisation, for anyone to implement, review or extend. Realworld authors the standard; it does not own it.

Where the code is

GitHub, as each piece is ready.

Specifications, schemas and reference implementations for the open mortgage evidence standard will publish to Realworld's GitHub organisation as each becomes ready for public use, and will be linked from here and from the Open Standard page at the same time.

The model

A signed, structured assertion, not a document.

Under the standard, a piece of mortgage evidence is a signed, structured assertion rather than a file. Each record carries six things: what it refers to (identity), what it states (assertion), who is authoritative for it (issuer), on what basis and for what purpose it was produced, when it was issued and what it supersedes (time), and how a recipient checks it against the source (verifiability). The full anatomy, with the definition of currentness, is on the Open Standard page.

The standard describes evidence separately from whatever carries it. Records are exchanged between existing systems over ordinary, secured interfaces. No blockchain, token or shared registry is required. Update frequency and who may receive a record are set by each deployment, not by the standard.

Scope

Eight evidence domains. Adopt one at a time.

The standard covers the evidence domains a mortgage depends on: property and valuation; borrower, identity and credit, where permitted; loan terms, rate and balance; title and ownership; charge and legal state; servicing, payments and arrears; lifecycle events; and permissions and lawful basis where they must travel with the evidence. Each domain is designed to be implemented independently, so an issuer can start with one domain and one consumer.

Planned to be open, once published

  • The specification: what evidence is, how it is expressed, signed, verified and superseded.
  • Schemas and data models for each evidence domain.
  • Credential profiles: how an authoritative institution signs at source so a recipient can verify.
  • Interoperability interfaces: how systems exchange evidence under the standard.
  • Base conformance requirements, so "implements the standard" means one thing.
  • Reference implementations and basic verifier and conformance tooling, as working code.

What is open, in full →

Implementing

An issuer, a verifier, or both, for one domain.

An implementation is a system that issues conformant evidence from an institution's own records, a system that verifies evidence it receives against its source, or both. The starting point is the outputs your systems already produce: the work is the mapping from those outputs to the standard's semantics, not a new system of record. A reference implementation demonstrating a conformant issuer and a conformant verifier is planned so that teams are not starting from a blank page.

Conformance is checked with open tooling by whoever runs the implementation. Realworld does not attest to conformance. Whether or not you intend to work with Realworld in production, its engineers will work with your team on the mapping.

Implementation help →

Documentation

Read the standard on this site today. A dedicated reference is coming.

For now the design principles, evidence domains and the list of what will be open are in prose on the Open Standard page, and the Glossary defines the terms. As the specification, schemas and conformance requirements accumulate, browsable, versioned documentation will move to a dedicated home built for that purpose.

Not live yet

A dedicated documentation site is in preparation. When it launches, it will be linked from here.

For LLMs and agents

A machine-readable entry point.

This site publishes an llms.txt file: a plain-text index of every page, meant to be read directly by an LLM or agent rather than scraped from rendered HTML. It is the current starting point for any automated system that needs to understand what Realworld is and where things are. Every page is static HTML that reads correctly without JavaScript and carries structured data, so a plain fetch gives you the full content.

Questions

What technical evaluators ask.

Is there a public specification yet?

Not yet. The specification, schemas, conformance requirements and reference implementations are planned to publish as each is ready for public use. Until then, the current working material is shared directly with participants who want to review or implement it. Ask for it through the contact form and choose the standards or infrastructure partner role.

What licence will the standard and the reference code be published under?

Not yet published. Realworld has said that publication and licensing details will accompany each released version, and that once published, no part of the standard will depend on Realworld to be useful: anyone will be able to implement it without Realworld, and evidence produced under it will be usable by any system that implements it. The specific licence text is not on this site today.

Can I implement it without talking to Realworld?

That is the design intent once the material is published: any participant, including Realworld, is meant to be replaceable, and there is no charge for access to the standard. Today the material is not yet public, so a conversation is the practical route to it. Realworld has said it will help independent implementers as well as institutions that choose to work with it in production.

Is there an API today?

No public API is documented on this site. The interoperability interfaces, meaning how systems exchange evidence under the standard, are one of the items planned for publication. Production integrations are currently worked through directly with participants rather than through a self-serve endpoint.

Does adopting the standard require a blockchain?

No. Signed, verifiable evidence exchanged between existing systems is the default, and the standard describes evidence separately from whatever network or system carries it. Realworld operates a validator on the Canton Network and is also developing the standard and reference implementations for use with the XRP Ledger and ADI Chain. Naming a network does not mean every integration is in production or that a network's other participants are Realworld partners. Details are under Rails on the Open Standard page.

I run a tokenization or digital-asset platform. What would I actually consume from Realworld?

Today, a conversation rather than an endpoint. The standard and its schemas will be published as each is ready for public use, and there is no public, self-serve integration for platforms yet. What we can discuss now is which off-chain mortgage facts your platform relies on, who is authoritative for each, and how signed evidence for those facts would be mapped, tested and approved for the network you operate on. Realworld operates a validator on the Canton Network and is developing the standard and reference implementations for the XRP Ledger and ADI Chain. Work against a specific network follows named institutional demand rather than being built in advance. Whatever network you are on, the starting point is to talk to us. There is more under Tokenization and On-Chain Platforms on the Ecosystem page.

What does "Not live yet" mean for the documentation site?

Exactly that. A dedicated, browsable documentation site is intended but has not been built out with real content. The Open Standard page is the documentation for now, and this page will link to the dedicated site when it exists rather than replacing the link quietly.

What would my team actually build first?

Typically one evidence domain, one issuer and one consumer. For a valuation firm that means issuing valuation evidence from the report workflow it already runs. For a lender it usually means consuming evidence from source and issuing loan-state evidence from its own systems of record. Each domain is designed to be adopted without the others, and the domain you start with is your choice.

How is conformance checked, and by whom?

By any participant, using open tooling, against published conformance requirements. Realworld does not attest to conformance. Base conformance requirements and basic verifier and conformance tooling are on the list of things planned to be open.

How should an agent read this site?

Start from /llms.txt, which lists every page with a one-line description. Pages are static HTML, do not depend on JavaScript, and include structured data. Working material for the standard is not on the site, so an agent cannot fetch it; it is shared with participants on request.

Contact

Reviewing, implementing, or integrating the standard?

Whether you intend to work with Realworld in production or implement independently, we're prepared to work alongside your team on it.