Pages:
Author

Topic: Bitcoin 0.12 release - page 3. (Read 11264 times)

legendary
Activity: 2282
Merit: 1023
February 15, 2016, 03:02:08 AM
#68
Can someone post please Bitcoin.conf? I'm not sure how this must look like now.
I'm interested for prune mode..I don't want synchronization 7 years..
as i understood this is gonna take about 2 gb space on hd, is this stable and safe?

I have downloaded version for Windows , 32 bit.
https://bitcoin.org/bin/bitcoin-core-0.12.0/


Just create a shortcut with the "Target" changed to "C:\Program Files\Bitcoin\bitcoin-qt.exe -prune=8000" (as an example). Just adding the "-prune=8000" at the end. 8000 means 8GB.

By the way, you will still need to download the entire 50GB blockchain, and the software prune the chain as it is being downloaded.
legendary
Activity: 2380
Merit: 1026
February 15, 2016, 02:30:19 AM
#67
Can someone please post Bitcoin.conf? I'm not sure how this must look like now.
I'm interested for prune mode..I don't want synchronization 7 years..
as i understood this is gonna take about 2 gb space on hd, is this stable and safe?

I have downloaded version for Windows , 32 bit.
https://bitcoin.org/bin/bitcoin-core-0.12.0/
sr. member
Activity: 690
Merit: 269
February 14, 2016, 08:26:42 AM
#66
We tested rc5 on Debian. it seems to work ok
legendary
Activity: 2310
Merit: 1422
February 13, 2016, 04:48:22 AM
#65
This could be the greatest plus thing we need and then I would be more than happy in contributing again.
When you talk about future, how far is this future? thanks  Wink
I think it would be done now, if not for all the drama in the last year.

In 0.12 you can run a pruned node and you'll at least relay blocks on the tip.

I hope to see more sophistication maybe towards then end of the year; I'm hesitant to give any concrete numbers in the current climate.

