Coinbase – Buy & Sell Bitcoin, Ethereum, and more with trust

Groestlcoin Release September 2018

Introduction

As always, the past 3 months since 22nd June have been crazy busy. The bears might still be around, but the show must go on and of course has not slowed the Groestlcoin development team in the slightest. Here’s a quick overview of what has already happened since the last release: - Integrated into the bitbns exchange, with the ability to buy Groestlcoin directly with the Indian Rupee. - Groestlcoin Rebrand Vote – Whilst there was much talk and push for a rebrand vote, the overall result was almost unanimously in favour of keeping our unique and conversation-starting name. With just 83 votes to Rebrand, and 2577 votes to No Rebrand. Thank you for all who voted, the funds raised are being used to fund ongoing hosting and development costs. - Integrated into the Cryptobridge exchange. Cryptobridge is a popular decentralised exchange where you always hold the private keys to your funds, only YOU have access to them. - Groestlcoin has been added to SimpleSwap – Groestlcoin can now be swapped with over 100 other cryptocurrencies, without signing up! - Groestlcoin has been added to UnoDax, one of the leading cryptocurrency exchanges in India, with TUSD, BTC and INR trading pairs. - Groestlcoin has been added to SwapLab.cc, where you can buy Groestlcoin using Bitcoin and over 50 other altcoins. Purchasing with VISA/Mastercard is coming VERY SOON. Discussed later: - Groestlcoin has been listed on #3 largest exchange in the world on volume, Huobi Global! More on this to come further on in the announcements. - Groestlcoin has been added to the Guarda Multi-Currency Wallet. - Groestlcoin has been added to Melis Multi-Device, Multi-Account, Multi-Platform, Multi-Signature advanced wallet! Already this list is far more than most other cryptocurrencies have achieved in the past 3 months. But this is just the tip of the iceberg of what has been developed.

What's been Happening?

GRSPay Released

We are so excited for this, that it has it's own separate reddit thread. Head over there now at https://www.reddit.com/groestlcoin/comments/9ikr5m/groestlcoin_releases_grspay/? to see more on this!
https://www.melis.io/assets/logo-navbar-4b6f0d372f15b2446d3fa4c68f346e4fb08ee113941186cee58fd6135f3f8b7d.svg

Melis Wallet

The the most advanced wallet for Bitcoin, Bitcoin Cash, Litecoin and now Groestlcoin.
With Melis you have the complete control of your bitcoins and private keys, you can define spending limits policies and make use of two or more factors authentication. Melis is open source, published on GitHub.

How Melis Works?

You can create as many accounts as you want. An account is a part of your wallet that can be customised to your requirements. You can choose how many co-signers are required to spend funds. The accounts are completely independent and act like separate wallets from each other but can be accessed via the same details. A core feature of Melis is the ability to set a ‘primary’ device. With this you can set an account as ‘Secure’ so it is only viewable (and accessible at all) from the Primary device. You can have a savings account hidden from the outside world whilst also having your ‘spending’ funds available on the go. With Melis you can create a multi-signature account between N people, where up to N signatures are required to sign a transaction, choosing if any of those should be mandatory.
Core Features:
https://guarda.co/assets/images/1PGo4ID.svg?1537791124643

Guarda Wallet

Safer than ever! Desktop Light Wallet - Anonymous and fast!
With Guarda Multi-currency Desktop Light Wallet you don’t need to register. Guarda has no access to your private keys or funds. You can receive, send, store, buy and exchange cryptocurrencies in complete anonymity and safety. All these features are available on Linux, Windows or MacOS. Choose the one that suits you!
More info about Guarda wallet on www.guarda.co
https://holytransaction.com/images/logo.png

Integrated into HolyTransaction

What is HolyTransaction?

HolyTransaction gives users access to the crypto world with a universal cryptocurrency wallet and instant exchange.

Features

For more information, visit Holy Transaction here.
https://www.groestlcoin.org/wp-content/uploads/2018/09/next-grs-groestlcoin.jpg

Integrated into NEXT Wallet

What is NEXT?

NEXT is a modern, next-generation stylish open-source Desktop wallet.

Features

For more information, visit NextWallet here.
https://blockchainfinancial.com/mediaserve2018/09/admin-06143647-bcf_logo_vec_256x256.png

Integrated into Blockchain Financial

What is Blockchain Financial?

Blockchain Financial is a set of web based services for individuals and companies that want to make things happen with the Cryptocurrencies Ecosystem. - For those that don't know anything about cryptocurrencies, we offer tools that will let them receive, send and operate with an assortment of coins. - For those that are already riding the wave, we offer tools that will let them do all those things that they weren't able to do.

Blockchain Financials mission

We're not here to reinvent the wheel. We're here to make it run smoother for you, and we provide some of the most useful services you'll find on the internet, made in a way that is easy to understand and use on a daily basis. In short, we're a bunch of people that claim to be Crypto Evangelists. We strongly believe in cryptocurrencies, and our main promise is to push them up so more people get involved and take all the advantages they offer.

More information from Blockchain Financial

Back in 2014, the world was taken by storm when Facebook approved the first cryptocurrencies tipping apps. The first was for Dogecoin, and the second was for multiple coins.
The project was hosted on whitepuma.net, and persisted for almost two years, built up a massive user community and gave a home to Bitcoin, Litecoin, Dogecoin and dozens of other bitcoin-based altcoins.
After very active months, the tipping hype started to fade away. Then, the developers decided to jump into the next stage: bringing not only tipping, but also mining and a widget that could be embedded on websites to allow everyone to accept payments. Sadly, the work was never completed because the project started to require an unsustainable amount of resources. Then, in a painful decision, a shutdown was announced by December 2015.
A couple of months after whitepuma.net was closed, the source code was released by its creator as Open Source on GitHub. But it wasn't maintained.
Now, some of the original members of the dev and admin teams gathered up with a handful of the WhitePuma's elite users, and decided to make something good with the best pieces of the old source code. That, with fresh new ideas and the power of the BardCanvas engine, synthesized the core of Blockchain Financial.
More info about Blockchain Financial wallet on .
For more information, visit [Blockchain Financial](www.blockchainfinancial.com)
https://www.huobi.com/image/logo.aeb4723.svg

Groestlcoin Listed on Huobi

Who are Huobi?

Huobi was founded in China and is now based in Singapore, with offices in Hong Kong, South Korea, Japan and the North America, currently sitting #3 in volume on Coinmarketcap. Huobi is a great leap forward for our growing presence in Asia and we are very excited to be listed here!
You can find the official Huobi announcement here.

Groestlcoin Core v2.16.3 - Please Update ASAP

A new major Groestlcoin Core version 2.16.3 is now available for download which includes both a Denial of Service component and a critical inflation vulnerability, so it is recommended to upgrade to it if you are running a full Groestlcoin node or a local Groestlcoin Core wallet.
v2.16.3 is now the official release version of Groestlcoin Core. This is a new major version release with a very important security updates. It is recommended to upgrade to this version as soon as possible. Please stop running versions of Groestlcoin Core affected by CVE-2018-17144 ASAP: These are 2.13.3 and 2.16.0.
As a result in this, all exchanges and services have been asked to upgrade to this version, so please be patient if wallets go in to maintenance mode on these services.

What's new in version v2.16.3?

