# LUCK\_Litepaper **Lucky Day -- A Telegram GameFi Platform on TON** Version 1.0 | March 2026 *** ## 1. Introduction Lucky Day is a Telegram Mini App gaming platform built on The Open Network (TON). It combines casual gaming with real on-chain rewards, making Web3 accessible to Telegram's massive user base without requiring any prior blockchain experience. Players open the app directly inside Telegram -- no downloads, no wallet setup required to start playing. They spin for prizes, compete in skill-based arena games, climb seasonal leaderboards, and earn rewards that carry real value on the TON blockchain. LUCK is the native utility token of the Lucky Day ecosystem. It serves as the bridge between in-game achievement and on-chain value, rewarding skilled and dedicated players while powering the platform's economy. ### Vision To build the leading casual GameFi platform on Telegram, where millions of players can enjoy engaging games and earn meaningful rewards -- all within the messaging app they already use every day. ### Core Principles * **Accessibility First** -- Zero friction onboarding through Telegram. No seed phrases, no gas fee confusion for new users. * **Play to Earn, Not Pay to Win** -- Free daily spins and arena plays ensure every player can participate and earn, regardless of spending. * **Transparent Economy** -- All token allocations, vesting schedules, and smart contracts are publicly verifiable on the TON blockchain. * **Sustainable Rewards** -- Reward emissions are calibrated against player growth to maintain long-term token value. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://doc.yourluckyday.app/luck_litepaper.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.