Bitcoin Core version 0.11.0 released

moli

moli

Well-known member
https://bitcoin.org/en/release/v0.11.0

Bitcoin Core version 0.11.0 released
12 July 2015
Bitcoin Core version 0.11.0 is now available from:

https://bitcoin.org/bin/bitcoin-core-0.11.0/

This is a new major version release, bringing both new features and bug fixes.

Please report bugs using the issue tracker at github:

https://github.com/bitcoin/bitcoin/issues

Note: There's a lot more to read, please go to the links... Our dev, UdjinM6 is listed under "Credits".

Thanks, UdjinM6 for doing this for us all. Someone posted this btc link in IRC and also said "thanks" to you:
[13:12:25] <eu-Robert> thanks UdjinM6

:smile:
 
Nah, wasn't a big contribution https://github.com/bitcoin/bitcoin/pull/5702 :tongue:

Wondering what took them sooooo long: Jan 24 i.e. ~half a year to include a trivial commit :eek: and it missed 10.x branch somehow so it still has broken docs there :confused:

EDIT:
as for release itself, two things hooked my attention

Block file pruning
very scary feature imo, I think full nodes count will go down even faster because many will prune now, we definitely need to find a way to stop this for MNs (or find some smart way to deal with this) if we are going to adopt this feature.

Fee estimation changes
I hope this one will fix weird fee calculation happening now on testnet with "smart fees" but haven't look through changes yet.


All other kind of memory optimization etc are nice, I also like most of internal refactoring they made, we might adopt some of them in our code too later.
 
Last edited by a moderator:
UdjinM6 said:
Block file pruning
very scary feature imo, I think full nodes count will go down even faster because many will prune now, we definitely need to find a way to stop this for MNs (or find some smart way to deal with this) if we are going to adopt this feature.
Click to expand...

:eek: indeed, but:
Code: 
if(fMasterNode)
    disablePruning();

:grin:
 
moli said:
(...)
Note: There's a lot more to read, please go to the links... Our dev, UdjinM6 is listed under "Credits".

Thanks, UdjinM6 for doing this for us all. Someone posted this btc link in IRC and also said "thanks" to you:
[13:12:25] <eu-Robert> thanks UdjinM6

:smile:
Click to expand...

Great work, as always, UdjinM6!

Thanks!
 
flare said:
Maybe we'll find a way to include a detection in our proof-of-service algo :)
Click to expand...

Ask for random transaction, preferably, but not necessarily, an older one. If it not delivers in an acceptable time (means it has to ask somewhere else to get it) increase its score.
 
Last edited by a moderator:
crowning said:
Ask for random transaction, preferably, but not necessarily, on older one. If it not delivers in an acceptable time (means it has to ask somewhere else to get it) increase its score.
Click to expand...
Yep, that should work.

I like the idea of enforcing masternodes to be full nodes and not degraded SPV/pruned nodes.
 
crowning said:
Ask for random transaction, preferably, but not necessarily, an older one. If it not delivers in an acceptable time (means it has to ask somewhere else to get it) increase its score.
Click to expand...
What does this mean?
 
moli said:
What does this mean?
Click to expand...

Right now Masternodes get already randomly checked by other Masternodes, and if they fail to answer their PoS-score is increased and at a certain score they are banned from the network.

Now imagine this test will include "send me details of transaction "xyz...". A full node will easily find this transaction in its local blockchain and return the details, a SPV/pruned node either can't answer at all or has to query some other (full-) node for the information, and this will need much more time.
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top