PricingDocsBlog
CA—
Launch app – free
  • Home
  • Analytics
  • Funnels
  • Retention
  • Live events
  • Docs
  • About
  • Blog
  • Whitepaper
  • Pricing
  • Trash
Larefe

Count people, not wallets

Larefe joins your programs and frontend into one stream, then groups wallets into likely-same-owner clusters, so funnels run on estimated users, not raw addresses.

~181M addresses. An estimated 40–70M people.a16z, 2025

Set up for free

  • First 1M events every month cost $0
  • No custom wallet instrumentation
  • Backfills your contract history on day one
Launch appRead the docs
Larefe AISample data

What can I help you with?

Ask about funnels, cohorts or a wallet…

Ask about any wallet

Larefe joins frontend events with decoded program instructions, so one funnel can start at a page view and end at a confirmed transfer. Ask in plain English; get the chart, the query and the wallets behind it.

Bring offchain data from CSV, Postgres and webhooks for the full picture.

Launch app - free
  • Trends
  • Funnels
  • Retention
  • Live events
  • Wallet clusters
  • and 7 more
Built-in tools for your agents:
TrendsFunnelsRetentionLive eventsWallet clustersSybil filterAttributionPathsWallet replayPriority fee analyticsLifecycleAlerts inboxPoints trackingSQLWebhooksDashboardsTrendsFunnelsRetentionLive eventsWallet clustersSybil filterAttributionPathsWallet replayPriority fee analyticsLifecycleAlerts inboxPoints trackingSQLWebhooksDashboards

Events, already decoded

Yes, the standard ones are labeled the moment you add an address. No, you don't have to write a subgraph first.

Decoded for you

TransferSwapMintBurnDepositStakeVoteBridgeClaimWithdraw

“You name it” events

vault.deposit_confirmedquest.completedpoints.claimedreferral.boundseason3.joinedwallet.connect_failedswap.quote_shownlp.position_openedbadge.mintedgovernance.delegated

How Larefe helps you grow onchain

1. Get the data in

Add a program address and drop in the web SDK. Larefe backfills every instruction, joins it to page views and campaign tags, and keeps indexing as slots land. 40+ other sources.

TidewellStable vaults. Boring on purpose.1,284 wallets online
Stable vault6.1% APY
0.42SOLMax
Connect SignDeposit
Why does my first deposit need SOL?
Every transaction pays a small priority fee in SOL. A brand-new wallet needs a little before its first deposit.
Message Tidewell…
larefe.capture() · 5 events
Live events
EVENTWALLETWHEN
claimrewards::claim()VBrH…iC69user #44121s ago
$wallet_connectbrowser extensionVBrH…iC69user #44124s ago
depositvault · 0.425uwD…bNFruser #33247s ago
transfershare token → walletVBrH…iC69user #441210s ago
$wallet_connectbrowser extensionWBrb…CCvquser #899913s ago
$pageview/points8adY…x12kuser #899616s ago
$tx_failedinsufficient funds for feeZYsi…eA3Wuser #350419s ago
claimrewards::claim()VBrH…iC69user #441222s ago
$wallet_connectin-app browserVBrH…iC69user #441225s ago
$pageview/pointsVBrH…iC69user #441228s ago
depositvault · 0.42VBrH…iC69user #441231s ago
Open live events
Priority fee analytics$program_call · vault.deposit
Compute units usedmedian 41,87010k50k90k
Value per depositmedian 0.42 SOL01.02.0
Time to first depositmedian 3m 12s0s5m10m
Priority fee paidmedian 0.000012 SOL00.0000180.000036
box p25–p75 · bar median · dot mean · whiskers 1.5×IQR
Larefe captures frontend and onchain events into one stream.

2. Query it with your agent (or use ours)

Larefe keeps a timeline for every wallet and every cluster. Ask Larefe AI, or your own agent, why deposits fell, and it follows the trail to the transaction that failed.

~/your-app — zsh
$ npx @larefe-protocol/sdk mcp add
AgentAdd to your agent
Why did vault deposits drop last week? Show me.
Larefe · 0 of 3 tools used
Found failed first depositsfailed: no SOL for the priority fee · 214 txs
Charted deposits by segmentnew vs returning wallets · 14 days
Read the failure tracevault.deposit · balance < priority fee
Deposits by wallet segment
Returning walletsNew wallets
Nov 3Nov 6Nov 9Nov 12Nov 16
View in Larefe
Reply to agent… larefe

3. Give your agent the alert to act on

Monitors watch your funnels and cohorts around the clock and file reports in your Alerts inbox. Each report carries the wallets and events behind it, so an agent can pick it up and start.

HomeChatsAnalyticsProductsSettings
Tidewell Search
Alerts inbox
ReportsMonitorsSettings
All priorities Newest first Triage mode T
P1fix(connect)Wallet connect fails in mobile in-app browsers#2043

Connect opens a blank screen for 9.4% of mobile sessions. Retry the handshake before redirecting.

