#bitcoind

[herijaya]

Mengapa Bitcoin Turun: Analisis Kejadian Agustus 2024

Mengapa Bitcoin Turun Longsor Ambruk: Analisis Kejadian Agustus 2024

[msicc]

Run your own Bitcoin Full Node on an Azure Linux VM

I just blogged: Run your own #Bitcoin Full Node on an #Azure #Linux VM (complete walkthrough) #btc #blockchain

One year ago, I began my journey in the crypto and blockchain area. Recently, multiple circumstances made me thinking about my own crypto-related server. Of course, I choose Azure for running this server (for the time being). It has been a while since I last touched Linux, so I had quite a bit to refresh and learn. In this post, I’ll show you the steps that are needed for setting up an…

View On WordPress

[madhu511-blog]

Bitcoin Price #endoftheday Donations welcomed BTC- 3EkXDyXEa9zA4kGWMxkvXBbmMmG9QPjLr3 #bitcoinsallday #bitcoinmanagement #btcdonation #bitcoindonations #bitcoinfreak #bitcointalk #bitcoinlover #bitcoinbillionaire #bitcoinfree #bitcoinwallet #bitcoind #bitcoimillionaire #bitcoinforever #bitcoinnewyork #bitcoindubai #dubaibitcoin #dubaibitcoinbuyer #bitcoingiveaway #bitcoinpredictions #bitcoingirl #bitcoins #bitcoinrequest #bitcoindonnie #bitcoins #bitcoindonate #bitcoinfreak #bitcoinfree @bitcoin.billionaires @freebitcoingiveaway @officialbrandimae @bitcoingiveaway @freecryptodaily #bitcoinacceptedhere #acceptbitcoin #paywithbitcoin #donatecrypto #paywithcrypto

[madhu511-blog]

Bitcoin Price #endoftheday Donations welcomed BTC- 3EkXDyXEa9zA4kGWMxkvXBbmMmG9QPjLr3 #bitcoinsallday #bitcoinmanagement #btcdonation #bitcoindonations #bitcoinfreak #bitcointalk #bitcoinlover #bitcoinbillionaire #bitcoinfree #bitcoinwallet #bitcoind #bitcoimillionaire #bitcoinforever #bitcoinnewyork #bitcoindubai #dubaibitcoin #dubaibitcoinbuyer #bitcoingiveaway #bitcoinpredictions #bitcoingirl #bitcoins #bitcoinrequest #bitcoindonnie #bitcoins #bitcoindonate #bitcoinfreak #bitcoinfree @bitcoin.billionaires @freebitcoingiveaway @officialbrandimae @bitcoingiveaway @freecryptodaily #bitcoinacceptedhere #acceptbitcoin #paywithbitcoin

[madhu511-blog]

Bitcoin Price #endoftheday Donations welcomed BTC-3Dcgbvk3RH6jDqYPqLRYzcGWjVCHrZixQZ #bitcoinsallday #bitcoinmanagement #btcdonation #bitcoindonations #bitcoinfreak #bitcointalk #bitcoinlover #bitcoinbillionaire #bitcoinfree #bitcoinwallet #bitcoind #bitcoimillionaire #bitcoinforever #bitcoinnewyork #bitcoindubai #dubaibitcoin #dubaibitcoinbuyer #bitcoingiveaway #bitcoinpredictions #bitcoingirl #bitcoins #bitcoinrequest #bitcoindonnie #bitcoins #bitcoindonate #bitcoinfreak #bitcoinfree @bitcoin.billionaires @freebitcoingiveaway @officialbrandimae @bitcoingiveaway @freecryptodaily #bitcoinacceptedhere #acceptbitcoin #paywithbitcoin

[guugllsearch]

New Post has been published on http://www.guugll.eu/bitcoin-core-version-0-16-0-released/

Bitcoin Core version 0.16.0 released

Bitcoin Core version 0.16.0 is now available from:

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

This is a new major version release, including new features, various bugfixes 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 higher. Upgrading directly from 0.7.x and earlier without re-downloading the blockchain is not supported. However, as usual, old wallet versions are still supported.

Downgrading warning

Wallets created in 0.16 and later are not compatible with versions prior to 0.16 and will not work if you try to use newly created wallets in older versions. Existing wallets that were created with older versions are not affected by this.

Compatibility

Bitcoin Core is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later. Windows XP is not supported.

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

Notable changes

Wallet changes

Segwit Wallet

