The max precision of numbers in Coda is 6. However, BTC (known as satoshis) require a precision of 8 decimal places. I would hope that a tech company would recognize the role of crypto and facilitate accurate recording of a coin. Please increase precision to at least 8. Thanks.

1 bitcoin is 100,000,000 satoshis. Keep track in Satoshis and it isn’t a problem. You can use whole numbers! Math is your friend. Or Instead of 1 bitcoin, move the decimal place two to the right and keep track. Then you can use six decimal places to your heart’s content. If your fiat conversions a…

Or, alternatively, Coda could support a higher level of precision – like the spreadsheets they seek to replace. Your (pedantic) workaround is nothing more than Coda’s limitations forcing me to do things in a way that’s not useful to me. That’s not a plan for success.

Floating point math vs integers https://0.30000000000000004.com/

LOL. JAW, you must be a real dream to live with. Your FP vs Int argument is old news, bro. Even 1979 Visicalc accurately-enough supported precision greater than eight decimal places. Here I am, over 30 years later, asking a tool provider to at least support eight decimal places. Shame.

Hi @Joey_Serio , you are right: having Coda dealing with higher precision would help you with your current issue. And it’s certainly not an insane topic that you correctly put into the “suggestion box”. I can understand your frustration. However, people took some time to read your post and sugges…

[image] Is Max Int 9007199254740992? What is the max int in Coda? Given that Power(2, 54) - 1 < Power(2, 54) Returns false and Power(2, 53) - 1 < Power(2, 53) returns true it seems to be 9007199254740992. Can anyone confirm that? @BenLee @Paul_Danyliuk , one of you …

Federico, suggestions are better if they’re not surrounded by snark (“Math is your friend”). However, the biggest issue is that JAW’s idea if self-evident to anybody who has ever worked with numbers. The point of my suggestion wasn’t “here’s a problem, give me a work-around.” The point, and why i…

I’m playing with a crypto based doc right now, and I’m using a shares first approach. I specify the base unit of currency, e.g. satoshis or gwei, and then allocate myself my currency in terms of that number. It turns out that that’s also how Bitcoin and Ethereum implement ownership of tokens under …

I appreciate your input. Again, I recognize that there are plenty of other ways to track this information – which I had previously deployed. My initial comment was to highlight the issue and make the Coda developers aware that at least one person is expecting a level of precision that has been avai…

Your observation and question about max Int size is also very important considering how floating points with precision greater than 6 have to be treated. I can’t imagine trying to use Coda for some of the research we’ve done in the past with large numbers at high precision.

Can't keep track of Bitcoin and other crypto with only 6 decimal places for numbers

Product Feedback

Connor_McCormick May 11, 2021, 3:00pm 7

One good reason to know max int

Topic		Replies	Views
More than 4 Decimal Spaces?	2	174	July 17, 2024
Bug: Rounding Error on a number that isn't being rounded Product Feedback	11	1419	June 30, 2021
18 digits number column - Bug Bugs	1	83	February 4, 2025
Further localization of currencies and numbers Product Feedback	36	4574	September 22, 2025
Problem with Uploading Data (Extra Decimal Points for Percentages) Bugs	1	843	January 6, 2020

Can't keep track of Bitcoin and other crypto with only 6 decimal places for numbers

Related topics