SCALPERS documentation

#Introduction

Collector Crypt (CC) tokenizes professionally-graded trading cards on Solana — each NFT is backed one-to-one by an authentic slab held in an insured vault. SCALPERS is a liquidity aggregator for that inventory on Base: it surfaces the full catalog, routes each trade, and settles in USDC on Base, so a user never bridges assets, manages a Solana wallet, or leaves Base.

What it provides

• Aggregation — Collector Crypt's 68,000-card marketplace, surfaced in a single Base-native feed.
• Mirror — a purchase or rip returns a one-to-one mirror ERC-721 on Base, backed by the vaulted slab.
• Exit — sell back into the aggregated liquidity for USDC, or redeem the physical card.

SCALPERS applies no hidden markup. A user pays the seller's or CC's price; the service fee is shown as a separate line before confirmation.

#The custody guarantee

One trust assumption remains, and it is the same one every graded-card holder already accepts: the grader and custodian (PSA / CGC and CC's vault) physically hold the slab. They can freeze an asset but cannot reassign ownership — and this is disclosed on-chain for every card.

#Card lifecycle

A single-exit lock keeps the two representations in sync: the mirror and the physical card are one asset, so at most one move is ever in flight. An owner can never end up holding both or neither.

#Custody, in code

The enforcement is in the contracts. A mirror can be moved only by its owner — and only while idle — or by the single allowlisted marketplace. No other transfer path exists:

// MirrorCard.sol — a mirror can only be moved by its owner or the marketplace
function _update(address to, uint256 tokenId, address auth) internal override {
    if (isMover[auth]) {
        // the single allowlisted marketplace (escrow / buy / return) — allowed
    } else if (auth == from) {
        require(state[tokenId] == State.Free, "card locked"); // owner transfer, only when idle
    } else {
        revert("external transfers disabled");               // no other path exists
    }
}

The physical card moves only on a Wormhole VAA — a message signed by the guardian set — that originates from the owner's action and from the vault's registered emitter. No SCALPERS key satisfies these checks:

// MirrorCard.sol — the only function that burns or unlocks a mirror
function settle(bytes calldata vaa) external {
    (VM memory vm, bool valid, string memory reason) = wormhole.parseAndVerifyVM(vaa);
    require(valid, reason);                                   // signed by the guardian set
    require(vm.emitterChainId == SOLANA_CHAIN_ID, "bad chain");
    require(vm.emitterAddress == solanaEmitter, "bad emitter"); // from the vault, only
    require(!consumedVAA[vm.hash], "vaa replayed");          // single use
    // No operator, owner, or relayer key satisfies these checks. Settlement occurs
    // only as a consequence of a verified action on the Solana vault.
}

#Settlement & capital

SCALPERS routes funds; it does not hold deposits or extend credit. No payout is funded from SCALPERS' own balance — each is funded by a counterparty and released only once that counterparty's funds have settled on-chain.

The only capital SCALPERS provisions is transaction gas (SOL and ETH-on-Base) plus a one-time, recoverable deploy deposit. There is no float, no buffer, and no fractional reserve: every purchase and payout is funded by the user or the counterparty and settles directly across the bridge.

#Cross-chain rails

Two established protocols carry messages and value between Base and Solana. SCALPERS adds no additional trust assumption on top of them.

The seller's payout address is committed at list time, so settlement is deterministic — proceeds can only reach the seller's own address:

// scalpers_vault (Solana) — proceeds are routed by the contract, not by an operator
pub fn settle_cc_sale(ctx, proceeds_amount: u64) -> Result<()> {
    require!(vault_token.amount == 0, CardStillHeld);  // the card has left the vault

    // Burn proceeds directly to the Base address the seller committed to at list time.
    // The recipient is fixed in the card's on-chain record and cannot be reassigned.
    let recipient = cctp::evm_to_recipient(&card.cc_payout);
    cctp::deposit_for_burn(&a, proceeds_amount, DOMAIN_BASE, recipient, signer)?;

    card.state = CardState::Released;
    card.pending_ack = ACK_CC_SOLD;  // instructs Base to burn the mirror
}

#Liquidity source

Every card SCALPERS aggregates is a Collector Crypt asset — an authentic slab graded by PSA, CGC, or BGS, held in an insured vault and tokenized one-to-one on Solana. CC's catalog is public, so SCALPERS surfaces it directly, with the grade, insured value, and on-chain mint shown on each card.

The displayed data matches what CC exposes: grader, grade and certificate ID, insured value, year, set, and the Solana mint address — each linked to a block explorer.

#Secondary liquidity

When an owner lists a card, it is posted on Collector Crypt's marketplace program (CcmRKTuZ…SQUr) — an on-chain Solana order book, settled in USDC with a flat 2% (200 bps) platform fee. That places the listing directly into Collector Crypt's own buyer liquidity. On a fill, proceeds settle to the owner's Base wallet through CCTP and the mirror is burned.

Collector Crypt's marketplace is escrowless by design — a listed card stays in the holder's wallet via a delegate, and the on-chain escrow holds only USDC, never the card. SCALPERS keeps the card in its vault throughout, so the custody guarantee above always holds. Magic Eden indexes Collector Crypt listings, so a card listed here can also surface to Magic Eden's audience — but every trade settles through Collector Crypt's program, not a third-party auction house.

Offers follow the same path: a buyer bids below the ask, the owner accepts or declines from their inventory, and the vault executes the sale at the committed price.

#On-chain references

SCALPERS is built on public, independent infrastructure that can be inspected directly. SCALPERS' own vault and contract addresses are published here at mainnet launch.

Each guarantee described here is enforced by the contract code above; the snippets are reproduced verbatim from the deployed sources.