THE MANIFEST

“Lazarus, come forth.” And he that was dead came forth, bound hand and foot with graveclothes. JOHN 11:43

FOUR DAYS IN THE TOMB.A man called by name, walking out of his own grave still bound in his burial cloths. The bystanders do not move to help him. They are too busy being afraid of what they are watching.

THE MARKET HAS ITS OWN VERSION.It happens every week on Ethereum. It happens every day on Base. A token deployed years ago, written off, begins quietly on-chain to receive buyers again. Holder counts inflect. Liquidity is reinforced. By the time the bystanders look up from their feeds, the chart is vertical and the trade that mattered closed eight hours ago.

THE THESIS, IN ONE LINE.Markets bury thousands of tokens every cycle. A small fraction are exhumed. The exhumation leaves a fingerprint on-chain. This document describes the fingerprint, and the engine that reads it[1].

WHAT LAZARUS IS NOT.Not a signal aggregator. Not a Telegram pump group with a subscription page. Lazarus is infrastructure: an indexer, a scoring engine, an execution layer, and a safety layer, built to recognize a community takeover while it is still a transaction pattern, before it becomes a tweet.

EVERY TOKEN FOLLOWS THE SAME ARC.A team deploys a contract. A liquidity pool is seeded. Attention floods in, peaks within days or weeks, then recedes. Volume falls. Holders stop adding. The dev wallet goes silent. The chart flat-lines. Most tokens never breathe again.

A SMALL SUBSET DO.The mechanism is what the on-chain community calls a community takeover, or CTO. A token whose original team has departed but whose contract is structurally intact (LP burned or locked, ownership renounced, no malicious mint or fee functions) gets adopted by a new community. Sometimes that community is organized. Sometimes it is a single accumulator with conviction and a Telegram group. Either way, the on-chain footprint is distinctive.

THE INFORMATION ASYMMETRY.In the majority of successful CTOs we have studied, on-chain accumulation precedes the off-chain social signal by between four and forty-eight hours[2]. Holder counts inflect first. Smart-money wallets enter first. Liquidity is reinforced first. The Telegram link, the X spaces, the influencer mention, all of that arrives later. By the time it does, the price has already repriced.

WHY THE ASYMMETRY PERSISTS.Detection requires infrastructure most participants do not run. An archive node. An indexed corpus of every dead token on the chain. Real-time vigil over every swap touching that corpus. Holder accounting maintained incrementally per block. A wallet labeling system that tells a fresh buyer from a returning veteran. The barrier is not intelligence. It is plumbing[3].

THE SHORT VERSION.The chain narrates the revival before the timeline does. The work is to listen.

FIRST, DEFINE A CORPSE.To find a revival you must define what was buried. Lazarus uses a deliberately conservative, multi-axis definition. A token enters the dead-token corpus when it satisfies a combination of quantitative and qualitative criteria.

THE QUANTITATIVE FLOOR.Contract age must exceed 180 days. Trailing 30-day average daily volume must fall below $500. Unique active holders, defined as wallets with non-zero balance that have transacted in the trailing 90 days, must number fewer than 50. The deployer wallet must show no contract interactions for at least 90 days. The most recent liquidity addition must precede the present by at least 60 days. A token failing any of these tests is not yet considered dead. It is declining, and the indexer continues to track it under a separate state.

THE QUALITATIVE PARTITION.Beyond the floor, the corpus is partitioned into four categories. Each has its own revival probability and its own typical CTO signature.

THE CORPUS IS REBUILT NIGHTLY.New entrants are added as their criteria mature. Previously-dead tokens that show life are promoted out of the corpus and into the active vigil set, where they receive higher-resolution tracking. The corpus is the universe of opportunity. The vigil set is the universe under active observation.

NOT AN EVENT. A SEQUENCE.A community takeover resolves into seven recognizable stages, each with its own on-chain signature, each emitted as a distinct telemetry record inside Lazarus. The stages do not always present in clean order, and a small fraction of revivals collapse before completing the arc. The modal revival traverses all seven, and the early stages are the most consistent.

STAGE 0 · DORMANCY.Baseline. The token is in the corpus, scored low, monitored but emitting nothing. STAGE 1 · SCOUT ACCUMULATION.One to three wallets enter, sizes small but deliberate, often labeled smart-money by historical pattern matching. The first whisper, almost imperceptible by design[4].

STAGE 2 · BROAD ACCUMULATION.Five to thirty wallets, distributed buys, often coordinated through a private chat the indexer cannot see. The on-chain tell is the holder-count inflection: the trailing 30-day baseline breaks. First stage at which the score crosses the lower alert threshold.