In any case something like theymos said sound awesome to me, maybe because I first heard the word Bitcoin linked to Bittorrent (I don't even remember how and when).
Don't worry about giving some dates, no rush. Let the talking continue. Thanks
legendary
Activity: 1232
Merit: 1094
February 12, 2016, 10:25:41 AM
#64
Not sure. That is just what I understood from the release notes and the bip. I suppose a more definitive answer could be gotten by looking at the code.

It could just be that they assume that most will update reasonably quickly.  Once most people are using 0.12, pruning nodes will be connected to 0.12 nodes anyway.

It looks like they have a "revert to inv" flag which is set if the node doesn't prefer headers.

https://github.com/bitcoin/bitcoin/blob/master/src/main.cpp#L5411

The only thing the fPruneMode flag does is stop it going back to far when sending blocks.  So, I guess, nevermind then Smiley.
staff
Activity: 3458
Merit: 6793
Just writing some code
February 12, 2016, 10:15:14 AM
#63
No, only 0.12+ because the sendHeaders message does not exist prior to 0.12.

It should fallback to inv messages in that case.  Is there a reason for not doing that?
Not sure. That is just what I understood from the release notes and the bip. I suppose a more definitive answer could be gotten by looking at the code.
legendary
Activity: 1232
Merit: 1094
February 12, 2016, 10:04:34 AM
#62
No, only 0.12+ because the sendHeaders message does not exist prior to 0.12.

It should fallback to inv messages in that case.  Is there a reason for not doing that?
legendary
Activity: 2870
Merit: 2474
https://JetCash.com
February 12, 2016, 06:03:51 AM
#61
The two disadvantages to running a full node seem to be storage and bandwidth (unless you run some cpu intensive programs). Storage isn't really a problem with modern hard drives. So bandwidth seems to be the big disincentive. At the moment I'm running a full node for around eight hours a day with no inbound connections. This is part of my mobile computing research. Hopefully, this is of some samll benefit to the Bitcoin system.
legendary
Activity: 1762
Merit: 1011
February 11, 2016, 09:32:51 PM
#60
Does it make any sense at all to think about paying folks running full nodes (with or without all old blocks) even if they aren't mining?

So, running a full node is the only way to use Bitcoin in its most trustless form. But there's nothing stopping people from, say, running a full client to achieve this trustlessness, but still turning off the accepting of incoming connections so save bandwidth; well, that is, until *everyone* else decides to do the same, and then there isn't anyone left running an archival node from which to download the blockchain.

Full nodes enforce the consensus rules.  But even miners aren't directly incentivized to run their own full nodes. However, miners and businesses may rely on particular behavior from custom full node features that they may want to make use of, so they will often be incentivized to run their own full nodes for this purpose.
legendary
Activity: 1762
Merit: 1011
February 11, 2016, 09:31:55 PM
#59
So when we expect this 0.12.0 release to be officially available?

Meanwhile classic gained ground, now they are 14% (830 nodes) of the total number of nodes.


RC4 or RC5 will be out soon, some additional bugs were discovered and taken care of.
staff
Activity: 4326
Merit: 8951
February 11, 2016, 04:13:59 PM
#58
This could be the greatest plus thing we need and then I would be more than happy in contributing again.
When you talk about future, how far is this future? thanks  Wink
I think it would be done now, if not for all the drama in the last year.

In 0.12 you can run a pruned node and you'll at least relay blocks on the tip.

I hope to see more sophistication maybe towards then end of the year; I'm hesitant to give any concrete numbers in the current climate.
legendary
Activity: 2702
Merit: 1468
February 11, 2016, 01:49:29 PM
#57
So when we expect this 0.12.0 release to be officially available?

Meanwhile classic gained ground, now they are 14% (830 nodes) of the total number of nodes.
legendary
Activity: 2310
Merit: 1422
February 11, 2016, 03:58:08 PM
#57
If everyone ran in pruned mode then would that be a problem?  How would a new node catch up from the beginning?  I'm sure it's just that I am missing the obvious point.  Sorry to be such a dummy.

Maybe the idea is at least a few nodes will always keep the full history?  I am willing to if that helps.

In the future Core will let you choose to "donate x GB to the network", and then you'll store a random range of historical blocks. Then nodes doing an initial sync will have to search out nodes that have the blocks they want from among these nodes storing chunks of the historical chain. It's a bit like how BitTorrent works.

This could be the greatest plus thing we need and then I would be more than happy in contributing again.
When you talk about future, how far is this future? thanks  Wink
staff
Activity: 3458
Merit: 6793
Just writing some code
February 11, 2016, 02:56:24 PM
#56
So when we expect this 0.12.0 release to be officially available?

Meanwhile classic gained ground, now they are 14% (830 nodes) of the total number of nodes.

Soon I think. Rc5 was tagged today and during the meeting today it was mentioned that rc5 would be the last rc for 0.12
legendary
Activity: 2786
Merit: 1031
February 11, 2016, 08:36:46 AM
#55
I'm looking forward to this.
The reduced Blockcahin size would help a lot, its 60GB in size already indeed.
The first installation took about two days, as i remember.
This was way too long.

With pruning mode enable you still need to download and verify the entire blockchain, if you don't wanna do this try a hosted or SPV wallet.
member
Activity: 70
Merit: 10
★YoBit.Net★ 350+ Coins Exchange & Dice
February 11, 2016, 08:32:42 AM
#54
I'm looking forward to this.
The reduced Blockcahin size would help a lot, its 60GB in size already indeed.
The first installation took about two days, as i remember.
This was way too long.
sr. member
Activity: 690
Merit: 269
February 11, 2016, 07:12:23 AM
#53
Ah! That's beyond my level of knowledge. Smiley

there's no point having million nodes. 5000 is enough and they would easily handle millions of transactions.

much more important is for people to archive a copy of blockchain and validate it. in this way we can discover every possible problem, scam or attack.
legendary
Activity: 2870
Merit: 2474
https://JetCash.com
February 11, 2016, 05:06:48 AM
#52
Does it make any sense at all to think about paying folks running full nodes (with or without all old blocks) even if they aren't mining?

The question is how you distinguish a real node from a fake one.

Ah! That's beyond my level of knowledge. Smiley
copper member
Activity: 1498
Merit: 1562
No I dont escrow anymore.
February 11, 2016, 03:42:58 AM
#51
Does it make any sense at all to think about paying folks running full nodes (with or without all old blocks) even if they aren't mining?

The question is how you distinguish a real node from a fake one.
legendary
Activity: 2870
Merit: 2474
https://JetCash.com
February 10, 2016, 11:37:59 PM
#50
Does it make any sense at all to think about paying folks running full nodes (with or without all old blocks) even if they aren't mining?

Paying them might get complicated. It could be worth giving them a partial refund on their own transaction fees though.
Pages:
Jump to: