Bscscan exports but report doesn't pick up gains and losses

[gmahe]

Export

So I've exported 2 files of my wallet on bscscan:

• Transaction
• Token Transfers (BEP-20)

Conversion tool / transaction records

When I do bittytax_conv file on each files I get different xlsx

For Transaction I get this format:

Type	Buy Quantity	Buy Asset	Buy Value in GBP	Sell Quantity	Sell Asset	Sell Value in GBP	Fee Quantity	Fee Asset	Fee Value in GBP	Wallet	Timestamp	Note	Txhash	Blockno	UnixTimestamp	DateTime	From	To	ContractAddress	Value_IN(BNB)	Value_OUT(BNB)	CurrentValue @ $293.394072807132/BNB	TxnFee(BNB)	TxnFee(USD)	Historical $Price/BNB	Status	ErrCode	Method

and for the Token Transfers (BEP-20) export I get this one:

Type	Buy Quantity	Buy Asset	Buy Value in GBP	Sell Quantity	Sell Asset	Sell Value in GBP	Fee Quantity	Fee Asset	Fee Value in GBP	Wallet	Timestamp	Note	Txhash	Blockno	UnixTimestamp	DateTime (UTC)	From	To	TokenValue	USDValueDayOfTx	ContractAddress	TokenName	TokenSymbol

They seem really different.

Transaction doesn't really have the token names I bought neither its value.

Token Transfers (BEP-20) seem to have the list of the token I bough and their quantity

Tax Report

So I use the command bittytax file without any conf file as I need to get GBP.

Token Transfers (BEP-20) export returns me some audit with 0 balance for all token

and Transaction export seem to return a proper tax report but costs and gains are 0 and I only see the fees.
That doesn't make sense as I have losses some years and profit some others.

What's wrong

What am I missing in the conversion?
Any help would be much appreciated!

Thanks

[nanonano]

Hi @gmahe,

For BSCscan, or any of the other EVM block explorers (i.e. Etherscan, HecoInfo, PolygonScan, SnowTrace, FTMScan).

You need to export the first 4 report types ("Transactions", "Internal Transactions", "Token Transfers" and "NFT Transfers").

Each export file is in a different format, some maybe empty if you haven't performed a transaction of that specific type. When you parse these files with the Conv tool it will generate a different worksheet for each one.

You might notice that the "Tokens Transfers" and "NFT Transfers" are matched as Etherscan exports. This is because the export format for these files is the same across all the different EVM explorers. The transaction record Wallet will also be labelled as an Ethereum address. You may have to rename these manually, unless as mentioned below.

It is important to note that each exported file has a filename which contains your wallet address. It is vital that you keep your wallet address in the filename, as this is used to identify if tokens are being sent out, or received to your wallet.

Once you have exported all 4 files, you should pass them ALL into the Conv Tool in one go. This will allow them to be analysed as a whole by the merge parser.

The merge parser will attempt to match transactions across the different export files with the same TxHash (Transactions ID), and perform the following.

1. Identify transfers fees for moving of Tokens or NFTs
2. Identify Staking transactions.
3. Identify Multi-token transactions (i.e. Swaps, LP-Tokens)

This is all best effort, you should always review that your transactions are correctly categorised.

If the merge parser makes any changes to the "Tokens Transfers" or "NFT Transfers" transaction records, it will also correctly rename the worksheet and wallet address according, so they no longer refer to Etherscan.

Once you have your BittyTax_Records.xlsx file with all the data merged, you need to review each transaction, and categogise it's Type correctly from the drop-down menu of valid choices, see https://github.com/BittyTax/BittyTax#transaction-records.

The tax report will only be correct if all your transactions complete (all wallets, exchanges) and they are all categorised correctly, otherwise it's a case of garbage in, garbage out.

[gmahe]

Thank you for taking the time! I can see it started doing well on bittytax BittyTax_Records.xlsx but sadly it fails on coingeko api
Too Many Requests for url: https://api.coingecko.com/api/v3/coins/..., Is there a workaround to that? maybe some sort of progress so we can start where we've left off and cache the progress/prices?

Very much appreciated you're taking the time to reply. 🥇

[nanonano]

If you just want to audit, use --audit, this will prevent any price API look ups.

Otherwise, it's best to avoid using CoinGeck. It will cache the historic prices it retrieves, so you could try waiting a couple of minutes and then running it again. To remove CoinGecko altogether, see #291 (comment).