LIONSGALA

VERSION 1.0 · AUGUST 2026 · BOT CHAIN

LIONSGALA
WHITEPAPER.

A transparent description of the current participation experience. The official contract address will be published only after deployment and explorer verification.

← Back to App
Table of contents

LIONSGALA WHITEPAPER

Version 1.0 — August 2026
Built on BOT Chain

Important Notice

LionsGala is an independent Web3 participation project. It is not affiliated with Lionsgate Entertainment, John Wick, or any related company, franchise, character, or rights holder.

LionsGala Points, referred to as “LGP,” are non-transferable participation points. LGP is not a cryptocurrency, security, financial instrument, deposit, investment product, ownership interest, or claim on project revenue. LGP has no cash value and cannot be purchased, sold, transferred, withdrawn, or exchanged for BOT or any other asset.

No token launch, financial return, reward, allocation, or airdrop is promised or guaranteed. Any future feature described in this document is exploratory, may change, and may be cancelled. Users should participate only for the current product experience and should not make financial decisions based on possible future utility.

1. Executive Summary

LionsGala is a lightweight on-chain membership experience built on BOT Chain. It gives users a simple way to connect an EVM-compatible wallet, record a membership action on-chain, receive a non-transferable participation score, and view verifiable project statistics.

The initial experience is intentionally narrow:

  1. A user connects a compatible wallet.
  2. The user switches to BOT Chain when required.
  3. The user confirms a one-time membership claim transaction.
  4. The wallet receives 100 LionsGala Points.
  5. The user may optionally pay 0.01 BOT once to increase the initial balance to 200 LionsGala Points.

This mechanism is not designed as an investment product. It is a transparent participation primitive that can later support badges, quests, access rules, creator programs, and community experiences without requiring a transferable token in the initial release.

2. The Problem

Many Web3 landing pages ask users to connect a wallet without providing a clear reason, a verifiable outcome, or an understandable next step. Other projects introduce a token, complex financial mechanics, or speculative promises before establishing a useful product experience.

This creates several recurring problems:

  • Wallet connection feels disconnected from product value.
  • Users cannot easily verify whether their participation was recorded.
  • Project statistics may depend on centralized or fabricated front-end data.
  • Points are often presented ambiguously, causing users to treat them as promised financial rewards.
  • Long onboarding flows create unnecessary friction for first-time users.

LionsGala addresses these issues by reducing the first experience to one wallet, one claim, one optional boost, and a publicly readable contract state.

3. Vision

LionsGala’s vision is to become a modular on-chain membership layer for digital culture and community participation on BOT Chain.

The project begins with a simple entry record rather than a transferable asset. Over time, a wallet’s LionsGala history may be used to display participation milestones, non-transferable badges, completed quests, campaign eligibility, and access to limited community experiences.

The project follows four design principles:

3.1 Verifiable by Default

Important participation states should be readable from a public smart contract rather than existing only in a private database.

3.2 Minimal First Action

A new user should understand the complete initial flow without reading a technical guide: connect, claim, and optionally boost.

3.3 No Speculation Required

The product should remain understandable and usable without a token price, yield mechanism, guaranteed reward, or airdrop narrative.

3.4 Progressive Expansion

Future features should be introduced only after the base membership contract, security model, analytics, and user experience are stable.

4. Product Experience

4.1 Wallet Connection

Users enter LionsGala through an EVM-compatible wallet. Connecting a wallet only exposes the selected public address to the application. Wallet connection alone does not authorize a transaction and does not transfer funds.

When the connected wallet is on another network, the application requests a switch to BOT Chain. If BOT Chain is not present in the wallet, the application may request permission to add the official network configuration.

4.2 Membership Claim

After connection, the user may submit the one-time claim transaction. A successful claim records the wallet as a LionsGala member and assigns 100 LGP to that address.

Each address may claim once. The user remains responsible for the network transaction fee required by BOT Chain.

4.3 Optional Gala Boost

A wallet that has already claimed may choose to submit a one-time boost transaction with an exact value of 0.01 BOT. A successful boost increases the wallet’s balance from 100 LGP to 200 LGP.

The boost is optional. It is presented separately from the free membership claim, requires an explicit wallet confirmation, and cannot be activated more than once per wallet.

4.4 Member State