Bitcoin Core 0.16.0 introduces full support for segwit in the wallet and user interfaces. A new -addresstype argument has been added, which supports legacy, p2sh-segwit (default), and bech32 addresses. It controls what kind of addresses are produced by getnewaddress, getaccountaddress, and createmultisigaddress. A -changetype argument has also been added, with the same options, and by default equal to -addresstype, to control which kind of change is used.

A new address_type parameter has been added to the getnewaddress and addmultisigaddress RPCs to specify which type of address to generate. A change_type argument has been added to the fundrawtransaction RPC to override the -changetype argument for specific transactions.

All segwit addresses created through getnewaddress or *multisig RPCs explicitly get their redeemscripts added to the wallet file. This means that downgrading after creating a segwit address will work, as long as the wallet file is up to date.

All segwit keys in the wallet get an implicit redeemscript added, without it being written to the file. This means recovery of an old backup will work, as long as you use new software.

All keypool keys that are seen used in transactions explicitly get their redeemscripts added to the wallet files. This means that downgrading after recovering from a backup that includes a segwit address will work

Note that some RPCs do not yet support segwit addresses. Notably, signmessage/verifymessage doesn’t support segwit addresses, nor does importmulti at this time. Support for segwit in those RPCs will continue to be added in future versions.

P2WPKH change outputs are now used by default if any destination in the transaction is a P2WPKH or P2WSH output. This is done to ensure the change output is as indistinguishable from the other outputs as possible in either case.

BIP173 (Bech32) Address support (“bc1…” addresses)

Full support for native segwit addresses (BIP173 / Bech32) has now been added. This includes the ability to send to BIP173 addresses (including non-v0 ones), and generating these addresses (including as default new addresses, see above).

A checkbox has been added to the GUI to select whether a Bech32 address or P2SH-wrapped address should be generated when using segwit addresses. When launched with -addresstype=bech32 it is checked by default. When launched with -addresstype=legacy it is unchecked and disabled.

HD-wallets by default

Due to a backward-incompatible change in the wallet database, wallets created with version 0.16.0 will be rejected by previous versions. Also, version 0.16.0 will only create hierarchical deterministic (HD) wallets. Note that this only applies to new wallets; wallets made with previous versions will not be upgraded to be HD.

Replace-By-Fee by default in GUI

The send screen now uses BIP125 RBF by default, regardless of -walletrbf. There is a checkbox to mark the transaction as final.

The RPC default remains unchanged: to use RBF, launch with -walletrbf=1 or use the replaceable argument for individual transactions.

Wallets directory configuration (-walletdir)

Bitcoin Core now has more flexibility in where the wallets directory can be located. Previously wallet database files were stored at the top level of the bitcoin data directory. The behavior is now:

For new installations (where the data directory doesn’t already exist), wallets will now be stored in a new wallets/ subdirectory inside the data directory by default.

For existing nodes (where the data directory already exists), wallets will be stored in the data directory root by default. If a wallets/ subdirectory already exists in the data directory root, then wallets will be stored in the wallets/ subdirectory by default.

The location of the wallets directory can be overridden by specifying a -walletdir=<path> option where <path> can be an absolute path to a directory or directory symlink.

Care should be taken when choosing the wallets directory location, as if it becomes unavailable during operation, funds may be lost.

Build: Minimum GCC bumped to 4.8.x

The minimum version of the GCC compiler required to compile Bitcoin Core is now 4.8. No effort will be made to support older versions of GCC. See discussion in issue #11732 for more information. The minimum version for the Clang compiler is still 3.3. Other minimum dependency versions can be found in doc/dependencies.md in the repository.

Support for signalling pruned nodes (BIP159)

Pruned nodes can now signal BIP159’s NODE_NETWORK_LIMITED using service bits, in preparation for full BIP159 support in later versions. This would allow pruned nodes to serve the most recent blocks. However, the current change does not yet include support for connecting to these pruned peers.

Performance: SHA256 assembly enabled by default

The SHA256 hashing optimizations for architectures supporting SSE4, which lead to ~50% speedups in SHA256 on supported hardware (~5% faster synchronization and block validation), have now been enabled by default. In previous versions they were enabled using the --enable-experimental-asm flag when building, but are now the default and no longer deemed experimental.

GUI changes

Uses of “µBTC” in the GUI now also show the more colloquial term “bits”, specified in BIP176.

The option to reuse a previous address has now been removed. This was justified by the need to “resend” an invoice, but now that we have the request history, that need should be gone.

Support for searching by TXID has been added, rather than just address and label.

A “Use available balance” option has been added to the send coins dialog, to add the remaining available wallet balance to a transaction output.

