BACKSTOP

Risks (8)

• HighClaim contradicted: Tokens launched on the platform feature a fee-funded on-chain redemption floor tracked in native coin that contracts will always buy back at, with pull-out refunds available beforeclaims-mismatchDeterministic

  The project claims token burns / buybacks, but no tokens of this contract were ever sent to a burn address or destroyed.

  Evidence

  • webhttps://backstop.fund/
    Show source

    Refundable bonded launches on Robinhood Chain. Bond toward a cap, pull out anytime before graduation, then graduate into a Uniswap V4 pool.

  • on-chainTransfer events of 0xa5a58a72047d67d27f4e3055494d53ee6901d99e to burn addresses + balanceOf(0x…dEaD)

  Confirmed by: facts

• HighLaunch sniped: 2 wallets took 100% of supply in 10 secondssnipersDeterministic

  The launch was captured: 2 wallets bought 100% of the supply within 10 seconds. A small, fast group set the early price and could sell into everyone who bought later — bad for launch fairness and a strong insider/bot signal. They now hold 0% of supply, so current dump pressure from them is low — most of it was already sold, i.e. they exited on later buyers.

  Evidence

  • on-chainsnipers: windowBlocks=100, wallets=2, pctSupplyBought=100.0003, pctSupplyHeldNow=0.0003
  • on-chaintoken.snipers
    Show source

    pctSupplyBought: 100.0003, pctSupplyHeldNow: 0.0003

  Confirmed by: facts, claude-opus-5.5, grok-4.7, gpt-5.6-sol

• HighDump risk: launch wallets still hold 33.1% of supplyholdersDeterministic

  Sniper / insider / bundled launch wallets still hold about 33.1% of the supply. If they sell, the price can collapse — current dump pressure is HIGH.

  Evidence

  • on-chainheld now: snipers 0.0003%, insiders 0%, clusters 33.15%
  • on-chaintoken.clusters[0] funder 0xec5266c9e44631e1ba22fd6377c38130c1f3b738
    Show source

    pctSupplyHeldNow: 28.0162

  • on-chaintoken.topHolders
    Show source

    0xd341A57Dc7c122Fe4b176536eCeAD58AF8B7d9e6 6.9528%, 0xc9186c13513123c7D14AEEb2A6b55B9eBc7e9d88 6.1641%, 0x741B828ACEba9A22e58913592f8242688032b884 6.0678%

  • on-chaintoken.clusters[1] funder 0xf70da97812cb96acdf810712aa562db8dfa3dbef
    Show source

    pctSupplyHeldNow: 3.1629

  • on-chaintoken.clusters[2] funder 0x18363e81880c98a1f357f9b6ed58488293b6d29b
    Show source

    pctSupplyHeldNow: 1.9682

  Confirmed by: facts, claude-opus-5.5, grok-4.7

• MediumSource code is not verifiedotherDeterministic

  The contract source is not published on the explorer, so nobody can read what it really does. The analysis relies on bytecode only.

  Evidence

  • on-chainexplorer: no verified source for 0xa5A58A72047d67d27f4E3055494d53ee6901D99e
  • on-chaincontract.verified = false
    Show source

    sourceFileCount: 0

  Confirmed by: facts, claude-opus-5.5, grok-4.7

• MediumMain pool liquidity is unlocked and held by an unverified contractliquidityAI

  The main Uniswap v4 pool has about $7,293 of liquidity. Its position is held 100% by an unlabelled contract, 0xb8ff…2066, and 0% of it is locked or burned. This is probably the launchpad's liquidity deployer or vault. Its code and admin are unknown, so we cannot confirm that the liquidity cannot be withdrawn. If whoever controls it can remove the position, holders would be left with no exit liquidity. The two other pools (worth $4 and $2) are held by unlocked wallets but are insignificant.

  Evidence

  • on-chaintoken.liquidity pool 0x69af668f5ba32c2a71aca611034ea03ecad64f278d06cb5383de5902dfe0f96c
    Show source

    liquidityUsd: 7293, lpBurnedPct: 0, lpLockedPct: 0

  • on-chaintoken.notes v4 position holders
    Show source

    v4 position liquidity holders: 0xb8ff1eab09d81965866d4ecde00d561d65682066 [other: unlabelled contract] 100%

  Confirmed by: claude-opus-5.5, grok-4.7, gpt-5.6-sol

• MediumLaunchpad owner can change fees, router, treasury and liquidity deployerownershipAI

  The factory that created the token (0xb48E…26a1) is owned by 0x785F…961f. It exposes setRouter, setTreasury, setConfig and claimDevTokens. The related launchpad contract 0xf370…a54D has the same owner. It exposes setProtocolFeeBps, setMaxAllocBps, setTreasury, setLiquidityDeployer and setVaultDeployer. None of these contracts are verified, so caps, timelocks and whether the changes affect already-launched tokens cannot be checked. In the worst case, the owner could raise protocol fees or point the router or liquidity deployer at its own contracts.

  Evidence

  • on-chainrelated creator-factory 0xb48E5659251e60629C619686f0134361914026a1 owner=0x785F5221c9fe9653Cf71859C8E606Af29814961f
    Show source

    fn setRouter(address) ... fn setTreasury(address) ... fn setConfig(uint256,uint256,uint256)

  • on-chainrelated 0xf37087FD24Df9df282c81602eb7026DF1D3Da54D owner=0x785F5221c9fe9653Cf71859C8E606Af29814961f
    Show source

    fn setProtocolFeeBps(uint16) ... fn setLiquidityDeployer(address) ... fn setVaultDeployer(address)

  Confirmed by: claude-opus-5.5, grok-4.7 · Disputed by: gpt-5.6-sol

