Satoshi 0.12.0 | Bitcointalksearch.org

shorena

copper member

Activity: 1498

Merit: 1499

No I dont escrow anymore.

Quote from: achow101 on January 14, 2016, 02:43:57 PM

Quote from: shorena on January 14, 2016, 01:57:52 PM

Are there release notes already? Can you give us/me a link, I was unable to find them.

They exist, but not official yet: https://github.com/bitcoin/bitcoin/blob/0.12/doc/release-notes.md

Thanks. Sounds very good for me esp. in terms of running a node on a server with limited resources.

Carlton Banks

legendary

Activity: 3430

Merit: 3071

Yeah, now that the release candidate is out, the notes cover all the features (as far as 0.12 features go), but obviously not unchangeable till final release.

achow101

staff

Activity: 3374

Merit: 6530

Just writing some code

Quote from: shorena on January 14, 2016, 01:57:52 PM

Are there release notes already? Can you give us/me a link, I was unable to find them.

They exist, but not official yet: https://github.com/bitcoin/bitcoin/blob/0.12/doc/release-notes.md

shorena

copper member

Activity: 1498

Merit: 1499

No I dont escrow anymore.

Quote from: dan91 on January 14, 2016, 01:40:56 PM

Quote from: achow101 on January 14, 2016, 01:34:54 PM

Quote from: Carlton Banks on January 14, 2016, 01:31:07 PM

Quote from: achow101 on January 14, 2016, 01:23:34 PM

Not true.

Which part? Everything you said corresponds with something I said.

The incoming connections part, not being a full node, and pruning not being helpful in the short term.

But as it stands with 0.11 currently right now.. It does not relay blocks that was the point? We were saying it hopefully will in 0.12

A pruned node version 0.11.2

# accepts incoming connections
# relays and verifies blocks
# relays and verifies transactions
# can not have a wallet
# does not provide old blocks to nodes catching up to the current blockheight

Quote from: Carlton Banks on January 14, 2016, 01:44:16 PM

-snip-
The lack of incoming connections/not full-node part comes from the 0.12 release notes, so I'm not too sure what to think about that (possibly that the text is correct). I'm not sure what you mean about pruning not being helpful in the short-term, it depends on whose perspective you're looking from. As a blanket statement, I didn't make it.

Are there release notes already? Can you give us/me a link, I was unable to find them.

Carlton Banks

legendary

Activity: 3430

Merit: 3071

Quote from: achow101 on January 14, 2016, 01:34:54 PM

Quote from: Carlton Banks on January 14, 2016, 01:31:07 PM

Quote from: achow101 on January 14, 2016, 01:23:34 PM

Not true.

Which part? Everything you said corresponds with something I said.

The incoming connections part, not being a full node, and pruning not being helpful in the short term.

The lack of incoming connections/not full-node part comes from the 0.12 release notes, so I'm not too sure what to think about that (possibly that the text is correct). I'm not sure what you mean about pruning not being helpful in the short-term, it depends on whose perspective you're looking from. As a blanket statement, I didn't make it.

dan91

newbie

Activity: 56

Merit: 0

Quote from: achow101 on January 14, 2016, 01:34:54 PM

Quote from: Carlton Banks on January 14, 2016, 01:31:07 PM

Quote from: achow101 on January 14, 2016, 01:23:34 PM

Not true.

Which part? Everything you said corresponds with something I said.

The incoming connections part, not being a full node, and pruning not being helpful in the short term.

But as it stands with 0.11 currently right now.. It does not relay blocks that was the point? We were saying it hopefully will in 0.12

achow101

staff

Activity: 3374

Merit: 6530

Just writing some code

Quote from: Carlton Banks on January 14, 2016, 01:31:07 PM

Quote from: achow101 on January 14, 2016, 01:23:34 PM

Not true.

Which part? Everything you said corresponds with something I said.

The incoming connections part, not being a full node, and pruning not being helpful in the short term.

Carlton Banks

legendary

Activity: 3430

Merit: 3071

Quote from: achow101 on January 14, 2016, 01:23:34 PM

Not true.

Which part? Everything you said corresponds with something I said.

achow101

staff

Activity: 3374

Merit: 6530

Just writing some code

Quote from: Carlton Banks on January 14, 2016, 12:34:21 PM

Quote from: dan91 on January 14, 2016, 11:35:46 AM

Quote from: Carlton Banks on January 14, 2016, 11:18:20 AM

Another benefit of 0.12 for those using the Core wallet (such as yourself) would be the ability to use the wallet with a pruned database size. This means the blockchain is stored upto a value (in MB) of your choice, instead of keeping all the oldest blocks. This feature existed in 0.11.x, but was incompatible with the operation of the wallet feature.

If you turn pruning on though you stop becoming a "full node" still? In 0.11 you stop having incoming connections i think.

Ah, didn't know about that difference (the incoming connections part).

So, using the pruning mode is not very good for the health of the Bitcoin network for multiple reasons in the short term, but it's worthwhile if the long-term outcome is the possibility of a user using pruning mode later going on to acquire the resources/inclination to run a full node.

Seems reasonable, but we'll see how it works out in practice. One interesting outcome IMO: Bitcoin Core on Android would be a far more realistic proposition with wallet and prune now working together. Possibly still not practical for real-world use, but tantalising nonetheless.

Not true. Pruning in 0.11 was bit very helpful since it wasn't completed yet. In 0.12 pruning is better. It still functions as a full node since all blocks and transactions are validated. It will also relay blocks and transactions. It should accept incoming connections as well. The wallet will be enabled as well.

dan91

newbie

Activity: 56

Merit: 0

Quote

