Work in progress · building with design partners

Understand what your users do onchain.

OnchainStory turns protocol positions, wallet activity, and capital flows into product intelligence your team can act on. See who is arriving, what they do, which integrations they use, where capital moves, and which changes matter.

Request a private demo See what OnchainStory reveals

Private protocol dashboard. Evidence behind every insight. No frontend SDK required for core onchain coverage.

aave.onchain-story.com/overview Sample data

Active suppliers: 12,480+3.1%
Net flow: −$12.4m7d
30d retention: 68%+2 pts

Sample accounts behind this week's change
Account	Segment	Integration	Change
0x1f…a3c4	Whale · 214d	Router · Exact	−$4.10m
0x9b…07de	Supplier · 96d	Direct · Unknown	−$2.65m
0x54…be21	Returning · 12d	Smart account · Probable	+$1.30m
0xc2…5f10	Whale · 410d	Aggregator · Exact	−$1.05m

Built for protocol teams

Evidence behind every insight
Read-only onchain data
Single-tenant deployment
No frontend SDK required

Platform

TVL tells you what changed. OnchainStory tells you who changed it — and what happened next.

Protocol teams still piece together user behavior with dashboards, one-off queries, wallet explorers, and manual investigation. Each module below turns one of those investigations into a maintained, reusable view.

User Explorer

Search your supported protocol population with financially meaningful filters instead of raw event queries.

Current and peak value, supply, collateral, debt
Tenure, active-capital days, assets held
Integrations and other protocols used

Capital Flow

Follow where meaningful capital came from and where it went after leaving, with exact and inferred routes kept apart.

Entry and exit sources
Cross-protocol destinations
Share-of-wallet and migration patterns

Evidence Layer

Every claim links back to the accounts, positions, transactions, source blocks, and calculations that produced it.

Confidence labels: Exact, Probable, Unknown
Explicit unknowns instead of silent zeroes
Reproducible, versioned insight rules

Insights and Watchlists

Deterministic rules surface what changed; AI groups and prioritizes the facts without inventing them.

Withdrawals followed by a competing venue
First-seen users from a known integration
Whale share-of-wallet declines

Protocol Overview

Cohort retention, net flows, integration usage, and version migration — each aggregate drills into the accounts behind it.

Which segment caused this week's outflow
Whether new collateral retains capital
Whether borrowers move to a new version

Semantic Packs

Each protocol is modeled through its own pack: contracts, positions, accounting, lifecycle, integrations, segments, and rules.

Aave V4 pack in the initial pilot
Reusable model, not a one-off dashboard
Selective cross-protocol context

Scope

Protocol-wide coverage, not a sampled wallet list.

Every protocol account

Current and historical accounts are discovered from onchain evidence, including users who arrive through third-party applications or call the contracts directly.
Exact positions, not estimates

Supply, collateral, debt, health, yield, and net value are verified against protocol state at a recorded block. A failed read stays explicit instead of becoming a zero.
Context beyond your protocol

Wider portfolio and capital-flow context is refreshed when it can change an insight, so entries and exits have a source and a destination.
Evidence on every claim

Each insight links to the accounts, positions, transactions, and blocks behind it, with its confidence stated rather than implied.

The first semantic pack targets Aave V4. We publish coverage and performance numbers once a pilot dataset validates them — not before.

Solutions

One evidence base. Different decisions.

The same maintained account universe answers the questions each team keeps investigating separately today.

Product and growth

Understand adoption, retention, user lifecycle, asset combinations, and the behaviors behind aggregate change. Discover what deserves a product response.

Integrations and BD

Measure attributed users, capital, activity, and retention. Identify which partners acquire new protocol usage and which mostly route existing users.

Leadership

Start from a concise view of the most material changes, then drill into segments, accounts, and evidence without waiting for a custom analysis.

Content and community

Find timely, defensible stories about migrations, returning users, new collateral adoption, and whale behavior — with the evidence attached.

Risk-adjacent research

See position health and protocol context where they explain user behavior. Specialist market, solvency, and governance risk analysis stays outside the product.

Data and engineering

Skip rebuilding indexers, position accounting, and cross-protocol matching for every new question your team wants to ask.

Security

A private workspace, on your terms.

Each deployment is isolated, read-only against protocol data, and analyzes public onchain accounts only. It never holds keys and never requests a signature.

Single-tenant deployment

Independent credentials, session secrets, and a read-only data mount per customer.
Public data only

Public protocol accounts are analyzed. Addresses are never enriched with private personal data or linked to a person without defensible evidence.
No write access, ever

The platform reads chain state. It never submits a transaction or requests a signature.
SOC 2 Type II and GDPR In progress

Formal certification and assessment are not yet complete. This line will state a date and auditor once they are.

Workspace policy

Sample data

Multi-factor authentication

Required for every workspace member
IP allowlisting

3 ranges configured
API key rotation

Every 90 days
Public share links

Disabled for this workspace

Unrecognized IP blocked

Sign-in from an unlisted range was rejected · 2 min ago

FAQ

The questions protocol teams ask first.

Is this another analytics dashboard?

It is a product-intelligence layer built around protocol accounts, exact positions, capital history, and reusable behavioral insights. It includes aggregate views, but every metric is designed to drill down to the users and evidence behind it.

Do we need to add a frontend SDK?

Not for core onchain coverage. OnchainStory discovers protocol activity from onchain evidence, including interactions through third parties or direct contract calls. Optional first-party data can improve application or campaign attribution.

Can you identify which frontend a user chose?

Only when the evidence supports it. A known router, smart account, or bundler gives Exact onchain evidence; recognizable call paths may be Probable; customer-provided application data is Attributed. Direct protocol calls stay Unknown, because the chain alone cannot prove which interface initiated them.

Does AI generate the insights?

Deterministic rules generate the underlying insight occurrences from structured facts. AI explains, groups, and prioritizes those facts. Every statement retains its evidence and its uncertainty.

Which protocols are supported?

The initial proof of concept is built around Aave V4. The platform adds other protocols through reusable semantic packs rather than one-off dashboards; each pack is announced once it is validated.

Is every address treated as one person?

No. Addresses and protocol accounts stay separate by default. Relationships are used only when they have a defensible source and a stated confidence level.

Design partners

Bring us the protocol questions your dashboards cannot answer.

We are inviting a small number of DeFi protocol teams to become design partners. A first engagement turns your protocol's account and position semantics into a private intelligence workspace, then focuses the product on the questions your team repeatedly investigates.

Tell us which protocol you work on and the three user or capital questions you most want answered.