Game errors: what happened and what to do

FD-101Wallet not found

What happened. The site did not find any Solana wallet in the browser. On a phone this happens when the site is open in a regular browser while the wallet is a separate app.

What to do. On a computer, install the Phantom, Solflare or Backpack extension and refresh the page. On a phone, open fairdrum.to in the wallet app's built-in browser.

Tokens: nothing was charged.

FD-102The wallet did not grant access

What happened. The wallet was found but did not give the site an address: it is locked, it has no Solana account, or the request was rejected.

What to do. Open the wallet, enter your password, make sure the Solana network is selected, and press “Connect wallet” again.

Tokens: nothing was charged.

FD-103Signature canceled

What happened. You closed the wallet window or pressed “Reject”. Without your signature the contract does nothing.

What to do. If it was accidental, press the game button again and confirm. To keep the window from appearing for every round, turn on play without signatures under the game button.

Tokens: nothing was charged.

FD-104Wallet not connected

What happened. The action needs a signature, but the wallet is not connected or has disconnected (for example, you switched accounts in the wallet).

What to do. Press “Connect wallet” in the site header and repeat the action.

Tokens: nothing was charged.

FD-105Not enough SOL for the network fee

What happened. Every action on the Solana network costs a small fee, and the first round also creates your player account (about 0.003 SOL, once). The wallet has no SOL left for this.

What to do. Keep a reserve of 0.01–0.02 SOL in the wallet on top of the top-up amount. If you are topping up with everything you have, reduce the amount.

Tokens: nothing was charged.

FD-106The wallet holds less SOL than you are depositing

What happened. The top-up amount is larger than what is in the wallet.

What to do. Enter a smaller amount or transfer SOL to the wallet from an exchange. The cashier has a link for swapping another cryptocurrency for SOL.

Tokens: nothing was charged.

FD-107A different account is selected in the wallet

What happened. The site built the action for one account, but the wallet signed with another: you switched accounts inside the wallet after connecting.

What to do. Click the address in the site header, disconnect the wallet and connect again with the right account.

Tokens: nothing was charged.

FD-201Not enough SOL on the game balance

What happened. The round size is larger than your game balance. The game balance is the SOL deposited into the contract, not everything in your wallet.

What to do. Press “Top up” or choose a smaller round. The cost of a round is always shown under the game button.

Tokens: nothing was charged.

FD-202This round size is not available right now

What happened. The contract accepts only rounds of an allowed size: up to 1 SOL in the games and up to 10 SOL on the main wheel.

What to do. Choose the round size with the buttons under the game. If the error appeared on its own, refresh the page.

Tokens: nothing was charged.

FD-203There is an unfinished round

What happened. You already have a round whose bet has been accepted but whose result has not arrived yet. Until it is finished, a new one cannot be started — this protects against a double bet.

What to do. Press the game's main button: it will show “Finish the spin” and finish the round. An unfinished round can be finished from any game and from any device.

Tokens: the bet has been accepted by the contract and is waiting for the result — it is not lost.

FD-204The player account has not been created yet

What happened. The wallet does not have a player account in the contract yet.

What to do. Press “Top up”: the account is created automatically with the first top-up; there is no separate registration.

Tokens: nothing was charged.

FD-205Bets are paused

What happened. The acceptance of new bets is temporarily paused — usually because the random-number oracle is not responding. The contract's guardian sets the pause automatically so that new bets do not get stuck waiting.

What to do. Please wait. Bets already placed are settled as usual; if the oracle never responds, they will be refunded. Withdrawals work.

Tokens: the balance has not changed.

FD-206The game has not been launched yet

What happened. The contract is not open for bets yet, or the site is connected to a network where the game does not exist.

What to do. Check that the wallet is switched to the Solana main network (Mainnet) and refresh the page.

Tokens: nothing was charged.

FD-207The site and the contract are different versions

What happened. The page in your browser and the contract on the network are different versions. Usually this is an old cached page right after a site update.

What to do. Refresh the page with the cache cleared: Ctrl+F5 on a computer; on a phone, close the tab and open the site again. If that does not help, wait 10–15 minutes.

Tokens: nothing was charged.

FD-208No free spins

What happened. This version of the game has no free spins: every round is paid from the game balance.

What to do. Play a regular round. If the button offered a free spin, refresh the page.

Tokens: nothing was charged.

FD-209Your loss limit has been reached

What happened. You set a daily loss limit yourself in your account, and it has been reached today. The site does not let you start a new round.

What to do. The game will reopen tomorrow. You can change or remove the limit in your account, in the “Your own limits” block.

Tokens: the balance has not changed.

FD-301The oracle has not written the number yet

What happened. The bet is recorded, but the independent oracle has not sent the random number yet. This usually takes 10 seconds to 3 minutes, longer when the network is busy.

