Replace watched-wallet leaderboard with single-address investigation model - #10
Merged
Merged
Conversation
…model Aligns this public demo with the current Whale Watcher concept. The prior demo modeled a ranked "watched wallet" leaderboard (8 wallets, entity-type filter chips, aggregate KPIs) — a pattern that actually belongs to the separate Holder Wall product. The real Whale Watcher is a single-address search tool. - Replace the leaderboard with a user-entered wallet-address / ENS search that assembles read-only analytical layers (balance, 7d activity, 7d volume, largest transfer, counterparties, trend, 12-week cadence) for one address. - New address-keyed fixture (clearly-synthetic hex-safe demo addresses + one ENS-style demo key). Only fixture addresses resolve; any other well-formed input honestly reports "no fixture evidence" rather than fabricating data. - Remove the whale/exchange/institution/protocol taxonomy, ranked list, entity filter chips, and aggregate KPI strip. - Own simple 0x/ENS format validation (not copied from the product's identity layer); no real ENS resolution; conceptual (text-only) mention of hand-off to related surfaces, no real cross-app navigation. - Update README + docs for the single-address model; add a regression test asserting an unknown address degrades honestly and the leaderboard strings never return. Fixtures-only, read-only, no wallet connection, no signing, no live provider.
sirmrdrgod
marked this pull request as ready for review
July 10, 2026 04:07
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
An alignment audit against the WalletWall product found this demo modeled a ranked "watched wallet" leaderboard (8 wallets, whale/exchange/institution/protocol filter chips, aggregate KPIs like "Tracked Wallets" / "Median Readiness") — but the real Whale Watcher is a single-address search-and-inspect tool. The leaderboard + entity-type pattern actually belongs to the separate Holder Wall product. The demo was honest but reflected a superseded model (the byproduct of an earlier "demote to fixture-only" simplification).
What changed
Public-safety boundary
No product source, private routes, Dune query IDs/SQL, signal/scoring internals, or production data copied. Fixtures-only, read-only, no wallet connection, no signing, no live provider spend. It demonstrates the concept, is not the complete production app, and its fixture output is not production analysis. No implication that WalletWall publicly monitors or endorses any fixed wallet list.
Validation
npm test→ 43/43 pass (incl. leaderboard-regression guard + honest-not-found test).vite buildsucceeds.git diff --checkclean. Secret scan clean.Draft for human review per repo agent conventions.
🤖 Generated with Claude Code