KyberSwap transaction ingestion creates incorrect decomposition
acknowledged
Bug Report:
What is the issue?
Transactions from KyberSwap Aggregator Executor V3 are ingested and decomposed into multiple trade legs that result in inconsistent cost basis display on sale transactions, despite correct underlying cost basis tracking.
Who is affected?
Users with transactions executed through KyberSwap Aggregator Executor V3 involving partial asset returns and multiple outputs.
What is the workaround?
Users can manually edit or recreate the transaction. For example, if a transaction sends a large amount of an asset, receives a slightly smaller amount of the same asset back, and also receives another asset, the transaction can be recreated to reflect the net amount disposed rather than the full amount sent plus the amount received back.
Keywords: kyberswap, ingestion, transaction decomposition, cost basis
Log In
Sarah R - CoinTracker
updated the status to
acknowledged
Correction: this was marked Complete in error by an automated audit — the linked engineering ticket (INT-9189) fixes a different KyberSwap flow (Uniswap V4 zap add-liquidity NFT minting), not the Aggregator Executor V3 trade-leg decomposition bug this post describes. Reverting to Acknowledged; still open. Apologies for the confusion.
Sarah R - CoinTracker
updated the status to
complete
This has been shipped! Thanks for the feedback.
M
Modern Frog
updated the status to
acknowledged