The application reads the following state directly from the membership contract:

  • Whether the address has claimed.
  • Whether the address has activated the boost.
  • The address’s current LGP balance.
  • Total member count.
  • Total boost count.
  • Total LGP issued.
  • Total BOT contributed through boosts.

This enables the application to restore the correct status after a refresh or when the same wallet returns on another device.

5. LionsGala Points

5.1 Definition

LionsGala Points are a non-transferable participation score maintained by the LionsGala smart contract.

5.2 Initial Distribution

ActionLGP ResultBOT Payment
One-time membership claim100 LGPNone, excluding network fee
One-time optional boost200 LGP total0.01 BOT, excluding network fee

The boost adds 100 LGP to the original 100 LGP balance. It does not create a recurring multiplier and does not apply to undefined future point systems unless separately announced.

5.3 Restrictions

LGP cannot be:

  • Transferred between wallets.
  • Sold or purchased as a standalone asset.
  • Redeemed for cash or BOT.
  • Used as collateral.
  • Withdrawn from the contract.
  • Treated as evidence of a guaranteed future allocation.

5.4 Future Utility

Potential future uses may include:

  • Displaying non-transferable membership tiers.
  • Unlocking profile badges.
  • Measuring completion of community quests.
  • Establishing eligibility for time-limited digital experiences.
  • Supporting creator or community campaigns.

These examples are exploratory. The existence, timing, rules, and availability of any future utility are not guaranteed.

6. Technical Architecture

6.1 Network

LionsGala is designed for BOT Chain mainnet:

  • Network name: BOT Chain
  • Chain ID: 677
  • Native asset: BOT
  • RPC endpoint: https://rpc.botchain.ai
  • Explorer: https://scan.botchain.ai

BOT Chain is an EVM-compatible Layer 1, allowing LionsGala to use common Solidity tooling and standard EVM wallet interfaces.

6.2 Front End

The front end is a responsive web application deployed on Vercel. It is responsible for:

  • Rendering the project website and whitepaper.
  • Connecting compatible wallets.
  • Requesting network changes.
  • Reading contract state.
  • Preparing claim and boost transactions.
  • Displaying transaction status and explorer links.

The front end does not hold user private keys and must never request a seed phrase.

6.3 Membership Contract

The initial contract maintains one record per wallet address. Its core functions are:

  • claim() — records first-time membership and assigns 100 LGP.
  • boost() — accepts exactly 0.01 BOT from an eligible member and updates the balance to 200 LGP.
  • getMember(address) — returns a consolidated view of a member’s state.
  • pause() and unpause() — provide an emergency response mechanism.
  • withdraw(address) — allows authorized withdrawal of accumulated BOT to a designated treasury recipient.

The contract also maintains aggregate counters so the front end can display live statistics without relying on fabricated numbers or scanning historical logs through the public RPC.

6.4 Events

The contract emits events for material state changes, including:

  • Membership claimed.
  • Membership boosted.
  • Treasury withdrawal.
  • Administrative pause state changes through the inherited security modules.

Events support public transparency and future indexing, while the MVP user interface reads current state directly from the contract.

7. Security Model

7.1 Contract Controls

The initial contract should use established OpenZeppelin security modules, including:

  • Two-step ownership transfer.
  • Emergency pause controls.
  • Reentrancy protection.

The contract updates member state before performing any external value transfer. The boost payment is retained by the contract and withdrawn through a separate authorized function rather than forwarded during the user’s boost transaction.

7.2 User Protections

The interface must:

  • Display the exact 0.01 BOT payment before transaction confirmation.
  • Clearly mark the payment as optional.
  • Never initiate a payment silently after wallet connection.
  • Display the destination contract and transaction hash through the public explorer.
  • Distinguish a rejected transaction from a failed transaction.
  • Explain that network fees are separate from the 0.01 BOT boost amount.

7.3 Administrative Risk

The contract owner can pause the system and withdraw accumulated BOT. This creates operational trust assumptions. The owner address and treasury process should be published after deployment. Future versions may evaluate a multisignature owner or timelocked administration.

7.4 Smart-Contract Risk

Smart contracts may contain defects despite testing and review. Users should interact only with the contract address published on the official LionsGala website and verify transaction details in their wallet.

8. Privacy and Data

