Topic: Bitcoin Core 0.18.1 Released (Read 1824 times)

Bitcoin Core 0.19.0.1 has been released

If you're rich and a fast learner, do it

If you're not, quit now, lol

Hi All,

I am a beginner of bitcoin. Is it worth to use this program to generate bitcoin in terms of input to output values?

Pls advice, thanks!

seems to work, thanks!

Try to change it to E:/Bitcoin/bitcoinqt.exe -datadir=G:\Bitcoindata . If it still doesn't work for some reason, create a new topic in this section.

I have not been using my bitcoin software for some time and my current version was 14.2.
I have upgraded  to the current version 18.1  (Windows)  It seams that the parameters has changed. The program complains on them
when I start the program

My parameters are:
 E:/Bitcoin/bitcoinqt.exe -datadir:G:/:Bitcoindata
 18.1 complains  14.2 works fine   

did not find backslash on this laptop so I used slash instead. on the computer running the program it is backslash

Bitcoin Core is the software that allows you to download the blockchain and verify every transaction that you receive independently, without needing to trust any third parties.

To generate (via mining) any significant amount of Bitcoin you will need to buy dedicated hardware, what is usually known as ASICs.

To put it plainly, what you mean is sending Bitcoin. Bitcoin Core is a good choice if you have plenty of free space on your drive (you will have to download about 250 GB of data) and don't want to trust anyone. Running a full node helps the network a lot. If you don't have much free space then you can use Bitcoin Core to run a pruned node (you will still have to download all the blocks to verify them before they get deleted; this takes some time) or download Electrum and verify it. It is a light client so you will connect to external servers from which you will obtain information about your transactions and unspent inputs. In both cases, you will be the only person in control of your coins.

Hi All,

I am a beginner of bitcoin. Is it worth to use this program to generate bitcoin in terms of input to output values?

Pls advice, thanks!

probably none, what I really mean is "if your bittorrent software is old, this might not work", as some people have lazy habits when it comes to updating software ("it works, right?")



it's more the strength of the Bittorrent network I'm really thinking about

• some people turn off things they think they don't need (e.g. DHT)
• some people use ancient bittorrent clients "because it still works, ain't broke, don't fix it", DHT support may be broken or missing

the tracker based system is vulnerable to censorship, the DHT less so.

Note that some centralisation actually still exist in the DHT, namely that you need to connect to a bootstrap node to become a DHT node in the first place. But this is much more difficult to disrupt than trackers IMO, the trackers are doing a more resource intensive job than DHT bootstrapping servers do, and they depend on both local and client-side configuration values (i.e. tracker urls) that can be easily attacked (but there are fewer DHT bootstrap servers than trackers)


in an attack against trackers:

if there was a widespread DoS attack against trackers, it would be alot of time and work before alternative trackers could be set up; all torrents would need to be moved to the new trackers, and then all users would need to add those trackers to their torrent client, one at a time for each torrent they are sharing. So, in practice the damage to the bittorrent network would likely never be fully recovered, as many users would not update their torrents with the new trackers, number of seeds would reduce, attack would cause significant damage to the content on the network, attack is a partial success


in an attack against DHT bootstrappers:

everyone would be forced to change to a new DHT bootstrapper. setting up a new DHT bootstrap server would be fast. No-one would need to change anything in their torrent client except the new bootstrap server url. all infohashes are the same, and so the bittorrent network would return to 100% health once everyone updated

---

tl;dr DHT peer discovery is more private, more decentralised, but most importantly more resilient

what would be the point of that, just a little bit¹ more decentralization?
if it is for privacy concerns then, IP changing techniques should be used (like VPN or TOR). otherwise with or without trackers your IP address will be revealed and anybody who wanted to know who is downloading this file has to only know the hash of it to be able to get a list of all the IP addresses of all the peers.

¹ a little bit, because "Kademlia DHT" isn't really decentralized, you are still connecting to a centralized server (initially)  that is hardcoded inside your torrent client to "connect" to the network and find other DHT nodes. something similar to bitcoin core initial node discovery mechanism connecting to hard coded servers.

nice


note that the magnet link below (which is just a truncated version of achow101's link) will download Bitcoin 0.18.1, but without giving your IP to any of those trackers (i.e. decentralised!). It might take a bit longer to find peers (a few minutes only)


requires bittorrent client with good DHT handling:

magnet:?xt=urn:btih:c3ba0cfee3ef8413098ac5e81db08a2670e9da8c&dn=bitcoin-core-0.18.1

Added it.

some names on the list of 0.18.1 contributors aren't as vocal as Luke, but have actually been developing Bitcoin longer than him


@achow101 do you have a magnet link to the binaries?


Thanks to all who contributed to 0.18.1, particularly the new person (technovert) who fixed poll(), that was an annoying bug

Kudos for the Bitcoin Core devs! I'd like to thank all contributors.

Thanks, fixed. My script was still a little broken.

all your links are broken, they wrap around the correct link as a quoted string:

Bitcoin Core version 0.18.1 is now available from:

https://bitcoincore.org/bin/bitcoin-core-0.18.1/

Or through BitTorrent:

    magnet:?xt=urn:btih:c3ba0cfee3ef8413098ac5e81db08a2670e9da8c&dn=bitcoin-core-0.18.1&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&tr=udp%3A%2F%2Fzer0day.ch%3A1337&tr=udp%3A%2F%2Fexplodie.org%3A6969

This is a new minor version release, including new features, various bug
fixes and performance improvements, as well as updated translations.

Please report bugs using the issue tracker at GitHub:

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

To receive security and update notifications, please subscribe to:

https://bitcoincore.org/en/list/announcements/join/

How to Upgrade

If you are running an older version, shut it down. Wait until it has
completely shut down (which might take a few minutes for older
versions), then run the installer (on Windows) or just copy over
/Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on
Linux).

