Kinetic Anvil
 Get in Touch
KINETIC › ANVIL
KINETIC ANVIL

Keep the recovery matter and its fund-flow trace in one record.

Anvil keeps the matter, traces BTC and ETH fund flows, and writes the map back to the record.

EXPLORE THE SANDBOX SEE WHAT ANVIL DOES

crypto.trace · Sandbox uses synthetic matter data

01 · MATTER
Recovery record
MATTER IDmatter_demo_04
SUBJECT WALLET0x742d...44e
CHAINETH
TRACE REQUESTED
03 · WRITEBACK
Fund-flow map
WALLETS06 observed
FLOW EDGES05 recorded
HYPOTHESES02 for review
RESULT ATTACHED
SYNTHETIC EXAMPLE · PRODUCT FLOW
One matter record
CONTEXT STAYS TOGETHER
BTC + ETH
FUND-FLOW TRACING
Conservative results
HYPOTHESES CARRY CONFIDENCE
Written back
RESULT ATTACHES TO THE MATTER
§ 01 · PRODUCT

One record for the matter and the trace

Keep the matter, trace inputs, status, and results together.

01 · RECORD

Keep the matter

Connect parties, judgment data, wallet inputs, jobs, trace maps, packets, ledger entries, and events.

02 · TRACE

Follow the fund flow

Trace BTC or ETH outflows across bounded hops.

03 · REVIEW

Write back the result

Store wallets, flow edges, terminal addresses, and confidence-labeled hypotheses on the matter.

§ 02 · TRACE

BTC and ETH fund-flow tracing

crypto.trace follows outflows across bounded hops and returns a structured map for review.

INPUT

Wallets, chain, and hop limit associated with a matter.

BTC

Outflows followed hop by hop.

ETH

Native ETH and ERC-20 outflows followed across bounded hops.

OUTPUT

Wallets, flows, terminal nodes, and confidence-labeled hypotheses.

BOUNDARY

Hypotheses require review. They do not establish custody, control, authority, or recovery.

CryptoAssetMapRESULT · SYNTHETIC
{ "matter_id": "matter_demo_04", "status": "succeeded", "wallets": [6 observed nodes], "flows": [5 fund-flow edges], "terminals": [3 terminal nodes], "exchange_hypotheses": [ { "basis": "labeled address", "confidence": "high" }, { "basis": "service-volume pattern", "confidence": "low" } ] }
§ 03 · SYSTEM OF RECORD

The trace remains connected to the matter

Anvil ties each trace and result to the matter that requested it.

01Matter

Parties, judgment data, and wallet inputs.

02Trace job

crypto.trace runs through the execution layer.

03Fund-flow map

Wallets, flow edges, terminals, and hypotheses.

04Record update

Result state and events remain available to connected systems.

§ 04 · TECHNICAL PROOF

A product institutions and developers can inspect

Review the contract, permissions, events, and SDK source.

45

Operations

Current dated contract across 11 resource groups.

✓

Credential-bound

Authenticated requests resolve within the credential's organization.

23

Event types

Signed webhook delivery supports connected systems.

2

SDK languages

Python and TypeScript SDK source under Apache-2.0.

QUICKSTART OPENAPI 3.1 VERSION 2026-07-05 TRUST STATUS
Current execution: crypto.trace, crypto.monitor, and impersonation.monitor are available. Remaining catalog verbs return 422 until shipped. Kinetic Anvil holds no client funds.
§ 05 · REFERENCE

Materials for technical, institutional, and academic review

DocumentationGUIDES + API REFERENCE ChangelogRELEASE HISTORY Institutional inquiryARCHITECTURE + ACCESS Academic inquiryPROTOCOL MATERIALS
§ 06 · ACCESS

Start with the product. Inspect the contract.

Use synthetic matter data to review the trace flow, or contact Kinetic about institutional requirements.

EXPLORE THE SANDBOX READ THE DOCS CONTACT KINETIC