Pages:
Author

Topic: Bitcoin Core 22.0 Released - page 2. (Read 2609 times)

newbie
Activity: 7
Merit: 9
November 16, 2021, 06:30:13 AM
#34
Because of version number change, bitcoin.org website orders releases odd way.

https://bitcoincore.org
https://i.ibb.co/wwX4xCD/bitcoincore-releasesorder.png
jr. member
Activity: 139
Merit: 6
November 15, 2021, 11:04:36 AM
#33
Are there any plans in the core development to at least allow users to run the core software without having to download and process the entire blockchain?

This would be great and I would be happy to support this!

In addition to pruning? Still have to download first, but once you activate pruning on your core node you can dump 90% of the chain from storage.
legendary
Activity: 3472
Merit: 10611
November 01, 2021, 12:10:26 AM
#32
Are there any plans in the core development to at least allow users to run the core software without having to download and process the entire blockchain?
This would be great and I would be happy to support this!
That would not make sense. Bitcoin core is as it has always been a full node and as a full node it needs to download and verify the entire blockchain; you can also decide whether you want to store the entire blockchain and be a full verifying node or store a small number of latest blocks and be a pruned full verifying node but the initial sync has to happen.

Additionally there is no need for bitcoin core to add such a feature since we already have an excellent implementation for an SPV client (where you don't download and verify the entire blockchain) called Electrum.
newbie
Activity: 33
Merit: 0
October 31, 2021, 07:54:56 AM
#31
Are there any plans in the core development to at least allow users to run the core software without having to download and process the entire blockchain?

This would be great and I would be happy to support this!
legendary
Activity: 3668
Merit: 6382
Looking for campaign manager? Contact icopress!
October 15, 2021, 12:22:05 PM
#30
Man, how big the blockchain is. I think about Satoshi's white paper and I imagine a system where each one of us can easily run a node on their computer, mine and make a small profit. Nowadays you need 400 GB to download the entire blockchain if you want to run the core software, you need ASICs to mine, etc. Are there any plans in the core development to at least allow users to run the core software without having to download and process the entire blockchain?

I think that this covers your question: https://bitcointalksearch.org/topic/can-i-just-run-a-pruned-node-without-downloading-historical-data-5364381
jr. member
Activity: 56
Merit: 5
October 15, 2021, 12:18:17 PM
#29
Man, how big the blockchain is. I think about Satoshi's white paper and I imagine a system where each one of us can easily run a node on their computer, mine and make a small profit. Nowadays you need 400 GB to download the entire blockchain if you want to run the core software, you need ASICs to mine, etc. Are there any plans in the core development to at least allow users to run the core software without having to download and process the entire blockchain?
legendary
Activity: 3668
Merit: 6382
Looking for campaign manager? Contact icopress!
October 11, 2021, 08:38:52 AM
#28
What's the version of Bitcoin Core 0.21.2 why is it after 22.0?

I'd say that 0.21.2 is just a bugfix for 0.21.0/0.21.1.
It's "after" 22.0 because it was implemented more recently. Still 22.0 remains the highest version.
member
Activity: 174
Merit: 12
October 11, 2021, 07:53:44 AM
#27
What's the version of Bitcoin Core 0.21.2 why is it after 22.0?
legendary
Activity: 3472
Merit: 10611
October 09, 2021, 12:00:00 AM
#26
Yes its the theoretically idea of Bitcoin but practically a coordinated dev team leads the ship with its updates and there are not 10 different Cores for setting up a full node.
That's for consensus rules, and there are already multiple implementation of full nodes. Not everything is a full node either.
Other than that there are a lot of features that other implementations have, for example core lacks one of the most popular features which is producing a mnemonic for wallet backups.

Quote
And by the way you agree on usability of LN?
Of course. And I would love to see LN added to core itself.
member
Activity: 637
Merit: 11
October 08, 2021, 05:27:19 PM
#25
And even if I could code it would be again a third party solution.
That makes no sense! Bitcoin is not centralized and there is no company or individual owning the right to write code for Bitcoin. In other words there is not "first party" for anything other than bitcoin core to be considered "third party". Any implementation of the protocol (and any extra options such as lightning network) is as valuable as the reference implementation.
Yes its the theoretically idea of Bitcoin but practically a coordinated dev team leads the ship with its updates and there are not 10 different Cores for setting up a full node.

And by the way you agree on usability of LN?
legendary
Activity: 3472
Merit: 10611
October 07, 2021, 11:59:06 PM
#24
And even if I could code it would be again a third party solution.
That makes no sense! Bitcoin is not centralized and there is no company or individual owning the right to write code for Bitcoin. In other words there is not "first party" for anything other than bitcoin core to be considered "third party". Any implementation of the protocol (and any extra options such as lightning network) is as valuable as the reference implementation.
member
Activity: 637
Merit: 11
October 07, 2021, 07:22:09 AM
#23
When can we expect a combined original Bitcoin Core wallet that supports Lightning?

The usability of core with a Lightning daemon is still a big mess.

And when ask why not do myself. Dev Team has the knowlege and the resources to do that. And even if I could code it would be again a third party solution.
legendary
Activity: 3472
Merit: 10611
October 05, 2021, 11:48:41 PM
#22
of course taproot is obviously a big improvement to the network and data base.  My hard drives are celebrating already.
Taproot doesn't have anything to do with "database" and won't change anything about it. Even if it did, your "hard drive" wouldn't notice it since it is just locked in and will activate in about a month.
newbie
Activity: 742
Merit: 0
October 05, 2021, 02:08:48 PM
#21
Taproot, schmaproot, this is what I'm most excited about.  Just kidding, of course taproot is obviously a big improvement to the network and data base.  My hard drives are celebrating already.  But I am really excited about GUI support for hardware wallets.  I updated the full node I'm running on my primary (Win10) PC last night but I didn't get a chance to play with it in combination with a hardware wallet.  I'll goof around with it and a spare hardware wallet
staff
Activity: 3458
Merit: 6793
Just writing some code
September 18, 2021, 09:46:16 AM
#20
Was bitcoin-core/gui#365 merged into this release? I can't find it in the above changelog (it fixes the issue with transaction data making the main window extremely large. I contributed to reporting that bug).
It is in this release. Sometimes the changelog generating script misses things.
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
September 18, 2021, 05:33:08 AM
#19
Was bitcoin-core/gui#365 merged into this release? I can't find it in the above changelog (it fixes the issue with transaction data making the main window extremely large. I contributed to reporting that bug).

I recall discussion over there saying it was going to be backported to 0.21.1 too.
copper member
Activity: 2338
Merit: 4543
Join the world-leading crypto sportsbook NOW!
September 15, 2021, 12:32:41 PM
#18
GUI
  • bitcoin-core/gui#4 UI external signer support (e.g. hardware wallet) (Sjors)

Taproot, schmaproot, this is what I'm most excited about.  Just kidding, of course taproot is obviously a big improvement to the network and data base.  My hard drives are celebrating already.  But I am really excited about GUI support for hardware wallets.  I updated the full node I'm running on my primary (Win10) PC last night but I didn't get a chance to play with it in combination with a hardware wallet.  I'll goof around with it and a spare hardware wallet (a KeepKey) tonight.

I plan on updating my node server this weekend, getting ready for taproot integration.

@achow101, just an FYI; the downloads page on bitcoincore.org still lists Wladimir's key, 01EA5486DE18A882D4C2684590C8019E36C2E964, but I didn't see it as one of the keys that signed the sums file.
Yes, the docs are getting updated. Wladimir's release key will still be used to sign the backport releases (0.20.2, 0.21.2, etc.), but he will use his personal key for in the signatures for future releases.

Thanks.  I've had your key and Wladimir's key in my keyring for months, so I thought it was funny that yours was the only signature confirmed.  I didn't know which of these keys is Wladimir's personal key, but I found it:

Code:
Signature made 09/10/21 10:33:30 Pacific Daylight Time
                using RSA key 9DEAE0DC7063249FB05474681E4AED62986CD25D
Good signature from "Wladimir J. van der Laan " [full]
                aka "Wladimir J. van der Laan " [full]
                aka "Wladimir J. van der Laan " [full]
legendary
Activity: 3472
Merit: 10611
September 15, 2021, 01:03:31 AM
#17
Looks like it's intentional (https://github.com/bitcoin/bitcoin/pull/20223). This remind me of Firefox/Chrome which use big number to make people think there's big improvement on their software.
I think its just that the bitcoin core team didn't move to 1.0 (first major release getting out of beta) for so long that at this point it looks weird to go from 0.21 to 1.0 so it looks like dropping the first zero made more sense to them.
Not to mention that core wasn't completely following semver and 0.x wasn't exactly considered "beta".
staff
Activity: 3458
Merit: 6793
Just writing some code
September 14, 2021, 08:17:56 PM
#16
@achow101, just an FYI; the downloads page on bitcoincore.org still lists Wladimir's key, 01EA5486DE18A882D4C2684590C8019E36C2E964, but I didn't see it as one of the keys that signed the sums file.
Yes, the docs are getting updated. Wladimir's release key will still be used to sign the backport releases (0.20.2, 0.21.2, etc.), but he will use his personal key for in the signatures for future releases.
copper member
Activity: 2338
Merit: 4543
Join the world-leading crypto sportsbook NOW!
September 14, 2021, 07:07:18 PM
#15
@achow101, just an FYI; the downloads page on bitcoincore.org still lists Wladimir's key, 01EA5486DE18A882D4C2684590C8019E36C2E964, but I didn't see it as one of the keys that signed the sums file.

Here's what I get:

Code:
gpg --verify P:\Installs\Cryptocurrency\Bitcoin_Clients\Bitcoin_Core\bitcoin-22.0\SHA256SUMS.asc P:\Installs\Cryptocurrency\Bitcoin_Clients\Bitcoin_Core\bitcoin-22.0\SHA256SUMS
Signature made 9/10/2021 4:29:17 AM Pacific Daylight Time
               using RSA key 0CCBAAFD76A2ECE2CCD3141DE2FFD5B1D88CA97D
Can't check signature: No public key
Signature made 9/9/2021 1:09:04 PM Pacific Daylight Time
               using RSA key 152812300785C96444D3334D17565732E08E5E41
               issuer "[email protected]"
Good signature from "Andrew Chow (Official New Key) " [full]
                aka "Andrew Chow " [full]
                aka "Andrew Chow " [full]
                aka "Andrew Chow " [full]
                aka "Andrew Chow " [full]
                aka "Andrew Chow " [full]
                aka "Andrew Chow " [full]
Signature made 9/9/2021 1:16:18 PM Pacific Daylight Time
               using RSA key 0AD83877C1F0CD1EE9BD660AD7CC770B81FD22A8
               issuer "[email protected]"
Can't check signature: No public key
Signature made 9/10/2021 6:00:35 AM Pacific Daylight Time
               using RSA key 590B7292695AFFA5B672CBB2E13FC145CD3F4304
               issuer "[email protected]"
Can't check signature: No public key
Signature made 9/9/2021 1:54:01 PM Pacific Daylight Time
               using RSA key 28F5900B1BB5D1A4B6B6D1A9ED357015286A333D
Can't check signature: No public key
Signature made 9/10/2021 7:26:03 AM Pacific Daylight Time
               using RSA key 637DB1E23370F84AFF88CCE03152347D07DA627C
Can't check signature: No public key
Signature made 9/9/2021 6:04:14 PM Pacific Daylight Time
               using RSA key CFB16E21C950F67FA95E558F2EEB9F5CC09526C1
               issuer "[email protected]"
Can't check signature: No public key
Signature made 9/10/2021 1:03:16 AM Pacific Daylight Time
               using RSA key 6E01EEC9656903B0542B8F1003DB6322267C373B
               issuer "[email protected]"
Can't check signature: No public key
Signature made 9/9/2021 1:07:53 PM Pacific Daylight Time
               using RSA key D1DBF2C4B96F2DEBF4C16654410108112E7EA81F
               issuer "[email protected]"
Can't check signature: No public key
Signature made 9/10/2021 12:14:14 AM Pacific Daylight Time
               using RSA key 82921A4B88FD454B7EB8CE3C796C4109063D4EAF
               issuer "[email protected]"
Can't check signature: No public key
Signature made 9/10/2021 10:33:30 AM Pacific Daylight Time
               using RSA key 9DEAE0DC7063249FB05474681E4AED62986CD25D
Can't check signature: No public key
Signature made 9/9/2021 1:22:36 PM Pacific Daylight Time
               using RSA key 9D3CC86A72F8494342EA5FD10A41BDC3F4FAFF1C
               issuer "[email protected]"
Can't check signature: No public key
Signature made 9/10/2021 2:59:33 AM Pacific Daylight Time
               using RSA key 74E2DEF5D77260B98BC19438099BAD163C70FBFA
               issuer "[email protected]"
Can't check signature: No public key
Pages:
Jump to: