Common 8LNDS Issues and How to Fix Them
Sent 8LNDS on the wrong network or watched a claim hang? Each fix starts with one contract address and the Base network check that prevents irreversible loss.
Most issues with 8LNDS fall into four categories: the token doesn't show up in the wallet (you need to import it by the contract address), claim doesn't work (no ETH for gas or tokens are still in vesting), balance mismatches between sources (dashboard vs wallet vs basescan), and trading errors on Uniswap (slippage, liquidity, wrong network). All of these can be solved if you understand the cause. The most irreversible mistake is sending 8LNDS to an address on an unsupported network, so always check that you're on the Base network before any transaction. Contract: 0x55f9c8992fc4abce5aca585bf8f18284a2379d4c.
Summary Table of Issues
| Issue | Cause | Solution |
|---|---|---|
| Don't see 8LNDS in MetaMask | Token not imported | Import tokens → contract address |
| 8LNDS disappeared after reinstalling MetaMask | Re-import needed | Import again by address |
| Claim doesn't work | No ETH for gas, tokens not unlocked | Top up ETH, check vesting |
| Claim transaction stuck | Low gas, network congestion | Speed Up or wait |
| Bought on Uniswap, don't see it in MetaMask | Token not imported | Import tokens |
| Receiving less 8LNDS than expected | Slippage + price impact | Reduce size, check liquidity |
| Can't sell — slippage error | High slippage or low liquidity | Increase slippage to 1-3% |
| Received fewer tokens than the PoL calculation | Vesting — unlocked in portions | Check the vesting schedule |
| Dashboard vs basescan show different numbers | Only claimed tokens are visible on basescan | This is normal |
| Transferred to the wrong network | Not Base | Funds most likely lost |
| Suspect a fake token | Similar ticker, different contract | Verify against the official address |
| Wallet compromised | Seed phrase leak | Urgently transfer to a new wallet |
Don't see 8LNDS in the wallet
The most common issue. After a claim or purchase, the token doesn't show up in MetaMask.
Cause
MetaMask only shows the balance of tokens that have been imported into the wallet. Unfamiliar ERC-20 tokens don't appear automatically.
Solution
- In MetaMask, switch to the Base network
- At the bottom of the token list → Import tokens
- In the Token Contract Address field, enter: 0x55f9c8992fc4abce5aca585bf8f18284a2379d4c
- The symbol (8LNDS) and decimals (18) will be pulled in automatically
- Click Add Custom Token → Import Tokens
After this, your 8LNDS balance will be displayed.
Claim doesn't work
The claim button is inactive or the transaction doesn't go through.
Possible causes
A. No ETH for gas
- Without ETH on the Base network, it's impossible to sign a transaction
- Solution: buy a little ETH on Base via Meld.io or withdraw it from an exchange
B. Tokens not yet unlocked under vesting
- Vesting is 2.5% immediately + 2.5% each week
- If the last unlock was less than a week ago, there's no new portion yet
- Solution: wait for the next unlock
C. The project's pool hasn't closed yet
- The bonus is only credited after the Funded stage
- If the pool is in the Open or Funding stage, the bonus isn't activated yet
- Solution: wait for the pool to close
D. Technical glitch
- Sometimes the interface caches outdated data
- Solution: reload the page, reconnect the wallet
If nothing helps
Contact support: [email protected], providing:
- Your wallet address
- A screenshot of the issue
- The transaction ID (if there was one)
Claim transaction "stuck"
The transaction has been sent but hasn't been confirmed.
Causes and solutions
- The Base network is busy — confirmation usually takes seconds, sometimes minutes
- Gas too low — increase it via Speed Up in MetaMask
- Nonce conflict — cancel via Cancel Transaction in MetaMask and try again
- Dead battery / internet — check your connection
On Base, getting stuck is rare. If a transaction has been pending for more than 30 minutes — something is definitely wrong and you need to act.
Bought on Uniswap — don't see it in the wallet
The purchase went through, but MetaMask shows 0 8LNDS.
Cause
The same as in issue #1 — the token isn't imported.
Checking that the purchase actually went through
- Open basescan.org
- Enter your wallet address
- Find the purchase transaction → you'll see an incoming transfer of 8LNDS
- If you see it — the tokens are yours, you just need to import them into MetaMask
- If you don't see it — something went wrong during the swap, check the transaction status in Uniswap
Received less 8LNDS than expected on purchase
Slippage + price impact are normal in DEX trading.
Causes
- Slippage — the allowed deviation of the actual price from the expected price
- Price impact — a large trade moves the price within the pool
- MEV (Maximum Extractable Value) — less relevant on Base than on Ethereum
Solutions
- Reduce the trade size — if liquidity is low, split it into several
- Check the slippage tolerance in Uniswap (usually 0.5-1%, up to 3% for low-liquidity tokens)
- Use aggregators (1inch, Matcha) — they find the best route
More details
Can't sell — slippage error
When trying to sell 8LNDS, Uniswap returns an error or the transaction doesn't go through.
Solutions
- Increase the slippage tolerance to 1-3% in Uniswap settings
- Split the sale into several smaller operations
- Wait if it's during a volatility peak
- Use aggregators for a better route
Received fewer tokens via PoL than expected
You invested, for example, 1,000 USDC → expected 40,000 8LNDS (at a price of $0.001), but the wallet shows less.
This is normal — vesting
All 40,000 8LNDS have been credited, but they unlock on a schedule:
- Immediately: 2.5% = 1,000 8LNDS
- After a week: another 2.5% = 2,000 8LNDS in total
- And so on over 39 weeks → totaling 40,000 8LNDS
Full breakdown
Check in the dashboard
In the Bonuses section, there should be a breakdown: total amount / unlocked / claimed / locked.
Numbers in the 8lends dashboard differ from basescan
A common misconception. This is normal behavior.
Why this happens
- The 8lends dashboard shows everything credited (including amounts not yet unlocked under vesting)
- basescan shows only tokens already transferred to your wallet (the ones you've claimed)
- The difference = the amount of tokens not yet claimed
More details
When you should worry
If after a claim you see that no transaction appears on basescan within 30 minutes — that's a problem. Contact support.
Transferred 8LNDS on the wrong network
The most dangerous mistake.
Scenarios
A. Sent to Ethereum Mainnet instead of Base
- If the address is the same — the tokens ended up at another EVM address on a different network
- There's no such 8LNDS contract on Ethereum Mainnet → the tokens physically don't exist there → they're lost
B. Sent to Solana, BSC, or another non-EVM network
- The address structure is different — usually the transaction won't go through
- But if it somehow did — the tokens are definitely lost
What to do
- In 99% of cases — the tokens are lost forever
- In 1% of cases (if sent to an EVM network where you have the same address) — theoretically they can be transferred back via a bridge, but this rarely applies to random ERC-20 tokens
- The lesson: always check the network in your wallet before sending
Prevention
- Never copy an address from old messages — it may be outdated
- Verify the network in MetaMask against the recipient's network
- Send a small test amount before a large transfer
I suspect I'm holding fake 8LNDS
In DeFi there are scam tokens with similar tickers, created to deceive.
How to check that your 8LNDS is genuine
Verify the contract address against the official one:
0x55f9c8992fc4abce5aca585bf8f18284a2379d4c
This address is published:
- On the official 8lends.io website
- In the whitepaper
- On basescan.org → check holders and transactions
- On GeckoTerminal → the official USDC/8LNDS pair
If you have a different address
It's a scam token, not the real 8LNDS. Actions:
- Don't trade this token — it's a loss of money
- Remove it from MetaMask via Hide Token
- Move your genuine funds to a new wallet if you suspect that your seed phrase has been compromised
- Report it to 8lends support — it may be part of a phishing attack
Wallet compromised — what about my 8LNDS
A critical situation. If you have reason to believe your seed phrase or private key is compromised:
Urgent actions
- Create a new wallet (a different seed phrase, ideally on a clean device)
- Urgently transfer all funds from the compromised one to the new one
- Notify 8lends support via [email protected] — they may help you migrate your account to a new address
What 8lends can do
- Re-link your account to a new address (with additional KYC verification)
- Transfer pending rewards (unlocked vesting) to the new address — if technically possible
- Cannot recover stolen funds — on-chain transactions are irreversible
More about wallet security
Frequently Asked Questions
How do I know the official 8LNDS contract is the right one? Verify it against the sources: (1) the official 8lends.io website, (2) the team's Telegram channels, (3) the whitepaper, (4) GeckoTerminal/DexScreener (they usually verify new tokens). Address: 0x55f9c8992fc4abce5aca585bf8f18284a2379d4c.
Why doesn't 8LNDS appear automatically in the wallet? MetaMask automatically supports only tokens it knows (for example, USDC, USDT on major networks). New or less popular tokens need to be imported by address. This is the standard for all Web3 wallets, not specific to 8LNDS.
Can tokens sent to a burn address be recovered? No. A burn address has no private key — no one can spend tokens from it. This is completely irreversible, and that's the point of a burn — the tokens disappear forever.
Can I sell all my 8LNDS in a single transaction? Technically yes, but the price impact will be enormous for a large amount in a small pool. It's recommended to split it into several transactions over several hours or days so as not to crash the price.
What if 8lends support takes a long time to respond? The standard response time is within 24 hours on business days. If it's longer — resend the request via Telegram https://t.me/eightlends. Providing specific data (address, transaction ID, screenshots) speeds up resolution.
Can 8lends block my tokens? No. 8LNDS are ERC-20 tokens in your wallet under your control. The team technically cannot block tokens that are already yours. The 8LNDS contract is a standard ERC-20 with no admin functions to block individual addresses.
What if I had 8LNDS in a lock mechanism at the time of the problem? It depends on the situation. If the wallet is not compromised — the tokens will return through the standard unlock process. If the wallet is compromised — contact support and explain the situation.
Can I get 8LNDS back if I accidentally sent it to a friend? Only if the friend voluntarily returns it — on-chain transfers are irreversible. This is a basic property of the blockchain, not specific to 8LNDS.
What should I do if I accidentally approved (Approve) a questionable smart contract? Use revoke.cash or MetaMask's built-in functionality to revoke approvals. Regularly checking which contracts have access to your tokens is a good security practice.
Should I connect to scam sites posing as 8lends? Never connect to suspicious clones. The official URL is app.8lends.io. Any other domain with a similar name is a scam. More about scam protection
See also:
Risk disclosure: crypto token operations are irreversible — sending to a wrong address or to an unsupported network can lead to irreversible loss of funds. 8lends has no technical ability to return tokens lost due to investor errors. Safeguarding the seed phrase and verifying contract addresses are the investor's responsibility. 8lends is a platform operated by CLEARCHAIN CORP, registered with FINTRAC (Canada) as a Money Services Business. Maclear AG (Switzerland), a member of PolyReg SRO under the supervision of FINMA, acts as Collateral Agent. Regulatory framework as of September 2026.