✓
Public address
Required to identify the holder and read the configured token balance.
Verification first
Trust the addresses, not the screenshots.
FlapSpin is designed so the important production components can be checked independently: token contract, network, reward inventory, spin accounting and settlement transactions.
| Component | What users should verify | Current site state |
|---|---|---|
| $FlapSpin token | Published BEP-20 contract on BNB Smart Chain | Awaiting launch address in config.js |
| Wallet network | BNB Smart Chain · chain ID 56 | Configured |
| Spin quota | Persistent wallet-level usage record | Frontend preview / production source required |
| Reward service | Secure endpoint or smart contract result | Awaiting production endpoint |
| Reward proof | BscScan transaction / claim record | Enabled by production settlement |
| Treasury | Public wallet or contract holding reward inventory | Publish at launch |
Wallet permissions
Connection is not custody.
A wallet connection lets the interface see the selected public address and request network changes. It should not require transferring tokens just to verify eligibility.
✓
Network switch
Used to move the wallet onto BNB Smart Chain when the current chain is different.
×
No seed phrase
FlapSpin never needs, stores or requests a wallet seed phrase or private key.
Launch standard: publish the final token contract, reward treasury, spin rules, probabilities, settlement endpoint/contract and verification links before enabling real rewards. The site is structured to accept those values without rebuilding the interface.