STAGE 3 · LP REINFORCEMENT.A treasury wallet for the new community adds liquidity. Slippage drops. Depth thickens by a margin that does not happen by accident. STAGE 4 · SOCIAL IGNITION.Telegram and X presence appear. The off-chain world finally mirrors what the chain has been narrating for hours.

STAGE 5 · CHART BREAK.Volume goes parabolic. Price discovery begins. STAGE 6 · VIRAL.Influencers enter, FOMO sets the bid. STAGE 7 · SETTLEMENT.The token finds a new equilibrium and matures, or attention rotates and it re-dies. Either way, by stage 6 the position should already be ladder-exiting. By stage 7 it should be closed.

WHERE LAZARUS IS USEFUL.Between stages 1 and 4. Beyond stage 4 the asymmetry collapses. The rest of the market sees what is happening with no special tooling. Lazarus does not chase late-stage entries. The system is calibrated for false negatives over false positives. Better to miss a revival than to buy a fake one[5].

THE DATA LAYER.Self-hosted archive nodes on Ethereum and Base. Full historical state. No dependency on third-party RPC providers in the indexing or scoring path, because those providers rate-limit, drop logs under load, and reorder events in ways that corrupt downstream state. An archive node is the floor.

THE EVENT INDEXER.Block-by-block log subscription. Transfer, Swap, Mint, Burn, OwnershipTransferred, Sync. State is maintained continuously, not polled. Reorgs are handled by retaining the last 64 blocks of mutable state and replaying when a reorg crosses that boundary[6].

UNIVERSE CONSTRUCTION.A nightly batch builds the dead-token corpus from the criteria in Chapter II. The batch is idempotent and deterministic. Same inputs always produce the same corpus. This matters for backtesting and for adversarial review.

THE REVIVABILITY FILTER.Each corpus member passes through a structural filter before scoring is allowed to fire. LP status is checked across Unicrypt, Team Finance, PinkLock, and the standard burn addresses. Ownership renouncement is verified by reading the contract directly. Honeypots are caught by simulating a buy and an immediate sell against forked state. Tax round-trip is measured to flag tokens whose on-chain economics make a revival uninvestable even if signal is real[7].

REAL-TIME VIGIL.Websocket subscription to swap and transfer events on the revivable universe. Sub-block latency from event observation to scoring engine input. The vigil set is bounded so that observation cost stays fixed under universe growth.

HOLDER ACCOUNTING.Maintained incrementally, transfer-event driven. No periodic full rescans. Per-token holder count is current to the last processed block. Holder velocity is the first derivative of that count, smoothed.

WALLET LABELING.A backfill of confirmed CTO participants seeds the smart-money set. New wallets are scored on early-entry pattern. Funding lineage is traced one hop back to detect bots and Sybil clusters. Labels are reviewed quarterly and decay if a wallet stops participating in successful revivals.

STRUCTURE OF THE COMPOSITE.The Lazarus score is a weighted sum of normalized component signals: S = Σ wᵢ · normᵢ(xᵢ). Each component is bounded to [0, 1] by a calibration curve. The weights wᵢ sum to 1. Exact weights are reviewed monthly against backtest PnL and held private. Structure is public, calibration is private.

THE COMPONENT SIGNALS.Holder velocity (first derivative of unique holders). Buyer diversity (Gini coefficient over recent buy sizes). Smart-wallet presence (count of smart-labeled wallets in the trailing window). LP delta (net liquidity change). Volume-to-liquidity inflection. Price-action sub-signal (used as a confirmation, never as a primary driver).

THRESHOLDS AND THEIR LOGIC.Two thresholds gate behavior. ALERT at 60 emits a notification and starts higher-frequency tracking on the token. EXECUTE at 82 is the bar for auto-execution, and only fires for users who have explicitly opted in. The gap between the thresholds is intentional. It gives the user time to review before capital moves.

PRECISION OVER RECALL.The model is tuned for false negatives. The cost of buying a fake revival is materially worse than the cost of missing a real one. The system would rather stay out of ten ambiguous setups than enter a single one that re-dies on the way up.

SCORE LIFECYCLE.A score is per-token. It rises with signal accumulation, decays with inactivity, and resets to baseline if structural conditions change (LP pulled, ownership re-acquired, contract proxied to a new implementation). A reset is loud. The system stops trusting prior state.

OPT-IN ONLY.Auto-execution is gated behind explicit per-user enable. The default state is alerts-only. Most users stay in alerts-only for weeks before flipping the switch, and the system encourages it.

