@ChiKredell2
Hello,
We’ve received a notification regarding the reported scam incident, and we’re very sorry to hear about what happened.
⚠️ Important Security Warning: Please be extremely cautious of anyone contacting you privately and claiming they can recover your funds. Do not share your seed phrase, private keys, passwords, authentication codes, or connect your wallet to any recovery website sent to you by an unknown party.
We’re following up on the case as a priority. From a technical standpoint, the first step is to trace the affected transactions and determine whether the stolen assets are still on the originating network or have been transferred, swapped, or bridged elsewhere. Where the token or protocol provides legitimate administrative security controls, the appropriate technical options can then be evaluated.
Please remain available, as we may need the wallet address and transaction hash associated with the incident to properly trace the movement of the assets.
The sooner the relevant transaction information is reviewed, the better the chances of identifying the movement of the funds before they are transferred further.
@HARSHLIFE73
Hi, we completely understand your frustration, but please don’t feel that your stXRP is useless or that you’ve been left without an exit option.
stXRP represents your position in the Firelight Protocol and the underlying XRP/FXRP backing that position. With Firelight moving into Phase 2, the protocol is transitioning into its full operational stage, including active cover, streamed emissions, and updated unstaking mechanics.
Most importantly, you are able to initiate the unstaking process if you would prefer to exit your stXRP position and ultimately return to XRP. Please keep in mind that unstaking is subject to the applicable unbonding/withdrawal period, so the underlying assets may not become available immediately after the request is submitted.
If you’re currently unable to initiate the unstaking process or something is preventing you from proceeding, please let us know exactly what you’re seeing and we’ll help you determine the appropriate next step.
@JohnPryora1i
Before claiming, make sure you have a small amount of FLR in your wallet to cover gas fees. Also, connect your wallet through the official claims portal using WalletConnect, then select Tangem and approve all required signature requests.
That’s unusual, as the process should work as expected. We recently assisted another client through the complete connection process yesterday, and everything was working correctly on their end. It’s possible that a step in the process may have been missed or completed incorrectly. We’d be happy to guide you through the process again to ensure everything is set up properly.
@JohnPryora1i
If you’re still encountering an error, please send us a Direct Message with your wallet address, a screenshot of the exact error message, and let us know whether you’re using iOS or Android. We’ll investigate immediately and help you resolve the issue .
@JohnPryora1i
Please make sure you’re using the latest version of the Tangem Wallet. Also, ensure the Flare network is enabled in the app. If it’s missing, go to Settings → Manage Tokens/Networks and enable Flare.
@Wildwestit28
Once we receive the details, we’ll investigate and take the necessary steps to determine whether any action can be taken before the assets are swapped or bridged to another chain. We’ll do our best to assist you as quickly as possible.
@Wildwestit28
Hi @Wildwestit28, we’re sorry to hear about your experience. Please send us the affected wallet address and the transaction hash (TXID) so our team can review the activity immediately.
@abcdog12377
Congrats indeed! 🎉 As for Firelight — last I heard timelines had shifted a bit, no official word from the team recently. Worth checking their official channels for the latest update.
@HMoonmission
We’ve flagged your report for review with the rewards distribution system (pool, farm, and delegation). In many cases like this, the issue is related to UI indexing delay or a wallet/portal sync mismatch rather than missing emissions.