> For the complete documentation index, see [llms.txt](https://docs.lotrio.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lotrio.app/help/glossary.md). # Glossary Short definitions for every technical term used in LOTRIO docs. | Term | Plain meaning | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **WIN POWER / WP** | A wallet's lottery weight. Normally 1 WP per whole 10,000 `$LOTRIO`, minus any remaining winner deduction. | | **WP recovery** | The return of 25% of a specific winner deduction after 24, 48, 72 and 96 subsequently completed prize draws. | | **Eligible wallet** | A non-system wallet with at least 1 live WP. Pons system contracts, the team treasury wallet, the buyback burner, the lottery and the dead address never receive WP. | | **Pot** | ETH available in the lottery contract for the next draw, excluding already owed prizes. Shown live on the website; frozen at each draw. | | **Creator fees** | The part of every Pons trading fee paid to the token's creator-fee recipient: 70% of the 1% Pons fee plus the 1% creator tax, ≈1.7% of trade value. | | **Treasury wallet** | The team wallet that Pons pays all `$LOTRIO` creator fees to. Before every draw the keeper moves 80% of the newly accrued fees from it into the lottery; 20% stays with the team. It is excluded from WP. | | **TreasuryFunded** | The event the lottery emits for every ETH deposit, with the sender and amount. Deposits from the published treasury wallet are the 80% fee share. | | **Pre-funding** | After graduation, Pons sweeps pool fees only hourly, so the keeper funds the pot from the treasury using a trade-time estimate and reconciles when the sweep lands. | | **Skipped round** | A due 15-minute window with a pot below 0.05 ETH or fewer than three eligible wallets. Nobody wins; the amount keeps accumulating for the next round. | | **Snapshot** | The fixed participant weights used for one specific draw. Later trades do not change it. | | **Merkle-sum root** | A compact on-chain commitment to every eligible wallet, its WP and the total WP. | | **Proof** | Data allowing the contract to verify that a wallet and WP belong to the committed root. | | **Commit** | The moment the contract saves the pot, participant root and future reveal block. | | **Reveal block** | A future Robinhood L2 block whose hash becomes the random seed. | | **Blockhash** | A cryptographic identifier of a mined block, used here as on-chain randomness. | | **Settlement** | Verification of the three winners followed by ETH payouts, winner deductions and the 5% buyback transfer. | | **Keeper** | A team-run off-chain bot that funds the pot from the treasury, advances ready draw steps, relays token transfers and runs buybacks, paying its own gas. It does not choose winners and cannot withdraw from the lottery. | | **Transfer relay** | The keeper wallet fixed in the lottery that reports `$LOTRIO` `Transfer` events. It cannot set balances; the lottery rereads them from the token. | | **Claim** | Fallback withdrawal used only when a wallet could not receive its automatic ETH prize. | | **Buyback and burn** | Spending 5% of every completed pot on `$LOTRIO` and sending the tokens to the dead address. | | **Buyback burner** | The immutable contract that receives the 5% share and buys and burns `$LOTRIO`. Only the keeper can trigger it, or anyone after 7 days without a burn; it has no owner and no withdraw function. | | **Dead address** | `0x…dEaD`, an address with no usable private key. Burned tokens are sent there; they are out of circulation and never count for WP. | | **Pons V2** | The Robinhood Chain launchpad that deploys and owns the `$LOTRIO` token, its bonding curve and, after graduation, its Uniswap V4 pool. | | **Bonding curve** | Pons' per-token contract that holds the supply and prices every trade before graduation. | | **Graduation** | The moment the curve has raised 4.2 ETH. Pons then moves trading to a Uniswap V4 pool and locks its liquidity permanently. | | **V4 pool** | The post-graduation `$LOTRIO`/ETH Uniswap V4 pool created and locked by Pons. | | **Creator tax** | The 1% fee on every `$LOTRIO` buy and sell on top of the 1% Pons trading fee. Pons fixes it forever at launch. | | **Pons fee escrow** | The Pons contract that holds creator-fee ETH until the recipient claims it. | | **BPS** | Basis points. 100 BPS = 1%; 200 BPS = 2%. | | **MEV** | Value that block builders or searchers may extract by changing transaction ordering, often affecting swap execution. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.lotrio.app/help/glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.