Skip to content

Replace watched-wallet leaderboard with single-address investigation model - #10

Merged
sirmrdrgod merged 1 commit into
mainfrom
feat/single-address-search-model
Jul 10, 2026
Merged

Replace watched-wallet leaderboard with single-address investigation model#10
sirmrdrgod merged 1 commit into
mainfrom
feat/single-address-search-model

Conversation

@sirmrdrgod

Copy link
Copy Markdown
Contributor

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

  • Single-address search workflow — the user enters a wallet address or ENS name, and the demo assembles read-only analytical layers (balance, 7d activity, 7d volume, largest transfer, counterparties, trend badge, 12-week cadence) for that one address.
  • Address-keyed fixture of clearly-synthetic demo addresses (+ one ENS-style demo key). Only fixture addresses resolve; any other well-formed input honestly shows a "no fixture evidence" panel rather than fabricating data.
  • Removed the ranked leaderboard, the whale/exchange/institution/protocol taxonomy, the entity-type filter chips, and the aggregate KPI strip — and added a regression test guarding against their return.
  • Own lightweight 0x/ENS format validation (not the product's identity layer); no real ENS resolution; the "hand-off to related surfaces" note is conceptual/text-only.
  • README + docs updated to describe the single-address model.

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 build succeeds. git diff --check clean. Secret scan clean.

Draft for human review per repo agent conventions.

🤖 Generated with Claude Code

…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
sirmrdrgod marked this pull request as ready for review July 10, 2026 04:07
@sirmrdrgod
sirmrdrgod merged commit 3736516 into main Jul 10, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant