Docs

Overview

What the engine actually does, and what's real today vs. still pending mainnet deployment.

What SnowballBNB is

SnowballBNB is an autonomous growth engine for tokens on BNB Chain. Every swap through a registered token pays a small fee; the engine converts that fee into buy pressure and permanent supply burns, without anyone manually triggering it. The marketing site's promise (“every transaction into organic volume, automatic buybacks, and permanent $SNOWBALL burns”) is backed by three contracts in contracts/, not just copy.

Current status

Not deployed to mainnet yet

The contracts are written and fork-tested against real BSC mainnet PancakeSwap contracts, and the deployment script dry-runs cleanly, but nothing has been broadcast. There is no live $SNOWBALL token, no real pair, no real fees flowing yet. Everything on this site that looks like a live number (holder counts, volume, burns) is either mock data or a graceful fallback until deployment happens. See Deployment for what's actually required to go live.
3 / 3
Contracts written
24 / 24
Tests passing
yes
Fork-tested vs. real PancakeSwap
not yet
Deployed to mainnet

The three contracts, in one sentence each

  • SnowballToken: the ERC-20 itself, with a fee that only applies on swaps (never plain wallet transfers), and a one-way gate that keeps trading closed until liquidity is seeded.
  • FeeRouter: “the engine.” Holds collected fees and, on demand, burns them (or swaps and burns, for other tokens) plus optionally pairs a portion into auto-liquidity.
  • SnowballRegistry: a permissionless directory so other projects can list their token (“connect one you already run”), curated by an owner-only verified flag.

Read Architecture next for how these three actually connect to each other and to PancakeSwap.