What to do. Do not start a new round. Wait and press “Finish the spin”. You can close the page: the keeper service will finish the round and the result will be on your balance. If the oracle does not respond within 20 minutes, the bet will be refunded in full (FD-312).

Tokens: the bet has been accepted by the contract and is waiting for the result — it is not lost.

FD-302The result is ready but not recorded

What happened. The oracle has already written the number, but the round has not been settled yet: neither the site nor the keeper service has done it yet.

What to do. Press “Finish the spin” and confirm the signature. The result does not depend on who presses: it is determined by the oracle's number.

Tokens: the bet has been accepted by the contract and is waiting for the result — it is not lost.

FD-303The round is already finished

What happened. The round has already been settled — most often by the keeper service while the page was waiting. It cannot be settled again.

What to do. Refresh the page. The result is already on your game balance; the round itself can be found on the “Verify a round” page.

Tokens: the result is already on your game balance.

FD-304Round closed without a result

What happened. The oracle responded, but the round was neither settled nor sealed within three and a half minutes of the bet (see FD-311). Under the contract's rules such a round is closed without a result: otherwise losing rounds could simply be abandoned.

What to do. This happens only if the page was closed and the keeper service was not running. Do not close the page during a round, or turn on signature-free play.

Tokens: this round's bet went to the prize bank and is not returned.

FD-305A round from an earlier version of the game

What happened. The account still has an unfinished round made on an earlier version of the contract. The new version of the site cannot settle it.

What to do. Press “Close the expired one” in your account, then start a new round.

Tokens: the bet has been accepted by the contract and is waiting for the result — it is not lost.

FD-306The round is settled, but the site did not read the result

What happened. The contract settled the round, but the site could not read the result record — the network node did not return it in time.

What to do. Refresh the page: the balance and the history are read from the contract again. The round can be checked on the “Verify a round” page.

Tokens: the result is already on your game balance.

FD-307Could not confirm that the bet was recorded

What happened. The transaction with the bet was sent, but the site did not see its record on the network: the network node was lagging or the transaction was lost.

What to do. Refresh the page and look at your game balance. If the bet was charged, the round is recorded and the main button will show “Finish the spin”. If it was not charged, press the button again.

Tokens: the bet was not charged; the network may have taken its fee for the attempt (fractions of a cent).

FD-308The randomness request address is taken

What happened. The address where the oracle must write your round's number was taken by someone in advance. The site skips such addresses on its own, but all the nearest ones turned out to be taken.

What to do. Place the bet again in a minute. If it happens several times in a row, someone is deliberately interfering with your wallet: withdrawals and your balance are not affected.

Tokens: nothing was charged.

FD-309Too early

What happened. The step was sent before the network was ready: settlement is possible only after the oracle has written its number, and an expired round can be closed only 20 minutes after the bet.

What to do. For settlement, wait a few seconds and try again. To close an expired round, wait until 20 minutes have passed since the bet.

Tokens: the bet has been accepted by the contract and is waiting for the result — it is not lost.

FD-310The round has expired

What happened. The round was not settled within 20 minutes: the page was closed and the keeper service did not get to it in time, or the oracle responded too late. Such a round is closed with a separate command. If the oracle responded, the contract pays the regular table prizes (without jackpots); if it did not, the bet goes to the prize bank.

What to do. Press the game's main button (“Finish the spin”) again: the site will close the round itself and show the total. The “Close the expired one” button in your account does the same.

Tokens: the bet has been accepted by the contract and is waiting for the result — it is not lost.

FD-311Round not sealed in time

What happened. The contract mixes the hash of the block in which the bet is recorded into the oracle's number: this way the outcome cannot be computed in advance. This hash is available for about three and a half minutes. Usually the round is settled within that time, or the keeper service seals it; here neither the site nor the service made it in time.

What to do. Wait until 20 minutes have passed since the bet and press the main button: the round will close. To keep this from happening, do not close the page while a round is in progress, or turn on play without signatures — then the site seals and settles the round itself.

Tokens: this round's bet went to the prize bank and is not returned.

FD-312The oracle did not respond — bet refunded

What happened. The oracle did not write the random number within 20 minutes — the round's time limit. Such a round has no outcome, so the contract refunded the bet in full: nothing from it went to the prize bank or to the administrator.

What to do. You do not need to do anything: the bet is already on your game balance. If this keeps happening, the oracle is working intermittently — hold off on new bets.

Tokens: the bet has been refunded to the game balance in full.

FD-401The network node is overloaded

What happened. The network node through which the site reads the blockchain has limited the number of requests. This is a connection problem, not a game problem.

What to do. Wait 10–20 seconds and try again. Do not press the button many times in a row.

Tokens: the balance has not changed.

FD-402The network node is lagging

What happened. The network node fell behind the blockchain and did not accept the transaction, treating it as “too new”.

