Enter app

Product 04 / Data & Reconstruction

On-chain data withfund-admin accuracy.

Syncrone replays every wallet from its first transaction, turns each event into a ledger entry, prices it at the block and reconciles it to your records. The same ledger powers NAV, performance and risk, and your systems can read it through the Portfolio API.

Enter appAPI reference
Coverage
5,000+ protocols · 30+ chains
Also
Hyperliquid fills · Solana · manual positions
History
Replayed from the first transaction
Ledger
Chain · block · timestamp · hash · USD at block
Portfolio API
One key, one schema, every chain
§ 01 · Historical reconstruction

Books from inception.Not from onboarding.

Most tools index from the day you connect. Syncrone replays the chain from your fund's first on-chain interaction through the same engine as today's data, so cost basis, cash flows and daily valuations exist for the months before you signed up.

Indexed from onboarding
TWR · visible history
+30.1%
Track record
21 months
Transactions replayed
0
Positions rebuilt
0
Replay log00 of 48 sampled
  1. No history before onboarding.

Fig. 1·The same sample fund, seen by a tracker connected in January 2025 and by Syncrone. Toggle to compare.

§ 02 · Capabilities

Raw chain events in.A fund ledger out.

  1. 01

    Every venue in one ledger

    5,000+ protocols across 30+ chains, Hyperliquid perpetuals built from executed fills, Solana holdings and DeFi positions, and manual positions for anything not visible on-chain. One set of positions, one NAV.

    • 5,000+ protocols
    • 30+ chains · Hyperliquid · Solana
  2. 02

    Reconstructed, not backfilled

    History is replayed from real events, not estimated from today's balances. Entry dates, cost basis and daily valuations come from the same methodology as live data, with no spreadsheet bridging the gap.

    • From the first transaction
    • Same engine as live data
  3. 03

    Events classified into entries

    Transfers, DeFi interactions, fills, funding payments and reward claims, each recorded with chain, block, timestamp, hash and USD value at the block. Cash flows sit beside transactions, so every NAV bridge has a source.

    • Classified events
    • Cash flows for NAV bridges
  4. 04

    Reconciled to your records

    Wallet, entity and token registries with point-in-time snapshots. Your internal records are matched to on-chain data, and breaks are flagged before a report is frozen.

    • Point-in-time registries
    • Breaks flagged before close
  5. 05

    Spam filtered out

    Tokens airdropped to fund wallets without being asked for are filtered out of positions and NAV, so the book reflects what the fund actually holds.

    • Spam filtering
    • Clean positions and NAV
  6. 06

    The same book, through the Portfolio API

    Holdings, positions and performance from organization down to asset, through the same figures the app shows. Priced and reconciled, not raw balances you still have to price.

    • x-api-key per organization
    • Cursor pagination, 500 rows a page
§ 03 · Portfolio API

One key. One schema.Every chain.

The Portfolio API serves exactly the figures the app shows. Build models and reports directly on reconciled data, without the months of pipeline work it usually takes.

  • GET/positionsNet value, collateral, debt and yield metrics
  • GET/holdingsDirect wallet balances
  • GET/assetsTokens inside each position
  • GET/performancePnL, ROI, TWR, APR from organization down to asset

x-api-key auth · keys issued per organization · cursor pagination, 500 rows a page

curl "https://api.syncrone.fi/api/performance\
?org_id=org_7Kq2&from_date=2026-07-01&to_date=2026-09-30" \
  -H "x-api-key: $SYNCRONE_API_KEY"
200 OKapplication/json
1{
2 "start_date": "2026-07-01T00:00:00Z",
3 "end_date": "2026-09-30T23:59:59Z",
4 "organizations": [
5 {
6 "org_name": "Sample Fund I",
7 "number_of_wallets": 14,
8 "metrics": {
9 "initial_value_usd": 71203118.52,
10 "net_flow_usd": 2500000,
11 "final_value_usd": 77425634.08,
12 "strategy_pnl": 1310442.17,
13 "market_pnl": 2412073.39,
14 "realized_pnl_usd": 893210.44,
15 "unrealized_pnl_usd": 2829305.12,
16 "time_weighted_return_pct": 5.08,
17 "apr_pct": 20.15
18 },
19 "wallets": [
20 "…14 wallets"
21 ]
22 }
23 ]
24}
✓ strategy + market = realized + unrealized = $3,722,515.56
✓ initial + net flow + P&L = final value
§ 04 · Who uses it

Read by the peoplewho sign off on it.

§ 05 · In practice

How it worksin practice.

What do you need from us to start?

A list of wallet addresses. Syncrone reconstructs positions and history from the chain, so there is no data migration. Instruments outside on-chain indexing are added as manual positions.

How far back does history go?

To each wallet's first on-chain transaction. Every event since then is replayed through the same engine as live data.

Do you need custody or signing permissions?

No. Syncrone reads public chain state for the addresses you add. Nothing is signed, and no keys are shared.

Can we load the data into our own warehouse?

Yes, through the Portfolio API: positions, holdings, assets and performance, with one key per organization and cursor pagination at 500 rows a page.

§ 06 · The rest of the platform

One engine.Every view of the same book.

Data & Reconstruction

Send a wallet list.We'll rebuild the rest.

Book a demo to see your wallets replayed from their first transaction into one reconciled ledger.

Enter appAPI reference