A toggle for unblinding the password fields on the password dialog has been added.

RPC changes

New rescanblockchain RPC

A new RPC rescanblockchain has been added to manually invoke a blockchain rescan. The RPC supports start and end-height arguments for the rescan, and can be used in a multiwallet environment to rescan the blockchain at runtime.

New savemempool RPC

A new savemempool RPC has been added which allows the current mempool to be saved to disk at any time to avoid it being lost due to crashes / power loss.

Safe mode disabled by default

Safe mode is now disabled by default and must be manually enabled (with -disablesafemode=0) if you wish to use it. Safe mode is a feature that disables a subset of RPC calls – mostly related to the wallet and sending – automatically in case certain problem conditions with the network are detected. However, developers have come to regard these checks as not reliable enough to act on automatically. Even with safe mode disabled, they will still cause warnings in the warnings field of the getneworkinfo RPC and launch the -alertnotify command.

Renamed script for creating JSON-RPC credentials

The share/rpcuser/rpcuser.py script was renamed to share/rpcauth/rpcauth.py. This script can be used to create rpcauth credentials for a JSON-RPC user.

Validateaddress improvements

The validateaddress RPC output has been extended with a few new fields, and support for segwit addresses (both P2SH and Bech32). Specifically: * A new field iswitness is True for P2WPKH and P2WSH addresses (“bc1…” addresses), but not for P2SH-wrapped segwit addresses (see below). * The existing field isscript will now also report True for P2WSH addresses. * A new field embedded is present for all script addresses where the script is known and matches something that can be interpreted as a known address. This is particularly true for P2SH-P2WPKH and P2SH-P2WSH addresses. The value for embedded includes much of the information validateaddress would report if invoked directly on the embedded address. * For multisig scripts a new pubkeys field was added that reports the full public keys involved in the script (if known). This is a replacement for the existing addresses field (which reports the same information but encoded as P2PKH addresses), represented in a more useful and less confusing way. The addresses field remains present for non-segwit addresses for backward compatibility. * For all single-key addresses with known key (even when wrapped in P2SH or P2WSH), the pubkey field will be present. In particular, this means that invoking validateaddress on the output of getnewaddress will always report the pubkey, even when the address type is P2SH-P2WPKH.

  Credits

Thanks to everyone who directly contributed to this release:

251, Aaron Clauson, Aaron Golliver, aaron-hanson, Adam Langley, Akio Nakamura, Akira Takizawa, Alejandro Avilés, Alex Morcos, Alin Rus Anditto Heristyo, Andras Elso, Andreas Schildbach, Andrew Chow, Anthony Towns, azuchi, Carl Dong, Chris Moore, Chris Stewart, Christian Gentry, Cory Fields, Cristian Mircea Messel, CryptAxe, Dan Raviv, Daniel Edgecumbe, danra, david60, Donal O’Connor, dongsamb, Dusty Williams, Eelis, esneider, Evan Klitzke, fanquake, Ferdinando M. Ametrano, fivepiece, flack, Florian Schmaus, gnuser, Gregory Maxwell, Gregory ,Sanders , Henrik Jonsson, Jack Grigg, Jacky C, James Evans, James O’Beirne, Jan Sarenik, Jeff Rade, Jeremiah Buddenhagen, Jeremy Rubin, Jim Posen, jjz, Joe Harvell, Johannes Kanig, John Newbery, Johnson Lau, Jonas Nick, Jonas Schnelli, João Barbosa, Jorge Timón, Karel Bílek, Karl-Johan Alm, klemens, Kyuntae Ethan Kim, laudaa, Lawrence Nahum, Lucas Betschart, Luke Dashjr, Luke Mlsna, MarcoFalke, Mark Friedenbach, Marko Bencun, Martin Ankerl, Matt Corallo, mruddy, Murch, NicolasDorier, Pablo Fernandez, Paul Berg, Pedro Branco, Pierre Rochard, Pieter Wuille, practicalswift, Randolf Richardson, Russell Yanofsky, Samuel Dobson, Sean Erle Johnson, Shooter, Sjors Provoost, Suhas Daftuar, Thomas Snider, Thoragh, Tim Shimmin, Tomas van der Wansem, Utsav Gupta, Varunram Ganesh, Vivek Ganesan, Werner Lemberg, William Casarin, Willy Ko , Wladimir J. van der Laan

http://www.guugll.eu/?p=8435

[ct3ch]

Square Cash now allows anyone to buy and sell bitcoin

