WAKE

The onchain trading environment on Base has matured rapidly since the network's launch. Daily new token deployments routinely exceed several thousand, the majority of which are short-lived. For active onchain participants, the bottleneck is no longer information availability — every transaction is public — but signal extraction. The data exists; the interpretive layer does not.

Existing tools fall into two categories. The first is the dashboard category: aggregated market data, leaderboards, and historical analytics. These tools tell users what has already happened. The second is the bot category: automated alerting on price movements, volume spikes, and liquidity changes. These tools tell users what is happening, but typically at the same moment retail also sees it.

What is missing is the interpretive layer between raw onchain activity and reactive market data: the wallets and tokens that consistently lead the rest of the market, surfaced in time to act on. This is the gap WAKE addresses.

The product is designed around a single thesis: in any liquid market, certain participants are systematically earlier than others. On Base, those participants are visible by address. Their behavior can be tracked, scored, and mirrored. Similarly, the wallets and patterns that precede token distribution events can be characterized in advance. Both of these signals exist in the data; both require infrastructure to surface in usable time.

WAKE is that infrastructure.

The retail participant on Base operates at a structural information disadvantage. By the time a token's price action becomes visible in standard dashboards, three classes of participant have already acted:

Insiders and deployers. The deploying wallet, allocated wallets, and connected addresses typically have privileged knowledge of intended marketing timing, supply unlocks, and exit plans. Their behavior precedes public price movement by minutes to hours.

Snipers. Wallets that consistently buy in the first three blocks of a new token launch. These wallets operate algorithmically, are often funded from shared sources, and exit on predictable patterns.

Smart money. Wallets with verifiable history of profitable Base trading. These wallets are typically operated by experienced traders or small funds. Their entries are informed by superior signal infrastructure and their exits are typically clean.

By the time a retail participant identifies an opportunity through social signal or visible price action, all three of the above classes have already taken their positions. The retail entry is, statistically, the late entry.

WAKE inverts this asymmetry by making the activity of the smart money class visible in real time, and by surfacing the exit behavior of the insider and sniper classes before it reaches retail visibility.

The system does not predict price. It surfaces the actions of participants whose actions historically precede price.

WAKE's architecture is built around two distinct intelligence layers that operate independently but are consumed through a single interface.

Layer 01 — Smart Money Mirror

This layer continuously evaluates every active wallet on Base against a multi-factor scoring model. Wallets that exceed defined thresholds are added to the mirror set. Their subsequent buy and sell transactions are surfaced in a live feed with sub-block latency from confirmation.

The mirror set is dynamic. Wallets that cease to meet the scoring thresholds are demoted; new wallets that demonstrate qualifying behavior are promoted. The set is recalculated continuously, with the top-tier set (TOP_100) reassessed every 24 hours.

Layer 02 — Exit Liquidity Detector

This layer continuously monitors every active token on Base for pre-distribution signatures. Seven distinct flag categories are evaluated independently. When a token triggers one or more flags above defined severity thresholds, an alert is published with full diagnostic context.

The detector is signature-driven. Its accuracy improves as the historical signature library expands. At publication, the library contains over forty distinct pre-distribution patterns drawn from analysis of Base launches over the prior eighteen months.

The two layers are independent. A token may be the subject of a smart money buy in Layer 01 and an exit warning in Layer 02 simultaneously, in which case both signals are surfaced. The interpretation is left to the operator.

The Smart Money Mirror is the central feature of WAKE. This section describes the wallet evaluation methodology in detail.

Wallet eligibility. A wallet is eligible for scoring if it has executed at least 50 distinct token trades on Base, holds a wallet age of at least 30 days, and shows non-trivial position sizing (defined as average position size exceeding 0.1 ETH).

Scoring inputs. Each eligible wallet is scored on the following dimensions:

> REALIZED_PNL_USD         total realized profit since wallet activation
> UNREALIZED_PNL_USD       mark-to-market on current positions
> WIN_RATE                 percentage of closed positions with positive return
> AVERAGE_HOLD_TIME        median hold duration across closed positions
> CAPITAL_EFFICIENCY       PnL per dollar of capital deployed
> TRADE_COUNT              total closed positions
> RECENT_ACTIVITY          activity weighting decayed over 90 days

Tier assignment. Wallets are bucketed into tiers based on composite score:

> TOP_10                   highest-scoring 10 wallets active in last 30 days
> TOP_100                  next tier of qualifying wallets
> TOP_1000                 broad mirror set
> WATCH                    wallets approaching qualification

Behavioral tagging. In addition to scoring, each wallet is tagged with behavioral attributes derived from its trading pattern:

> EARLY_BUYER              consistently enters within first 5% of price discovery
> MOMENTUM_TRADER          enters on volume confirmation
> LONG_HOLDER              median hold time exceeds 7 days
> SCALPER                  median hold time under 1 hour
> CONTRARIAN               enters during volume retracements
> ROTATOR                  exits one position to enter another in same block

Tags are not exclusive; a wallet may carry multiple tags simultaneously. Tags inform the interpretation of any given trade but do not affect scoring.

Confidence scoring on individual trades. When a mirrored wallet executes a trade, the trade is published with a confidence score from 0 to 100. The confidence score reflects how characteristic the trade is of the wallet's historical pattern. A trade executed by an EARLY_BUYER tagged wallet within the first 5% of a new token's volume curve will score higher confidence than the same trade executed near a token's all-time high.

The Exit Liquidity Detector continuously evaluates every active token on Base against seven flag categories.

Flag 01 — DEV_DUMP

Triggered when the deploying wallet, or any wallet connected to it through funding or transaction history, executes a sell larger than 0.5% of supply within a single transaction. Severity scales with size relative to circulating supply and proximity to launch.

Flag 02 — SNIPER_EXIT

Triggered when wallets identified as snipers (bought within first three blocks of token deployment) begin coordinated selling. The flag activates when more than 25% of the sniper cohort has reduced position by 50% or more within a 60-minute window.

Flag 03 — TOP10_DISTRIBUTION

Triggered when the top 10 holders by token balance reduce aggregate position by more than 5% within a single 24-hour window. The flag accounts for the difference between active distribution and routine portfolio rebalancing.

Flag 04 — LP_REMOVAL

Triggered when any liquidity provider removes more than 10% of total LP from the token's primary trading pool. The flag is muted if the removal is by a known liquidity manager (e.g., automated rebalancers) and elevated if the removing wallet is connected to the deployer.

Flag 05 — BRIDGE_OUT

Triggered when a top 50 holder bridges tokens off Base in a single transaction exceeding 0.25% of supply. Bridge-out events frequently precede off-network distribution.

Flag 06 — LARGE_SELL

Triggered when any single wallet executes a sell exceeding 1% of circulating supply, regardless of wallet classification. This is the most general flag and the most prone to false positives.

Flag 07 — COORDINATED_EXIT

Triggered when multiple flags above fire within a compressed time window, weighted by the connectivity graph of the involved wallets. Coordinated exits are the highest-severity event class and frequently precede the largest price declines.

Severity scoring. Each flag carries a severity rating: LOW, MEDIUM, HIGH, or CRITICAL. Severity is determined by the magnitude of the underlying event relative to historical baselines for tokens of similar age, supply, and liquidity profile.

Pattern matching layer. In addition to the discrete flag system, each token's current state is continuously compared against a library of historical pre-distribution signatures. A match exceeding 75% similarity triggers a pattern alert in addition to any active flags. Pattern alerts include a reference to the historical analogue and the eventual outcome of that analogue.

This section formalizes the mathematical structure of the WAKE scoring system. The model is intentionally transparent: every score on the platform is reproducible from the public input data using the formulas described here.

Wallet composite score. A wallet's composite score is calculated as:

score = (
    0.30 * normalize(realized_pnl_usd) +
    0.20 * normalize(win_rate) +
    0.15 * normalize(capital_efficiency) +
    0.10 * normalize(average_hold_time_score) +
    0.10 * normalize(trade_count) +
    0.10 * normalize(recent_activity) +
    0.05 * normalize(unrealized_pnl_usd)
)

Each input is normalized against the active wallet population using a percentile rank, producing a score on the range [0, 1]. The composite is then scaled to the range [0, 100] for display.

Average hold time scoring. Hold time is not monotonically rewarded. A wallet with a median hold of one hour and one with a median hold of six months are both scored highly; a wallet with a median hold of two days is scored lower. This is because consistent strategies (scalping or position trading) both demonstrate execution skill, while inconsistent strategies do not.

Capital efficiency. Defined as realized PnL divided by total capital deployed across all positions. This metric distinguishes wallets that generate returns from skill from wallets that generate returns from size.

Recent activity decay. Activity older than 90 days is weighted at 50%. Activity older than 180 days is weighted at 25%. Activity older than 365 days does not contribute to scoring. This ensures that historically dominant wallets that have ceased trading do not occupy the leaderboard indefinitely.

The Exit Liquidity Detector's pattern matching system is the most data-intensive component of WAKE. This section describes its operation.