LionsGala uses public wallet addresses as membership identifiers. Wallet addresses and contract interactions are visible on the public blockchain.

The MVP does not require users to submit a legal name, phone number, or identity document. Standard hosting and analytics providers may process technical information such as IP address, browser type, device information, and page activity, subject to the published Privacy Policy.

Users should not assume that blockchain activity is anonymous. Public addresses may be connected to other activity through external analysis or information disclosed elsewhere.

9. Treasury and Use of Boost Payments

The optional 0.01 BOT boost payment is collected by the LionsGala membership contract. Subject to project decisions and applicable requirements, treasury funds may be used for:

  • Hosting and infrastructure.
  • Smart-contract development and security work.
  • Design and product maintenance.
  • Community operations.
  • Future campaigns or experiences.

No holder or participant receives ownership of treasury funds, a revenue share, a dividend, or a repayment right. Treasury descriptions are operational intentions rather than binding allocation commitments.

10. Sybil Resistance and Fairness

The MVP applies a one-claim-per-wallet rule. This limits duplicate claims from the same address but does not prove that each wallet represents a unique person. A single person may control multiple wallets.

LionsGala does not claim that the initial point system is fully Sybil-resistant. Future campaigns may apply additional eligibility rules, time windows, participation requirements, reputation signals, or other safeguards. Any such rules should be disclosed before the relevant campaign begins.

11. Roadmap

Phase 1 — Entry

  • Launch the original LionsGala brand and website.
  • Deploy and verify the membership contract on BOT Chain.
  • Enable wallet connection, one-time claim, and optional boost.
  • Publish live contract statistics and the project whitepaper.

Phase 2 — Identity

  • Explore non-transferable badges.
  • Add a member profile showing verifiable participation history.
  • Improve contract ownership and treasury transparency.
  • Expand monitoring and incident-response procedures.

Phase 3 — Community

  • Explore time-limited quests and campaigns.
  • Introduce creator and community participation formats.
  • Evaluate access rules based on verifiable actions rather than transferable assets.

Phase 4 — Coordination

  • Explore community proposal processes.
  • Evaluate additional utility only after security, legal, and product review.
  • Consider broader BOT Chain ecosystem integrations where they provide clear user value.

All roadmap items are subject to change. A roadmap is not a promise of delivery, economic value, or future rewards.

12. Governance

The initial release is operated by the LionsGala project team. LGP does not provide voting rights or protocol ownership.

Future community feedback mechanisms may be introduced, but any governance system would require separate technical design, security review, and published terms. The project will not describe ordinary polls or feedback forms as decentralized governance.

13. Risks

Participation involves several risks, including:

  • Smart-contract defects or unexpected behavior.
  • Network congestion, RPC outages, or transaction failure.
  • Loss of wallet access or compromise of private keys.
  • Phishing sites or fraudulent contract addresses.
  • Changes to BOT Chain infrastructure or wallet compatibility.
  • Regulatory or legal changes.
  • Project roadmap changes or discontinuation.
  • No future utility being introduced for LGP.
  • The 0.01 BOT payment changing in market value after a transaction.

Users are responsible for reviewing wallet prompts, confirming the official contract address, and deciding whether the optional boost is appropriate for them.

14. Disclaimers

LionsGala is provided on an experimental and “as available” basis. Nothing in this whitepaper is financial, investment, legal, tax, or accounting advice.

References to possible badges, access, community experiences, quests, rewards, tokens, or airdrops do not create an obligation to launch them. No participant should expect profit from the efforts of the project team or any third party.

The website Terms of Use and Privacy Policy apply in addition to this whitepaper. Where a future campaign has separate rules, those rules will govern that campaign.

The following information should be completed only after production deployment:

  • Official website: To be published
  • BOT Chain contract: To be published after deployment
  • Contract explorer page: To be published after verification
  • Official social accounts: To be published

Users should not interact with contract addresses distributed through unofficial direct messages or unverified third-party pages.

16. Conclusion

LionsGala begins with a deliberately simple proposition: create a verifiable membership record, assign a non-transferable participation score, and give users a transparent optional way to boost that initial score.

By avoiding a transferable token and refusing to promise future financial rewards, the initial release can focus on product clarity, contract transparency, and a credible on-chain user experience. Future development will be evaluated on the basis of security, usefulness, community quality, and responsible disclosure.