This is a major release of Groestlcoin Core fixing a Denial of Service component and a critical inflation vulnerability (https://nvd.nist.gov/vuln/detail/CVE-2018-17144) exploitable by miners that has been discovered in Groestlcoin Core version 2.13.3 and 2.16.0. It is recommended to upgrade to 2.16.3 as soon as possible. If you only occasionally run Groestlcoin Core, then it's not necessary to run out and upgrade it right this second. However, you should upgrade it before you next run it. If you know anyone who is running an older version, tell them to upgrade it ASAP. Stored funds are not at risk, and never were at risk. At this time we believe over half of the Groestlcoin hashrate has upgraded to patched nodes. We are unaware of any attempts to exploit this vulnerability. However, it still remains critical that affected users upgrade and apply the latest patches to ensure no possibility of large reorganizations, mining of invalid blocks, or acceptance of invalid transactions occurs.

The Technicals

In Groestlcoin Core 2.13.3, an optimization was added (Bitcoin Core PR #9049) which avoided a costly check during initial pre-relay block validation that multiple inputs within a single transaction did not spend the same input twice which was added in 2012 (Bitcoin Core PR #443). While the UTXO-updating logic has sufficient knowledge to check that such a condition is not violated in 2.13.3 it only did so in a sanity check assertion and not with full error handling (it did, however, fully handle this case twice in prior to 2.1.0.6). Thus, in Groestlcoin Core 2.13.3, any attempts to double-spend a transaction output within a single transaction inside of a block will result in an assertion failure and a crash, as was originally reported. In Groestlcoin Core 2.16.0, as a part of a larger redesign to simplify unspent transaction output tracking and correct a resource exhaustion attack the assertion was changed subtly. Instead of asserting that the output being marked spent was previously unspent, it only asserts that it exists. Thus, in Groestlcoin Core 2.16.0, any attempts to double-spend a transaction output within a single transaction inside of a block where the output being spent was created in the same block, the same assertion failure will occur. However, if the output being double-spent was created in a previous block, an entry will still remain in the CCoin map with the DIRTY flag set and having been marked as spent, resulting in no such assertion. This could allow a miner to inflate the supply of Groestlcoin as they would be then able to claim the value being spent twice.
Groestlcoin would like to publicly thank Reddit user u/Awemany for finding CVE-2018-17144 and reporting it (https://lists.linuxfoundation.org/pipermail/bitcoin-core-dev/2018-Septembe000064.html). You deserve gratitude and appreciation from cryptoworld, and you have ours. If you want to support him for his work, please consider donating to him on his bitcoin cash address: bitcoincash:qr5yuq3q40u7mxwqz6xvamkfj8tg45wyus7fhqzug5
http://i.imgur.com/3YhyNZK.png

Groestlcoin Electrum-GRS 3.2.2 - Ledger & Trezor Edition

What is Electrum-GRS?
Electrum-GRS is a lightweight "thin client" groestlcoin wallet Windows, MacOS and Linux based on a client-server protocol. Its main advantages over the original Groestlcoin client include support for multi-signature wallets and not requiring the download of the entire block chain.

Changes:

http://i.imgur.com/3YhyNZK.png

Electrum-GRS Mobile Android

What is Electrum-GRS Mobile?

Electrum-grs is a lightweight "thin client" groestlcoin wallet Android based on a client-server protocol. Its main advantages over the original Groestlcoin client include support for multi-signature wallets and not requiring the download of the entire block chain.

Changes

Groestlcoin EasyVanity Released

Groestlcoin EasyVanity is a Windows app is built from the ground-up in C# and makes it easier than ever before to create your very own bespoke Groestlcoin address(es), even whilst not connected to the internet! You can even generate multiple keys with the same prefix and leave it on overnight whilst your CPU or GPU collects and stores these addresses locally.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then Groestlcoin EasyVanity is the right choice for you to create a more personalized address.

Features

• Ability to continue finding keys after first one is found • Includes warning on startup if connected to the internet • Ability to output keys to a text file (And shows button to open that directory) • Ability to make your match case sensitive (Where possible) • Show and hide the private key with a simple toggle switch, and copy the private key straight to your clipboard • Show full output of commands • Includes statistics whilst the application is running • Ability to choose between Processor (CPU) and Graphics Card (GPU) • Automatically detects 32 or 64 bit systems • Features both a Light and Dark Material Design inspired Themes • EasyVanity's search is probabilistic, and the amount of time required to find a given pattern depends on how complex the pattern is, the speed of your computer, and whether you get lucky. • EasyVanity includes components to perform address searching on your CPU (vanitygen) and your OpenCL-compatible GPU (oclvanitygen). Both can be built from source, and both are included in the Windows binary package. • Prefixes are exact strings that must appear at the beginning of the address. When searching for prefixes, Easyvanity will ensure that the prefix is possible, and will provide a difficulty estimate. • The percentage displayed just shows how probable it is that a match would be found in the session so far. If it finds your address with 5% on the display, you are extremely lucky. If it finds your address with 92% on the display, you are unlucky. If you stop EasyVanity with 90% on the display, restart it, and it finds your address with 2% on the display, your first session was unlucky, but your second session was lucky. • EasyVanity uses the OpenSSL random number generator. This is the same RNG used by groestlcoin and a good number of HTTPS servers. It is regarded as well-scrutinized. Guessing the private key of an address found by EasyVanity will be no easier than guessing a private key created by groestlcoin itself. • To speed up address generation, EasyVanity uses the RNG to choose a private key, and literally increments the private key in a loop searching for a match. As long as the starting point is not disclosed, if a match is found, the private key will not be any easier to guess than if every private key tested were taken from the RNG. EasyVanity will also reload the private key from the RNG after 10,000,000 unsuccessful searches (100M for oclvanitygen), or when a match is found and multiple patterns are being searched for. • Free software - MIT. Anyone can audit the code. • Written in C# - The code is short, and easy to review.

Groestlcoin Sentinel (Android & Blackberry) – Mainnet + Testnet

What is Sentinel?

Groestlcoin Sentinel is the easiest and fastest way to track/receive/watch payments in your offline Groestlcoin Wallets. Groestlcoin Sentinel is compatible with any standard Groestlcoin address, BIP44 XPUB (Extended Public Key) BIP49 YPUB and BIP84 ZPUB
Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets). Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that particular wallet.

What's New?

The P2SH paperwallet supports creating P2SH paperwallets in bulk, keypair generation with QR codes and sweeping tool. Groestlcoin believes strongly in privacy, the live version does not collect and store IP or transaction data.
Changes
Features
The BECH32 paperwallet supports creating BECH32 paperwallets in bulk, keypair generation with QR codes and sweeping tool. Groestlcoin believes strongly in privacy, the live version does not collect and store IP or transaction data.
Features
![WebWallet](https://i.imgur.com/Z2oj7bj.png)

Groestlcoin Web Wallet Update 1.4

What is Groestlcoin Web Wallet?
Groestlcoin Webwallet is an open source, multisignature, HD Wallet and more! Webwallet is a a open source browser based Groestlcoin webwallet.
Webwallet is a playground for Groestlcoin in javascript to experiment with. It supports multisig, OP_HODL, RBF and many more. Groestlcoin believes strongly in privacy, the live version does not collect and store IP or transaction data.
Changes:
submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

How to set up an incentivized node in Ubuntu [likely works for other Linux as well…]

There has been a post lately about how you can participate in a program by bitnodes which is intended to incentivize running a full node.
In the comment section of the post there were some instruction by AndrewToth as to how to set the whole thing up. Unfortunately it didn’t work for me directly. I would therefore like to share how I finally managed to get it done.
If you would like to run a scrip to do all the heavy lifting for you, please perform steps 1, 2 and 12 now and then just copy paste this into the terminal and hit enter: wget -O bitnodes-incentive.sh http://pastebin.com/download.php?i=607WQaBy && sed -i 's/\/' bitnodes-incentive.sh && chmod +x bitnodes-incentive.sh && ./bitnodes-incentive.sh The script will also advise you to do the required port forwarding. You can look at the script here.
1 Find out your local IP by opening a terminal and typeifconfig. You will see your local IP listed under eth0 as inet addr. In the subsequent steps of this tutorial it will be referenced as $localip. So whenever you read $localip it means, your local IP you have just found out. It would be helpful to make this IP static.
2 Set up a full node. You need to download Bitcon Core, run it until you are synchronized. It needs to allow more than 8 connections and you therefore need to turn on port forwarding on your router. So if the machine which runs the full node has $localip in your subnet, you need to tell your router to forward port 8333 to $localip port 8333. If you open Bitcoin-QT it will tell you on the lower right corner, how many connections it has. If the number turns >8 after 5-10 minutes, you are all set. If you need a more detailed tutorial, you may try this one. Beware, if you don’t run a full node yet, allow it between 12 and 24 hours to synch.
3 Now you need to know your own public IP address. You can e.g. find it out like this. In the subsequent steps of this tutorial it will be referenced as $ip, so whenever you reed $ip it means, your public IP you have just found out.
4 Get a Bitcoin address. Please use one which you control the key to. I guess you know the deal. In the subsequent steps of this tutorial it will be referenced as $address, so whenever you reed $address it means, your Bitcoin address.
5 Open a new terminal and copy paste the following into the terminal each followed by enter key (beware $address means your address, no “$” sign needed): mkdir bitcoin-address cd bitcoin-address vi index.html i $address You will see a lot of “~” in the terminal. Don’t worry. It’s supposed to be like that.
6 Hit the escape key.
7 Type :wq and hit enter key.
8 Type python -m SimpleHTTPServer 8000 and hit enter key. In case you should have to restart this web-server you will have to do it from the "bitcoin-address" directory created in step 5. want to use alternative port?
9 Now go back to your router configuration page and set it to forward port 80 to $localip port 8000. Beware, $localip is not your public IP which you have found out in step 3 but the subnet IP of the machine you run your node on which you have found out in step 1.
10 Confirm steps 5-9 worked by using a different internet connection (e.g. 4g on your phone) and type $ip in the address bar. You should see a simple webpage with only your Bitcoin address on. If you see that, you are set to go on.
11 Activate your node by opening your web browser and entering https://bitnodes.21.co/nodes/$ip-8333/ in the address bar. Beware of the $ip you have to replace with your specific parameter.
12 Open a new terminal and copy paste sudo apt-get install curl and hit enter key. You will be asked for your root password to do this step.
13 Open a new terminal and copy paste this:curl -H 'Accept: application/json; indent=4' -d 'bitcoin_address=$address' -d 'url=http://$ip' https://bitnodes.21.co/api/v1/nodes/$ip-8333/ Beware of the $address and $ip (2x) you have to replace with your specific parameters. There is a "success": true message in the terminal after this step.
14 Open your browser on the system with runs your node and the following in the address bar: https://bitnodes.21.co/api/v1/nodes/$ip-8333/ Beware of the $ip you have to replace with your specific parameter. Url and bitcoin_address parameters should not be empty. If you wait ten minutes and reload the page you should also get "verified": true. This means you are now in the node incentive program. Any incentives will be payed to your Bitcoin address, shall you receive any. I think it depends on luck.
15 Open your browser on the system which runs your node and the following in the address bar: https://bitnodes.21.co/nodes/$ip-8333/ Beware of the $ip you have to replace with your specific parameter. Alternatively just reload the page from step 11 if you still have it open. You can now see some statistics for your node plus you should also be able to see it’s Bitcon address and verification url.
16 You can see where your node is in the leaderboard by entering this into the address bar of your browser: https://bitnodes.21.co/nodes/leaderboard/?q=$ip Beware of the $ip you have to replace with your specific parameter. You can now see the PIX rank of your node. It needs to be above 8 to have your node successfully in the ballot. PIX rank explanation given on the site.
Thanks to bitnodes.io, Addy Yeow and AndrewToth for helping me out to set up my own incentivized node.
Now I wish you all the best! Please tell me if it works, I will be back later to answer questions or correct things.
Edit1: I have done lots of formatting updates. Added Point 14 16.
Edit2: Added steps proposed by Explodicle. Installation of curl and activation of node at bitnode.io.
Edit3: Added the dedicated folder for web-server index.html
Edit4: Alternative port options added as suggested by n00tz.
Edit5: Awesome script added to top section. All props to Explodicle.
Edit6: Changed instructions and the script to work with new address "bitnodes.21.co" instead of "getaddr.bitnodes.io"
submitted by SimonBelmond to Bitcoin [link] [comments]

It's about time Bitcoin was associated to biomedical research

Introducing Bitsolve, no it's not a alt coin. This is, however, a work in progress, and is constructed to provide a direction, if not, a potential architecture to how we can use Bitcoin technology to accomplish goals that directly contribute to the betterment and understanding of human health. Edits, correction, improvements are the goals for this post. Be explicit.
BitSolve: An open source incentivized decentralized free-market peer-2- peer architecture that harnesses the computational power of the world in order to solve complex and/or large-scale biological problems while providing real-time monetary compensation in bitcoin to anyone with a CPU.
The computational resources required to solve biological problems are hard to over-estimate. Since the 1990s, bioinformatics and computational biology have emerged as crucial elements in solving problems in virtually every field of biology. Such needs are predicted to increase as dataset generation explodes due to technologies such as next-generation sequencing, high-throughput proteomics, metabolomics and epigenomics. Furthermore, scientists are beginning to appreciate holistic approaches in modeling biological systems such as whole cell, and organ level dynamics via integrating several datasets from multiple sub-cellular technologies that utilize computationally intensive algorithms.
There is an enormous amount of computation power that is currently inaccessible to the life scientist. This power is available not in laboratories or institutions, but rather in personal computers in homes and hands (smart phones, tablets) that belong to people all around the world. These computers are often idle or are underperforming because of computationally trivial activities such as web browsing, checking e-mail or typing into a word processor. There would be an exponential boost in computation power available to life scientists if such CPU power could be harnessed for solving biological problems. Furthermore, as each individual would upgrade their hardware for their own private use, this would free scientists from this task, freeing them to focus on hypothesis testing and the scientific questions at hand.
BitSolve would enable any scientist in any part of the world to ask sophisticated questions from an ever more increasing dataset without ever having to worry about updating hardware or statistical software. Distributed computational architectures are not entirely novel, not even for biological analysis. However, previous systems have had one major flaw: they have relied on the voluntary donation of computation resources by individuals at home. As individuals have had zero monetary incentive to lend their power, many of them have been reluctant to do so.
We propose a system called BitSolve that provides a direct monetary incentive to anyone in the world with a computational unit and an internet connection, where individuals get paid directly and immediately for devoting their computer's CPU time over the internet. Such a system could have additional benefits as well. For instance, it would allow individuals and scientists to bid for a CPU poweprice that would drive down the price of computation power in a free market environment. This would encourage third world citizens to participate in the network due to their relatively lower electricity costs. BitSolve will thus enable truly global participation on an even competitive plane, where the mere ownership of a device with a computational unit will simultaneously be a revenue source for the owner, and a cheap and ample computational source for researchers.
How does it work?
The architecture would be a piece of software that anyone could download. The software would be coded in a cross-platform programming language such as C++, Java, QT etc, so that it could be run on most desktops, laptops, smart phones, and tablets. Once the software is run, the user's computational unit becomes part of a network of computers running the same software. Anyone running the software can choose to become a “CPU giver” or a “CPU requester.” It is important to note that, nowhere during the process is there a need for entering any personal information, making this a relatively friction free adoption technology.
A CPU giver: A CPU giver is someone whom has downloaded the software and agrees on renting out their CPU for a certain time on an agreed upon price. A “CPU giver” would ask for a certain price for example x BTC/min or at a market price. The software would determine the market price of the “CPU giver” after running a test on the CPU to estimate the available resources and then strike a price based on the real-time market exchange. The “CPU giver” could then leave the computational unit, which, if selected in the market, would conduct parts of an analysis, broadcast the completion of analysis, and after receiving confirmation from the network of true completion, would receive funds from the CPU requester that would directly be transferred to the CPU giver's wallet. All of this would happen automatically and without the need for a third party. A CPU requester: A CPU requester is someone who is seeking computational power in the network and has funds in bitcoin allotted for the required analysis. The CPU requester would have a statistical algorithm to be conducted with a certain dataset. After choosing the dataset and copying the R script to the software, the CPU requester then chooses the price that they are willing to pay for the analysis. “CPU givers” that have fast CPUs would ask for a high price, and those with slower CPUs would ask for a lower one. In other words, if CPU requesters wants the analysis conducted in a small amount of time, they would pay a higher price, whereas, they would bid for a lower price if the analysis can be run in a longer period of time. The software would also include a real time CPU/price exchange market that would serve as a reference for bidding. Once the price is chosen, the information is broadcasted across the network and CPU givers are chosen automatically (corresponding with asking prices). The request is then processed and the parts of the data are analyzed securely. Once the analysis is complete, the network using existing Bitcoin proof-of-work algorithm verifies the completion, and the payment of bitcoin is made from the CPU requester to the CPU giver. The results are then returned to the requester and operation is complete.
Can you describe the software?
The software would have four main components 1. R Statistical package (http://www.r-project.org/): R is the open source, statistical engine that would be the interface for the analyst to program their analysis. R is also the most widely used and rapidly evolving statistical platform used by life scientists due in part to its open source and thus free nature. 2. MutliThreader:Java based open source interpreter that converts the R program into smaller portions that can be sent to separate computers in the network to conduct the analysis and also handles the peer-2-peer communication. 3. A Bitcoin (http://bitcoin.org/en/) (open-source) client that would handle the real-time financial transactions. 4. Java based open source exchange system and handles the bidding for CPU by price for the CPU requester and the bidding of CPU by price for the CPU giver. 5. Java based open source allocation for integrating other types of computation not applicable to R for future expansion. * Note the specific software requirements are not mandatory but use the framework of what is possible in 2013. We also acknowledge that some parts of the systems can be implemented with software such as mastercoin (open-source) and colored coins(open-source). The two essential parts would be a bitcoin client and R statistical software. Why Peer-2-peer and not distributed? Is there a difference? Past architectures that have sought to harness the computational power of personal computers have been distributed from one to many, as in one laboratory aims to distribute their software to many individuals to conduct their analysis exclusively and specifically.(Pande Lab, Stanford). A peer-2- peer united open source system, would entail that any one that uses the free software can act as a CPU “giver” as well as a CPU “requester”. More importantly, because the entire process does not require personal information, the bidding process for CPU time would be free of considerations regarding project scope or vocational seniority. Due to this “freedom,” a graduate student in Boston, could program his personalized analysis of black hole dynamics to run on super computers in Stanford by bidding a higher price, while on the same market a precocious 15 year old in Korea, could bid a lower price to have his father's farm optimization algorithm run on slower and thus cheaper smart phones in India. The diversity in juxtapositions is intentional and should highlight that although this paper discusses the benefits with the life scientist in mind, the implementation does not limit, and to a certain degree, demands context and identity free analysis. This provision is primarily meant to ensure swift and diverse advancement of the software and to have enough CPU 'requesters' to implicate free market dynamics that will lower the prices and thus ensure highest value for CPU speed per houprice. It may be useful to note this will be the first time CPU speed/price will self stabilize on a global level to an optimal value that will be devoid of price inflation due to taxes associated with local governments and geographical distance to the CPU manufacturer etc. Peer-2-peer is extremely robust. Since previous distributed systems have had one governing computational node that does all its CPU requesting, they have been vulnerable to attacks and other security risks. Since this system is peer-2-peer, anonymous, and decentralized, there would never be a target to attack in the first place, ensuring security and robustness. Taking the system down would only be attainable by compromising the Internet in its entirety. Can you explain how the monetary compensation works? Bitcoin is a revolutionary technology. It is a completely decentralized, peer- 2-peer, open source, Internet currency/asset. Bitcoin uses peer-to-peer technology to operate with no central authority or banks. The network collectively carries out the managing of transactions and the issuing of bitcoins. Bitcoin's unique and groundbreaking properties make new applications for financial transactions that were virtually non-existent with legacy technologies now possible. This project would not be possible if monetary compensation of CPU givers entailed entering personal data, bank information etc. This would carry significant friction for scaling and in some countries wouldn't be possible even in theory because of high numbers of unbanked individuals and archaic financial systems. The only friction in this model is where anyone requesting a CPU would first need to exchange their local currency into bitcoin, which can be done in several online bitcoin exchanges that accept a plethora of local currencies. Since the ratio of CPU givers to CPU requesters is expected to be very high, this is unlikely to cause major problems in scaling now or in the future. CPU givers would only be required to download the software and run it in order to start accepting monetary compensation. It is also useful to note that the bitcoin network itself may be used as a source for computational power, although this would carry with it limited diversity in the type of computation possible.
submitted by bitcoinsSG to Bitcoin [link] [comments]

Bitcoin Core 0.10.0 released | Wladimir | Feb 16 2015

Wladimir on Feb 16 2015:
Bitcoin Core version 0.10.0 is now available from:
https://bitcoin.org/bin/0.10.0/
This is a new major version release, bringing both new features and
bug fixes.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
The whole distribution is also available as torrent:
https://bitcoin.org/bin/0.10.0/bitcoin-0.10.0.torrent
magnet:?xt=urn:btih:170c61fe09dafecfbb97cb4dccd32173383f4e68&dn;=0.10.0&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr;=udp%3A%2F%2Fopen.demonii.com%3A1337&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F
Upgrading and downgrading

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).
Downgrading warning
Because release 0.10.0 makes use of headers-first synchronization and parallel
block download (see further), the block files and databases are not
backwards-compatible with older versions of Bitcoin Core or other software:
  • Blocks will be stored on disk out of order (in the order they are
received, really), which makes it incompatible with some tools or
other programs. Reindexing using earlier versions will also not work
anymore as a result of this.
  • The block index database will now hold headers for which no block is
stored on disk, which earlier versions won't support.
If you want to be able to downgrade smoothly, make a backup of your entire data
directory. Without this your node will need start syncing (or importing from
bootstrap.dat) anew afterwards. It is possible that the data from a completely
synchronised 0.10 node may be usable in older versions as-is, but this is not
supported and may break as soon as the older version attempts to reindex.
This does not affect wallet forward or backward compatibility.
Notable changes

Faster synchronization
Bitcoin Core now uses 'headers-first synchronization'. This means that we first
ask peers for block headers (a total of 27 megabytes, as of December 2014) and
validate those. In a second stage, when the headers have been discovered, we
download the blocks. However, as we already know about the whole chain in
advance, the blocks can be downloaded in parallel from all available peers.
In practice, this means a much faster and more robust synchronization. On
recent hardware with a decent network link, it can be as little as 3 hours
for an initial full synchronization. You may notice a slower progress in the
very first few minutes, when headers are still being fetched and verified, but
it should gain speed afterwards.
A few RPCs were added/updated as a result of this:
  • getblockchaininfo now returns the number of validated headers in addition to
the number of validated blocks.
  • getpeerinfo lists both the number of blocks and headers we know we have in
common with each peer. While synchronizing, the heights of the blocks that we
have requested from peers (but haven't received yet) are also listed as
'inflight'.
  • A new RPC getchaintips lists all known branches of the block chain,
including those we only have headers for.
Transaction fee changes
This release automatically estimates how high a transaction fee (or how
high a priority) transactions require to be confirmed quickly. The default
settings will create transactions that confirm quickly; see the new
'txconfirmtarget' setting to control the tradeoff between fees and
confirmation times. Fees are added by default unless the 'sendfreetransactions'
setting is enabled.
Prior releases used hard-coded fees (and priorities), and would
sometimes create transactions that took a very long time to confirm.
Statistics used to estimate fees and priorities are saved in the
data directory in the fee_estimates.dat file just before
program shutdown, and are read in at startup.
New command line options for transaction fee changes:
  • -txconfirmtarget=n : create transactions that have enough fees (or priority)
so they are likely to begin confirmation within n blocks (default: 1). This setting
is over-ridden by the -paytxfee option.
  • -sendfreetransactions : Send transactions as zero-fee transactions if possible
(default: 0)
New RPC commands for fee estimation:
  • estimatefee nblocks : Returns approximate fee-per-1,000-bytes needed for
a transaction to begin confirmation within nblocks. Returns -1 if not enough
transactions have been observed to compute a good estimate.
  • estimatepriority nblocks : Returns approximate priority needed for
a zero-fee transaction to begin confirmation within nblocks. Returns -1 if not
enough free transactions have been observed to compute a good
estimate.
RPC access control changes
Subnet matching for the purpose of access control is now done
by matching the binary network address, instead of with string wildcard matching.
For the user this means that -rpcallowip takes a subnet specification, which can be
  • a single IP address (e.g. 1.2.3.4 or fe80::0012:3456:789a:bcde)
  • a network/CIDR (e.g. 1.2.3.0/24 or fe80::0000/64)
  • a network/netmask (e.g. 1.2.3.4/255.255.255.0 or fe80::0012:3456:789a:bcde/ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff)
An arbitrary number of -rpcallow arguments can be given. An incoming connection will be accepted if its origin address
matches one of them.
For example:
| 0.9.x and before | 0.10.x |
|--------------------------------------------|---------------------------------------|
| -rpcallowip=192.168.1.1 | -rpcallowip=192.168.1.1 (unchanged) |
| -rpcallowip=192.168.1.* | -rpcallowip=192.168.1.0/24 |
| -rpcallowip=192.168.* | -rpcallowip=192.168.0.0/16 |
| -rpcallowip=* (dangerous!) | -rpcallowip=::/0 (still dangerous!) |
Using wildcards will result in the rule being rejected with the following error in debug.log:
 Error: Invalid -rpcallowip subnet specification: *. Valid are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). 
REST interface
A new HTTP API is exposed when running with the -rest flag, which allows
unauthenticated access to public node data.
It is served on the same port as RPC, but does not need a password, and uses
plain HTTP instead of JSON-RPC.
Assuming a local RPC server running on port 8332, it is possible to request:
In every case, EXT can be bin (for raw binary data), hex (for hex-encoded
binary) or json.
For more details, see the doc/REST-interface.md document in the repository.
RPC Server "Warm-Up" Mode
The RPC server is started earlier now, before most of the expensive
intialisations like loading the block index. It is available now almost
immediately after starting the process. However, until all initialisations
are done, it always returns an immediate error with code -28 to all calls.
This new behaviour can be useful for clients to know that a server is already
started and will be available soon (for instance, so that they do not
have to start it themselves).
Improved signing security
For 0.10 the security of signing against unusual attacks has been
improved by making the signatures constant time and deterministic.
This change is a result of switching signing to use libsecp256k1
instead of OpenSSL. Libsecp256k1 is a cryptographic library
optimized for the curve Bitcoin uses which was created by Bitcoin
Core developer Pieter Wuille.
There exist attacks[1] against most ECC implementations where an
attacker on shared virtual machine hardware could extract a private
key if they could cause a target to sign using the same key hundreds
of times. While using shared hosts and reusing keys are inadvisable
for other reasons, it's a better practice to avoid the exposure.
OpenSSL has code in their source repository for derandomization
and reduction in timing leaks that we've eagerly wanted to use for a
long time, but this functionality has still not made its
way into a released version of OpenSSL. Libsecp256k1 achieves
significantly stronger protection: As far as we're aware this is
the only deployed implementation of constant time signing for
the curve Bitcoin uses and we have reason to believe that
libsecp256k1 is better tested and more thoroughly reviewed
than the implementation in OpenSSL.
[1] https://eprint.iacr.org/2014/161.pdf
Watch-only wallet support
The wallet can now track transactions to and from wallets for which you know
all addresses (or scripts), even without the private keys.
This can be used to track payments without needing the private keys online on a
possibly vulnerable system. In addition, it can help for (manual) construction
of multisig transactions where you are only one of the signers.
One new RPC, importaddress, is added which functions similarly to
importprivkey, but instead takes an address or script (in hexadecimal) as
argument. After using it, outputs credited to this address or script are
considered to be received, and transactions consuming these outputs will be
considered to be sent.
The following RPCs have optional support for watch-only:
getbalance, listreceivedbyaddress, listreceivedbyaccount,
listtransactions, listaccounts, listsinceblock, gettransaction. See the
RPC documentation for those methods for more information.
Compared to using getrawtransaction, this mechanism does not require
-txindex, scales better, integrates better with the wallet, and is compatible
with future block chain pruning functionality. It does mean that all relevant
addresses need to added to the wallet before the payment, though.
Consensus library
Starting from 0.10.0, the Bitcoin Core distribution includes a consensus library.
The purpose of this library is to make the verification functionality that is
critical to Bitcoin's consensus available to other applications, e.g. to language
bindings such as [python-bitcoinlib](https://pypi.python.org/pypi/python-bitcoinlib) or
alternative node implementations.
This library is called libbitcoinconsensus.so (or, .dll for Windows).
Its interface is defined in the C header [bitcoinconsensus.h](https://github.com/bitcoin/bitcoin/blob/0.10/src/script/bitcoinconsensus.h).
In its initial version the API includes two functions:
  • bitcoinconsensus_verify_script verifies a script. It returns whether the indicated input of the provided serialized transaction
correctly spends the passed scriptPubKey under additional constraints indicated by flags
  • bitcoinconsensus_version returns the API version, currently at an experimental 0
The functionality is planned to be extended to e.g. UTXO management in upcoming releases, but the interface
for existing methods should remain stable.
Standard script rules relaxed for P2SH addresses
The IsStandard() rules have been almost completely removed for P2SH
redemption scripts, allowing applications to make use of any valid
script type, such as "n-of-m OR y", hash-locked oracle addresses, etc.
While the Bitcoin protocol has always supported these types of script,
actually using them on mainnet has been previously inconvenient as
standard Bitcoin Core nodes wouldn't relay them to miners, nor would
most miners include them in blocks they mined.
bitcoin-tx
It has been observed that many of the RPC functions offered by bitcoind are
"pure functions", and operate independently of the bitcoind wallet. This
included many of the RPC "raw transaction" API functions, such as
createrawtransaction.
bitcoin-tx is a newly introduced command line utility designed to enable easy
manipulation of bitcoin transactions. A summary of its operation may be
obtained via "bitcoin-tx --help" Transactions may be created or signed in a
manner similar to the RPC raw tx API. Transactions may be updated, deleting
inputs or outputs, or appending new inputs and outputs. Custom scripts may be
easily composed using a simple text notation, borrowed from the bitcoin test
suite.
This tool may be used for experimenting with new transaction types, signing
multi-party transactions, and many other uses. Long term, the goal is to
deprecate and remove "pure function" RPC API calls, as those do not require a
server round-trip to execute.
Other utilities "bitcoin-key" and "bitcoin-script" have been proposed, making
key and script operations easily accessible via command line.
Mining and relay policy enhancements
Bitcoin Core's block templates are now for version 3 blocks only, and any mining
software relying on its getblocktemplate must be updated in parallel to use
libblkmaker either version 0.4.2 or any version from 0.5.1 onward.
If you are solo mining, this will affect you the moment you upgrade Bitcoin
Core, which must be done prior to BIP66 achieving its 951/1001 status.
If you are mining with the stratum mining protocol: this does not affect you.
If you are mining with the getblocktemplate protocol to a pool: this will affect
you at the pool operator's discretion, which must be no later than BIP66
achieving its 951/1001 status.
The prioritisetransaction RPC method has been added to enable miners to
manipulate the priority of transactions on an individual basis.
Bitcoin Core now supports BIP 22 long polling, so mining software can be
notified immediately of new templates rather than having to poll periodically.
Support for BIP 23 block proposals is now available in Bitcoin Core's
getblocktemplate method. This enables miners to check the basic validity of
their next block before expending work on it, reducing risks of accidental
hardforks or mining invalid blocks.
Two new options to control mining policy:
  • -datacarrier=0/1 : Relay and mine "data carrier" (OP_RETURN) transactions
if this is 1.
  • -datacarriersize=n : Maximum size, in bytes, we consider acceptable for
"data carrier" outputs.
The relay policy has changed to more properly implement the desired behavior of not
relaying free (or very low fee) transactions unless they have a priority above the
AllowFreeThreshold(), in which case they are relayed subject to the rate limiter.
BIP 66: strict DER encoding for signatures
Bitcoin Core 0.10 implements BIP 66, which introduces block version 3, and a new
consensus rule, which prohibits non-DER signatures. Such transactions have been
non-standard since Bitcoin v0.8.0 (released in February 2013), but were
technically still permitted inside blocks.
This change breaks the dependency on OpenSSL's signature parsing, and is
required if implementations would want to remove all of OpenSSL from the
consensus code.
The same miner-voting mechanism as in BIP 34 is used: when 751 out of a
sequence of 1001 blocks have version number 3 or higher, the new consensus
rule becomes active for those blocks. When 951 out of a sequence of 1001
blocks have version number 3 or higher, it becomes mandatory for all blocks.
Backward compatibility with current mining software is NOT provided, thus miners
should read the first paragraph of "Mining and relay policy enhancements" above.
0.10.0 Change log

Detailed release notes follow. This overview includes changes that affect external
behavior, not code moves, refactors or string updates.
RPC:
  • f923c07 Support IPv6 lookup in bitcoin-cli even when IPv6 only bound on localhost
  • b641c9c Fix addnode "onetry": Connect with OpenNetworkConnection
  • 171ca77 estimatefee / estimatepriority RPC methods
  • b750cf1 Remove cli functionality from bitcoind
  • f6984e8 Add "chain" to getmininginfo, improve help in getblockchaininfo
  • 99ddc6c Add nLocalServices info to RPC getinfo
  • cf0c47b Remove getwork() RPC call
  • 2a72d45 prioritisetransaction
  • e44fea5 Add an option -datacarrier to allow users to disable relaying/mining data carrier transactions
  • 2ec5a3d Prevent easy RPC memory exhaustion attack
  • d4640d7 Added argument to getbalance to include watchonly addresses and fixed errors in balance calculation
  • 83f3543 Added argument to listaccounts to include watchonly addresses
  • 952877e Showing 'involvesWatchonly' property for transactions returned by 'listtransactions' and 'listsinceblock'. It is only appended when the transaction involves a watchonly address
  • d7d5d23 Added argument to listtransactions and listsinceblock to include watchonly addresses
  • f87ba3d added includeWatchonly argument to 'gettransaction' because it affects balance calculation
  • 0fa2f88 added includedWatchonly argument to listreceivedbyaddress/...account
  • 6c37f7f getrawchangeaddress: fail when keypool exhausted and wallet locked
  • ff6a7af getblocktemplate: longpolling support
  • c4a321f Add peerid to getpeerinfo to allow correlation with the logs
  • 1b4568c Add vout to ListTransactions output
  • b33bd7a Implement "getchaintips" RPC command to monitor blockchain forks
  • 733177e Remove size limit in RPC client, keep it in server
  • 6b5b7cb Categorize rpc help overview
  • 6f2c26a Closely track mempool byte total. Add "getmempoolinfo" RPC
  • aa82795 Add detailed network info to getnetworkinfo RPC
  • 01094bd Don't reveal whether password is <20 or >20 characters in RPC
  • 57153d4 rpc: Compute number of confirmations of a block from block height
  • ff36cbe getnetworkinfo: export local node's client sub-version string
  • d14d7de SanitizeString: allow '(' and ')'
  • 31d6390 Fixed setaccount accepting foreign address
  • b5ec5fe update getnetworkinfo help with subversion
  • ad6e601 RPC additions after headers-first
  • 33dfbf5 rpc: Fix leveldb iterator leak, and flush before gettxoutsetinfo
  • 2aa6329 Enable customising node policy for datacarrier data size with a -datacarriersize option
  • f877aaa submitblock: Use a temporary CValidationState to determine accurately the outcome of ProcessBlock
  • e69a587 submitblock: Support for returning specific rejection reasons
  • af82884 Add "warmup mode" for RPC server
  • e2655e0 Add unauthenticated HTTP REST interface to public blockchain data
  • 683dc40 Disable SSLv3 (in favor of TLS) for the RPC client and server
  • 44b4c0d signrawtransaction: validate private key
  • 9765a50 Implement BIP 23 Block Proposal
  • f9de17e Add warning comment to getinfo
Command-line options:
  • ee21912 Use netmasks instead of wildcards for IP address matching
  • deb3572 Add -rpcbind option to allow binding RPC port on a specific interface
  • 96b733e Add -version option to get just the version
  • 1569353 Add -stopafterblockimport option
  • 77cbd46 Let -zapwallettxes recover transaction meta data
  • 1c750db remove -tor compatibility code (only allow -onion)
  • 4aaa017 rework help messages for fee-related options
  • 4278b1d Clarify error message when invalid -rpcallowip
  • 6b407e4 -datadir is now allowed in config files
  • bdd5b58 Add option -sysperms to disable 077 umask (create new files with system default umask)
  • cbe39a3 Add "bitcoin-tx" command line utility and supporting modules
  • dbca89b Trigger -alertnotify if network is upgrading without you
  • ad96e7c Make -reindex cope with out-of-order blocks
  • 16d5194 Skip reindexed blocks individually
  • ec01243 --tracerpc option for regression tests
  • f654f00 Change -genproclimit default to 1
  • 3c77714 Make -proxy set all network types, avoiding a connect leak
  • 57be955 Remove -printblock, -printblocktree, and -printblockindex
  • ad3d208 remove -maxorphanblocks config parameter since it is no longer functional
Block and transaction handling:
  • 7a0e84d ProcessGetData(): abort if a block file is missing from disk
  • 8c93bf4 LoadBlockIndexDB(): Require block db reindex if any blk*.dat files are missing
  • 77339e5 Get rid of the static chainMostWork (optimization)
  • 4e0eed8 Allow ActivateBestChain to release its lock on cs_main
  • 18e7216 Push cs_mains down in ProcessBlock
  • fa126ef Avoid undefined behavior using CFlatData in CScript serialization
  • 7f3b4e9 Relax IsStandard rules for pay-to-script-hash transactions
  • c9a0918 Add a skiplist to the CBlockIndex structure
  • bc42503 Use unordered_map for CCoinsViewCache with salted hash (optimization)
  • d4d3fbd Do not flush the cache after every block outside of IBD (optimization)
  • ad08d0b Bugfix: make CCoinsViewMemPool support pruned entries in underlying cache
  • 5734d4d Only remove actualy failed blocks from setBlockIndexValid
  • d70bc52 Rework block processing benchmark code
  • 714a3e6 Only keep setBlockIndexValid entries that are possible improvements
  • ea100c7 Reduce maximum coinscache size during verification (reduce memory usage)
  • 4fad8e6 Reject transactions with excessive numbers of sigops
  • b0875eb Allow BatchWrite to destroy its input, reducing copying (optimization)
  • 92bb6f2 Bypass reloading blocks from disk (optimization)
  • 2e28031 Perform CVerifyDB on pcoinsdbview instead of pcoinsTip (reduce memory usage)
  • ab15b2e Avoid copying undo data (optimization)
  • 341735e Headers-first synchronization
  • afc32c5 Fix rebuild-chainstate feature and improve its performance
  • e11b2ce Fix large reorgs
  • ed6d1a2 Keep information about all block files in memory
  • a48f2d6 Abstract context-dependent block checking from acceptance
  • 7e615f5 Fixed mempool sync after sending a transaction
  • 51ce901 Improve chainstate/blockindex disk writing policy
  • a206950 Introduce separate flushing modes
  • 9ec75c5 Add a locking mechanism to IsInitialBlockDownload to ensure it never goes from false to true
  • 868d041 Remove coinbase-dependant transactions during reorg
  • 723d12c Remove txn which are invalidated by coinbase maturity during reorg
  • 0cb8763 Check against MANDATORY flags prior to accepting to mempool
  • 8446262 Reject headers that build on an invalid parent
  • 008138c Bugfix: only track UTXO modification after lookup
P2P protocol and network code:
  • f80cffa Do not trigger a DoS ban if SCRIPT_VERIFY_NULLDUMMY fails
  • c30329a Add testnet DNS seed of Alex Kotenko
  • 45a4baf Add testnet DNS seed of Andreas Schildbach
  • f1920e8 Ping automatically every 2 minutes (unconditionally)
  • 806fd19 Allocate receive buffers in on the fly
  • 6ecf3ed Display unknown commands received
  • aa81564 Track peers' available blocks
  • caf6150 Use async name resolving to improve net thread responsiveness
  • 9f4da19 Use pong receive time rather than processing time
  • 0127a9b remove SOCKS4 support from core and GUI, use SOCKS5
  • 40f5cb8 Send rejects and apply DoS scoring for errors in direct block validation
  • dc942e6 Introduce whitelisted peers
  • c994d2e prevent SOCKET leak in BindListenPort()
  • a60120e Add built-in seeds for .onion
  • 60dc8e4 Allow -onlynet=onion to be used
  • 3a56de7 addrman: Do not propagate obviously poor addresses onto the network
  • 6050ab6 netbase: Make SOCKS5 negotiation interruptible
  • 604ee2a Remove tx from AlreadyAskedFor list once we receive it, not when we process it
  • efad808 Avoid reject message feedback loops
  • 71697f9 Separate protocol versioning from clientversion
  • 20a5f61 Don't relay alerts to peers before version negotiation
  • b4ee0bd Introduce preferred download peers
  • 845c86d Do not use third party services for IP detection
  • 12a49ca Limit the number of new addressses to accumulate
  • 35e408f Regard connection failures as attempt for addrman
  • a3a7317 Introduce 10 minute block download timeout
  • 3022e7d Require sufficent priority for relay of free transactions
  • 58fda4d Update seed IPs, based on bitcoin.sipa.be crawler data
  • 18021d0 Remove bitnodes.io from dnsseeds.
Validation:
  • 6fd7ef2 Also switch the (unused) verification code to low-s instead of even-s
  • 584a358 Do merkle root and txid duplicates check simultaneously
  • 217a5c9 When transaction outputs exceed inputs, show the offending amounts so as to aid debugging
  • f74fc9b Print input index when signature validation fails, to aid debugging
  • 6fd59ee script.h: set_vch() should shift a >32 bit value
  • d752ba8 Add SCRIPT_VERIFY_SIGPUSHONLY (BIP62 rule 2) (test only)
  • 698c6ab Add SCRIPT_VERIFY_MINIMALDATA (BIP62 rules 3 and 4) (test only)
  • ab9edbd script: create sane error return codes for script validation and remove logging
  • 219a147 script: check ScriptError values in script tests
  • 0391423 Discourage NOPs reserved for soft-fork upgrades
  • 98b135f Make STRICTENC invalid pubkeys fail the script rather than the opcode
  • 307f7d4 Report script evaluation failures in log and reject messages
  • ace39db consensus: guard against openssl's new strict DER checks
  • 12b7c44 Improve robustness of DER recoding code
  • 76ce5c8 fail immediately on an empty signature
Build system:
  • f25e3ad Fix build in OS X 10.9
  • 65e8ba4 build: Switch to non-recursive make
  • 460b32d build: fix broken boost chrono check on some platforms
  • 9ce0774 build: Fix windows configure when using --with-qt-libdir
  • ea96475 build: Add mention of --disable-wallet to bdb48 error messages
  • 1dec09b depends: add shared dependency builder
  • c101c76 build: Add --with-utils (bitcoin-cli and bitcoin-tx, default=yes). Help string consistency tweaks. Target sanity check fix
  • e432a5f build: add option for reducing exports (v2)
  • 6134b43 Fixing condition 'sabotaging' MSVC build
  • af0bd5e osx: fix signing to make Gatekeeper happy (again)
  • a7d1f03 build: fix dynamic boost check when --with-boost= is used
  • d5fd094 build: fix qt test build when libprotobuf is in a non-standard path
  • 2cf5f16 Add libbitcoinconsensus library
  • 914868a build: add a deterministic dmg signer
  • 2d375fe depends: bump openssl to 1.0.1k
  • b7a4ecc Build: Only check for boost when building code that requires it
Wallet:
  • b33d1f5 Use fee/priority estimates in wallet CreateTransaction
  • 4b7b1bb Sanity checks for estimates
  • c898846 Add support for watch-only addresses
  • d5087d1 Use script matching rather than destination matching for watch-only
  • d88af56 Fee fixes
  • a35b55b Dont run full check every time we decrypt wallet
  • 3a7c348 Fix make_change to not create half-satoshis
  • f606bb9 fix a possible memory leak in CWalletDB::Recover
  • 870da77 fix possible memory leaks in CWallet::EncryptWallet
  • ccca27a Watch-only fixes
  • 9b1627d [Wallet] Reduce minTxFee for transaction creation to 1000 satoshis
  • a53fd41 Deterministic signing
  • 15ad0b5 Apply AreSane() checks to the fees from the network
  • 11855c1 Enforce minRelayTxFee on wallet created tx and add a maxtxfee option
GUI:
  • c21c74b osx: Fix missing dock menu with qt5
  • b90711c Fix Transaction details shows wrong To:
  • 516053c Make links in 'About Bitcoin Core' clickable
  • bdc83e8 Ensure payment request network matches client network
  • 65f78a1 Add GUI view of peer information
  • 06a91d9 VerifyDB progress reporting
  • fe6bff2 Add BerkeleyDB version info to RPCConsole
  • b917555 PeerTableModel: Fix potential deadlock. #4296
  • dff0e3b Improve rpc console history behavior
  • 95a9383 Remove CENT-fee-rule from coin control completely
  • 56b07d2 Allow setting listen via GUI
  • d95ba75 Log messages with type>QtDebugMsg as non-debug
  • 8969828 New status bar Unit Display Control and related changes
  • 674c070 seed OpenSSL PNRG with Windows event data
  • 509f926 Payment request parsing on startup now only changes network if a valid network name is specified
  • acd432b Prevent balloon-spam after rescan
  • 7007402 Implement SI-style (thin space) thoudands separator
  • 91cce17 Use fixed-point arithmetic in amount spinbox
  • bdba2dd Remove an obscure option no-one cares about
  • bd0aa10 Replace the temporary file hack currently used to change Bitcoin-Qt's dock icon (OS X) with a buffer-based solution
  • 94e1b9e Re-work overviewpage UI
  • 8bfdc9a Better looking trayicon
  • b197bf3 disable tray interactions when client model set to 0
  • 1c5f0af Add column Watch-only to transactions list
  • 21f139b Fix tablet crash. closes #4854
  • e84843c Broken addresses on command line no longer trigger testnet
  • a49f11d Change splash screen to normal window
  • 1f9be98 Disable App Nap on OSX 10.9+
  • 27c3e91 Add proxy to options overridden if necessary
  • 4bd1185 Allow "emergency" shutdown during startup
  • d52f072 Don't show wallet options in the preferences menu when running with -disablewallet
  • 6093aa1 Qt: QProgressBar CPU-Issue workaround
  • 0ed9675 [Wallet] Add global boolean whether to send free transactions (default=true)
  • ed3e5e4 [Wallet] Add global boolean whether to pay at least the custom fee (default=true)
  • e7876b2 [Wallet] Prevent user from paying a non-sense fee
  • c1c9d5b Add Smartfee to GUI
  • e0a25c5 Make askpassphrase dialog behave more sanely
  • 94b362d On close of splashscreen interrupt verifyDB
  • b790d13 English translation update
  • 8543b0d Correct tooltip on address book page
Tests:
  • b41e594 Fix script test handling of empty scripts
  • d3a33fc Test CHECKMULTISIG with m == 0 and n == 0
  • 29c1749 Let tx (in)valid tests use any SCRIPT_VERIFY flag
  • 6380180 Add rejection of non-null CHECKMULTISIG dummy values
  • 21bf3d2 Add tests for BoostAsioToCNetAddr
  • b5ad5e7 Add Python test for -rpcbind and -rpcallowip
  • 9ec0306 Add CODESEPARATOFindAndDelete() tests
  • 75ebced Added many rpc wallet tests
  • 0193fb8 Allow multiple regression tests to run at once
  • 92a6220 Hook up sanity checks
  • 3820e01 Extend and move all crypto tests to crypto_tests.cpp
  • 3f9a019 added list/get received by address/ account tests
  • a90689f Remove timing-based signature cache unit test
  • 236982c Add skiplist unit tests
  • f4b00be Add CChain::GetLocator() unit test
  • b45a6e8 Add test for getblocktemplate longpolling
  • cdf305e Set -discover=0 in regtest framework
  • ed02282 additional test for OP_SIZE in script_valid.json
  • 0072d98 script tests: BOOLAND, BOOLOR decode to integer
  • 833ff16 script tests: values that overflow to 0 are true
  • 4cac5db script tests: value with trailing 0x00 is true
  • 89101c6 script test: test case for 5-byte bools
  • d2d9dc0 script tests: add tests for CHECKMULTISIG limits
  • d789386 Add "it works" test for bitcoin-tx
  • df4d61e Add bitcoin-tx tests
  • aa41ac2 Test IsPushOnly() with invalid push
  • 6022b5d Make script_{valid,invalid}.json validation flags configurable
  • 8138cbe Add automatic script test generation, and actual checksig tests
  • ed27e53 Add coins_tests with a large randomized CCoinViewCache test
  • 9df9cf5 Make SCRIPT_VERIFY_STRICTENC compatible with BIP62
  • dcb9846 Extend getchaintips RPC test
  • 554147a Ensure MINIMALDATA invalid tests can only fail one way
  • dfeec18 Test every numeric-accepting opcode for correct handling of the numeric minimal encoding rule
  • 2b62e17 Clearly separate PUSHDATA and numeric argument MINIMALDATA tests
  • 16d78bd Add valid invert of invalid every numeric opcode tests
  • f635269 tests: enable alertnotify test for Windows
  • 7a41614 tests: allow rpc-tests to get filenames for bitcoind and bitcoin-cli from the environment
  • 5122ea7 tests: fix forknotify.py on windows
  • fa7f8cd tests: remove old pull-tester scripts
  • 7667850 tests: replace the old (unused since Travis) tests with new rpc test scripts
  • f4e0aef Do signature-s negation inside the tests
  • 1837987 Optimize -regtest setgenerate block generation
  • 2db4c8a Fix node ranges in the test framework
  • a8b2ce5 regression test only setmocktime RPC call
  • daf03e7 RPC tests: create initial chain with specific timestamps
  • 8656dbb Port/fix txnmall.sh regression test
  • ca81587 Test the exact order of CHECKMULTISIG sig/pubkey evaluation
  • 7357893 Prioritize and display -testsafemode status in UI
  • f321d6b Add key generation/verification to ECC sanity check
  • 132ea9b miner_tests: Disable checkpoints so they don't fail the subsidy-change test
  • bc6cb41 QA RPC tests: Add tests block block proposals
  • f67a9ce Use deterministically generated script tests
  • 11d7a7d [RPC] add rpc-test for http keep-alive (persistent connections)
  • 34318d7 RPC-test based on invalidateblock for mempool coinbase spends
  • 76ec867 Use actually valid transactions for script tests
  • c8589bf Add actual signature tests
  • e2677d7 Fix smartfees test for change to relay policy
  • 263b65e tests: run sanity checks in tests too
Miscellaneous:
  • 122549f Fix incorrect checkpoint data for testnet3
  • 5bd02cf Log used config file to debug.log on startup
  • 68ba85f Updated Debian example bitcoin.conf with config from wiki + removed some cruft and updated comments
  • e5ee8f0 Remove -beta suffix
  • 38405ac Add comment regarding experimental-use service bits
  • be873f6 Issue warning if collecting RandSeed data failed
  • 8ae973c Allocate more space if necessary in RandSeedAddPerfMon
  • 675bcd5 Correct comment for 15-of-15 p2sh script size
  • fda3fed libsecp256k1 integration
  • 2e36866 Show nodeid instead of addresses in log (for anonymity) unless otherwise requested
  • cd01a5e Enable paranoid corruption checks in LevelDB >= 1.16
  • 9365937 Add comment about never updating nTimeOffset past 199 samples
  • 403c1bf contrib: remove getwork-based pyminer (as getwork API call has been removed)
  • 0c3e101 contrib: Added systemd .service file in order to help distributions integrate bitcoind
  • 0a0878d doc: Add new DNSseed policy
  • 2887bff Update coding style and add .clang-format
  • 5cbda4f Changed LevelDB cursors to use scoped pointers to ensure destruction when going out of scope
  • b4a72a7 contrib/linearize: split output files based on new-timestamp-year or max-file-size
  • e982b57 Use explicit fflush() instead of setvbuf()
  • 234bfbf contrib: Add init scripts and docs for Upstart and OpenRC
  • 01c2807 Add warning about the merkle-tree algorithm duplicate txid flaw
  • d6712db Also create pid file in non-daemon mode
  • 772ab0e contrib: use batched JSON-RPC in linarize-hashes (optimization)
  • 7ab4358 Update bash-completion for v0.10
  • 6e6a36c contrib: show pull # in prompt for github-merge script
  • 5b9f842 Upgrade leveldb to 1.18, make chainstate databases compatible between ARM and x86 (issue #2293)
  • 4e7c219 Catch UTXO set read errors and shutdown
  • 867c600 Catch LevelDB errors during flush
  • 06ca065 Fix CScriptID(const CScript& in) in empty script case
Credits

Thanks to everyone who contributed to this release:
  • 21E14
  • Adam Weiss
  • Aitor Pazos
  • Alexander Jeng
  • Alex Morcos
  • Alon Muroch
  • Andreas Schildbach
  • Andrew Poelstra
  • Andy Alness
  • Ashley Holman
  • Benedict Chan
  • Ben Holden-Crowther
  • Bryan Bishop
  • BtcDrak
  • Christian von Roques
  • Clinton Christian
  • Cory Fields
  • Cozz Lovan
  • daniel
  • Daniel Kraft
  • David Hill
  • Derek701
  • dexX7
  • dllud
  • Dominyk Tiller
  • Doug
  • elichai
  • elkingtowa
  • ENikS
  • Eric Shaw
  • Federico Bond
  • Francis GASCHET
  • Gavin Andresen
  • Giuseppe Mazzotta
  • Glenn Willen
  • Gregory Maxwell
  • gubatron
  • HarryWu
  • himynameismartin
  • Huang Le
  • Ian Carroll
  • imharrywu
  • Jameson Lopp
  • Janusz Lenar
  • JaSK
  • Jeff Garzik
  • JL2035
  • Johnathan Corgan
  • Jonas Schnelli
  • jtimon
  • Julian Haight
  • Kamil Domanski
  • kazcw
  • kevin
  • kiwigb
  • Kosta Zertsekel
  • LongShao007
  • Luke Dashjr
  • Mark Friedenbach
  • Mathy Vanvoorden
  • Matt Corallo
  • Matthew Bogosian
  • Micha
  • Michael Ford
  • Mike Hearn
  • mrbandrews
  • mruddy
  • ntrgn
  • Otto Allmendinger
  • paveljanik
  • Pavel Vasin
  • Peter Todd
  • phantomcircuit
  • Philip Kaufmann
  • Pieter Wuille
  • pryds
  • randy-waterhouse
  • R E Broadley
  • Rose Toomey
  • Ross Nicoll
  • Roy Badami
  • Ruben Dario Ponticelli
  • Rune K. Svendsen
  • Ryan X. Charles
  • Saivann
  • sandakersmann
  • SergioDemianLerner
  • shshshsh
  • sinetek
  • Stuart Cardall
  • Suhas Daftuar
  • Tawanda Kembo
  • Teran McKinney
  • tm314159
  • Tom Harding
  • Trevin Hofmann
  • Whit J
  • Wladimir J. van der Laan
  • Yoichi Hirai
  • Zak Wilcox
As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/).
Also lots of thanks to the bitcoin.org website team David A. Harding and Saivann Carignan.
Wladimir
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-February/007480.html
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

Lasizwe Dambuza - YouTube Correlation Statistics Tutorial sobre carteira de bitcoins (Bitcoin-QT). How to Use Bitcoin With Tor How to run Bitcoin Core 0.9.2.1 on external Hard Drive

Verifique las firmas de las versiones Download torrent Source code Mostrar historial de versiones Bitcoin Core Release Signing Keys v0.8.6 - 0.9.2.1 v0.9.3 - 0.10.2 v0.11.0+ O escoja su sistema operativo Bitcoin-Qt is a full Bitcoin client and builds the backbone of the network. It offers the highest levels of security, privacy, and stability. However, it has fewer features and it takes a lot of space and memory. Bitcoin-Qt can used as a desktop client for regular payments or as a server utility for merchants and other payment services. Features: Bitcoin-Qt version 0.8.3 is now available from: gettxoutsetinfo returns statistics about the unspent transaction output database. Significant changes to the networking code, reducing latency and memory consumption. Avoid initial block download stalling. Remove IRC seeding support. Performance tweaks. Added testnet DNS seeds. Port details: bitcoin Virtual Peer-to-Peer Currency Client (QT) 0.19.1_2 net-p2p =9 0.19.0.1_2 Version of this port present on the latest quarterly branch. Maintainer: [email protected] Port Added: 2011-05-20 22:50:57 Last Update: 2020-06-03 19:32:06 SVN Revision: 537830 People watching this port, also watch: node, tmux, coreutils, smartmontools, rtorrent Also Listed In: finance Fixed SSL issue with compiling QT clients. Added an estimate for time range for staking rewards in QT wallet. Added translations for 50 languages. Russian, Portuguese, and German have been reviewed and updated. Please suggest any translation changes. Staking nodes: (nodes do not create wallets or stake by default)

[index] [11623] [19579] [44305] [37331] [45814] [35317] [2417] [10617] [7976] [7645]

Lasizwe Dambuza - YouTube

For Bitcoin Core Client updates: https://bitcoincore.org @bitcoincoreorg in Twitter Linux terminal commands: sha256sum, tar, cp, sudo, rm, exit, less * All other commands have been covered in ... How To Pay Off Your Mortgage Fast Using Velocity Banking How To Pay Off Your Mortgage In 5-7 Years - Duration: 41:34. Think Wealthy with Mike Adams Recommended for you bitcoin private key database download bitcoin private key database with balance 2018 ... export private key bitcoin-qt bitcoin key resistance bitcoin keyring ... bitcoin key statistics bitcoin key ... Hey Babes! Welcome to my Youtube Channel. I have made videos I think you might like.. If you don't know me. My name it's Lasizwe ( Babes Wamaleyvels). Many p... BITCOIN SETUP FOR HUUUGE BULL RALLY?!! 💰Crypto Analysis TA Today & BTC Cryptocurrency Price News Now - Duration: 13:38. Crypto Kirby Trading 13,976 views 13:38