The Wallet Hut | Incredible Deals on Name Brand Wallets

Today marks the official release of Bitcoin Core 0.15.0, the fifteenth generation of bitcoin’s original software client launched by Satoshi Nakamoto almost nine years ago. Overseen by Bitcoin Core lead maintainer Wladimir van der Laan, this latest major release was developed by nearly 100 contributors over a six-month period, with major contributions through Chaincode Labs, Blockstream and MIT’s Digital Currency Initiative.

bitcoin Core 0.15.0 offers significant performance and usability improvements over previous versions of the software implementation. It also introduces several new features to better deal with the current status of the network.

These are some of the more notable changes.

Chainstate Database Restructure

One of the biggest changes compared to previous versions of the software involves how the state of bitcoin’s blockchain is stored. This “chainstate” or “UTXO-set” is saved in a dedicated database, whereas previously it had been categorized per transaction. If one transaction sent bitcoins to several outputs (“addresses”), these different outputs were stored as a single database entry, referring to that one transaction.

With bitcoin Core 0.15.0, these outputs are instead stored in a single database entry each. If a single transaction sends bitcoins to different outputs, every output is stored separately. While this method does claim more disc space, it requires less computational resources if one of these outputs is spent later on.

The most concrete benefit of this new data structure is that initial sync-time for new nodes is decreased by about 40 percent. It also introduces simpler code, reduces memory usage  and more. Additionally, it fixes a bug that could theoretically crash bitcoin Core nodes, controversially revealed at last weekend’s Breaking bitcoin conference in Paris.

Improved Fee Estimation

As bitcoin blocks have been filling up over the last year or two, not all transactions fit in the first block that is mined. Instead, miners typically prioritize the transactions that include the most fees. If a user wants to have his transaction confirmed quickly, he should include a high enough fee. If he’s not in a rush, a lower fee should suffice.

However, the bitcoin network deals with inherent unpredictability in terms of the speed at which blocks are found or the number of transactions that is being transmitted at any time. This makes it hard to include the right transaction fee.

bitcoin Core 0.15.0 lowers this fee uncertainty: The newest version of the software includes significantly better fee estimation algorithms. This is mostly because the software takes more data into account when making the estimations, such as the fees included in older confirmed transactions, as well as fees in unconfirmed transactions — the fees that proved insufficient.

Additionally, users can enjoy more flexibility. For one, bitcoin Core 0.15.0 for the first time allows users to include fees that could take their transactions up to a week to confirm. And, also newly introduced, users can choose to accept more or less risk that their transaction could be delayed due to a sudden influx of transactions.

Replace-by-fee in User Interface

Even with improved fee estimation, it is possible that users will still need to wait longer than they want for their transactions to confirm, perhaps because there is a sudden rush of transactions on the network, or maybe because a user changed his mind and prefers to have a transaction confirm faster than originally paid for, or for other reasons.

For these cases, some wallets let users add a “replace-by-fee” tag to their transactions. With such a tag, nodes and miners on the network know that the sender may want to replace that transaction with a newer transaction that includes a higher fee. This effectively allows users to bump the transaction in line to have it confirmed faster.

bitcoin Core nodes have supported replace-by-fee for well over a year now: They already replace “replace-by-fee” tagged transactions if the new transaction includes more fees. But it was never easy to utilize for bitcoin Core wallet users themselves.

Until now.

The bitcoin Core 0.15.0 wallet introduces a replace-by-fee toggle in its user interface. This lets users include the appropriate tag, allowing them to easily increase the fees on their transactions later on.

Multi-wallet Support (Client and RPC Only)

bitcoin Core 0.15.0 lets users create several wallets for the first time. These wallets all have their own separate bitcoin addresses, private keys and, therefore, funds. Users can utilize the different wallets for different purposes; for example, one wallet can be used for personal day-to-day purchases, another for business-related transactions, and a third just for trading.

Using several wallets can offer a number of benefits. For instance, it makes accounting easier and more convenient. Additionally, users can more easily benefit from increased privacy as the different wallets cannot be linked to each other by blockchain analysis. It’s also possible to use different wallets for specific applications and more.

For now, multi-wallet support is not yet available for regular wallet users; only advanced users who operate from the command line or through connected applications can utilize the feature.

Other Improvements

