Hey Team,
I am running into an issue – I have a few cryptos staked on Kraken. However, the value of the staked cryptos shows as 0. I believe this isn’t Emma’s fault, but rather the Kraken API doesn’t share those £ value.
I was running this through ChatGPT and found a potential fix below. So my feature request would be to enquire about how easy/feasible it would be to implement option 1 below “Map Tickers / Merge Tokens”
Adding a screenshot to show what it looks like on my end. The “Kraken SOL” account is at 0.00, and the Kraken SOL.F (the staked account) also shows the value of £0, while there are actually 8.34 SOL in there.
____
GPT Excerpt
How to Fix It (Within Your Portfolio Tracker)
The solution lies within the settings of your portfolio tracker software. You need to tell the software how to treat these staked assets. Most reputable trackers have a feature for this.
Look for settings with names like:
-
Map Tickers / Merge Tokens: This is the most common solution. You’ll find a setting where you can map the staked ticker to its base asset. For example, you would create a rule that says: “Treat
ETH2.SasETHfor pricing purposes.” -
Coalesce Balances: Some trackers use this term, meaning it will combine the balances of
ETHandETH2.Sunder the singleETHticker for valuation. -
Manual Edits: As a last resort, you might have to manually edit the transaction where you staked the asset. For example, change the “Staked ETH” transaction from a “Withdrawal” of ETH to a “Transfer to Pool” or a “Swap” from ETH to ETH2.S (and then map ETH2.S to ETH). This is tedious and not recommended if a mapping feature exists.
Example for Koinly: In Koinly, you can go to Settings → “Merge Staked Balances” and it will automatically handle most of Kraken’s common staked assets. For others, you may need to go to the “Currencies” tab and set a “Worth” value for the custom token.
Example for CoinTracker: CoinTracker often requires you to manually classify the “staking” transaction as a transfer. When you do this, you can select the staked token (e.g., DOT.S) and manually edit it to map to the unstaked token (DOT).