• LowDocs say launched tokens are auto-verified, but this one is notclaims-mismatchAI

  Backstop's docs say every token launched on the pad has a fixed supply with no mint, owner, pause, or blacklist, and that each token is verified on the explorer by bytecode match. The on-chain basics for this $BACKSTOP contract say ownership has not been renounced and the contract is not verified. If an owner still exists, holders cannot treat the 'no owner' claim as true until the source is published and the owner role is shown to be powerless or gone.

  Evidence

  • webhttps://backstop.fund/docs
    Show source

    1,000,000,000 tokens (18 decimals), fixed. No mint, owner, pause, or blacklist.

  • webhttps://backstop.fund/docs
    Show source

    Each launched token is a fresh , verified automatically by matching bytecode.

  • on-chainownerRenounced=false; verified=false; target=0xa5a58a72047d67d27f4e3055494d53ee6901d99e

  Confirmed by: grok-4.7 · Disputed by: claude-opus-5.5, gpt-5.6-sol

• LowClaimed 7-day team-token lock is short and not shown on-chainclaims-mismatchAI

  The project account says 26.29M $BACKSTOP from the team's first buy is locked on-chain for 7 days and tells people to check the token page. The contract basics we were given do not show a locker balance or unlock time, so the lock is unverified here. Even if the post is accurate, a 7-day lock is short: the team could sell that stack soon after it unlocks.

  Evidence

  • Xhttps://x.com/Backstop_Fund/status/2118461332076777930
    Show source

    🔒 Dev tokens LOCKED for 7 days. 26.29M $BACKSTOP from the team's first buy is locked onchain. Verify it yourself on the token page.

  Confirmed by: grok-4.7, gpt-5.6-sol · Disputed by: claude-opus-5.5

Positive signals (1)

• PositiveBuy and sell both work with 0% token taxhoneypotAI

  On a fork, a real buy and sell both succeeded at exactly the expected amounts, with 0% buy, sell and transfer tax. A second wallet that received tokens by transfer could also sell, and a sell after one hour still worked. Only the 1% v4 pool LP fee applies. There is no honeypot behaviour today.

  Evidence

  • forksimulation canBuy/canSell
    Show source

    buyTaxPct: 0, sellTaxPct: 0, transferTaxPct: 0

  • forksimulation notes
    Show source

    second wallet (received via transfer) could sell

  Confirmed by: claude-opus-5.5, grok-4.7, gpt-5.6-sol

Notes (4)

• InfoLaunched via factory; deployer never held tokensdeployer-historyAI

  The token was created by factory 0xb48E…26a1, and 100% of supply was minted to it as the launch or liquidity source. Deployer 0x4174…265d never received tokens and holds 0%. No deployer history is recorded.

  Evidence

  • on-chaintoken.notes
    Show source

    Initial supply minted to contract 0xb48e5659251e60629c619686f0134361914026a1 (100% — bonding curve / launchpad / vault)

  • on-chaintoken.notes
    Show source

    Deployer 0x4174b6b538a719a6dcf863a04729603fa07a265d holds 0% now

  Confirmed by: claude-opus-5.5, grok-4.7, gpt-5.6-sol

• InfoWebsite buy test did not finish due to our tool timeoutwebsiteAI

  The website buy test failed because of our own browser-driving AI timeout, not an on-chain revert. No transactions or approvals were made. The sell test was skipped. The test URL pointed to a different token page (0xe1dC…a7C4). Nothing about the site's transaction behaviour was verified.

  Evidence

  • forkdappTests 'Buy token' step error
    Show source

    LLM error: The operation was aborted due to timeout

  Confirmed by: claude-opus-5.5, grok-4.7, gpt-5.6-sol

• InfoUser alleges deleted posts and repeat launches (unconfirmed)socialAI

  A reply accuses the account of deleting older messages and of launching this token multiple times, and says DMs are closed. Searches for the contract address and for $BACKSTOP relaunch talk did not turn up corroborating posts, archives, or a second contract address. Treat this as an unverified allegation, not proof of a relaunch or a cover-up.

  Evidence

  • Xhttps://x.com/The1onerangerr/status/2118472931395432936
    Show source

    @Backstop_Fund You’ve deleted all the older messages now 🤦‍♂️ doesn’t look good

  • Xhttps://x.com/The1onerangerr/status/2118472208733315092
    Show source

    How many times has this token been launched ? I’ve been going through your x post, seems like it’s been launched multiple times.

  Confirmed by: grok-4.7, gpt-5.6-sol

• InfoX account and domain created the same day, seven weeks before launchsocialAI

  @backstop_fund was created on 2026-09-19 and backstop.fund was registered the same day, with Wayback first seeing the site the next day. The token was deployed on 2026-11-05. That lines up with a new project, not an old unrelated account that was renamed for this launch. Followers are only 45, and launch posts have small engagement, which fits the size rather than a bought audience. No team names are published, so 'who runs this' stays unverifiable.

  Evidence

  • webhttps://backstop.fund/
  • Xhttps://x.com/Backstop_Fund/status/2118453556105613714
    Show source

    It's live. $BACKSTOP The token for the only launchpad where the floor has your back.

  Confirmed by: grok-4.7 · Disputed by: gpt-5.6-sol