No quests appearing despite staking on Crypto.com

Hey everyone, I’m having some trouble with my Crypto.com account. I’ve connected my wallet and I’m pretty sure I’m staking, but for some reason the app keeps telling me I’m not eligible for quests. It’s really frustrating because I want to earn those extra rewards.

Has anyone else run into this issue? I’ve double-checked everything and it all looks correct on my end. Maybe there’s a delay in the system recognizing my staking status?

I’d really appreciate any advice or tips on how to fix this. Thanks in advance for your help!

hey there Lee_Books! :raising_hand_man: i’ve been using crypto.com for a while now and lemme tell ya, sometimes these things can be tricky. have you checked if your staking amount meets the minimum requirement for quests? :thinking: it’s different for each tier, so that might be why.

also, when did you start staking? sometimes it takes a lil while for the system to catch up, ya know? like a day or two.

oh, and here’s a random thought - have you tried using the mobile app instead of the website? sometimes one works better than the other for me.

let us know if any of this helps! i’m curious to hear what ends up working for ya. good luck! :four_leaf_clover:

I encountered a similar problem a while back. It’s worth noting that eligibility for quests isn’t instantaneous after staking. There’s usually a processing period, which can take up to 24-48 hours. If you’ve recently staked, I’d suggest waiting a bit longer before taking further action.

Another point to consider is the staking amount. Ensure you’ve met the minimum requirement for quest eligibility. This varies depending on your card tier and region.

If the issue persists after waiting and verifying your stake, contacting Crypto.com support directly is your best bet. They can check your account status and resolve any backend issues that might be preventing quest access.

yo man, i had the same issue last month. it was driving me nuts! turned out there was a glitch in their system. try logging out completely, clear browser cache, and log back in. that fixed it for me. if not, hit up their support team. they’re actually pretty helpful