Quote
warning fee estimation is currently not possible
i guess it is because of the fork coming in 25th ??
awesome, makes sense now.,
Topic: Bitcoin Core 0.15.0.1 Released - page 3. (Read 30661 times)
i guess it is because of the fork coming in 25th ??
awesome, makes sense now.,
Quote
warning fee estimation is currently not possible
i guess it is because of the fork coming in 25th ??
Quote
warning fee estimation is currently not possible
i guess it is because of the fork coming in 25th ??
Question/concern..
Not sure of all the "sauce" that goes into generating the public/private keys for bitcoin, but in any of it, is there any RSA Public key being used? If so seems there is a hack out now that's able to factor large prime numbers..
Just google "KRACK and ROCA" its so bad that even WPA2 clients are vulnerable..
Icon
Not sure of all the "sauce" that goes into generating the public/private keys for bitcoin, but in any of it, is there any RSA Public key being used? If so seems there is a hack out now that's able to factor large prime numbers..
Just google "KRACK and ROCA" its so bad that even WPA2 clients are vulnerable..
Icon
Note that KRACK affects WPA2 directly, not RSA, and ROCA is an issue with a specific implementation of RSA not the algorithm itself. But no, Bitcoin only uses elliptic curve cryptography on secp256k1, an area of cryptography founded on the hardness of the discrete logarithm problem which is different to the prime factorization problem RSA relies upon. It also uses SHA2 and RIPEMD160 for hashing but that's separate too.
Question/concern..
Not sure of all the "sauce" that goes into generating the public/private keys for bitcoin, but in any of it, is there any RSA Public key being used? If so seems there is a hack out now that's able to factor large prime numbers..
Just google "KRACK and ROCA" its so bad that even WPA2 clients are vulnerable..
Icon
No. ECDSA is not affected by that issue. Not sure of all the "sauce" that goes into generating the public/private keys for bitcoin, but in any of it, is there any RSA Public key being used? If so seems there is a hack out now that's able to factor large prime numbers..
Just google "KRACK and ROCA" its so bad that even WPA2 clients are vulnerable..
Icon
Am finding it difficult to understand this bitcoin core
Question/concern..
Not sure of all the "sauce" that goes into generating the public/private keys for bitcoin, but in any of it, is there any RSA Public key being used? If so seems there is a hack out now that's able to factor large prime numbers..
Just google "KRACK and ROCA" its so bad that even WPA2 clients are vulnerable..
Icon
Not sure of all the "sauce" that goes into generating the public/private keys for bitcoin, but in any of it, is there any RSA Public key being used? If so seems there is a hack out now that's able to factor large prime numbers..
Just google "KRACK and ROCA" its so bad that even WPA2 clients are vulnerable..
Icon
My Bitcoin Core node is still crashing during startup at random times. Sometimes it loads just fine, other times the start screen becomes not frozen with the "not responding" message and i have to close it.
The faulty module seems to be ntdll.dll. I thought the 0.15.0.1 fix was supposed to fix this but it still crashes.
The faulty module seems to be ntdll.dll. I thought the 0.15.0.1 fix was supposed to fix this but it still crashes.
The 0.15.0.1 release fixed only a specific bug caused by a fee setting being removed. You must have a different issue.
I have found this syncs blockchain much faster vs old wallet versions, not sure if i just got lucky but at 1 stage i was downloading 1.67% per hour on my current laptop and usually if i get anywhere near 0.5% per hour on pre 0.15 versions i was pretty chuffed. Thanks for all the hard work from devs Smiley.
thanks..
thanks..
My Bitcoin Core node is still crashing during startup at random times. Sometimes it loads just fine, other times the start screen becomes not frozen with the "not responding" message and i have to close it.
The faulty module seems to be ntdll.dll. I thought the 0.15.0.1 fix was supposed to fix this but it still crashes.
The faulty module seems to be ntdll.dll. I thought the 0.15.0.1 fix was supposed to fix this but it still crashes.
Is there any possibility that the bitcoin will going down after segwit?
SegWit have no downsides so It can't make the price go down. It's being almost two months since SegWit activation and as you can see, the price is going nowhere but UP.
Is there any possibility that the bitcoin will going down after segwit?
Amidst all this, but I kind of think all this fork thing is propagated by some sole developers who wants gain for the selves even though community benefits little somehow.
Which ever fork, BITCOIN remains BTC
Which ever fork, BITCOIN remains BTC
There's probably going to be another split between bitcoin legacy and SegWit2X version of bitcoin.
That is irrelevant and will just be another altcoin. Make sure to proceed with caution as it has no replay protection, thus spending it might be dangerous.
Once again the bitcoin affiliate consumer does not base it on the core but the constant flow. It pertains to the actual bitcoin to cash out after all.
There's probably going to be another split between bitcoin legacy and SegWit2X version of bitcoin.
Apparently so. MeshCollider and achow101 are both technically well informed in general, and I also checked their explanations made sense to me, which they did.
I love core team, this is why segwit2x has no support. As far as i can tell just big businesses trying to control btc
I don`t see much of a speed change
If you think that, then you have very bad perception and you have no idea how to benchmark. v0.15.0 is faster on any kind of hardware by a significant margin that can be easily confirmed with a test (e.g. IBD or reindex time). 
I don`t see much of a speed change
Jump to: