Protocol Overview

How "Wrapping" Works (Technical Flow)

The core function of the Lazarus Protocol is to separate a digital asset from its compromised history. In the Solana ecosystem, a token often "dies" because the original developer abandoned the project, rug-pulled the liquidity, or lost the private keys. However, the holder distribution (the community) remains valuable.

The Wrapping process creates a 1:1 derivative that is mathematically pegged to the old asset but governed by the CogniFi autonomous system. This is achieved through a "Lock and Mint" architecture.

The Transaction Lifecycle:

1. Initiation: A user approves the LazarusWrapper smart contract to spend a specific amount of their dead token (e.g., $DEAD).

2. Encapsulation: The contract transfers the $DEAD tokens into a Program Derived Address (PDA) Vault. This vault is immutable and has no admin keys. The original tokens are effectively removed from circulation permanently.

3. Sanitization: The contract mints an equivalent amount of wLA (Wrapped Lazarus Asset) to the user.

4. Transformation: Unlike the original token, the new wLA token has:

   • Immutable Metadata: No developer can change the name or image later.

   • Revoked Authorities: The Freeze and Mint authorities are set to None or controlled strictly by the DAO.

   • Standardized Decimals: All wLA tokens are normalized to 9 decimals to ensure compatibility with high-precision AMMs.

The "Gravedigger" Module: Identifying Dead Liquidity

The Gravedigger is an off-chain indexer service that feeds data to the ElizaOS agents. Its purpose is to identify high-value targets for resurrection. It does not look for "new" coins. It looks for "zombies."

Detection Algorithm:

The Gravedigger scans the Solana ledger for liquidity pools meeting specific criteria:

1. Dormancy: The last_trade_timestamp on the Raydium or Orca pool is older than 30 days.

2. Locked Value: The pool still contains > 10 SOL in liquidity.

3. Holder Dispersion: The token has > 1,000 unique wallet addresses holding a balance > 0.

4. Renounced Ownership: The contract metadata indicates that the original UpdateAuthority has been revoked (a sign that the original dev cannot interfere).

When a target is identified, the Gravedigger pushes a RESURRECTION_OPPORTUNITY event to the Agent Swarm, triggering an automated evaluation of whether to launch a hostile takeover.