Youd be suprised from the other rediculas requests and odd messages i get.... Somedays its entertaining other days its hard to stay professional when your constantly wondering if the person your talking to will start spouting off random sayings. Its comes with running a biz.... I suppose....

Thanks for the input but I'm very aware of floating point precision flaws and I think it more has to do with rounding Bitcoins' 8 decimals and compressing them into a common format for everyone which is usually 2 decimals(also aimed at USA so I picked the 2 decimal precision)

Also on top of that all my prices are linked to USD costs not BTC so they are converted on the fly for each display for example

Product "A" costs around $250 so to show the customer the price in BTC value I gotta divide which at the current rate $3.1

Obviously displaying a 12 decimal precision number will look un-attractive to buyers so I compress it to a common format of 2 decimal places which PHP outputs as


How ever a "sub-total" is never the "total" cost I have to include shippingcosts and once in a while "tax" so lets look at this example (remember my prices in my database are link in USD format)



Check


Compare Values


Round 87.096774193548 BTC


Notice the extra Bitcent?
even though customers are Paying the same thing as they would be.... it just "looks" more.

If you want to clip decimals, a good method to use is:

$foo = "8.91232323234223";
echo bcadd($foo, '0', 5);  // truncates to 5 decimal places

hope that helps.

Also, you should *always* round down and absorb the cost yourself.