ETH/ETH2 staking transactions appear as a send and receive on Kraken
planned
Sarah T. - CoinTracker
Users may experience:
- Kraken ETH/ETH2 staking transactions are showing as a send and receive transaction and not pairing as a trade as would be expected.
Expected behavior:
- Transactions should correctly pair trade transaction.
- Ideally these transactions should show as a stake and unstake when ETH is traded for ETH2 or vice versa.
As a user, what should I do?
To correct this, you can create a manual transaction to accurately represent the trade and then categorize it as either a stake or unstake. For guidance on how to manually add a transaction, please refer to this
guide on manually adding a transaction
. To change the category of a transaction, please visit this guide on changing a transaction category
.How can users provide feedback?
You can upvote this forum post to indicate you are experiencing this behavior. The post status will be changed to
Complete
once a fix is rolled out to all users. Up-voters will be notified of the status change.I need additional assistance, who can I contact?
For further assistance, please contact our
support team directly
.Thank you for your understanding and cooperation as we work to enhance your CoinTracker experience!
Keywords: Kraken, ETH, ETH2, staking, transactions, manual transaction, categorize
Log In
This post was marked as
planned
This post was marked as
confirmed
This post was marked as
planned
This post was marked as
confirmed
This post was marked as
in progress
Sarah T. - CoinTracker
Merged in a post:
ETH On Kraken is misaccounted for ETH2
C
CT-5Oe1mYYO
In my account the ETH2 is still showing up for the Kraken exchange, I have a brand new account for both Kraken & cointracker & I tried reimporting, but whatever I do, cointracker doesn't mark it as Ethereum which is severely messing up the accounting & the cost basis. This seems to be due to the staking of ethereum which for some unknown reason is turned into ETH2 instead of remaining as ETH.
Sam - CoinTracker
This bug is still active as of June 2024.
This post was marked as
confirmed
Sarah T. - CoinTracker
submitted