What to do. Repeat the action in 2–3 seconds.

Tokens: nothing was charged.

FD-403The transaction did not go through in time

What happened. The network did not confirm the transaction within the allotted time. Such a transaction will not go through later: it has expired.

What to do. Check your game balance and history. If the bet was not charged, try again. If it was charged, the round is recorded: press “Finish the spin”.

Tokens: the bet was not charged; the network may have taken its fee for the attempt (fractions of a cent).

FD-404The network rejected the transaction

What happened. The network checked the transaction and rejected it. The cause is usually outdated data on the page.

What to do. Refresh the page and try again. If the error repeats, write down the time and the code, and do not repeat the action blindly.

Tokens: the bet was not charged; the network may have taken its fee for the attempt (fractions of a cent).

FD-405No connection to the Solana network

What happened. The browser could not reach a Solana network node: there is no internet connection, or a VPN, an ad blocker or a corporate network is in the way.

What to do. Check your internet connection, turn off the VPN and blockers for fairdrum.to, and refresh the page. The balance is kept in the contract and will not go anywhere.

Tokens: the balance has not changed.

FD-501The signature-free session has expired

What happened. The signature-free session has run out of time. You chose its duration yourself when you opened it.

What to do. Open a new session with one signature under the game button. The bet that the session could not place was not charged.

Tokens: nothing was charged.

FD-502The session limit is used up

What happened. The signature-free session has used up the bet limit you set for it.

What to do. Open a new session — you can choose a higher limit. Or play with confirmation of every round in the wallet.

Tokens: nothing was charged.

FD-503The browser did not save the session key

What happened. The session key is stored in the browser's storage. In a private window, or when data storage is blocked, it cannot be saved.

What to do. Open the site in a regular window and allow data storage for fairdrum.to. Play with a signature for every round works without this.

Tokens: nothing was charged.

FD-601Withdrawal is still locked

What happened. Withdrawal from the game balance opens 12 hours after the last top-up — this is a contract rule, the same for everyone. Every new top-up restarts the 12 hours.

What to do. The opening time is shown in the cashier. Do not top up the balance if you plan to withdraw in the next few hours.

Tokens: the balance has not changed.

FD-602Invalid amount

What happened. The amount is zero or larger than the available balance. The available balance does not include jackpot parts that have not been paid out yet.

What to do. Enter the amount again or press “Max”.

Tokens: the balance has not changed.

FD-603No permission for this action

What happened. Only the account owner can perform this action, but another wallet signed it.

What to do. Check which account is selected in the wallet, reconnect the wallet and try again.

Tokens: the balance has not changed.

FD-604Vault protection was triggered

What happened. Before every payout and after every settlement the contract checks that the vault holds no less than it owes to all players and pots. If it does not, the operation is rejected entirely — so a bug or an attack cannot take other people's funds out of the vault.

What to do. This is an emergency safeguard; it is not triggered in normal operation. Your balance has not changed. Try again later; if it happens again, do not place new bets until the project announces that the cause has been fixed.

Tokens: the balance has not changed.

FD-900Unknown error

What happened. An error that is not in this reference: the site shows its original text.

What to do. Refresh the page and try again once. Check the balance and the history. If the error repeats, write down its text and the time.

Tokens: the balance has not changed.

The result has not arrived for more than a minute

The number is sent by an independent oracle: usually 10 seconds to 3 minutes. A stopwatch runs on the button. You can close the page — the keeper service will finish the round and the result will be on your balance.

The game button is inactive

The reason is written on the button: connect the wallet, top up the balance or wait for the result of the current round. If autoplay is running, stop it with the “Stop” button.

I closed the page in the middle of a round

The bet and the number are recorded on the network. Open any game: the button will offer “Finish the spin”, or the round has already been finished and the result is on your balance.

The balance on the site does not match the wallet

These are different amounts: the game balance is in the contract, the rest is in the wallet. After a top-up or a withdrawal, refresh the page.

The prize is smaller than in the table

A single prize cannot be larger than a quarter of the prize bank at the moment of the bet. If the bank is small, a large prize is cut down — this is a contract rule, and it is shown in the game's prize table.

The field showed a win, but less than the bet came back

A round is several 0.01 SOL stakes at once: there are ten in a 0.1 SOL round. The field shows the best of them (for example, ×2 for one stake out of ten), while the others may not have won. The total for the whole round is on the “Returned X of Y SOL” line under the field.

The wallet window does not appear

Check whether the browser has blocked the pop-up window, and open the wallet manually: the request is waiting there. On a phone, open the site inside the wallet app.

The wallet says “Transaction failed simulation”

This is a warning from the wallet itself when the network is busy. Press “Reject” and try again in a few seconds — nothing is charged.

The page looks broken or is in the wrong language

Refresh the page with the cache cleared (Ctrl+F5). The language is switched with the globe button in the header.