Understand holder behavior without flattening every wallet
CryptoPunks market structure is shaped by collectors, funds, lenders, traders, vaults, and protocol contracts that may touch many wallets. Aggregate entity intelligence connects wallet clusters, scorecards, holdings, PnL, loans, bids, listings, and accumulation behavior.
Last updated July 4, 2026. Wallet/entity analysis lives in the app; this page summarizes aggregate publication policy and public workflow.
What entity behavior can explain
Accumulation
When major holders add Punks, supply can tighten in specific cohorts or trait groups.
Distribution
Listings from concentrated holders can change floor pressure and near-floor depth.
Lending activity
Borrowing and refinancing behavior can signal liquidity needs or collateral stress.
Wallet clustering
Grouping related wallets avoids double-counting the same participant's activity.
What PunkPredictor entity intelligence tracks
The app's entity layer joins wallet membership, market-event history, portfolio valuation, loans, and scorecard percentiles. It is meant to answer "who is acting?" without pretending every address is an independent participant.
Wallet membership
Manual entities, algorithmic clusters, direct wallets, proxy wallets, ENS names, social handles, and versioned entity records are resolved into a stable analysis target.
Holdings and value
Current Punk count, featured or most valuable Punk, estimated portfolio value, realized PnL, unrealized PnL, total profit, and claim history.
Market activity
Buys, sales, transfers, internal transfers, bids, cancelled bids, asks created, asks removed, wraps, unwraps, event counts, 30-day activity, and volume.
Lending and risk
Active loans, repaid loans, defaults, current loan exposure, lender and borrower behavior, and collateral context are connected back to entity behavior.
Trader and collector scorecards
Wallet and entity scorecards split market behavior into trader and collector identities. That separation matters because a high-frequency flipper, a long-hold collector, a fund, and a protocol vault can all look active while meaning very different things for the market.
Trader score
Trading identity uses realized profit, win rate, flip ROI, flip time, trade volume, turnover, active trade days, and activity density.
Collector score
Collector identity uses Punk count, hold time, grail count, longest hold, minted Punks, and low lifetime turnover.
Percentile context
Scores become ranks such as top-percentile trader or collector only after comparing against the latest eligible entity population.
Dominant identity
An entity can be more trader-like, more collector-like, or balanced. The public interpretation should preserve that distinction.
How entity grouping changes market interpretation
- Resolve the actor Search can match entity names, tags, handles, ENS names, profiles, or raw wallet addresses before routing to a wallet or entity view.
- Group related wallets carefully A participant using hot wallets, vaults, custody addresses, or proxy wallets should not be counted as multiple unrelated buyers or sellers.
- Separate infrastructure from participants Protocol vaults, marketplace helpers, wrappers, and lending contracts are labeled or excluded where they would pollute trader and collector rankings.
- Read activity through context Listings, bids, loans, transfers, and sales mean different things depending on whether the actor is accumulating, distributing, refinancing, or moving inventory internally.
Leaderboard and actor context
The leaderboard layer makes aggregate entity behavior scannable: wallets, profit, current holdings, claimed Punks, buys, sales, spent, received, event counts, recent activity, volume, transfers, bids, wraps, asks, and latest event timing. The important SEO angle is not a thin list of addresses; it is the explanation of why those fields change market structure.
Privacy and publication policy
PunkPredictor should publish aggregate holder behavior, not low-context address pages designed only for indexing. Public SEO pages should explain market structure while keeping sensitive or uncertain entity labels out of crawlable surfaces.
Public entity pages should be conservative
Publish aggregates
Good public pages explain wallet clustering, scorecard dimensions, market-event categories, and cohort-level behavior.
Avoid thin address pages
Indexing one page per address without strong context creates doorway risk and can expose low-confidence labels.
Mark uncertainty
Manual, algorithmic, protocol, proxy, and versioned entities should be treated differently in both UI and crawlable copy.
Use verified freshness
Entity score snapshots, featured Punks, and rank fields should only be published when the source snapshot has a clear data-as-of contract.
Related market intelligence
Lending
Connect holder behavior to collateral, defaults, refinancing, and risk.
Trait prices
See how entities can affect supply in scarce cohorts.
Underpriced listings
Track model-vs-ask gaps that may reflect seller urgency.
Wallet analysis
Open the interactive wallet product for address-level inspection.
CryptoPunks entity FAQ
Why group CryptoPunks wallets into entities?
A collector, fund, trader, or protocol can use multiple wallets. Entity grouping helps interpret accumulation, distribution, liquidity, and lending behavior without treating every address as a separate market participant.
What does PunkPredictor measure for CryptoPunks entities?
PunkPredictor measures wallet membership, Punk holdings, claimed Punks, buys, sales, transfers, bids, asks, wraps, active loans, portfolio value, realized and unrealized PnL, trader score, collector score, and score percentiles where data quality allows.
Why separate protocol entities from collectors and traders?
Protocol vaults, wrappers, lending contracts, and marketplace helpers are infrastructure. PunkPredictor labels or excludes those entities in ranking contexts so they do not compete with human collectors, funds, or traders.
Does PunkPredictor publish private wallet labels?
No. Crawlable SEO pages should use aggregate, non-sensitive entity behavior. Low-context individual wallet/entity pages should not be published as public SEO surfaces.