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.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
- Data: CC-BY 4.0 — cite "DueWall Labs (duewall.com)" and link back.
- Code: MIT.
- Schema: duewall-adapters/docs/SCHEMA.md
Links
- Live site: https://duewall.com
- API docs: https://duewall.com/api/
- Open-source adapters & snapshots: https://github.com/OneLight1688/duewall-adapters
Metadata
Release files for duewall 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| duewall-0.3.1.tar.gz | 6.8 kB | Without provenance | Details for duewall-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| duewall-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for duewall-0.3.1-py3-none-any.whl |
Total release size: 14.5 kB
Release files / duewall-0.3.1.tar.gz
| Download URL | duewall-0.3.1.tar.gz |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
943364734247340a00e5f12c18dc0ab60b8bba196225ee64fb294e3dd3fff23c
|
|
BLAKE2b-256 checksum How to use checksums |
b9de50733c284c10b542703e93f78121a77c06c29f9cacac0d607700dce36885
|
| 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.3.1-py3-none-any.whl
| Download URL | duewall-0.3.1-py3-none-any.whl |
|---|---|
| Size | 7.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
287cff188ec979ac6c5ae8c295526517707d798de8e2e22b486fe9f034760270
|
|
BLAKE2b-256 checksum How to use checksums |
b8de7986371c2888d97905cb3889c1351b0e435fb9d947ab84106e05dc3e3589
|
| 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.3.1
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.