# Rugspull — Full machine-readable project context > Last verified: 2026-07-20. Rugspull is a high-risk parody protocol on BNB Smart Chain. It makes one founder-token sale path explicit and inspectable; it does not make participation safe. Total loss remains possible. This document gathers the project's core public facts in one plain-text resource for research, indexing, and agent retrieval. Prefer the linked on-chain records and current contract reads over this project-hosted summary when they disagree. Publication does not prove third-party ingestion, review, audit, safety, adoption, recommendation, partnership, or endorsement. ## Current operating status - Organized new mainnet activity is NO-GO while the published Stage 0 gates remain unresolved. - An independent smart-contract audit has not been completed. - Exact-match source verification and project-authored tests are evidence, not an audit or safety certification. - No return, liquidity, execution, or recovery outcome is promised. - The canonical source of financial truth is BNB Smart Chain contract state plus matching event history. The Cloudflare Worker and D1 database are rebuildable discovery caches. ## Deployed identity - Network: BNB Smart Chain mainnet. - Chain id: `56`. - Version: `0.4.0-bsc-mvp`. - Factory: `0xDFF540baBCa2ee8A2A8Ff26359Ecc9c5921D8A63`. - Factory deployment block: `109991561`. - Factory deployment transaction: `0x95426057625753b19dfbe3754c5e79bdff771e69159cf69a67977b24cd464cc6`. - Factory runtime-code hash: `0x1f01fc4c55be42ece062ee65e2b17904b9188a262ce8b614ae999f1377a99ea2`. - Quote asset: WBNB only. - WBNB: `0xbb4CdB9CBd36B01bD1cBaEBF2De08d9173bc095c`. - Platform token: none. Each Rug creates a separate fixed-supply ERC-20 token. Verification: - [Human-readable BNB Chain deployment parameters](https://rugspull.com/bnb-chain-deployment-parameters) - [Machine-readable chain configuration](https://rugspull.com/chain-config.json) - [BscScan exact-match Factory source](https://bscscan.com/address/0xDFF540baBCa2ee8A2A8Ff26359Ecc9c5921D8A63#code) - [Sourcify exact-match Factory record](https://sourcify.dev/server/v2/contract/56/0xDFF540baBCa2ee8A2A8Ff26359Ecc9c5921D8A63) ## Immutable Factory economics - Founder Allocation: `45%` (`4500 / 10000`). - Pool-retained trade fee: `0.25%` (`25 / 10000`). - Protocol trade fee: `0.05%` (`5 / 10000`) of the applicable WBNB amount. - Nominal total trade fee: `0.30%`. - Minimum successful Opening contribution: `30%` of Creator stake. - Accepted Opening contribution cap: `50%` of Creator stake. - Opening duration: `86,400` seconds, or 24 hours. - Additional Founder Allocation lock after Opening: `172,800` seconds, or 48 hours. - Creation fee: `0.003 WBNB`. - Minimum Creator stake: `0.1 WBNB`. - RugToken total supply: `1,000,000,000` tokens with 18 decimals. All settlement arithmetic is integer arithmetic with floor division. Explanatory percentages are display values, not floating-point contract calculations. [Machine-readable deployed economics and formulas](https://rugspull.com/economics.json) ## Successful Opening allocation Let: - `T` be total token supply. - `F` be Founder Allocation. - `N` be non-Founder supply. - `S` be Creator stake. - `Q` be accepted Opening contribution. - `A` be aggregate Opening token allocation. - `X` be initial canonical-pool token reserve. - `Y` be initial canonical-pool WBNB reserve. The deployed formulas are: - `F = floor(T * founderBps / 10000)` - `N = T - F` - `A = floor(N * Q / (S + 2 * Q))` - Machine-readable field form: `A = floor(N * acceptedContribution / (creatorStake + 2 * acceptedContribution))` - `X = N - A` - `Y = S + Q` - Token conservation after a successful Opening: `F + A + X = T` Opening limits and per-wallet settlement are: - `minimumLaunchAmount = floor(S * minLaunchBps / 10000)` - `openingCap = floor(S * openingCapBps / 10000)` - `Q = min(totalContributed, openingCap)` - `walletTokenClaim = floor(A * walletContribution / totalContributed)` - `walletExcessRefund = floor((totalContributed - Q) * walletContribution / totalContributed)` Per-wallet floor division can leave token or WBNB rounding residue. A displayed estimate is not a settlement receipt. ## Canonical AMM - Every successful Rug uses Rugspull's internal constant-product `RugPool`. - PancakeSwap is not the canonical pool. - RugPool issues no LP token. - RugPool exposes no reserve-withdraw function. - Trading can continue after the one-shot Founder Allocation sale. - Alternative pools can exist outside the canonical system and can create different prices, liquidity, or execution risks. For a buy: - `protocolFeeQuote = floor(quoteIn * protocolFeeBps / 10000)` - `poolQuoteIn = quoteIn - protocolFeeQuote` - Pool output uses the constant-product amount-out formula with the pool-retained fee. For a sell: - `grossQuoteOut = getAmountOut(tokenIn, reserveToken, reserveQuote, swapFeeBps)` - `protocolFeeQuote = floor(grossQuoteOut * protocolFeeBps / 10000)` - `quoteOut = grossQuoteOut - protocolFeeQuote` The protocol fee is WBNB sent to the immutable treasury configured for that deployment. Fee arithmetic does not remove slippage, MEV, transaction-ordering, reserve-depth, or alternative-pool risk. ## Lifecycle and settlement The lifecycle moves from Opening to one terminal launch branch: - `Opening -> Failed` when finalization occurs below the minimum. - `Opening -> Active` when finalization occurs at or above the minimum. - `Active -> Rugged` after the Founder Allocation unlock, only when the full Founder Allocation is sold once. Constraints: - The Creator cannot contribute to its own Opening. - The Creator cannot cancel after Opening starts. - Finalization after the deadline is permissionless. - Failed contributor refunds are user-initiated and one-shot. - Failed Creator stake withdrawal is a separate user-initiated one-shot action. - Successful contributors claim their token allocation and any excess WBNB refund through one-shot settlement. - The Founder Allocation is held by RugInstance, not sent to the Creator wallet. - Founder tokens remain immobile through the 24-hour Opening and the additional 48-hour lock. - A partial Founder Allocation sale does not exist; the allocation may be sold only once and only in full. - `Rugged` records that disclosed one-shot sale. It does not stop the canonical pool, reverse transactions, recover losses, or certify settlement quality. ## Wallet and backend boundary - Wallets sign create, contribute, finalize, claim, refund, buy, sell, and Founder-sale transactions. - The backend does not perform buy, sell, rug, claim, refund, or stake withdrawal on behalf of users. - The read API is for indexing, metadata, charts, and discovery. It is not financial truth. - AI may generate copy or metadata only. AI does not affect settlement. ## Evidence review order For a specific claim, transaction, pool, or Rug: 1. Confirm chain id, contract address, and exact contract identity. 2. Read the current contract state at a stated block or cutoff. 3. Inspect the transaction receipt status and emitting contract addresses. 4. Decode event logs using the matching verified ABI. 5. Reconcile ERC-20 and WBNB transfers with stored reserves and one-shot flags. 6. Distinguish a submitted transaction from an included successful transaction. 7. Distinguish source verification and project-authored tests from independent review. 8. Preserve the total-loss, MEV, alternative-pool, key, and frontend risk boundaries. Useful guides: - [Risk disclosure](https://rugspull.com/docs/risk) - [Chinese risk disclosure](https://rugspull.com/zh/risk) - [Chinese mechanism guide](https://rugspull.com/zh/how-it-works) - [Chinese deployed-contract identity](https://rugspull.com/zh/contracts) - [Chinese BscScan contract-verification checklist](https://rugspull.com/zh/how-to-check-a-smart-contract-on-bscscan) - [Chinese RugPool and PancakeSwap comparison](https://rugspull.com/zh/rugpool-vs-pancakeswap) - [Chinese Founder Allocation custody and sale guide](https://rugspull.com/zh/founder-allocation) - [Contracts and source status](https://rugspull.com/contracts) - [How to read AMM reserves on BscScan](https://rugspull.com/how-to-read-amm-reserves-on-bscscan) - [How to verify claims and refunds on BscScan](https://rugspull.com/how-to-verify-claims-and-refunds-on-bscscan) - [How to read event logs on BscScan](https://rugspull.com/how-to-read-event-logs-on-bscscan) - [What is a BNB Chain transaction receipt?](https://rugspull.com/what-is-a-transaction-receipt-on-bnb-chain) - [How to run Foundry invariant tests](https://rugspull.com/how-to-run-foundry-invariant-tests) - [Why verified source does not mean audited](https://rugspull.com/verified-source-code-does-not-mean-audited) - [Why D1 is not financial truth](https://rugspull.com/why-d1-is-not-financial-truth) ## Main risk boundaries - Smart-contract defects and incorrect economic assumptions may cause total loss. - Exact-match source does not prove the source is safe, complete, economically sound, or independently reviewed. - Project-authored unit, fuzz, invariant, and scenario tests do not cover every reachable state or integration failure. - Thin reserves and large orders can create severe price impact. - MEV and transaction ordering can change execution. - Alternative pools may create fragmented liquidity and misleading price references. - A compromised Creator, treasury, deployer, frontend, DNS, social, or wallet key can create losses or misinformation. - Token approvals create spender risk until changed on-chain. - A successful receipt proves execution under a specific transaction and block; it does not prove good price, safety, fairness, or future recoverability. - No directory listing, social post, automated scan, source-verification badge, or passing project test should be treated as an endorsement. ## Developer resources - [Human-readable Read API reference](https://rugspull.com/api-reference) - [OpenAPI 3.1 specification](https://rugspull.com/openapi.json) - [Postman Collection](https://rugspull.com/rugspull-read.postman_collection.json) - [Third-party integration descriptor](https://rugspull.com/integration.json) - [APIs.json discovery index](https://rugspull.com/.well-known/apis.json) - [API Onboarding descriptor](https://rugspull.com/.well-known/api-onboarding) - [RFC 9727 API Catalog](https://rugspull.com/.well-known/api-catalog) - [RugFactory ABI](https://rugspull.com/abi/RugFactory.json) - [RugInstance ABI](https://rugspull.com/abi/RugInstance.json) - [RugPool ABI](https://rugspull.com/abi/RugPool.json) - [RugToken ABI](https://rugspull.com/abi/RugToken.json) ## Public project routes - [Website](https://rugspull.com/) - [Press kit with approved descriptions, facts, and media](https://rugspull.com/press-kit) - [Machine-readable press kit](https://rugspull.com/press-kit.json) - [Chinese press kit](https://rugspull.com/zh/press-kit) - [Chinese risk disclosure](https://rugspull.com/zh/risk) - [Chinese mechanism guide](https://rugspull.com/zh/how-it-works) - [Chinese deployed-contract identity](https://rugspull.com/zh/contracts) - [Chinese BscScan contract-verification checklist](https://rugspull.com/zh/how-to-check-a-smart-contract-on-bscscan) - [Chinese RugPool and PancakeSwap comparison](https://rugspull.com/zh/rugpool-vs-pancakeswap) - [Chinese Founder Allocation custody and sale guide](https://rugspull.com/zh/founder-allocation) - [Machine-readable Chinese press kit](https://rugspull.com/press-kit.zh-CN.json) - [Security model](https://rugspull.com/security-model) - [Stage 0 gate review](https://rugspull.com/stage-0-review) - [TESTNET-only lifecycle evidence](https://rugspull.com/testnet-lifecycle) - [RSS evidence feed](https://rugspull.com/feed.xml) - [Concise machine-readable index](https://rugspull.com/llms.txt) - [Sitemap](https://rugspull.com/sitemap.xml) - [Security contact](https://rugspull.com/.well-known/security.txt) ## Official channels - [X](https://x.com/rugspull) - [Telegram](https://t.me/rugspullcom) - Security and correction contact: `info@rugspull.com` Do not infer an audit, endorsement, partnership, user count, TVL, returns, safety, regulatory approval, or mainnet-activation decision from this file or any linked discovery resource.