For now, block pruning disables block relay. In the future, nodes with block pruning will at a minimum relay “new” blocks, meaning blocks that extend their active chain.

So maybe you will be able to relay in 0.12 but only current blocks it says 2 days is what it stores minimum, and not historical. If thats true it will increase the health in parts but if too many current full nodes switch it could slow down new nodes joining as historical nodes will become fewer and will have to serve more data?

Carlton Banks

legendary

Activity: 3430

Merit: 3071

Quote from: dan91 on January 14, 2016, 11:35:46 AM

Quote from: Carlton Banks on January 14, 2016, 11:18:20 AM

Another benefit of 0.12 for those using the Core wallet (such as yourself) would be the ability to use the wallet with a pruned database size. This means the blockchain is stored upto a value (in MB) of your choice, instead of keeping all the oldest blocks. This feature existed in 0.11.x, but was incompatible with the operation of the wallet feature.

If you turn pruning on though you stop becoming a "full node" still? In 0.11 you stop having incoming connections i think.

Ah, didn't know about that difference (the incoming connections part).

So, using the pruning mode is not very good for the health of the Bitcoin network for multiple reasons in the short term, but it's worthwhile if the long-term outcome is the possibility of a user using pruning mode later going on to acquire the resources/inclination to run a full node.

Seems reasonable, but we'll see how it works out in practice. One interesting outcome IMO: Bitcoin Core on Android would be a far more realistic proposition with wallet and prune now working together. Possibly still not practical for real-world use, but tantalising nonetheless.

dan91

newbie

Activity: 56

Merit: 0

Quote from: Carlton Banks on January 14, 2016, 11:18:20 AM

Not at all, I think you did misunderstand.

Another benefit of 0.12 for those using the Core wallet (such as yourself) would be the ability to use the wallet with a pruned database size. This means the blockchain is stored upto a value (in MB) of your choice, instead of keeping all the oldest blocks. This feature existed in 0.11.x, but was incompatible with the operation of the wallet feature.

If you turn pruning on though you stop becoming a "full node" still? In 0.11 you stop having incoming connections i think.

Carlton Banks

legendary

Activity: 3430

Merit: 3071

Not at all, I think you did misunderstand.

Another benefit of 0.12 for those using the Core wallet (such as yourself) would be the ability to use the wallet with a pruned database size. This means the blockchain is stored upto a value (in MB) of your choice, instead of keeping all the oldest blocks. This feature existed in 0.11.x, but was incompatible with the operation of the wallet feature.

Jet Cash

legendary

Activity: 2688

Merit: 2444

https://JetCash.com

I'm not sure I understand your post. I and most others know that I am a Bitcoin newbie. I read the link explaining the changes in 0.12, and there didn't appear to be anything relevant to me. I'm running a full node just to maintain a single wallet, so my needs are pretty basic.

If I'm giving offence, then I can reduce my posting.

Carlton Banks

legendary

Activity: 3430

Merit: 3071

Try to find the positives from my former comment also. You can expect a better response to your questions if you are not, simultaneously:

behaving as if you have a lot of experience to know what you're doing
asking for direct answers to questions with subjective outcomes, as a consequence that you're not quite sure what you're doing

There's somewhat of a contradiction between those 2, and many will simply decline to answer at all (to wit, this thread). I hope that helps.

Jet Cash

legendary

Activity: 2688

Merit: 2444

https://JetCash.com

Quote from: Carlton Banks on January 14, 2016, 08:45:25 AM

The libsec256k/SSL deprecation will speed up your sync time, either you need that or you don't. But you're demonstrably making decisions for yourself already about which client (with which features) is "the best move for me", so I wouldn't expect many replies to your latter question.

I've found that, human nature being what it is, if I make a statement of intent, then people seem to provide all the negative factors to indicate why I was wrong.

Your comment about speeding up sync time is valuable to me, and is an example of this. I'm still new to Bitcoin, and I have a mass to learn.

Carlton Banks

legendary

Activity: 3430

Merit: 3071

Quote from: Jet Cash on January 14, 2016, 02:41:19 AM

Thanks for the info and the link. It doesn't look as if there is anything in there that a small operator like me will need, so I think I'll stay with 0.11.2. Is that the best move for me?

The libsec256k/SSL deprecation will speed up your sync time, either you need that or you don't. But you're demonstrably making decisions for yourself already about which client (with which features) is "the best move for me", so I wouldn't expect many replies to your latter question.

achow101

staff

Activity: 3374

Merit: 6530

Just writing some code

Quote from: Jet Cash on January 14, 2016, 02:41:19 AM

Thanks for the info and the link. It doesn't look as if there is anything in there that a small operator like me will need, so I think I'll stay with 0.11.2. Is that the best move for me?

Yes. However when 0.12 is officially released in February, you should upgrade to it.

Jet Cash

legendary

Activity: 2688

Merit: 2444

https://JetCash.com

Thanks for the info and the link. It doesn't look as if there is anything in there that a small operator like me will need, so I think I'll stay with 0.11.2. Is that the best move for me?

achow101

staff

Activity: 3374

Merit: 6530

Just writing some code

Quote from: Jet Cash on January 13, 2016, 11:09:22 AM

I'm running 0.11.2, and I've got a peer running XT. I saw this 0.12.0 running for about an hour this morning. There weas also a 0.11.99 which I believe is a test version. Good to see there are some improvements on the way. Does anyone know what they are?

Any satoshi client ending in 99 is a build of the matter branch from the git repo. 0.12 is a build from the 0.12 branch but 0.12 isn't ready for release.

Topic: Satoshi 0.12.0 (Read 2665 times)