← all claims · /whales
xrpl.whales.whale_tier_threshold
Every displayed large_xfer/tagged event satisfies the selected tier threshold (default ≥100K XRP); walker-capture floor (≥50K XRP) and MCP-tool floor (≥100K XRP) are both named accurately wherever either is described.
yellow
Public-infrastructure dependent OR no independent cross-check path yet. Free-tier only until Batch B walker migration lands (post-soak, ~2026-08-31) and/or an independent verification walker is wired for this series.
What this claim says
- label
- Every displayed large_xfer/tagged event satisfies the selected tier threshold (default ≥100K XRP); walker-capture floor (≥50K XRP) and MCP-tool floor (≥100K XRP) are both named accurately wherever either is described.
- page
- /whales
- claim id (yaml)
whale_tier_threshold- behavior
BOUNDED- Layer 2 rules
- R6
- Layer 3 source
self-attested-only
Risk note
Rows displayed with amount_drops < tier_drops violate the pill's claim. R6 will catch this once implemented. Trustset events legitimately bypass the tier per the explainer copy (line 330) — R6 must exempt type='trustset'. Scope-widened 2026-08-04 after an external evaluator caught the two-tier threshold collapsing into a single "100K XRP" statement in methodology while the walker file's constant of the same name was actually 50K. Any copy that names `WHALE_XRP_THRESHOLD_DROPS` must disambiguate walker-capture (xrpl_stream.py, 50K) from MCP/display floor (mcp_tools_value_flows.py + app.py, 100K).
Evidence — code paths that back this claim
- templates/whales.html:326-338 tier pills (1m / 100k / 50k)
- templates/whales.html:363 'Streaming validated XRPL transactions ≥ N XRP'
- db.py:read_whale_events (tier_drops arg)
- xrpl_stream.py:WHALE_XRP_THRESHOLD_DROPS (walker capture, default 50k XRP)
- mcp_tools_value_flows.py:WHALE_XRP_THRESHOLD_DROPS (MCP + display floor, 100k XRP)
- templates/methodology.html §whales (must name both capture and display thresholds)