Topic: CoinTracking - Profit/Loss Portfolio and Tax Reporting for Digital Currencies - page 21. (Read 122389 times)

What's the recommended way to "dispose of" defunct, unsellable tokens leftover in a wallet?  (E.g. Old BSC tokens with no pancakeswap liquidity). Something that books the related capital loss, and removes them from CT's ongoing coin balance reports.

Also, can you provide any detail as to what BSC import improvements have been made?  From latest release notes:
> "- Binance Smart Chain Blockchain Import Update (fix for new smart contracts, missing transactions)"

Thank you

@Plenty
Understand your point. And it is addressed. Thank you for your further patience.

I have had an ongoing support ticket for three months already!  First I was being reassured that the fix was being worked on.  Then I had huge apologies from support.  Again I was reassured the issue would be fixed.  Then two updates and it is still not fixed.  And unfortunately, I have neither the time, ability, nor interest for cointracking or my accountant to poke into my portfolio to manually add the translactions.  This is not a fix.  In fact if I had taken this advice months ago, I would have be required to pay someone for three months of transaction imports.  The whole idea of the platform is for automated blockchain accounting.  How hard is it to make sure that bug is fixed when the customer has indicated the technical problem with precision from the Exchange itself, repeatedly reminded you and the support staff via the ticket, and given you THREE MONTHS to simply add the Admin Debit field to the API?  There is no excuse except incompetence or malevolence.

PLEASE FIX THE BROKEN API AND PUSH IT INTO PRODUCTION.

Thank you!

~Paying Customer

@plenty
Please reply to the ticket your raised so that we can check the status there.
It is always possible to add transactions in the meantime manually if an API does not bring them in for whatever reason acknowledging it takes some effort here.

Nine API updates and not one was the Gemini fix. Sir, how can you say my issue has a high priority and that your team is working on it but it's been three months since Gemini clearly explained that Admin Debit was added to their API and CT still needs to fix this?  Your software has not given me a correct balance in three months, and my estimated tax reports to the IRS will be wrong due to CT's failure to update.  Please kindly fix this issue and push it to production as quickly as possible!
 

 

@clmns
We add this to our road map. We focus on Top20 chains first.

If they offer CSV export just sent us an example to check if it is usable/importable.

Hi, any chance to add DefiChain native wallet (not Cake DeFi) exports? (including liquidity mining) Either CSV or straight from the wallet/chain would be greatly appreciated.

Updates and Improvements

- Exodus CSV Import now supports the new file format
- AscendEX CSV Import now supports the new file format
- Binance CSV Complete Import Update (fix for transaction types + missing transactions)
- Crypto.com CSV Import Update (fix for internal transfers, DUST transactions)
- Nexo CSV Import Update (fix for missing transaction types)
- Coinex CSV Import Update (fix for missing trade pairs)
- Cake Defi CSV Import Update (fix for internal transfers)
- Coinex CSV Import Update (fix for missing trade pairs)
- HitBTC CSV Import Update (fix for deposits/withdrawals)
- Coinbase CSV Import Update (fix for FIAT purchasing fees)
- Gate.io CSV Import Update (fix for wrongly imported transactions)
- Exodus CSV Import Update (fix for missing transactions)

- Okex API Import Update (support of API v5)
- Binance API Import v2 Update (fix for transaction types, missing transactions)
- Indodax API Import Update (fix for withdrawal fees)
- Coinspot API Import Update (fix for fees)
- Gate.io API Import Update (support of API v4 with margin and future trades, fix for missing transactions)
- Swyftx API Import Update (fix for missing transactions)
- Bitvavo API Import Update (fix for fees, wrongly imported transactions)
- Bithumb API Import Update (fix for missing transactions)
- Coinbase API Import Update (fix for wrongly shown error message)

- BitBox Wallet CSV Import Update (fix for missing coins)

- Ethereum Blockchain Import Update (fix for new smart contracts, missing/duplicated/wrongly imported transactions, NFT trades)
- Binance Smart Chain Blockchain Import Update (fix for new smart contracts, missing transactions)
- Binance Chain Blockchain Import Update (fix for new smart contracts)

- Several Ticker updates for correct assignments and price history
- Corporate accounts: Backups can be created for all sub-accounts
- Tax report: PDF download update for loss transactions
- Date format was changed on the Enter Coins page
- Added Stratos partner benefits

@Plenty
We are working daily on many improvements. We will release a summary of new features and fixes soon.
And we are working on the GEMINI topic as well beside other things. Thank you for your patience.

It's been three months since I laid out my API problem for you directly from Gemini.  Will the API fix for the Gemini issue be released at the same time Polygon support is released?
What is the expected date for the next Cointracking platform update?

Thanks 

1 & 2 Yes, correct unless you add a start date to this API job. Then only transactions after this date will be imported (again).
 
If some transactions are imported wrongly please send us an E-Mail to [email protected] with transaction and wallet ID.

Hello,

Cointracking was unable to properly interpret a "multi swap" trade using the new ETH/DEX wallet import, and instead created two entries (a deposit and a withdrawal).  The old ETH importer was able to figure this particular type of transaction out.

I have a few questions:

1. When you delete an entry from the ETH/DEX wallet importer, it will always be reimported next time it syncs, correct?

2. Presuming the above is true, is there any way to tag an entry to be ignored without having it reimported?

Thanks!

                 

MATIC - almost done and will be released soon.

When Polygon support?

Thanks Andreas for clarifying.  I misunderstood the IOTA -> MIOTA example on Advanced Settings page.

@MuAnon
Not sure if I get you here.
It should only be done if you need to reset all your asset values, but only as "emergency case", but not regularly.
So this is nothing about back and forth as asset values are key.
And yes it will wipe out all manually set/adjusted asset values of course.

Could use some top-down workflow advice...which order to do things.

For example "Reset calculated Asset Values". Are we supposed to always do this after bulk-correction of wrongly assigned coins/tokens?

But that will also wipe out all manual asset valuation edits?

If so, what's the solution for going back and forth between these two tasks?

Thx

@theratears
We add this to our improvement list.

Hi could you please look at supporting Ronin wallet imports. Mainly used for Axie Infinity