PROTOCOL PAPER / VERSION 1.0
LAUNCH APP
FRUITFLY POWER / PROTOCOL WHITEPAPER

A power-weighted NFT staking protocol on BNB Chain.

FruitFly Power turns each Genesis NFT into a permanent on-chain power unit. Users stake NFTs, combine their power, and receive FLYP from a fixed reward pool according to their share of total active power.

VERSION 1.0SEPTEMBER 2026BNB SMART CHAIN · CHAIN ID 56DEPLOYED
01 / EXECUTIVE_SUMMARY

Digital ownership becomes measurable power.

FruitFly Power is a three-contract protocol deployed on BNB Smart Chain. A FruitFly Genesis NFT stores an immutable power score. The staking contract takes custody of the NFT, adds its score to the user’s position, and continuously accounts for FLYP rewards. No CPU work, hash calculation, or off-chain mining process is involved.

100MFIXED FLYP SUPPLY
80MSTAKING ALLOCATION
1,000GENESIS MAX SUPPLY
10YREWARD WINDOW
02 / ARCHITECTURE

Three contracts, one reward path.

01

FruitFly Power Token

An ERC-20 token named FruitFly Power with symbol FLYP. The full 100,000,000-token supply was minted once at deployment. The deployed token exposes no additional mint function.

02

FruitFly Genesis

An ERC-721 collection named FruitFly Genesis with symbol FFLY and a deployed maximum supply of 1,000 NFTs. Each token stores one power value between 90 and 270.

03

FruitFly Staking

A custody-based staking contract that receives approved NFTs, tracks user power, accumulates rewards, processes claims, and returns NFTs when users unstake.

03 / NFT_POWER

A permanent score with a capped 3× range.

The standard mint path assigns power through four weighted bands. Higher power is intentionally less frequent. Once assigned, the power value has no setter and cannot be rerolled.

CLASSPROBABILITYPOWER RANGE
COMMON70%90–110
RARE22%140–180
EPIC7%190–230
LEGENDARY1%240–270
RANDOMNESS DISCLOSURE

The deployed standard mint uses block data and owner-supplied entropy; it is not backed by a verifiable-randomness oracle. The owner also has an administrative mintWithPower function that can assign any valid score from 90 to 270. Users should treat mint fairness as dependent on operator policy until these controls are replaced or constrained.

04 / REWARD_ENGINE

Continuous emission, proportional allocation.

The staking allocation is divided over a ten-year window. Accounting is updated when a user stakes, unstakes, claims, or reads pending rewards. Each active position earns according to its fraction of total staked power.

USER REWARDelapsed time × reward rate × user power ÷ total power
BASE REWARD RATE80,000,000 FLYP ÷ 315,360,000 seconds ≈ 0.253678 FLYP / second
15-MINUTE REFERENCE≈ 228.31 FLYP shared across active power

A claim transfers accrued FLYP to the user. Successful claims for the same position must be at least 15 minutes apart. Users may unstake their NFTs without claiming first; already-accounted rewards remain attached to the position.

No reward-per-power increment is recorded while total staked power is zero. Final-period and unused-fund behavior depends on the timing of contract updates and should be reviewed before broad public distribution.

05 / TOKEN_ECONOMY

A fixed supply with an 80% staking allocation.

ALLOCATIONFLYPSHARESTATUS
STAKING REWARDS80,000,00080%FUNDED TO STAKING CONTRACT
ECOSYSTEM / TREASURY20,000,00020%INITIALLY HELD BY DEPLOYMENT OWNER
TOTAL100,000,000100%FIXED AT DEPLOYMENT

The contracts do not create liquidity, set a market price, guarantee exchange listings, or promise returns. Any external launchpad, liquidity venue, or market-making arrangement operates outside the deployed token, NFT, and staking contracts.

06 / USER_LIFECYCLE

Approve. Stake. Accrue. Claim. Unstake.

  1. 01
    CONNECT

    Connect MetaMask or OKX Wallet and switch to BNB Smart Chain.

  2. 02
    APPROVE

    Approve the staking contract to transfer the selected Genesis NFT.

  3. 03
    STAKE

    The NFT moves into staking custody and its stored score is added to the user’s power.

  4. 04
    ACCRUE & CLAIM

    FLYP accrues relative to total power and can be claimed subject to the interval rule.

  5. 05
    UNSTAKE

    The NFT returns to the owner and stops contributing power. Accounted rewards remain claimable.

07 / DEPLOYED_CONTRACTS

Verify every address on BscScan.

08 / TRUST_AND_RISKS

What the contracts guarantee—and what they do not.

  • Owner controls: NFT minting, direct power assignment through mintWithPower, and metadata base URI updates are restricted to the NFT owner.
  • Randomness: power assignment is pseudo-random and not oracle-verifiable.
  • Custody: staked NFTs are held by the staking contract until unstaked.
  • Immutable schedule: the reward rate, start time, end time, NFT address, and reward-token address are fixed in the deployed staking contract.
  • No emergency recovery: the current contracts do not expose a general rescue or migration function.
  • Smart-contract risk: deployment on-chain does not equal an independent security audit. Users should review source code and limit exposure accordingly.
  • Market risk: FLYP has no guaranteed price, liquidity, redemption value, or financial return.
09 / CURRENT_SCOPE

A deployed first protocol version.

Version 1.0 covers the deployed FLYP token, Genesis NFT, staking custody, proportional reward accounting, wallet connectivity, and the public web interface. It does not include decentralized governance, a randomness oracle, an on-chain NFT public-sale contract, automated liquidity, cross-chain functionality, or an external launchpad integration.

LEGAL NOTICE

This document is technical information, not financial, investment, tax, or legal advice. It does not constitute an offer or a promise of profit. Digital assets and smart contracts involve substantial risk, including total loss.