VOTE for TRILLION token quantity

Currently, Accointing can support more than 99 Billion tokens. There are many tokens with Quadrillion supplies now, so please increase the limit.

Love,
Tom Jones

The limit should at the very least be 999 Trillion, but i don’t think there should even be a limit. Ive gotten to almost 200 Billion in a single transaction worth about $650, so obviously if i would have invested more it would have been a lot higher than that.

1 Like

Can we get this fixed as soon as possible please.

2 Likes

What you, unfortunately, will have to do until Accointing implements this is. In your manual transaction use the max coin limit. Then make another manual transaction to add the rest.
Let me know if this works or if a coin limit is also reached on the wallet page.
It worked when I tried it :slight_smile:
image
image

1 Like

Hi Matt,
Your suggestion worked for me. I entered it like this manually. In the mobile app, GEMS and ZOOT are now displayed with the correct number for me.

In the display in the browser (Accointing - Cryptocurrency Portfolio Tracking & Tax Software) both (GEMS and ZOOT) are not listed and their “value” also seems to be missing. For me there is a difference in the total value in the Accointing App and in the browser.

1 Like

hey @CryptoCalypso can you send photos of the incorrect GEMS and ZOOT and send it to the following email:

I’m going to need you to help me out with the following:

  1. Account details
  2. Screenshot of the error you received
  3. Wallet/Exchange you were using when you encountered this issue
  4. Exchange or Wallet API keys, Wallet Address or CSV used to try to replicate the error (if required, send passphrase and secret key as well)
  5. A link to this page

Please send all of this to support@accointing.com and we will try to help you out as quickly as possible.

Unfortunately there are already many tokens with that high supply.
And if you buy soon enough you get 100 of trillions. In that case, I can’t use it (adding 1000 transactions)

1 Like

Same here. 99,999,999,999 still seems to be the max amount. When will this be changed?

When can we expect this to be implemented? It’s really hard and annoying to check every transaction in trillions and add it manual.

1 Like

AS of now, it is just on the roadmap.

When adding this way, I now get an accurate value for my coins, but my cost basis is all wrong (or at least not showing up in the main overview page. How should I classify these deposits?

1 Like

Make sure the manual transaction is at the correct date and time and your average price per coin should be fine. Make then the same second when doing this temporary fix.
Remember that we get our cost basis of coins from CoinMarketCap, so compare it to CMC to see if the cost basis is calculating correctly in our system.

Here is the breakdown of classifications: Crypto Tax Classifications : Accointing AG
Here is how you are taxed per classification: https://www.accointing.com/the-hub/?s=classifications&id=3300&post_type=post

Another vote for this. In my opinion we need support for at least 999 trillion tokens.

with the ridiculous token amounts for some of the meme coins this makes Accointing basically unusable:

121706400000 nUSD → 64056000000000000 DOGEZILLA

even the workaround (of split it to multiples) fails as I’d have to add thousands of transaction :slight_smile:

In the frontend we commonly round prices (esp. fiat representation of values) to 2 digits. On the internal side, we keep a precision of 8 decimals though. This is relevant to for the tax calculation and is precise enough. For coin quantities and values, we currently have a maximum of 9999999999999.99999999

I believe this post is to vote on extending this to more in both directions.

the internal representation definitely also needs to be updated as the current precision is just not sufficient for some coins and results in wrong asset value amounts. in my example case, the values of the coins converted to CHF is off by a factor of 1’000’000 now, the app & site show CHF 0.0002 instead of CHF 200.00 - which is not surprising as neither the before nor the after-comma precision suffices :slight_smile:

an elegant workaround (at least from a user’s perspective) for this could be to update the fields to accept a denominator, so f.e. M = millions, B = billions, T = trillions etc. so in my crazy example the 64056000000000000 DOGEZILLA could be entered as 64056000B DOGEZILLA.

1 Like

We have increased our system to the following:
999,999,999,999,999,999,999.99999999

1 Like

works great, thanks alot!

This topic was automatically closed after 14 hours. New replies are no longer allowed.