Yes, the internal representation of Bitcoins is the 64-bit unsigned INT, but I'm talking about storing customer account balances, trade prices, etc. I would not

Yes, the internal representation of Bitcoins is the 64-bit unsigned INT, but I'm talking about storing customer account balances, trade prices, etc. I would not use DECIMAL if I were writing an alternative client for Bitcoin or for some other software that must create network transactions at a low level. Even the RPC protocol for the main Bitcoin client returns fixed-point numbers and expects non-integers for input arguments [1]. But I think we can all agree that using FLOAT for this kind of thing is just plain wrong. [1] https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_Calls_list https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_Calls...