Documentation

Methods and coverage.

How Cluvy distinguishes a reported relationship from a verified transaction.

Case sources

The case follows a curated set of Bitcoin and Ethereum addresses. Reported labels and event times are attributed to the references below. The blockchain provider is queried independently when opening evidence.

Evidence and lookup

Bitcoin evidence includes observed inputs and the selected output. Multiple inputs can fund one output. A direct input/output match establishes transaction participation, and attribution remains a separate matter.

Ethereum receipts cover top-level value and ERC-20 transfer logs. When the receipt is unavailable, an Ethereum index can provide a separately labelled result. Ethereum address discovery covers recent indexed activity. The address-history RPC fallback is marked partial. Cached evidence retains the successful read timestamp.

Monitoring

Single-wallet and group rules establish a baseline before recording matching transfers. Your private rules and delivery history are separate from the shared case ledger. Discord and Slack are optional. Ambiguous sends stay marked unknown.

Case index

Signed-in visitors can refresh a rotating batch of case wallets. The VPS runner can continue refreshing when browsers are closed. The first read establishes a baseline. Later observed outgoing transfers are shown in Movement Log and RSS, with labels for pending and confirmed activity.

Wallet coverage shows the last successful read of each address. A read becomes stale after 20 minutes. If a later read fails, the ledger retains the last successful timestamp and balance.

API