PRDWatch Methodology

Live PRD Market

Price, 24-hour volume, liquidity and transaction counts are pulled from the tracked PRD/USDT Uniswap V3 market through DEX Screener. The dashboard caches results server-side so each visitor does not create a new upstream API request.

Historical Price

Price history uses GeckoTerminal OHLCV data for the PRD liquidity pool. Selected-range performance is calculated from the first and last available closing prices in that range.

Historical Market Metrics

The dashboard records rolling PRD market snapshots in PRDWatch's database for 24-hour PRD volume, 24-hour USD volume, liquidity, trades, fully diluted value and configured max supply. Historical OHLCV data may be used to backfill volume and price-derived FDV where reliable. Liquidity and rolling transaction-count history are collected locally from the time the feature is enabled rather than reconstructed from unrelated data.

Whale Watch

ERC-20 transfers are retrieved through Alchemy. A BUY is a PRD transfer from the known PRD/USDT pool. A SELL is a PRD transfer to that pool. Other large transfers remain TRANSFER unless a verified system-wallet label supports a more specific classification.

Top Holders

Current top-holder balances come from Ethplorer. PRDWatch records snapshots over time to calculate 24-hour and 7-day changes. A holder balance changing does not automatically mean the holder bought or sold.

Burn & Supply Pressure

Detected burns currently include PRD transferred to the Ethereum zero address or common dead address. Net supply pressure is current daily issuance minus detected 24-hour burns. Other protocol-specific burn mechanisms are not counted until their on-chain implementation is verified.

TRUU vs PRD

The deal checker uses a configured 1 TRUU = 1 PRD migration assumption and then applies the configured claim-tax model. The two whitepapers reviewed do not state that 1:1 migration ratio or the PRD claim-tax schedule. Effective TRUU cost per modeled net PRD equals TRUU price divided by the percentage of PRD retained after the configured tax. Gas, fees, slippage, vesting and migration-rule changes are not included.

Claim Tax

The PRDCTR and Truth whitepapers reviewed do not specify a PRD claim-tax schedule. PRDWatch currently retains a configured external model that starts at 52% and decreases one percentage point every seven days. This model must not be interpreted as whitepaper-verified protocol timing.

PRD Emissions

PRDCTR Whitepaper v1.3 states a 55B PRD target allocation to node rewards across all years, with Year 1 completed at 27.375B PRD, Year 2 at 13.6875B PRD or 37.5M/day, Year 3 at 6.84375B PRD or 18.75M/day, and annual halving thereafter. PRDWatch calculates the annual rollover automatically using the supplied operational timestamp of February 1 at 12:01 AM Central Time. That timestamp is not stated in the whitepaper, so it is labeled as an operator-supplied assumption rather than a whitepaper-verified date.

Truth Team Vesting

The Truth whitepaper states that the 5% team allocation has a two-year linear vest beginning when node fee payments start. This is a Truth team-allocation vesting rule and is not treated by PRDWatch as a general PRD holder claim lock.

Market Pulse

The Market Pulse is a transparent rule-based score, not an AI prediction. Positive or negative points come from 24-hour price direction, 5M+ PRD whale net flow, buy-versus-sell transaction counts, and liquidity direction when enough history exists. Scores of +3 or higher display Accumulation, -3 or lower display Distribution, and values between them display Neutral.

Advertising

Sponsored placements are clearly labeled and tracked separately from analytics. Ad impressions and clicks do not affect Market Pulse, market data, news ranking, holder analytics, or any PRDWatch calculations.

Site Analytics

PRDWatch uses first-party site analytics to measure page views and feature usage. A random browser identifier is hashed before storage; the analytics system records page paths, device category and external referring host rather than requiring a raw IP address for visitor counting. Analytics are used to understand site usage and do not affect PRD market calculations or rankings.

Personal Alerts

Alerts are opt-in. Browser alert settings and history are stored locally, while verified email subscriptions are stored server-side so email alerts can fire when the dashboard is closed. When Voice Alerts are enabled and the dashboard is open, PRDWatch evaluates supported web alert conditions on a recurring schedule and also checks for recent verified email triggers so the matching voice alert can play on the open site. Modern browsers can block automatic audio until the visitor interacts with the page; if that happens, PRDWatch holds the alert sound and plays it on the next click or key press. Browser notifications require the visitor's permission.

Wallet Lookup

Wallet Lookup reads public PRD and TRUU ERC-20 balances and recent token transfers for an Ethereum address through Alchemy. It does not connect to a wallet, request a signature, or access private keys.

News & Updates

Official PRDCTR destinations are pinned and labeled Official. Independent coverage is discovered through Google News RSS using PRDCTR-specific search terms and labeled News. PRDWatch filters obvious ticker-name collisions and does not treat third-party coverage as an official PRDCTR statement.

Wallet Names & Aliases

PRDWatch gives verified system wallets their confirmed public label. When available, a wallet’s verified ENS primary name is used next. Other anonymous public addresses receive a permanent, randomly generated two-word PRDWatch alias so repeated activity is easier to follow. These aliases are not claims about who owns a wallet. The underlying Ethereum address remains available from Wallet Details.

Wallet Intelligence Tracking

Wallet Intelligence begins when its collector is first installed. On its first successful run it attempts to collect from midnight America/Chicago that calendar day and records both the installation tracking time and the earliest event actually collected. Results are never described as lifetime trading or lifetime profit.

Exact PRD Swap Values

PRD trades come only from Swap logs emitted by the configured PRD/USDT Uniswap V3 pool. Signed pool deltas determine direction: PRD leaving the pool is a buy and PRD entering the pool is a sell. The corresponding six-decimal Ethereum USDT delta supplies the actual quote amount, USD value, and execution price. Ambiguous events retain no exact USD value and do not enter cost basis or P&L.

FIFO Tracked P&L

An exact observed buy creates a known-cost FIFO lot. Opening holdings and transfer-ins have unknown cost. Sells consume inventory FIFO; realized tracked P&L is calculated only for the portion matched to known-cost lots. Transfer-outs and burns consume inventory but create no profit or loss. Remaining known-cost lots use the current PRD market price for unrealized tracked P&L. Total Tracked P&L is known realized plus known unrealized P&L. Gas is not included, and these estimates are analytics—not tax accounting.

Trader Attribution & Exclusions

PRDWatch prefers a direct non-pool EOA participant. When a router or contract is the endpoint, the initiating transaction EOA may be used with its attribution quality recorded. Unreliable attribution remains preserved but unranked. Pools, routers, contracts, burn addresses, bridges, exchanges, treasuries, reserves, and other system wallets can be classified and excluded in protected wallet administration. Verified names continue to override ENS and aliases.

TRUU Trading Limitation

Primary TRUU trading occurs on XT, whose individual customer trades and wallets are not visible on Ethereum. PRDWatch therefore does not turn TRUU ERC-20 transfers into buys, sells, or wallet P&L. A transfer is not a trade. Wallet-level TRUU trading will remain unavailable unless a verified on-chain market is explicitly configured later, and even then it would not represent XT activity.

How PRDWatch Calculates Its Data