// A PRODUCT PROPOSAL FOR BLOCKWORKS

Investigate stablecoin
supply changes.

Screen USD-pegged assets, inspect supply history and chain balances, and save a research brief for review. Supply observations come from public DefiLlama data. The Sources workspace adds Blockworks dataset and research reads when authorized access is configured.

Built by Anthony Spezzano
Independent showcase · No Blockworks affiliation

RESEARCH WORKFLOWPUBLIC DATA

// Supply comparison → sourced brief

01
question

What changed in reported supply?

02
source

Public DefiLlama stablecoin data

provider ID · current supply · prior supply
03
observation

Absolute and percentage supply change

delta = current − previous
04
output

Markdown brief + JSON source record

01Select an assetUSD-pegged stablecoins
02Compare supplyDay, week, or month
03Export the briefObservation and source record
— 01 WORKING PROTOTYPE

Compare reported supply.

Select an asset and comparison period. Inspect the values behind the change.

PUBLIC DATA / DEFILLAMA
OBSERVATION / AWAITING SOURCE

Loading the source data.

Values appear only after a successful source response.

Show the evidence JSON
No observation yet.

Supply change alone does not establish transfers, net inflows, demand, reserve quality, or redeemable liquidity. Fetch time is shown; the upstream response does not establish a measurement timestamp.

— 02 THE BLOCKWORKS EXTENSION

// API + MCP / ACCESS UNVERIFIED

Add research
to the numbers.

Browse Blockworks dataset definitions, read historical series, and retrieve research through the Sources workspace. Live reads require authorized access; successful results can be attached to a brief with their query and source timestamps.

View Blockworks Data
INTEGRATION STATUS

Adapter implemented and fixture-tested. Live dataset coverage and account entitlements remain unverified.

01

Discover the dataset

tabular_catalogtimeseries_catalog

Find the relevant tables and time series. Check asset identity, metric definitions, units, historical coverage, and update frequency.

02

Retrieve and validate

tabular_datatimeseries_data

Retrieve current and historical values. Keep source timestamps and missing values; calculate changes only across compatible observations.

03

Search the research

search_documents

Search research and news for the asset and period. Include citations and publication dates. Label possible explanations separately from measured changes.

04

Test the complete workflow

Have analysts review and export the brief. Track time to a usable result, citation coverage, unsupported claims, and whether they return to the workflow.

Illustrative workflow, not an executed tool trace.

— 03 SELECTED WORK

Data products in practice.

Selected work in stablecoin operations, integrations, and developer tooling.

SELECTED IMPLEMENTATIONS

Stablecoin observatory

Inspect stablecoin collateral, facilities, and receipt evidence in a read-only workspace. Source expiry and coverage gaps are visible alongside the data. Historical flow ingestion remains unfinished.

Open workspace Private access may be required.

Settlement Desk

A Relay reference integration for inspecting payment obligations, diagnosing quotes, and investigating receipts. Live observations are identified separately from simulated cases.

Explore the reference Read-only demonstration. No payment execution.

Replicant

A writing and review workspace with 20 documented MCP tools. Includes scoped access, access revocation, generation allowances, and saved work that persists between sessions.

Open the studio Some operations require authenticated access.

Signet Explorer

Inspect Orders and Filler attribution across the Host and Rollup chains. Protocol views and health checks help developers investigate cross-chain settlement.

Explore the testnet Testnet tooling; no mainnet scale claim.

/// NEXT: ANALYST VALIDATION

Start with the analyst’s
daily stablecoin brief.

Validate the desk alongside analysts preparing a daily brief: check supply changes, read the related research, and export the evidence. Their missing fields and manual steps would guide the next API and MCP improvements.

Discuss the integration