PRE-TRADE RE-CHECKS.Every safety check that ran in the universe build runs again at execution time. Honeypot resimulation against current forked state. LP depth recheck against the live pool. Ownership recheck. Tax round-trip recheck. None of these checks are cached. The state of a contract at universe build is not the state of the contract at execution.

PRIVATE MEMPOOL ROUTING.MEV Blocker on Base. Flashbots Protect on Ethereum. The transaction does not enter the public mempool. Sandwich risk is reduced to zero in the common case, materially in adversarial cases.

SLIPPAGE DISCIPLINE.Capped per trade. Driven by simulation, not by user input. The simulator quotes the round-trip against current pool state and refuses to submit if the quoted slippage exceeds the cap. This is not negotiable at execution time.

PER-TOKEN ISOLATION.Each token gets a separate execution wallet. Blast radius is contained. PnL accounting is clean. A single hostile contract cannot drain the rest of the portfolio because it never had access to it.

POSITION MANAGEMENT.Configurable exit rules per token: hard stop, trailing stop, take-profit ladders, time stop, rug-detector exit, liquidity-degradation exit. The ladders are the default. Rug-detector and liquidity-degradation exits are always armed regardless of user configuration.

BUDGETS, ENFORCED INDEPENDENTLY.Global budget cap, per-token cap, per-trade cap. Enforced by an independent risk worker that the buy and sell workers cannot override. The risk worker is the source of truth for available headroom. Any execution that would exceed headroom is rejected at submission.

LOSS LIMITS WITH TEETH.Daily loss limit triggers an automatic halt. Weekly loss limit requires a manual reset before trading resumes. The reset is intentionally inconvenient. It exists to interrupt the user's emotional state, not just the bot's.

THE KILL SWITCH.Reachable from a Telegram command, a local CLI, and a dashboard button. All three converge to the same primitive: halt all workers, mark open positions for safe exit, suppress new alerts. Resume requires explicit human action.

WORKER ISOLATION.Buy worker and sell worker run as separate processes. The death of the buy worker cannot prevent the sell worker from exiting open positions. Heartbeat monitoring auto-restarts crashed workers and pages an operator if a restart loop is detected.

PAPER MODE FIRST.The first month is paper-trade by default. The user sees real signals, watches the system make real decisions against simulated capital, and only flips to live execution after the system has proven itself on their own tolerance for the strategy.

ETHEREUM IS THE DEEPEST CATACOMB.Eight years of deployments. The largest population of dead tokens on any EVM chain. Mainnet CTOs move millions in hours when they fire. Mainnet smart money is sophisticated, which means signal quality is high even where signal frequency is lower than on cheaper chains.

BASE IS THE FASTEST CYCLE.Cheap gas means more launches, more abandonments, more revivals per unit time. Coinbase distribution amplifies successful Base CTOs into a different attention regime than mainnet ever sees. Infrastructural maturity (block time, finality, RPC quality, indexer support) is now sufficient for the Lazarus stack to run without compromise.

WHY NOT THE OTHERS.Solana has different on-chain primitives, less EVM tooling overlap, and a revival pattern that does not map cleanly to the Lazarus model. BSC has the volume but the noise floor is hostile to a precision-tuned scorer. Arbitrum and Optimism have lower dead-token populations and currently fail the opportunity-cost calculation against ETH and Base. None of this is permanent. All of it is gated on demonstrated v1 success.

SHIPPED, SHIPPING, AND PLANNED.The roadmap below is intentionally narrow. Each milestone is a real deliverable with a measurable acceptance bar, not a marketing item. Items marked SHIPPED have been demonstrated against live data. ACTIVE items are in rolling release to whitelisted users. PLANNED items are scoped but not yet built.

THE ANTI-COMMITMENT.No multi-chain expansion will be promised before v1 has a published track record on ETH and Base. No feature will be added that materially weakens the safety layer. No cohort cap will be lifted before signal-decay analysis confirms that lifting it is safe.

DOCUMENT.The Manifest, version 0.1.4. Hash 0x4c4f56455f4c4f56455f4c4f56455f. Last updated at the timestamp shown in the header bar at the top of this page. Distributed as a single HTML page rendered server-side, with a print stylesheet for clean offline archiving.

AUTHORSHIP.Written and maintained pseudonymously by the Lazarus protocol team. Contributions to the underlying research were drawn from a wider on-chain research community whose members prefer not to be named. They have our gratitude regardless.

VOICE.The cadence of this document is deliberate. It is a working protocol specification with the syntax of a grimoire because the subject deserves both. Treat it as a working document. It will change as the protocol changes.

The market has a pulse. The chain remembers. Lazarus listens.

• › protocol@lazarus.fail
• › status.lazarus.fail
• › t.me/lazarus_protocol