How Rektd Calculates Everything
Public on-chain ledger analysis without invented prices or hidden accounting shortcuts. Below is the current methodology for realised PnL, missed-upside classifications, chain-specific verification, caching, and public leaderboard privacy.
Bundle Privacy & Leaderboard Exclusion
On Rektd, you can inspect multiple wallets simultaneously by pasting comma-separated addresses or using the + Add Wallet bundle builder. This allows traders to combine their sniper bots, burner addresses, and storage vaults into one consolidated PnL statement.
Why Bundles Are Never Added to the Public Leaderboard
Wallet associations are private trading alpha. If Rektd indexed combined bundles on the public Leaderboard, anyone could deanonymize your entire wallet cluster, connect your personal vault to your public burner, and track your trade executions.
- Strict Leaderboard Filter: report pages explicitly skip leaderboard insertion whenever the request contains multiple addresses (
isBundle = true). A bundle may still use normal server-side analysis caches for performance, but its wallet combination is never published as a leaderboard entry. - No Public Bundle Association: Rektd does not expose the submitted wallet combination through the public leaderboard.
- Only Single Wallets Compete: Only standalone single wallets are eligible to appear on the public Leaderboard.
Multi-Chain Protocol Architecture
Rektd operates dedicated high-throughput indexing engines tailored to each supported blockchain:
Chain History + Venue Proof
Reads wallet history and balance deltas from the chain, then normalises venue-specific swap shapes into one accounting format. Dense or unusual wallets can use the secondary indexed feed while strict market checks remain source-aware.
- • Helius wallet history with indexed-feed fallback for dense or hard-to-parse wallets
- • SOL/USD is matched to the time of each trade; cost basis does not use today's SOL price
- • Market history combines cached charts, launch/venue data, and strict fallbacks instead of one universal feed
- • Focus cards use exact current on-chain mint supply for market-cap display; when historical supply at that old slot is not proven, estimate provenance stays in the card note while the number itself remains uncluttered
Transfers, Receipts & Verified Pool History
Walks wallet transfers, decodes receipts and gas, then independently verifies the market history needed by the report. Cheap current reads can use the chain's public RPC; immutable historical proof is checkpointed through archive-capable RPC sources.
- • Strict sell-history proof across eligible v2/v3/v4 pools, curves and chain-priced quote assets
- • Lifetime ATH is promoted only after archive-complete swap coverage; creation events prove the empty pre-pool prefix
- • Historical supply for focus cards comes from exact
totalSupply()calls at immutable blocks - • Receipts, pool trades and proof checkpoints are persisted so later wallets can reuse immutable work
Complete Means Proven
Rektd does not turn a partial market scan into a final result. The report tracks independent completeness for wallet history, basis, sell-market history, supply and ATH. When a strict proof cannot finish inside the page budget, completed checkpoints are saved and the next pass resumes from them instead of silently guessing the missing range.
Realised PnL & Weighted Average Cost
The headline PnL on Rektd is realised PnL: gains or losses from quantities actually sold on-chain. Open inventory is not mixed into that headline; when reliable current valuation is available, open-position value is shown separately.
When a wallet buys a token at multiple price points before selling, Rektd uses a quantity-weighted average cost for that wallet and token. Every buy updates one blended cost basis; a sell removes cost at that average.
Weighted Average Cost Example
After the sale, 10,000 tokens remain with $2,000 of blended cost basis ($0.20 each). Rektd does not use FIFO lot queues.
Jeets, Roundtrips & Paperhands
The three classic mistakes meme traders make. A miss is evaluated against the verified peak in the interval where that quantity was actually exposed — while held, after sale, or before reacquisition. Roundtrip measures the held interval; Jeet/Paperhand measure the post-sale interval, so a single exit can legitimately carry one of each when both intervals qualify. Their category totals are therefore not meant to be added into one combined "missed" number. It is not a blanket multiplication by a token's lifetime ATH:
Selling Green Too Early
You took profit (≥ 1.05x), but the token pulled a massive run after your exit (≥ 1.20x higher).
Holding The Peak Down
The coin ran up ≥ 1.25x while you held it, but you overstayed and gave back over 20% of peak gains before selling.
Panic Selling Dips
You panicked and took a loss (< 1.0x), only for the token to rebound (≥ 1.05x) without you.
Win Rate & Realised Trade Cycles
Rather than counting every single transaction as a separate trade (which artificially distorts stats for bots that execute micro-orders), Rektd consolidates buys and sells into Realised Trade Cycles per token:
- If you scale into a position with 4 DCA buys and exit in 2 sells, that represents 1 complete trading cycle.
- Win Rate Formula: Winning Realised Cycles / Total Realised Cycles. A still-open position enters once it has a priced sale in the selected period.
- Trade Multiple: For a closed trade row, exit value is compared with the cost assigned to that sold quantity.
Spam & Dust Filtering
Sub-dollar trades and leftover wallet dust are ignored to prevent bot transactions and malicious tracking airdrops from diluting your real performance.
Tokens received with zero purchase history are not treated as investments. Selling an airdrop counts as pure profit, but receiving scam spam never generates artificial losses.
Transfers between your own linked wallets are flagged as non-trading movements rather than buys or sells.
Daily PnL Calendar (UTC+0 Standard)
All daily trading calendars, streak calculations, and green/red day tiles are synchronized to Universal Coordinated Time (UTC+00:00):
- Daily Boundaries: Each calendar day opens at 00:00:00 UTC and closes at 23:59:59 UTC.
- Block Timestamp Integrity: Every swap timestamp is tied to chain time (
blockTimeon Solana and block timestamps on Robinhood Chain). - Identical Shared Cards: By standardizing on UTC+0, shared cards and verification links produce identical results for viewers across all timezones worldwide.