Model

A canonical representation of tokenized financial instruments.

Mudara is built on a structured financial intelligence model that represents real-world assets as interconnected systems, not isolated tokens. Each instrument is decomposed into its underlying legal, operational, and on-chain components, enabling consistent analysis across issuers, jurisdictions, and asset classes.

Most systems
"A token with metadata."
Mudara models
"A network of legal claims, operational dependencies, and blockchain representations."

This allows every asset to be analyzed consistently, regardless of issuer or structure.

Core principle

Separation of layers

Every RWA is composed of distinct but connected layers. Mudara models each layer independently, then connects them into a unified graph.

The Mudara data model

A graph of financial entities

At the core of the system is a graph of financial entities — eight entity types, independently modeled, then connected.

entity_graph.render()
ENTITY Issuer LEGAL WRAPPER SPV / Trust TOKEN Token CUSTODY Custodian VALUATION Oracle ASSET Underlying Asset VALUATION NAV Methodology REDEMPTION Redemption Rules COMPLIANCE Compliance Rules
Every entity is independently modeled, then connected into one graph — this is the Mudara data model.
Entity types

Eight entities, fully specified

01 — Asset Entity05

Represents the underlying economic exposure. Examples: U.S. Treasury Bills, private credit portfolio, money market fund, real estate pool.

  • Asset type
  • Risk profile
  • Yield source
  • Maturity structure
  • Collateral composition
02 — Issuer Entity07

The legal entity responsible for issuance.

  • Legal name
  • Jurisdiction
  • Regulatory status
  • Financial statements
  • Audit history
  • Capital structure
  • Related entities
03 — Legal Wrapper06

SPV / Fund / Trust — defines how assets are structured legally.

  • Structure type (SPV, fund, trust, etc.)
  • Bankruptcy remoteness
  • Jurisdiction
  • Investor rights
  • Offering documentation
  • Transfer restrictions
04 — Token Entity07

On-chain representation of the instrument.

  • Contract address
  • Chain(s)
  • Token standard
  • Upgradeability
  • Admin controls
  • Mint / burn mechanics
  • Bridge dependencies
05 — Custody Entity06

Where underlying assets are held.

  • Custodian name
  • Sub-custodians
  • Segregation model
  • Insurance coverage
  • Rehypothecation policy
  • Proof-of-reserves linkage
06 — Valuation Entity06

Defines how the instrument is priced.

  • NAV methodology
  • Pricing frequency
  • Data sources
  • Oracle providers
  • Adjustment rules
  • Latency between valuation and reporting
07 — Redemption Entity06

Defines liquidity and exit mechanics.

  • Redemption frequency
  • Settlement method
  • Minimum thresholds
  • Fees
  • Gates / suspension rules
  • Liquidity buffers
08 — Compliance Entity06

Defines investor access and regulatory constraints.

  • KYC / KYB requirements
  • Jurisdictional availability
  • Investor eligibility
  • Regulatory classification
  • Transfer restrictions
  • Sanctions screening dependencies
Beyond fields

Relationships matter more than fields.

The true value of Mudara is not in isolated attributes, but in how entities connect. This graph structure enables systemic analysis of risk, exposure, and comparability.

Worked example

Tokenized Treasury Fund

A simplified representation. Each element is independently modeled and machine-readable.

treasury_fund.mdrinstance example
Issuer: Asset Manager A
   ↓
SPV: Money Market Fund Structure
   ↓
Token: On-chain share class
   ↓
Underlying Asset:
    - U.S. Treasury Bills
    - Cash deposits

Custodian:
    - Tier 1 global custodian

NAV:
    - Daily marked-to-market
    - Fed funds rate + spread

Redemption:
    - T+1 settlement
    - USD or stablecoin payout

Compliance:
    - Accredited investors only (US)
    - EU distribution restricted
Design philosophy

Mudara is not a dataset. It is a financial instrument ontology.

This enables auditability at the level institutional users expect.

Why this model matters

Structure changes what's possible

Without structure04
  • RWAs cannot be compared01
  • Risk cannot be normalized02
  • Due diligence is manual03
  • Data remains fragmented04
With structure04
  • Instruments become comparable01
  • Risk becomes quantifiable02
  • Compliance becomes machine-readable03
  • Research becomes scalable04
Output

A queryable financial graph

Mudara exposes this model through API access, graph queries, a research interface, and structured exports.

  • API

    Structured instrument data

    Programmatic access to every field in the instrument graph.

  • GRAPH

    Relationship queries

    Traverse dependencies between issuers, custodians, and oracles.

  • UI

    Research interface

    An institutional interface for exploring instruments directly.

  • EXPORT

    Risk & compliance layers

    Structured exports built for downstream risk and compliance workflows.

"What is this token?"
"Show all tokenized funds with bankruptcy-remote structures, T+1 redemption, and audited NAV within 30 days."
The result

A shift from token-level observation to instrument-level understanding.

This is the foundation of Mudara.

Get started

Understand RWAs as financial instruments, not tokens.