Square’s Cash App has been helping people send and receive money without fees for a while now. Originally an money-by-email service, Cash App has grown into a more robust offering with its own prepaid Visa card. The company has been testing buying and selling Bitcoin via the app, as well, and has finally made it official. Blockchaiiiiinnnnn! You can now buy and sell Bitcoin instantly with the…

View On WordPress

[guugllsearch]

New Post has been published on http://www.guugll.eu/bitcoin-core-0-15-1-released/

Bitcoin Core 0.15.1 Released

Bitcoin Core version 0.15.1 released

Bitcoin Core version 0.15.1 is now available from:

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

or

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

This is a new minor version release, including various bugfixes 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 higher, 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.

The file format of fee_estimates.dat changed in version 0.15.0. Hence, a downgrade from version 0.15 or upgrade to version 0.15 will cause all fee estimates to be discarded.

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. Upgrading directly from 0.7.x and earlier without redownloading the blockchain is not supported. However, as usual, old wallet versions are still supported.

Downgrading warning

The chainstate database for this release is not compatible with previous releases, so if you run 0.15 and then decide to switch back to any older version, you will need to run the old release with the -reindex-chainstate option to rebuild the chainstate data structures in the old format.

If your node has pruning enabled, this will entail re-downloading and processing the entire blockchain.

Compatibility

Bitcoin Core is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later. Windows XP is not supported.

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

Notable changes

Network fork safety enhancements

A number of changes to the way Bitcoin Core deals with peer connections and invalid blocks have been made, as a safety precaution against blockchain forks and misbehaving peers.

Unrequested blocks with less work than the minimum-chain-work are now no longer processed even if they have more work than the tip (a potential issue during IBD where the tip may have low-work). This prevents peers wasting the resources of a node.

Peers which provide a chain with less work than the minimum-chain-work during IBD will now be disconnected.

For a given outbound peer, we now check whether their best known block has at least as much work as our tip. If it doesn’t, and if we still haven’t heard about a block with sufficient work after a 20 minute timeout, then we send a single getheaders message, and wait 2 more minutes. If after two minutes their best known block has insufficient work, we disconnect that peer. We protect 4 of our outbound peers from being disconnected by this logic to prevent excessive network topology changes as a result of this algorithm, while still ensuring that we have a reasonable number of nodes not known to be on bogus chains.

Outbound (non-manual) peers that serve us block headers that are already known to be invalid (other than compact block announcements, because BIP 152 explicitly permits nodes to relay compact blocks before fully validating them) will now be disconnected.

If the chain tip has not been advanced for over 30 minutes, we now assume the tip may be stale and will try to connect to an additional outbound peer. A periodic check ensures that if this extra peer connection is in use, we will disconnect the peer that least recently announced a new block.

The set of all known invalid-themselves blocks (i.e. blocks which we attempted to connect but which were found to be invalid) are now tracked and used to check if new headers build on an invalid chain. This ensures that everything that descends from an invalid block is marked as such.

Miner block size limiting deprecated

Though blockmaxweight has been preferred for limiting the size of blocks returned by getblocktemplate since 0.13.0, blockmaxsize remained as an option for those who wished to limit their block size directly. Using this option resulted in a few UI issues as well as non-optimal fee selection and ever-so-slightly worse performance, and has thus now been deprecated. Further, the blockmaxsize option is now used only to calculate an implied blockmaxweight, instead of limiting block size directly. Any miners who wish to limit their blocks by size, instead of by weight, will have to do so manually by removing transactions from their block template directly.

GUI settings backed up on reset

The GUI settings will now be written to guisettings.ini.bak in the data directory before wiping them when the -resetguisettings argument is used. This can be used to retroactively troubleshoot issues due to the GUI settings.

Duplicate wallets disallowed

Previously, it was possible to open the same wallet twice by manually copying the wallet file, causing issues when both were opened simultaneously. It is no longer possible to open copies of the same wallet.

Debug -minimumchainwork argument added

A hidden debug argument -minimumchainwork has been added to allow a custom minimum work value to be used when validating a chain.

Low-level RPC changes

The “currentblocksize” value in getmininginfo has been removed.

dumpwallet no longer allows overwriting files. This is a security measure as well as prevents dangerous user mistakes.

backupwallet will now fail when attempting to backup to source file, rather than destroying the wallet.

listsinceblock will now throw an error if an unknown blockhash argument value is passed, instead of returning a list of all wallet transactions since the genesis block. The behaviour is unchanged when an empty string is provided.

  source: https://bitcoin.org/en/release/v0.15.1

http://www.guugll.eu/?p=8197