Apart from the above mentioned notable changes, bitcoin Core 0.15.0 includes a number of additional performance improvements, as most new major bitcoin Core releases do. Concretely, these changes speed up how quickly blocks are downloaded from the network, they let nodes start up faster, and up-to-date nodes will be able to validate new blocks more quickly, in turn benefiting network-propagation time.

Finally, it’s worth mentioning that bitcoin Core 0.15.0 will disconnect from BTC1 peers on the network. This means that the bitcoin network will experience less disruption if the SegWit2x hard fork splits the network, as both types of nodes will more easily find compatible peers. While this change has gotten some media attention, this change shouldn’t really be noticeable.

Thanks to Chaincode Labs developer John Newbery for feedback and suggestions. For more details on what’s new in bitcoin Core 0.15.0, see the release notes, or watch bitcoin Core contributor Gregory Maxwell’s “deep dive” presentation at the San Francisco bitcoin developers meetup.

An ethical hacker breached the database of a phony darknet website offering hitman services and leaked the data. The information from the data dump helped the FBI in their investigation of a man who murdered his wife.

In November 2016, Stephen Carl Allwine, 47, of Cottage Grove, Minnesota, killed his wife in “one of the most bizarre cases ever seen,” police officers reported. The husband tried to mask the murder as a suicide, including putting a 9 mm pistol next to Amy Allwine’s elbow. However, detectives arriving on the scene identified the case as murder and collected evidence — mostly electronic devices, such as computers — belonging to Mr. Allwine. Later on, in January, investigators arrested and charged Mr. Allwine with second-degree murder based on the forensic evaluation of the confiscated electronic equipment.

In May 2016, a hacker called “bRpsd” breached the database of a controversial hitman service offered on a darknet website. The service, “Besa Mafia,” offered a link between customers and hitmen, who could register on the site anonymously. The price for a murder ranged between $5,000 and $200,000, but clients seeking to avoid fatalities could also hire a contractor to beat up a victim for $500 or set somebody’s car on fire for $1,000.

The hacker uploaded the data dump to a public internet website. The leaked files contained user accounts, email addresses, personal messages between the Besa Mafia admin and its customers, “hit” orders and a folder named “victims,” providing additional information on the targets.

The breach highlighted the fake nature of the website, which operated only to collect money from the customers. Chris Monteiro, an independent researcher who also hacked into the site, stated the owner or owners of Besa Mafia had made at least 50 bitcoins ($127,500 based on the current value of the cryptocurrency) from the scam operation.

According to a message posted by a Besa Mafia administrator and uncovered in the dump, “[T]his website is to scam criminals of their money. We report them for 2 reasons: to stop murder, this is moral and right; to avoid being charged with conspiracy to murder or association to murder, if we get caught.”

The leak of the Besa Mafia database helped the police investigating the murder of Mrs. Allwine. As the officers analyzed her husband’s devices, they discovered the suspect had accessed the dark web as early as 2014. Furthermore, investigators identified the pseudonym Mr. Allwine used on the darknet, “dogdaygod,” which was also linked to his email, “dogdaygod@hmamail.com,” in some cases. Detectives found bitcoin addresses in the conversations between Besa Mafia and Mr. Allwine, which linked the husband directly to the “dogdaygod” pseudonym, providing authorities with necessary evidence for the case.

Eventually, law enforcement agents analyzed the data dump bRpsd leaked and discovered Mr. Allwine’s email in the list. In addition, investigators found messages between the suspect and the Besa Mafia admin. According to a criminal complaint, Mr. Allwine paid between $10,000 to $15,000 to the supposed hitman service to kill his wife. The complaint detailed how Mr. Allwine had decided to have the hitman shoot Mrs. Allwine at close range and burn down the house afterward.

However, once the funds were transferred, the Besa Mafia communicator told Mr. Allwine that “local police [have] stopped the hitman [from] driving a stolen vehicle and taken [him] to jail prior to the hit,” thus rendering him unable to complete his “service.” The complaint cited Sergeant McAlister who reported that during that time, “no one was apprehended in Minnesota and western Wisconsin in a stolen vehicle and possession of a gun.”

It is likely that the ethical hacker’s data breach had an impact on Mr. Allwine’s case; on March 24, 2017, the Washington County District Court charged him with first-degree murder. In addition, officers have gathered more evidence in the case — a drug called scopolamine was discovered at 45 times higher than the recommended level in Mrs. Allwine’s body. Investigators subsequently discovered that her husband had also ordered the substance on the dark web.