LJT token approvals: what your wallet is asking you to authorize
Understand LJT approvals, spending caps and wallet signatures in Lemon Jet. Learn what each prompt authorizes and how revoking permission works.
You choose an LJT amount and a multiplier, then your wallet asks you to approve something before it asks you to play. That first prompt has its own job: setting a token spending allowance.
Understanding the difference helps you read each request on its merits. An approval changes what a contract may spend. A prediction commits an amount to a game. One can succeed even if you decide not to complete the other.
Four wallet prompts with different purposes
| Request | What it does |
|---|---|
| Connect wallet | Makes the selected wallet available to the site through the wallet connection. |
| Sign in | Proves control of the wallet for an application session. |
| Approve LJT | Grants a particular spender an allowance for LJT. |
| Confirm prediction | Submits the selected stake and multiplier to the game contract. |
A normal connection does not itself create an LJT allowance. Likewise, Lemon Jet's wallet sign-in message authenticates a session rather than submitting a bet. Its format follows Sign-In with Ethereum, including the site's domain and details that bind the signature to that sign-in request.
Read the actual message. A prompt labelled "Sign" is not enough to identify its effect: other signature formats can authorize token spending. Confirm that a sign-in request names the expected site and describes authentication.
What an LJT allowance permits
An allowance belongs to a specific combination: your wallet, the token, the spender and the network. Granting a contract permission to spend LJT does not grant it the same allowance for every other asset.
The approval transaction records a spending limit in the LJT token contract. That spender can then use the token's allowance mechanism, subject to its contract logic. The ERC-20 standard defines how approvals and transfers using allowances work.
In Lemon Jet, the game contract uses the allowance to transfer the LJT stake when you place a prediction. The approval itself does not transfer that stake or start the round, although processing the approval costs network gas.
For the balances needed across both steps, see ETH on Base for LJT.
The current game requests a large spending cap
When the existing allowance is too small for the chosen stake, the current game flow requests the maximum allowance supported by the token amount type. In practical wallet terms, that is an unlimited LJT spending cap.
The purpose is to avoid another approval before each prediction. The tradeoff is that the permission extends beyond the single stake currently on screen, including LJT the wallet may receive later.
If your wallet supports editing the cap, you can choose a smaller amount. It must cover the intended action, and later actions may require another approval. MetaMask documents this in its spending cap guide. Wallet interfaces differ, so inspect the final request before confirming.
An approval cannot reveal the result of a future prediction. It also does not change the payout rules described in what LJT is used for.
Check the spender as well as the amount
Before approving LJT:
- Confirm the site and network. Open Lemon Jet through its known site and check that the request uses Base.
- Check the token. The request should identify LJT when approving LJT.
- Check the spender. The transaction goes to the token contract, but the spender is the contract receiving permission. Inspect that field too.
- Review the cap and fee. Decide whether the requested allowance matches what you want to authorize.
Use the official app's contract links to compare the LJT token and the game and vault contract. A familiar token symbol alone does not identify the spender.
Vault approval requests can differ
Do not assume every deposit screen requests the same cap. The current vault modal requests a very large allowance. The wallet's LJT-to-vault-share conversion, labelled eLJT in the app, requests the entered amount when an additional approval is needed.
Both use the game vault as spender, so an existing allowance may already cover the next action. Read each request independently. The staking vault guide explains the position created by the separate deposit transaction.
Disconnecting and revoking do different things
Disconnecting ends the wallet connection to the site. It does not erase an allowance already recorded on Base. MetaMask explains this distinction in its disconnecting guide.
To remove an LJT allowance, use a wallet or approval-management tool that supports Base, locate the correct token and spender, and submit a revocation. Wait for confirmation. Revoking is an on-chain action with a network fee, as described in MetaMask's approval revocation guide.
FAQ
Have I placed a bet if only the approval succeeded?
No. The approval sets permission. Check whether a separate prediction transaction was submitted using the transaction status guide.
Why am I asked to approve LJT again?
The allowance may be below the requested amount, revoked, or associated with a different wallet or spender. Check the current request and wallet selection.
Does revoking return my stake or withdraw my vault deposit?
No. Revocation changes permission for future spending. It does not reverse confirmed transfers, cancel an accepted prediction or redeem vault shares.
Does a sign-in signature always mean there is no spending permission?
Lemon Jet's sign-in message authenticates a session. Read every new request: the presence of a signature button alone does not establish what it authorizes.
When you continue with the first prediction guide, review the permission and the prediction as two separate decisions.