FLAZE Vault

Product

Release notes

Current public release is v1.6.2.1.1. Notes below describe user-facing changes only.

  1. v1.6.2.1.1 — Minor fixes

    Current
    • Minor fixes.

  2. v1.6.2.1 — Subdomain integration

    • The platform is also available at vault.flaze.org and stake.flaze.org.

  3. v1.6.2 — Flaze ecosystem menu

    • Header includes a Flaze Ecosystem menu after How it works, with FlazePad, FlazeSwap, the Flaze website, X, and Telegram.

  4. v1.6.1 — CoinGecko listing check

    • Community publish checks CoinGecko’s BNB Chain token list so listed tokens such as FLAZE are recognised.

  5. v1.6 — Community listings require further validation

    • A community pool can only be published if the token contract meet new requirements.
    • The publish stays locked until validation passes.

  6. v1.5.1 — Back end improvements

    • Back end improvements.

  7. v1.4 — Featured Flaze pools, logos, and faster updates

    • Official FLAZE token vaults sit in a Featured Flaze pools row of four above the community list.
    • The staking list shows 12 vaults per page, with previous and next. Sort by APY or lock length, high or low.
    • Featured FLAZE vaults stay on screen when Community is selected.
    • More token logos load from PancakeSwap, Trust Wallet, and 1inch lists.
    • Minor UI improvements.
    • Platform performance improvements.

  8. v1.3.1 — Unfunded official vaults cannot be staked

    • Official vaults now use the same staking rule as community vaults: the stake button stays off until a reward reserve is deposited.
    • Home cards show Unfunded when the reserve is empty. No rewards can be paid until the vault is funded.

  9. v1.3 — Unfunded community pools cannot be staked

    • Staking is closed on community vaults until the listing wallet deposits a reward reserve.
    • The stake button is disabled with a notice that the creator has not funded the pool.
    • Creators are told on the create page that they must fund rewards, keep the reserve topped up, and that Flaze is not responsible for underfunded pools.
    • Community pools that stay unfunded may be removed 14 days after they are listed.

  10. v1.2.1 — Wallet connect expanded

    • Phone wallets can pair over WalletConnect QR on the live HTTPS site.
    • Desktop browser wallets (such as MetaMask) continue to connect in-page.
    • Connection uses the official Reown AppKit modal. Always confirm the site address before you sign.

  11. v1.2 — Community pool funding

    • The wallet that listed a community vault can deposit the same token as a reward reserve from the vault page.
    • APY is paid only from that reserve. An empty reserve means rewards cannot pay out.
    • Funding uses two wallet confirmations: token approval, then the deposit.
    • You can add more rewards later from the same creator wallet.

  12. v1.1 — Community pools

    • Projects can list their own BEP-20 staking vaults on BNB Chain.
    • Each listing sets APY, lock length, and a minimum stake.
    • A FLAZE listing fee is burned. A small BNB fee is charged with the transaction.
    • Community vaults are listed by those projects. They are not run or endorsed by Flaze.

  13. v1.0 — Initial release with MetaMask support

    • Public staking site on BNB Chain.
    • Connect with a desktop browser wallet such as MetaMask.
    • Stake, claim, unstake at lock end, or emergency-exit for a BNB fee.

  14. v0.1 — Beta test

    • Closed trial of the vault interface and staking flow.
    • Used to check listings, wallets, and on-chain settlement before public use.