The first time you run version 0.15.0 or newer, your chainstate database
will be converted to a new format, which will take anywhere from a few
minutes to half an hour, depending on the speed of your machine.

Note that the block database format also changed in version 0.8.0 and
there is no automatic upgrade code from before version 0.8 to version
0.15.0 or later. Upgrading directly from 0.7.x and earlier without
redownloading the blockchain is not supported.  However, as usual, old
wallet versions are still supported.

Compatibility

Bitcoin Core is supported and extensively tested on operating systems
using the Linux kernel, macOS 10.10+, and Windows 7 and newer. It is not
recommended to use Bitcoin Core on unsupported systems.

Bitcoin Core should also work on most other Unix-like systems but is not
as frequently tested on them.

From 0.17.0 onwards, macOS <10.10 is no longer supported. 0.17.0 is
built using Qt 5.9.x, which doesn't support versions of macOS older than
10.10. Additionally, Bitcoin Core does not yet change appearance when
macOS "dark mode" is activated.

Known issues

Wallet GUI

For advanced users who have both (1) enabled coin control features, and
(2) are using multiple wallets loaded at the same time: The coin control
input selection dialog can erroneously retain wrong-wallet state when
switching wallets using the dropdown menu. For now, it is recommended
not to use coin control features with multiple wallets loaded.

0.18.1 change log

P2P protocol and network code

• #15990 Add tests and documentation for blocksonly (MarcoFalke)
• #16021 Avoid logging transaction decode errors to stderr (MarcoFalke)
• #16405 fix: tor: Call event_base_loopbreak from the event's callback (promag)
• #16412 Make poll in InterruptibleRecv only filter for POLLIN events (tecnovert)

Wallet

• #15913 Add -ignorepartialspends to list of ignored wallet options (luke-jr)

RPC and other APIs

• #15991 Bugfix: fix pruneblockchain returned prune height (jonasschnelli)
• #15899 Document iswitness flag and fix bug in converttopsbt (MarcoFalke)
• #16026 Ensure that uncompressed public keys in a multisig always returns a legacy address (achow101)
• #14039 Disallow extended encoding for non-witness transactions (sipa)
• #16210 add 2nd arg to signrawtransactionwithkey examples (dooglus)
• #16250 signrawtransactionwithkey: report error when missing redeemScript/witnessScript (ajtowns)

GUI

• #16044 fix the bug of OPEN CONFIGURATION FILE on Mac (shannon1916)
• #15957 Show "No wallets available" in open menu instead of nothing (meshcollider)
• #16118 Enable open wallet menu on setWalletController (promag)
• #16135 Set progressDialog to nullptr (promag)
• #16231 Fix open wallet menu initialization order (promag)
• #16254 Set AA_EnableHighDpiScaling attribute early (hebasto)
• #16122 Enable console line edit on setClientModel (promag)
• #16348 Assert QMetaObject::invokeMethod result (promag)

Build system

• #15985 Add test for GCC bug 90348 (sipa)
• #15947 Install bitcoin-wallet manpage (domob1812)
• #15983 build with -fstack-reuse=none (MarcoFalke)

Tests and QA

• #15826 Pure python EC (sipa)
• #15893 Add test for superfluous witness record in deserialization (instagibbs)
• #14818 Bugfix: test/functional/rpc_psbt: Remove check for specific error message that depends on uncertain assumptions (luke-jr)
• #15831 Add test that addmultisigaddress fails for watchonly addresses (MarcoFalke)

Documentation

• #15890 Remove text about txes always relayed from -whitelist (harding)

Miscellaneous

• #16095 Catch by reference not value in wallettool (kristapsk)
• #16205 Replace fprintf with tfm::format (MarcoFalke)

Credits

Thanks to everyone who directly contributed to this release:

• Andrew Chow
• Anthony Towns
• Chris Moore
• Daniel Kraft
• David A. Harding
• fanquake
• Gregory Sanders
• Hennadii Stepanov
• John Newbery
• Jonas Schnelli
• João Barbosa
• Kristaps Kaupe
• Luke Dashjr
• MarcoFalke
• MeshCollider
• Pieter Wuille
• shannon1916
• tecnovert
• Wladimir J. van der Laan

As well as everyone that helped translating on Transifex.

---