Signature library. The signature library at publication contains 47 distinct pre-distribution patterns derived from supervised analysis of 8,400 Base token launches over the prior 18 months. Each signature is represented as a multivariate time series of normalized features (holder concentration, volume profile, LP composition, wallet flow) over the 24 hours preceding a distribution event.

Live matching. Every active token's live state is continuously compared against the signature library using dynamic time warping (DTW) on the feature vectors. DTW is selected over simpler distance metrics because pre-distribution patterns frequently occur at varying time scales — a distribution event may unfold over two hours or twenty hours, and the underlying signature is invariant to this scaling.

Match threshold. A match score above 0.75 triggers a pattern alert. The threshold was selected to balance precision and recall against the historical signature set; lower thresholds produce more false positives, higher thresholds miss valid signals.

Continuous learning. The signature library is updated on a rolling basis. Confirmed distribution events that did not match any existing signature are characterized and added to the library. Existing signatures that produce false positives at scale are refined or retired.

The WAKE terminal is the primary user-facing interface. This section describes its construction.

Frontend. Built in React with Vite, deployed as a single-page application. Routing handled by the application router. State management uses native React hooks; no Redux or external state library is required given the application's structure. Styling uses Tailwind with a custom design token system.

Realtime layer. The terminal connects to the WAKE event stream via WebSocket. The stream delivers structured events (smart_money.buy, smart_money.sell, exit.flag, pattern.match) with sub-second latency from block confirmation.

Indexer. Block-level events on Base are consumed by a custom indexer that maintains the wallet behavior model, the token state model, and the signature matcher in continuous synchronization with chain state. The indexer is designed for replay: the entire system state can be reconstructed from any historical block.

API. A REST API exposes the same data consumed by the terminal, for users with Tier 3 access who wish to build their own interfaces or automated systems on top of WAKE's signals. The API is documented in the public docs and is rate-limited based on tier.

Webhook system. Tier 3 users may register webhook endpoints to receive event pushes directly. Webhook payloads are signed using HMAC-SHA256 with a secret provisioned at registration.

Self-hosting. The terminal frontend is open source and may be self-hosted. The indexer and event stream are operated by the WAKE team and are accessed by self-hosted instances via API key.

$WAKE is the access token for the WAKE terminal. This section describes its full mechanical structure.

Launch protocol. $WAKE is launched as a fair-launch token on Base via the Bankr deployment protocol. Bankr uses the Clanker token standard, which deploys tokens directly through a bonding curve with no presale, no private round, and no team allocation.

Total supply. 1,000,000,000 $WAKE. Fixed. The contract's mint function is disabled at deployment. The supply cannot be inflated by any party at any time.

Distribution. Every $WAKE in circulation is acquired through the open market. The bonding curve serves as the price discovery mechanism during the initial launch phase; once the bonding curve completes (graduation), liquidity migrates to a DEX on Base and the LP tokens are burned permanently. After graduation, $WAKE trades exclusively on the open market.

Contract structure. The $WAKE contract is immutable. There is no proxy pattern. Ownership is renounced to the zero address at deployment, meaning no party (including the deploying wallet) can modify contract behavior, transfer ownership, or execute administrative actions. The contract has no blacklist function, no pause function, and no transfer restrictions.

Tax structure. Buy tax: 0%. Sell tax: 0%. Transfer tax: 0%. $WAKE generates no fees of any kind from holder activity.

Utility. $WAKE serves a single function: gating access to the WAKE terminal at tiered levels. The token is not a security, is not staked, generates no yield, and does not entitle holders to any share of platform revenue. The platform generates no revenue at the time of publication; if and when revenue mechanisms are introduced, they will not flow to $WAKE holders by virtue of their holding.

Risks. Holding $WAKE exposes the holder to price volatility, smart contract risk (mitigated by immutability and renouncement), platform risk (the WAKE team may cease operations), and access risk (the terminal may be discontinued, in which case $WAKE retains no utility). Section 12 addresses risk disclosures in greater detail.

WAKE terminal access is gated by $WAKE balance. Three tiers exist.

TIER_01 — 1,000,000 $WAKE (0.1% of supply)

Read-only smart money feed. Visibility into TOP_10 wallets only. No alerts. No dashboard access. No API access.

TIER_02 — 5,000,000 $WAKE (0.5% of supply)

Full smart money mirror feed (all tiers). Full Exit Liquidity Detector with all seven flags. Email alerts at configurable thresholds. Dashboard access with all leaderboards and visualizations. One saved filter profile.

TIER_03 — 20,000,000 $WAKE (2.0% of supply)

