Basically, the title. I had someone in discord help me narrow down that there’s probably an RPC error in a node and that’s why I haven’t been able to claim rewards for two weeks.
Some basic info:
-I’ve been staking in the Nami wallet and the Berry pool for a long time, probably a couple of years.
-I’ve been claiming my rewards weekly up until last Monday when I got this error: “Transaction not possible (maybe reward amount too small)”
-I took it at face value and waited a week, but now I’m getting the same error. I’m up to 22 ADA in claimable rewards, which is a lot more than I usually claim, so it doesn’t seem like the reward amount is too small.
Can anyone help with this, or shed some info? Thanks all in advance, I appreciate any and all assistance.
You do not need to “claim” rewards. The reward value is automatically added to your staking balance after each epoch. Claiming your reward each epoch is only costing you money.
However, loading your seed phrase into another wallet would also work.
Hey, thank you all - some really helpful stuff here.
I did a combination of things. I restored my seed phrase in a different wallet to hedge my bets, as I wasn’t sure what might be going on in my Nami wallet. Trying out Lace now.
Now that I know I don’t have to claim my rewards, I’m happy to wait for my funds to be auto-deposited, I wasn’t aware of that mechanism previously.
Staking rewards are automatically added the the wallet staking balance for the following epochs. There is no need to “claim” rewards.
The only really relevant part is what happens when you spend from that wallet. For some wallets (like Daedalus) when you spend, the current staking balance is automatically used as one of the inputs for that transaction. For some other wallets (@rhyslbw mentions Nami), the current staking balance must be explicitly added as one of the transaction inputs.
current staking balance is automatically used as one of the inputs for that transaction… the current staking balance must be explicitly added as one of the transaction inputs.
For OP clarity, this is conceptually an input, not technically a “transaction input” (or txIn). I like to think about this type of thing as a “funding source”, which can also include things like deposit returns.
Good to hear you’re trying Lace @Darwyn43. As you’ve found out it handles the withdrawal of rewards when a balance is available in the next transaction you make, which is most optimal for UX and fees, at least by default.
This thread helped me move from Nami to Lace, but as of several weeks ago, the Lace wallet started to become stuck on a loading screen and would never finish. In that time, Nami started to work again, so I moved back to Nami for basic functionality, hoping a Lace update might eventually fix my issue there. Since then, however, the reverse has happened - as you probably know, Nami has become part of Lace, and now I can no longer access Nami. Yet the Lace issue never resolved and I’m still stuck on loading.
Everyone here was quite helpful before - does anyone have a thought on how I might get Lace to load? I now don’t have access to my funds (although I’ll try to see if I can find them on Cardanoscan next as a temporary fix).
You can always restore in yet another wallet app – e.g., Eternl or Typhon – with your seed phrase.
They are all just interfaces to the same wallets on the chain. (There are some differences in features, like Nami not being able to access the multiple addresses used by other wallet apps or no other wallet app being able to manage the multi-delegation feature Lace invented, but if you haven’t used multi-delegation Eternl and Typhon should be able to work out of the box.)
Okay, I thought this might be the direction. Thank you both. I did really LIKE Lace…if I uninstall the Chrome extension and re-download it, can I restore the wallet in Lace?
Yeah, and I probably should have. But I assumed that I’d have to restore the wallet if I got rid of the extension and I was trying to avoid it if I didn’t have to. Turns out it was way easier - reinstalling just fixed it. So yeah, false alarm. Thank you all for the help, super helpful as usual.