Skip to main content

duewall

Read-only Python client for the DueWall maturity calendar of tokenized credit — "the liability time-axis for tokenized credit."

On-chain data is a rear-view mirror: Maple's public API lists 266 loans, all matured, zero forward maturities visible on-chain. The forward-looking layer lives in documents — loan agreements and fund factsheets. DueWall reads them, with per-field source links, human verification and a coverage-grade system, and serves the result as a free public API.

It also serves claim-vs-observed verification: issuer claims checked against on-chain and document-layer observations, three-state verdicts (consistent / discrepant / untestable), every check evidence-linked. Badges are earned, never bought.

Install

pip install duewall

Usage

Zero dependencies (stdlib only).

from duewall import DueWall

dw = DueWall()

dw.meta()                               # record counts, license, schema links
dw.events()                             # all events: maturities, redemption
                                        # windows, NAV reports — each with a
                                        # coverage grade (A/B/M) + source_url
dw.forward()                            # future-dated obligations (the layer
                                        # on-chain lacks)
dw.forward(days=90)                     # next 90 days only
dw.terms()                              # human-verified liquidity terms per fund
dw.pools()                              # pool NAV + TVL/APY snapshot
dw.maturity_wall()                      # monthly on-chain maturity distribution
dw.price_history()                      # daily on-chain NAV/price series
dw.index()                              # DLI — rules-based equal-weight NAV
                                        # benchmark (grade-A pools), anchored
dw.spreads()                            # credit spread ladder vs 3M Treasury
dw.dcr()                                # DCR — Sky Savings Rate measured from
                                        # the on-chain sUSDS accumulator
dw.verification()                       # claim-vs-observed verification:
                                        # three-state verdicts, evidence-linked
dw.discrepancies()                      # only checks where an issuer claim does
                                        # NOT match observed state
dw.allowlist()                          # rule-based verified-issuer allow-list
                                        # for investment-policy engines
dw.allowlist_names()                    # just the current member short names
dw.by_grade("A")                        # human-verified records only

Example — are the issuer's claims true?

from duewall import DueWall

dw = DueWall()
v = dw.verification()
print(v["counts"])                      # {'claims_registered': 25, 'checks_total': 30,
                                        #  'consistent': 29, 'discrepant': 1, ...}
for d in dw.discrepancies():
    print(d["token"], d["claim_type"], "claimed:", d["claim_text"],
          "observed:", d["observed"], d["evidence_url"])

Badges are earned, never bought: a fund wears Verified only while its grade-A terms hold and checks stay consistent — see duewall.com/verify/. The same data is available as MCP tools (get_verification, get_dli, ...) in duewall-adapters for AI agents.

Pro users pass their API key to raise the quota and unlock bulk exports:

dw = DueWall(key="your-key")            # free key: duewall.com/account

Example — what matures next?

from duewall import DueWall

dw = DueWall()
for e in sorted(dw.forward(days=180), key=lambda x: x["date"] or ""):
    print(e["date"], e["token"], e["event_type"],
          f"${e['amount_usd']:,.0f}" if e.get("amount_usd") else "",
          e["source_url"])

Coverage grades (A / B / M)

Every record carries a grade describing data completeness — never credit quality:

Grade Meaning
A Terms human-verified against issuer factsheets & published
B Events covered by machine adapters with source links; terms pending
M Below the TVL bar for a dedicated adapter; monitored

Rules: an event never exceeds the grade of its entity; unmatched rows default to B; new issuers enter at B and move to A only after a factsheet pass in human verification. Full policy: duewall.com/coverage/.

Integrity — Bitcoin-anchored

Every daily snapshot is hash-chained (each day binds the previous anchor) and timestamped via OpenTimestamps: receipts at duewall.com/anchor/, verifiable with ots verify — anyone can prove the data existed at its stated date, unaltered.

License & citation

Metadata

Release files for duewall 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for duewall 0.4.0
File Size Uploaded Provenance Actions
duewall-0.4.0.tar.gz 7.0 kB Without provenance Details for duewall-0.4.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for duewall 0.4.0
File Interpreter ABI Platform Actions
duewall-0.4.0-py3-none-any.whl Python 3 none any Details for duewall-0.4.0-py3-none-any.whl

Total release size: 14.9 kB

Release files / duewall-0.4.0.tar.gz

Download URL duewall-0.4.0.tar.gz
Size 7.0 kB
Tags Source
SHA-256 checksum
How to use checksums
2a91a4f5610f2c07bb5a742e7025d90111c7abd1e8c493a5d9a938c477eaa59f
BLAKE2b-256 checksum
How to use checksums
61ffcddb36a92cfbb89e14e939f886d66d0d74cbad6c155977a69f37a64c40ec
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.10

Release files / duewall-0.4.0-py3-none-any.whl

Download URL duewall-0.4.0-py3-none-any.whl
Size 7.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d6db2bc47a02355d324a1ae00bc5ddb154973eac9b599c5603cd75a4a216cc8a
BLAKE2b-256 checksum
How to use checksums
f609169f3b5214f89efc324bd3556477e1e52aebcb24772cb615db5acb9821bd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.10

Security for duewall 0.4.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page