Re: [Bitcoin-development] # error Bitcoin cannot be compiled without assertions. NOT

2014-06-04 Thread Jannis Froese
There are reasons to have assertions enabled by default in software like Bitcoin Core, where incorrect behaviour can be costly. But this comes at a prize: our assertions have to satisfy certain performance requirements. It's no longer possible to do expensive, redundant checks in performance

Re: [Bitcoin-development] moving the default display to mbtc

2014-05-03 Thread Jannis Froese
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03.05.2014 02:54, Ben Davenport wrote: No one quotes amounts as 63 k$ or 3 M$. The accepted standard at least in the US is currency-symbolamountmodifier, i.e. $63k or $3M. As you said, that's in the US, and I strongly suspect the sole reason

Re: [Bitcoin-development] BIP0071 media type registration with IANA

2014-04-26 Thread Jannis Froese
Am 2014-04-26 22:17, schrieb Mike Hearn: Bitcoin is not a vendor, so I doubt that would work. By my interpretation of RFC 6838, the Bitcoin Foundation or even Gavin himself could register a vendor tree for Bitcoin. In the case of the foundation registering, getting the subtree named vdn.bitcoin

Re: [Bitcoin-development] 0 confirmation txs using replace-by-fee and game theory

2014-04-24 Thread Jannis Froese
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24.04.2014 14:15, Mike Hearn wrote: Beyond needing to double balances, what if the shop is selling me a phone on contract? So the actual cost of the phone is lower than the real price on the assumption of future revenue. Alice double spends

Re: [Bitcoin-development] bits: Unit of account

2014-04-20 Thread Jannis Froese
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I agree that a unit based on 1e-6 BTC is easier to use in practice than BTC. The name microbitcoin is ok-ish. Nearly all countries officially use the SI-system, but that doesn't mean that the average citizen knows all the SI prefixes. Mega, kilo and