StudioOutsiderEstimate a process

POC candidate / application in preparation / v0.1

Blockchain analysis needs context, traceability and human review.

LedgerIntel is an early-stage prototype for investigating blockchain addresses, transactions and fund flows through graph analysis and AI-assisted explanations.

wallet contextfund flowsgraph analysishuman review
Request a private presentationSee the prototype scope
LedgerIntel project shellBlockchain intelligence R&D surface

Problem frame

Public blockchain data is visible, but a defensible conclusion is still hard work.

Relevant context is spread across networks, explorers and data providers. LedgerIntel explores a single analytical workflow that keeps source context, uncertainty and human judgement visible.

SRC

Fragmented sources

Problem
Wallet activity and related context live across different networks, explorers and providers.
Approach
A controlled integration layer requests relevant records through defined API and MCP flows.
Purpose
The analyst can review connected context without manually switching between every source.
Evidence
source coverage / freshness / unavailable-result rate
GRF

Relationships are not a list

Problem
Transaction tables alone do not clearly show address relationships and movement paths.
Approach
Graph expansion, exploratory clustering and fund-flow views organize connected entities and transfers.
Purpose
Potentially relevant relationships become easier to inspect and document.
Evidence
trace depth / graph size / evidence links
REV

Risk labels need explanation

Problem
A single score can hide missing data, assumptions and false-positive risk.
Approach
AI-assisted explanations are treated as decision support, with sources and uncertainty kept visible.
Purpose
A qualified person remains responsible for verification and the final conclusion.
Evidence
source accuracy / indeterminate rate / reviewer decision
LOG

Analysis needs a trail

Problem
An insight is difficult to review later when inputs, versions and decisions are not recorded.
Approach
The project direction includes reproducible queries, status handling and a reviewable evidence trail.
Purpose
Findings can be challenged, corrected and repeated as data changes.
Evidence
query trace / source version / review status

Prototype surface

The current integration layer defines six analytical workflows.

These are development interfaces and investigation paths, not a claim of complete chain coverage, certified AML capability or production readiness.

WALAPI / MCP FLOW

Wallet context

Request risk indicators and transaction history for a supplied address and supported chain.

address / chain
  • risk indicator fields
  • transaction history path
  • source context when available
TRCAPI / MCP FLOW

Fund-flow tracing

Explore inbound and outbound movement around a wallet within a bounded trace depth.

inflow / outflow
  • bounded depth
  • volume context
  • trace relationships
BRGAPI / MCP FLOW

Cross-chain context

Review bridge transfers and exploratory exposure to supported bridge protocols.

source / target chain
  • bridge identification
  • transfer context
  • exposure path
GRFAPI / MCP FLOW

Address graph

Expand connected addresses and explore possible clustering patterns for analyst review.

nodes / edges
  • graph expansion
  • cluster candidates
  • relationship context
AIXASSISTED REVIEW

AI explanations

Generate an assisted classification or explanation that remains subordinate to evidence and expert review.

context / confidence
  • transaction classification
  • risk-factor summary
  • explicit uncertainty
AMLINTEGRATION POINT

Watchlist checks

Connect AML, watchlist and sanctions sources where suitable licensed data is available.

flagged / clear / unknown
  • three-state outcome
  • source attribution
  • human verification

Development direction

A broader architecture is a roadmap, not a list of completed features.

The project concept connects blockchain sources, ingestion, analytical storage and an intelligence layer. Each stage must be validated separately before it can be described as production capability.

  1. 01

    Data sources

    Blockchain nodes, network APIs and explorers with explicit provenance and licensing.

  2. 02

    Controlled ingestion

    Bounded collection, normalization, freshness tracking and failure states.

  3. 03

    Analytical storage

    Relational, graph and event-oriented stores selected for a proven workload.

  4. 04

    Intelligence layer

    Graph analysis, retrieval and AI-assisted explanation with evaluation and guardrails.

  5. 05

    Application and reporting

    Review workflows, evidence export and specialist-facing interfaces after security validation.

Trust boundaries

The page says what the project is — and equally clearly what it is not.

LedgerIntel is presented as a POC candidate in active R&D until data quality, security, legal and operational gates are evidenced.

POC

Application in preparation

LedgerIntel is being prepared for proof-of-concept funding calls while the integration prototype and evidence package continue to mature.

candidate / not awarded or funded
HIL

Human in the loop

Scores, labels, possible links and AI explanations require verification by a qualified person.

decision support / not a verdict
SEC

Security gate

A public or invite-only application requires isolated secrets, authenticated access, monitoring and tested recovery.

no public app link
VAL

Validation gate

Coverage, false positives, false negatives and unavailable states need documented evaluation.

no unsupported accuracy claim

Responsible disclosure

Experimental analysis must not look like a compliance verdict.

The public project page deliberately avoids unsupported customer, accuracy, certification and production claims.

Decision support

Outputs support investigation and do not determine whether an address or person has committed wrongdoing.

No professional advice

The prototype does not provide legal, compliance, tax, financial or regulatory advice.

Changing coverage

Networks, sources, functions and availability may change during development.

Synthetic demos

Public demonstrations should use synthetic or explicitly approved data, never secrets or client evidence.

Studio Outsider products

It is presented separately from LedgerIntel because the two products have different maturity, risk and validation paths.

Open FiskalBill

POC / private evaluation

Have a concrete blockchain-analysis scenario?

We can discuss the required networks, available data sources and a bounded development pilot without collecting wallet or case details through this public page.

Request a technical conversation