large-transaction-monitoring

Explain a confirmed Solana transaction, including balance deltas, logs, compute usage, and a retry-safe error classification.

Track a crypto off-ramp / USDC-to-bank transfer by its id. Returns status, amount, currency, recipient and quote snapshots, deposit address, reference, and any error. Poll until the fiat bank payout completes. Pay 0.01 USDC.

Create a crypto off-ramp transfer: sell USDC and send fiat to a bank account. From a locked quote and a recipient, returns a transfer_id and a Base USDC deposit_address plus the exact amount to send. Fund it on-chain, then call /confirm-transfer. Converts stablecoin to a bank payout in 80+ currencies. Funding wallet KYC and sanctions enforced upstream. Pay 0.01 USDC.

CoinJoin / mixing transaction detection. Identifies Wasabi, JoinMarket, Whirlpool patterns plus generic peel chains.

Find large recent transfers for known wallets across Base, Ethereum, Arbitrum, and Solana

Decision procedure for when an agent's predictable onchain payment or trade needs mempool opacity. Covers: front-runnable pattern scoring for scheduled payments, recurring x402 settlements, and timer-driven DEX trades; value thresholds that trigger private-transaction relay routing; timing randomization and deadline jitter to break mempool prediction; slippage and priority-fee discipline for visible transactions; batch-and-reveal grouping for multi-part settlements; and the fallback ladder from

Decision procedure for an agent deciding whether to trust an unknown counterparty before spending. Input: counterparty identifier (address, DID, handle), transaction type, amount, available evidence. Output: verdict with tiered actions. Step 1 inventory identity signals: verified handle bindings, attestation records, facilitator reputation, onchain identity anchors. Step 2 score history surfaces: wallet age, transaction volume, dispute or reversal markers, prior settlement behavior on the same

Operational procedure for multi-agent fleets sharing one capped virtual wallet: reserving spend before payment, detecting race conditions when two agents claim the same remaining cap, applying priority tiers for arbitration, and reconciling settled, failed, and swept-back funds within the same wallet cycle.

Decision procedure for reconciling wallet-layer policy against agent-layer intent when a wallet provider enforces hard spend limits and merchant allowlists on agent virtual wallets. Detects three drift classes (HARD_BLOCK when the wallet rejects a legitimate payment, OVER_PERMISSIVE when the wallet allows merchants outside agent intent, BENIGN when intent sits inside wallet bounds), assigns a resolution action per class, sets reconciliation cadence before high-value payments and after policy

Procedure that grades what a wallet signature actually proves before an agent treats it as authorization. Classifies an incoming signature as one of three scopes: (1) payment-capability only, the signature proves the wallet moved value but nothing about intent; (2) delegated intent, the signed payload binds principal, agent ID, and purpose; (3) policy-conforming authority, the payload also references the governing policy, quote hash, or delegation record. Returns a verdict: accept as full

Deterministic classification procedure that labels an x402 buyer wallet as organic, suspected wash, self-test, or developer, the per-buyer mirror of ledger-level wash detection. Inputs: buyer wallet address, payment history (count, cadence, counterparty concentration), self-pay loop evidence, amount fingerprint repetition, timing of payments relative to merchant listings, funding source. Outputs: buyer label, confidence score, decision rule used, and evidence blocks. Thresholds: self-pay loops where payor equals payee or flows through 2-3 owned wallets within short windows classify as suspected wash; burst cadence with identical amounts to the same merchant across fresh addresses classifies as suspected wash; wallet that only pays its own listings or its own endpoints is self-test; wallet with regular organic counterparty diversity, varying amounts, and settlement receipts is organic; developer labels apply to testnet faucet funding or dev-tool endpoints. Falsifiers: low volume is not wash; a developer wallet that self-tests then buys organically must be re-labeled; burst cadence alone is not wash without counterparty concentration; a fresh address repeating the exact amount of a prior wallet is linkable and wash-suspect. Kill criteria: never label a wallet wash on cadence alone, never treat missing receipts as evidence of wash, never apply a label to a wallet with fewer than 3 distinct counterparties.

Cheap poll: has the spending authority over this Safe changed since you last looked? You pass the fingerprint this route gave you last time; it recomputes the current one and compares. Call it with no fingerprint to get a baseline. The fingerprint covers owners, threshold, guard, moduleGuard, the singleton implementation, and the whole module graph including the owners and threshold of modules that are themselves Safes -- a change one level down flips it, which a flat owner list would miss. It deliberately excludes the nonce, so ordinary transactions do not read as an authority change. Nothing is stored on our side: you hold the baseline, so there is no account and no subscription. No archive reads either, which is why this is cheap; when it reports changed, buy GET /safe-signer-drift for what changed and in which block. A truncated walk returns indeterminate, never unchanged. Required: chain_id and address. Optional: fingerprint.

Decision procedure for reconciling wallet-layer policy against agent-layer intent when a wallet provider enforces hard spend limits and merchant allowlists on agent virtual wallets. Detects three drift classes (HARD_BLOCK when the wallet rejects a legitimate payment, OVER_PERMISSIVE when the wallet allows merchants outside agent intent, BENIGN when intent sits inside wallet bounds), assigns a resolution action per class, sets reconciliation cadence before high-value payments and after policy changes, and emits a machine-readable reconciliation record with drift class, resolution, remaining headroom, and policy version hashes. Includes failure modes: provider API down, allowlist TTL expiry, stale agent intent after task reassignment, and multi-wallet providers with divergent policy APIs. Inputs: wallet policy snapshot, agent intent ledger, recent settlement history, provider error codes. Output: reconciliation verdict and record schema.

Whale-алерты: крупные переводы токена на Base за окно блоков (from/to/сумма/tx), с порогом

Last Day in Crypto: Brazil Holds, BIP-110 Stall, BTCPay Remote Access. Brazil's central bank set up 24-hour holds for some crypto transfers from 2027, the BIP-110-enforcing Bitcoin branch stalled after two blocks, and BTCPay restricted remote Lightning access after its active-exploit fix.

Get the global leaderboard of smart wallets

Base transaction receipt by hash for $0.001 USDC via eth_getTransactionReceipt.

Get the current transaction nonce for an EVM wallet on Base (or Ethereum) via eth_getTransactionCount. Use before broadcasting a transaction.

Peer-to-peer mempool observations from a node with 200+ direct peers, including pending txs before inclusion and large-swap detection (value, venue, gas). Pre-confirmation visibility a public RPC does not give.

A ranked snapshot of ANM holders at a pinned chain height — up to 1000 accounts with exact nANM balances as decimal strings, plus the total address count and the head it was taken at. The shape airdrops, governance weighting and distribution analysis actually need, in one call instead of thousands of balance lookups.

Endpoint specially designed for platforms that want to identify transaction data by the transaction title.

POST JSON: {"txid":"<64hex>","includeHex":false} mempool.space tx status. Does not broadcast. Prefer LNURL / Nostr tools on this host. Spec: https://api.major-miners.com/.well-known/l402-services

Verifiable call log: every signal this desk has published, timestamped and countable (?asset=BTC optional). Audit us for a penny before you spend a dime — no accuracy claims, compute your own. Descriptive research, not financial advice.

Verify a Base transaction actually did what a counterparty says it did: confirmation depth, success or revert, value, token, sender and recipient. Use it to confirm an inbound payment before releasing goods or data.