Web SDKJust now
P2feat(onboarding)Explain the priority fee before the first deposit

Unfunded wallets stall at the first signature. Show the expected priority fee in SOL and offer the sponsored path.

Program eventsJust now
P2fix(points)Exclude cluster #77 from season points

412 wallets share one funder and claim inside the same window. Confidence: high.

Sybil filterJust now
P3fix(analytics)Restore the deposit_confirmed event#2041

The new vault page stopped sending confirmations. Restoring it keeps the funnel accurate.

Monitor · Deposit funnelJust now
agent — ~/tidewell
⏎ send · 96% context left

4. Check that the fix worked

When a change ships, Larefe re-runs the same funnel on the same wallet segment and posts the before and after. If the number didn't move, the alert reopens and the loop starts again.

Sponsor the first priority fee for new wallets #482

Larefe · merged into main by you

Merged
Conversation 3Commits 1Files changed 1+4 −1

Larefe opened this from Alert #12

First deposits fail for wallets with no SOL for the priority fee, so new depositors leave. Adds a fee payer for wallets funded in the last 24h, plus a test.

Larefe on Larefe, right now

We index our own contracts and site with Larefe. These alerts fired on our product; each one was triaged, fixed and checked by a person on the team.

37

alerts that Larefe raised and a person resolved in the last 7 days

  1. 1
    Flag a 38-wallet cluster claiming the same quest in one block

    alert #1188 · 19 min ago

  2. 2
    Restore the claim_confirmed event after the rewards page deploy

    alert #1186 · 22 min ago

  3. 3
    Split the first signature into its own funnel stage for new wallets

    alert #1183 · 31 min ago

  4. 4
    Retry wallet connect once on in-app browsers before redirecting

    alert #1181 · 31 min ago

  5. 5
    Exclude bridge-in transfers from the first-deposit cohort

    alert #1176 · 49 min ago

Pricing, without the sales call

Every plan starts with 1.0M free events and 10,000 wallet replays a month. After that you pay per event, and the price per event drops as you grow.

9.9M
100K1M10M100M500M
Estimated monthly bill$320

≈ 1.86 SOL at the reference price ($172.4)

Start free
Per-event price by monthly volume
Events / monthPrice per event
0K–1.0MFree
1.0M–2.0M$0.00005
2.0M–15M$0.000034
15M–50M$0.000029
50M–100M$0.000021
100M+$0.000015

What $LAREFE does

  • Pay any invoice in $LAREFE and take 20% off.
  • Stake 25,000 $LAREFE to add 1.0M free events every month.
  • Vote on which chains and decoders ship next.

Access and discounts only — no yield, no promises about price.

Questions people actually ask

No. It is a cluster of wallets that are likely controlled by the same owner, inferred from shared funding sources, shared deposit addresses and timing. Larefe never attaches a name, an email or an identity to a cluster, and every chart shows estimated users next to raw wallets so you can see the gap.
With a published heuristic you can read and override: a common funder within two hops, claims inside the same short window, and cluster size (large airdrops have cut clusters above 20 wallets). Each flag carries a confidence level. No filter catches every farmer, and a strict one also catches real users, so the default is conservative and the threshold is yours. How the filter works.
No. Add the program address and Larefe decodes its instructions and events from the published interface, then backfills history. On the frontend, one line of SDK captures page views, clicks and wallet connects.
A page view, an autocaptured click, a wallet connect, a decoded instruction or a transfer. Backfilled history is counted once, when it is first indexed.
This deployment indexes Solana; new slots show up in roughly 2 seconds. Coverage is listed per chain with its freshness in the docs — we would rather list fewer chains than claim all of them.
Pay any invoice in $LAREFE for 20% off, stake 25,000 $LAREFE to add 1M free events a month, and vote on which chains and decoders ship next. It is access, not an investment: there is no yield.
A wallet address that can be linked to a person can be personal data, so we treat it that way: hashed visitor IDs, no third-party cookies, an EU hosting option and a data-processing agreement. Read the privacy policy.

Shameless CTA

If the funnels didn't sell you on Larefe, maybe these classic marketing tactics will.

3 people (would have) added Larefe to their cart**if this were a real cart
Larefe Web, boxed
LarefeNew!Larefe Web
NOTFINANCIALADVICE
Free tier1M eventsEVERY MONTH

*Larefe is a web product and cannot be installed from a CD. We checked. Twice.

FEE-FREE

Larefe Web

Digital download*

Select your plan

1M events / month, then it pauses

Starts at:

$0 FREE >1 left at this price!!

Get started

Hurry: slot 522,935,708 is being indexed right now.
Act now and get $0 off your first event.

indexer head · Solana slot

Product

TrendsFunnelsRetentionLive events

Learn

DocsBlogWhitepaperPricing

Company

AboutPrivacyTerms

Network

CA—

Comms

GitHub

© 2026 Larefe. Wallet clusters are estimates, never identities. Not financial advice.