All TIER_02 features. Webhook integrations with signed payloads. Full REST API access with elevated rate limits. Unlimited saved filter profiles. Custom pattern uploads to the matcher. Priority data feed (sub-block latency vs. block latency for lower tiers).

Tier verification is performed by a balance check at the time of terminal access. Holders whose balance falls below their tier threshold lose tier-level access immediately. There is no lockup, vesting, or staking requirement; the gate is purely a balance check.

The roadmap below describes the publicly committed milestones for the project's first twelve months. Dates are targets, not guarantees.

Phase 01 — Launch (Month 0)

Token deployment via Bankr. Site publication. Closed beta cohort onboarding begins. Public repo opens on Gitlawb.

Phase 02 — Smart Money Mirror live (Month 1–2)

Indexer operational against Base mainnet. Live mirror feed available to Tier 2+ beta cohort. Email alerts active.

Phase 03 — Exit Liquidity Detector live (Month 3–4)

Flag system operational. Pattern matcher initialized with launch signature library. Severity scoring tuned against live data.

Phase 04 — API and Webhooks (Month 5–6)

REST API publicly documented. Webhook system live for Tier 3. Self-hosting documentation published.

Phase 05 — Expansion (Month 7–12)

Signature library expansion via continuous learning. Additional wallet behavioral tags. Dashboard visualizations expanded. Custom pattern uploads for Tier 3.

The roadmap is published as a commitment. Slippage on any milestone will be communicated publicly via @WakeOnBase with explanation. The repository commit history serves as the public verification of build progress.

This section is required reading for any prospective $WAKE holder.

$WAKE is not an investment. $WAKE is a utility token granting access to a software product. It is not a security. It does not entitle holders to revenue, dividends, equity, governance rights, or any claim against the WAKE team or any associated entity. Holding $WAKE is not an investment in the WAKE project. Any expectation of price appreciation is speculative and the holder bears full responsibility for that speculation.

The WAKE terminal is software, not advice. Signals surfaced by the terminal are descriptions of onchain activity. They are not recommendations to buy, sell, or hold any token. The WAKE team makes no claim that following the signals will produce positive returns. Past performance of mirrored wallets does not predict future returns. Trading decisions made on the basis of WAKE signals are the sole responsibility of the trader.

Technical risk. The WAKE terminal may experience downtime, data inaccuracies, indexer lag, or false signals. The team will work to minimize these but cannot guarantee uninterrupted or accurate service.

Smart contract risk. The $WAKE contract is immutable and ownership is renounced. This eliminates upgrade and admin risk but does not eliminate the risk of latent vulnerabilities in the contract itself. The contract is verified on Basescan and may be reviewed by any party.

Regulatory risk. The regulatory treatment of utility tokens varies by jurisdiction and is subject to change. Holders are responsible for compliance with the laws of their own jurisdiction.

Platform risk. The WAKE team may discontinue operation of the terminal at any time. In such event, $WAKE retains no utility and the holder retains only the token itself, which has no claim against the team.

No fiduciary duty. No relationship of trust or fiduciary obligation exists between the WAKE team and any $WAKE holder. The team makes no representations beyond what is published in the documentation and code.

Public Base network documentation; Bankr / Clanker token standard documentation; published post-mortems of Base token launches over the prior 18 months. Full reference list is maintained in the public repository.

BONDING_CURVE       Pricing mechanism where token price is a function of supply
CLANKER             Token standard used by Bankr for fair-launch deployments
DTW                 Dynamic time warping; time-series similarity metric
EXIT_LIQUIDITY      Tokens being sold by insiders into retail buying pressure
FAIR_LAUNCH         Token launch with no allocation, presale, or private round
GRADUATION          Completion of bonding curve and migration to a DEX
LP                  Liquidity provider; tokens held to enable trading
LP_BURN             Permanent destruction of LP tokens; prevents pool drainage
MINT_FUNCTION       Contract method that creates new tokens; disabled in WAKE
RENOUNCEMENT        Transfer of contract ownership to zero address
SIGNATURE           Time-series pattern characterizing a market behavior
SMART_MONEY         Wallets with verifiable history of profitable trading
SNIPER              Wallet that buys within first blocks of a token launch

WAKE consumes data from the following sources:

> Base RPC endpoints              block-level transaction data
> Basescan API                    contract verification status
> Base DEX subgraphs              pool and liquidity data
> Secondary DEX subgraphs         additional venue activity
> Direct contract reads           token balance and supply data

All data sources are public. WAKE adds no proprietary data; the platform's value is in the aggregation, scoring, and presentation of public data, not in privileged data access.