Running a full node using Bitcoin-daemon. Instructions for ...

Issues with bitcoin-qt

I know this is frequently posted, but I'm incensed at how absurdly slow reindexing becomes. There's got to be something wrong with the sync mechanism.
I was 100% synced a week ago on my MacBook Pro. Latest version of the client (v0.17.0.1). I rsync'd the whole bitcoin dir (blocks, chainstate, index, etc) to another disk, ran a node on another machine using that copy for a couple of hours, then I stopped the node and rsync'd back to the Mac.
Bitcoin-qt did not like the updated blockchain. The other machine didn't like its blockchain either. Oh well, I thought, maybe it didn't shutdown properly and borked the last block. I'll let it reindex, in a few minutes it'll be grand.
But no. Bitcoin-qt decided that it was time to start over from scratch, ignoring the flawless 99.999% of data on disk. Yay.
That was 10 days ago. At one point several days ago it was about 3 hours from finishing, with a progress of around 19% per hour. A day later progress was at 0.25%. This can't be right, I thought, maybe there's a bug, a memory leak or something. I'll shut it down and restart it. Of course it's going to restart from where it left, right? Right?
No. It started from 0% again.
Several days later, it's at 0.14% and predicting it'll finish sometime next week. CPU is 96% idle, RAM is at 25%, bandwidth is 120 Mb/s and the disk is used by bitcoin-qt and nothing else. It's the only thing running on this Mac and has been for the past two weeks. NOTHING is different between 19% and 0.14% in terms of bandwidth, CPU, RAM, or disk I/O. This very machine, under the exact same conditions, was able to process 19% of the blockchain in one hour.
In the meantime, I can't move my BTC because my wallet, which has all the blocks including the ones containing the transactions with my BTC in them, doesn't believe the blocks are there.
Bitcoin-qt is broken in more ways than one. First, something is causing this absurd variation in performance. Second, it's not saving state, which is particularly painful when it takes ages to get to the end to the blockchain. Is state only kept in RAM? I've seen other threads suggesting a change in the config (dbcache seems to be the main one), but I can't just change the setting without restarting, and restarting is not an option because I'll lose everything again.
Sorry, this is extremely frustrating. I'm thinking of extracting the private key and abandoning the idea of running my own wallet. It's unusable.
submitted by jungle to Bitcoin [link] [comments]

Interested in contributing to the BTC network? Here is the steps to get a full node up and running in Linux.

These instructions will work both on a VPS cloud server or a personal computer. You may find cheap VPS somewhere online for rent.
What Is A Full Node?
A full node is a program that fully validates transactions and blocks. Almost all full nodes also help the network by accepting transactions and blocks from other full nodes, validating those transactions and blocks, and then relaying them to further full nodes.
Most full nodes also serve lightweight clients by allowing them to transmit their transactions to the network and by notifying them when a transaction affects their wallet. If not enough nodes perform this function, clients won’t be able to connect through the peer-to-peer network—they’ll have to use centralized services instead.
Many people and organizations volunteer to run full nodes using spare computing and bandwidth resources—but more volunteers are needed to allow Bitcoin to continue to grow. This document describes how you can help and what helping will cost you.
Costs And Warnings
Running a Bitcoin full node comes with certain costs and can expose you to certain risks. This section will explain those costs and risks so you can decide whether you’re able to help the network.
Special Cases
Miners, businesses, and privacy-conscious users rely on particular behavior from the full nodes they use, so they will often run their own full nodes and take special safety precautions. This document does not cover those precautions—it only describes running a full node to help support the Bitcoin network in general.
Please consult an expert if you need help setting up your full node correctly to handle high-value and privacy-sensitive tasks.
Secure Your Wallet
It’s possible and safe to run a full node to support the network and use its wallet to store your bitcoins, but you must take the same precautions you would when using any Bitcoin wallet. Please see the securing your wallet page for more information.
Minimum Requirements
Bitcoin Core full nodes have certain requirements. If you try running a node on weak hardware, it may work—but you’ll likely spend more time dealing with issues. If you can meet the following requirements, you’ll have an easy-to-use node.
Note: many operating systems today (Windows, Mac, and Linux) enter a low-power mode after the screensaver activates, slowing or halting network traffic. This is often the default setting on laptops and on all Mac OS X laptops and desktops. Check your screensaver settings and disable automatic “sleep” or “suspend” options to ensure you support the network whenever your computer is running.
Possible Problems
Legal: Bitcoin use is prohibited or restricted in some areas.
Bandwidth limits: Some Internet plans will charge an additional amount for any excess upload bandwidth used that isn’t included in the plan. Worse, some providers may terminate your connection without warning because of overuse. We advise that you check whether your Internet connection is subjected to such limitations and monitor your bandwidth use so that you can stop Bitcoin Core before you reach your upload limit.
Anti-virus: Several people have placed parts of known computer viruses in the Bitcoin block chain. This block chain data can’t infect your computer, but some anti-virus programs quarantine the data anyway, making it more difficult to run a full node. This problem mostly affects computers running Windows.
Attack target: People who want to disrupt the Bitcoin network may attack full nodes in ways that will affect other things you do with your computer, such as an attack that limits your available download bandwidth or an attack that prevents you from using your full node’s wallet for sending transactions.
Linux Instructions
The following instructions describe installing Bitcoin Core on Linux systems.
Ubuntu 14.10 Instructions for Bitcoin Core 0.10.0.
If you use Ubuntu Desktop, click the Ubuntu swirl icon to start the Dash and type “term” into the input box. Choose any one of the terminals listed:
Alternatively, access a console or terminal emulator using another method, such as SSH on Ubuntu Server or a terminal launcher in an alternative desktop environment.
Type the following line to add the Bitcoin Personal Package Archive (PPA) to your system:
sudo apt-add-repository ppa:bitcoin/bitcoin
You will be prompted for your user password. Provide it to continue. Afterwards, the following text will be displayed:
Stable Channel of bitcoin-qt and bitcoind for Ubuntu, and their dependencies
More info: https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin
Press [ENTER] to continue or ctrl-c to cancel adding it
Press enter to continue. The following text (with some variations) will be displayed and you will be returned to the command line prompt:
gpg: keyring /tmp/tmpixuqu73x/secring.gpg' created gpg: keyring/tmp/tmpixuqu73x/pubring.gpg' created gpg: requesting key 8842CE5E from hkp server > > > >keyserver.ubuntu.com gpg: /tmp/tmpixuqu73x/trustdb.gpg: trustdb created gpg: key 8842CE5E: public key "Launchpad PPA for Bitcoin" imported gpg: no ultimately trusted keys found gpg: Total number processed: 1 pg: imported: 1 (RSA: 1) OK
Type the following line to get the most recent list of packages:
sudo apt-get update
A large number of lines will be displayed as different update files are downloaded. This step may take several minutes on a slow Internet connection.
To continue, choose one of the following options
sudo apt-get install bitcoin-qt
sudo apt-get install bitcoind
sudo apt-get install bitcoin-qt bitcoind
After choosing what packages to install, you will be asked whether you want to proceed. Press enter to continue.
If you’re logged in as an administrative user with sudo access, you may log out. The steps in this section should be performed as the user you want to run Bitcoin Core. (If you’re an expert administrator, you can make this a locked account used only by Bitcoin Core.)
Before using the Bitcoin Core daemon, bitcoind, you need to create its configuration file with a user name and password. First create the .bitcoin directory, create (touch) the file, and set the file’s permissions so that only your user account can read it. From the terminal, type:
mkdir ~/.bitcoin touch ~/.bitcoin/bitcoin.conf chmod 600 ~/.bitcoin/bitcoin.conf
Then you can run the command bitcoind. It will print output similar to this:
bitcoind Error: To use the "-server" option, you must set a rpcpassword in the configuration file: /home/bitcoinorg/.bitcoin/bitcoin.conf It is recommended you use the following random password: rpcuser=bitcoinrpc rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions. It is also recommended to set alertnotify so you are notified of problems; for example: alertnotify=echo %s | mail -s "Bitcoin Alert" [email protected] The “rpcpassword” displayed will be unique for your system. You can copy the rpcuser and rpcpassword lines into your configuration file using the following commands. Note that in most Ubuntu terminals, you need to press Ctrl-Shift-C to copy and Ctrl-Shift-V to paste because Ctrl-C and Ctrl-V have different meanings in a Unix-style terminal.
echo rpcuser=bitcoinrpc >> ~/.bitcoin/bitcoin.conf echo rpcpassword=XXXXXX >> ~/.bitcoin/bitcoin.conf (Warning: Don’t use XXXXXX as your RPC password. Copy the rpcpassword displayed by bitcoind for your system.)
Now you can start Bitcoin Core daemon for real. Type the following command:
bitcoind -daemon
It will print a message that Bitcoin Core is starting. To interact with Bitcoin Core daemon, you will use the command bitcoin-cli (Bitcoin command line interface). Note: it may take up to several minutes for Bitcoin Core to start, during which it will display the following message whenever you use bitcoin-cli:
error: {"code":-28,"message":"Verifying blocks..."}
After it starts, you may find the following commands useful for basic interaction with your node:
to safely stop your node, run the following command:
bitcoin-cli stop
A complete list of commands is available in the Bitcoin.org developer reference.
When Bitcoin Core daemon first starts, it will begin to download the block chain. This step will take at least several hours, and it may take a day or more on a slow Internet connection or with a slow computer. During the download, Bitcoin Core will use a significant part of your connection bandwidth. You can stop Bitcoin Core at any time using the stop command; it will resume from the point where it stopped the next time you start it.
Optional: Start Your Node At Boot
Starting your node automatically each time your computer boots makes it easy for you to contribute to the network. The easiest way to do this is to start Bitcoin Core daemon from your crontab. To edit your crontab, run the following command:
crontab -e
@reboot bitcoind -daemon Save the file and exit; the updated crontab file will be installed for you. Now Bitcoin Core daemon will be automatically started each time your reboot your computer.
If you’re an Ubuntu expert and want to use an init script instead, see this Upstart script.
You have now completed installing Bitcoin Core. If you have any questions, please ask in one of Bitcoin’s many communities, such as Bitcoin StackExchange, BitcoinTalk technical support, or the #bitcoin IRC chatroom on Freenode.
To support the Bitcoin network, you also need to allow incoming connections. Please read the Network Configuration section for details.
Network Configuration
If you want to support the Bitcoin network, you must allow inbound connections.
When Bitcoin Core starts, it establishes 8 outbound connections to other full nodes so it can download the latest blocks and transactions. If you just want to use your full node as a wallet, you don’t need more than these 8 connections—but if you want to support lightweight clients and other full nodes on the network, you must allow inbound connections.
Servers connected directly to the Internet usually don’t require any special configuration. You can use the testing instructions below to confirm your server-based node accepts inbound connections.
Home connections are usually filtered by a router or modem. Bitcoin Core will request your router automatically configure itself to allow inbound connections to Bitcoin’s port, port 8333. Unfortunately many routers don’t allow automatic configuration, so you must manually configure your router. You may also need to configure your firewall to allow inbound connections to port 8333. Please see the following subsections for details.
Testing Connections
The BitNodes project provides an online tool to let you test whether your node accepts inbound connections. To use it, start Bitcoin Core (either the GUI or the daemon), wait 10 minutes, and then visit the GetAddr page (https://getaddr.bitnodes.io/). The tool will attempt to guess your IP address—if the address is wrong (or blank), you will need to enter your address manually.
For more instruction and reviews based off BTC please follow my subreddit /BTC_Reviews
all material from this post was found here --> https://bitcoin.org/en/full-node
submitted by Mattjhagen to Bitcoin [link] [comments]

Help appreciated: bitcoin-qt runs fine on mac, copy dir to linux, bitcoind doesn't like it.

TL;DR: It's ok to ignore this post, you're not my personal tech support. :)
I've been running a full bitcoin-qt core node on and off on my mac without issues for years (well, until I hosed my blockchain, had to reindex and came here to vent about how slow it was - fixed thanks to yogibreakdance).
I'm trying to move it to a Raspberry Pi so I can have it running full time inside a closet and have the blockchain always up to date, available to sync back to the mac to move my BTC when I need to.
After copying the whole bitcoin dir to the RPI, bitcoind immediately throws "Error initializing block database", removes most of the chainstate contents and stops.
I tried changing file permissions, deleting everything except the blocks and chainstate dirs, using a config file appropriate for the RPI... No change.
If I run bitcoind -reindex-chainstate, it seems to work. At least it starts reindexing, but I don't have the patience to wait till it finishes, it might take months.
Some possibly relevant info: On the mac side the blockchain is stored on a 4 TB Mac OS Extended external disk, on the RPI side it's stored on a 1TB Ext4 external disk, published through samba and mounted on the mac. I use "rsync -rt --size-only" to move the files. Both bitcoin clients are v0.17.0.1. Empty wallet on both sides. On the RPI side, dirs are 777 and files 600 (I tried 777 too).
A couple of weeks ago I had it running, the only difference was that the RPI drive was formatted as NTFS. I switched to Ext4 because NTFS was slow and didn't play nice with the mac.
My google-fu got me nowhere. Hoping someone here might point me in the right direction.
submitted by jungle to Bitcoin [link] [comments]

PIVX Core v3.0.6 released (November 30th) - Optional Upgrade

Github release info and binaries
Forum Post
Important information about the automint and zPIV backup requirements

How to Upgrade

This release is optional but recommended. The latest mandatory upgrade is v3.0.5.1, but if you have any problems with earlier versions the latest version is recommended.
If you are running an older version, gracefully 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/PIVX-Qt (on Mac) or pivxd/pivx-qt (on Linux).
There are no special steps needed like config file changes but a backup is always a good idea.
A note from presstab in case it gets buried in the comments
Command line install and upgrade guide

Notable Changes

(but you should still read the release notes on Github)

Automated Database Corruption Repair

There have been cases of blockchain database corruption that can occur when PIVX client is not closed gracefully. The most common cases of corruption have been identified and the wallet will now automatically fix most of these corruptions. Certain corruption states are still unable to be fixed, but now provide more detailed error messages to the user as well as prompting the user to reindex their database.

More Accurate Error Messages

Some error messages in the wallet have been too vague and done little to help developers and the support team properly identify issues. Error messages have been refined and are now more specific.

Reduction of Debug Log Spam

Many 3rd party services have reported that their debug logs have been overloaded with messages about unknown transaction types. This log spam has been fixed.

Removal of Heavy Running Transaction Search Code

Many areas of the block validation code use a "slow" transaction search, which searches redundantly for transactions. This "slow" search has been removed upstream in Bitcoin and is now removed in PIVX. This provides a more efficient syncing process and generally better performing wallet.

Sync Fix for Block 908000

Many wallets were having trouble getting past block 908000. This block recalculates certain aspects of the money supply and zPIV transactions, and is known to take longer to sync. Code has been added to allow block 908000 to be validated without the user needing to enter any special commands into the debug console.

Working Testnet

Testnet is now accessible with this release of the wallet. Testnet can be accessed using the -testnet startup flag.

zPIV Spending Fix

zPIV that were minted between block 891730 and 895400 were experiencing an error initializing the accumulator witness data correctly, causing an inability to spend those mints. This has been fixed.

Credits

Thanks to everyone who directly contributed to this release:
As well as everyone that helped translating on Transifex.
submitted by turtleflax to pivx [link] [comments]

[BITCOIN REAL GUIDE FOR NEWBIES!] Everything you have to know about BITCOIN REAL in 3 minutes.

Introduction:
When the great revolution that is bitcoin began, the anonymous desired to test two parameters - a trustless, decentralized database (a distributed ledger or blockchain) protected by the everlasting security of cryptography and robust transaction systems capable of sending value across the world without intermediaries. Yet, the past 9 years have excruciatingly shown the lack of a third missing feature, which the brought the community to take action upon vacancy, ending up with the creation of endless Bitcoin Forks "real" Bitcoins", such as BitcoinCash, BitcoinGreen, BitcoinPrivate, BitcoinDiamond. All of these coins have been created because of this third and fundamental feature is missing. Bitcoin lacks innovation. Or rather it has innovation, it simply is extremely slow and cautious., and in the cryptocurrency, innovation is moving fast, the fastest possible. And this is the need that we seek to satisfy.

What is Bitcoin Real?
Bitcoin Real is a Bitcoin Fork which will happen on the TBD block. It will have all the features of the most popular Bitcoin Forks such as master nodes and staking, segregated witness, bigger blocks, proof of work + proof of stake, ASIC resistance) and it will be airdropped with following value across the world without intermediaries. Yet, the past 9 years excruciatingly shown ratios to each coin holder of each forked chain.
A secure blockchain network providing instant payment solutions across the globe with the revolution in block-chain technology-dilemma to choose any two from a trio of trust/security, mass adoption and decentralization has become real for projects. Bitcoin Real (BR) is one of the very few projects that will tap into all three parameters of blockchain together with providing robust transaction system.
In terms of verification of transactions, BR is using 8 MB block size in which several transactions can be verified instantly. The total size of Blockchain will be 140 GB through which BR will be able to cover many of the users’ transaction simultaneously. From the facts, it takes 60 seconds to break a block time in BR. So, around 400000 transactions per second can be done in BR.


Where can I buy Bitcoin Real?

You can purchase BitcoinReal from the exchanges listed below.

Where can I store my coins?

You can store your coins in the desktop wallet provided by the Community.

Contact Information?

Telegram: https://t.me/BitCoinRealPublic
Website: https://www.bitcoinreal.org/
Github: https://github.com/bitcoinreal
submitted by LiteSpeedDev to bitcoinrealcoin [link] [comments]

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]

01-13 07:43 - 'Lost Bitcoin passphrase: Does anyone have any experience with the new recovery tool Passware Forensic Kit?' (self.Bitcoin) by /u/NitrousNed removed from /r/Bitcoin within 5-15min

'''
Here's my situation.....
I know this is an all too common problem (and you've probably heard a lot of similar stories) but I'd appreciate any advice I can get. I purchased some bitcoins back in 2013. They were in a Bitcoin-QT wallet on my now very old and slow Macbook (which I still have). However, I wrote my passphrase on a piece of paper that is long gone now! I'm well aware that without the passphrase or seed phrase I'm unable to recover the coins.
HOWEVER, I might know part of the passphrase - but not too sure. I've now created a new BitcoinCore wallet and have imported the located the wallet.aes.json or wallet.dat file from the old mac (just waiting for the initial synchronization which should be finished in a couple of days.
I know it is difficult (if not impossible) to crack the passphrase via brute-force but I just heard about new Forensic software called Passphrase ([[link]2 ) that apparently has the ability to recover lost bitcoin passwords from Bitcoin.info and Bitcoin Core wallet services. It is very expensive (USD$1,095/year) but just wondering if anyone has used it before or knows how effective it will be in my situation.
Hoping someone can help!!!!!
Thanks


'''
Lost Bitcoin passphrase: Does anyone have any experience with the new recovery tool Passware Forensic Kit?
Go1dfish undelete link
unreddit undelete link
Author: NitrousNed
1: **w.pa*sware.c*m/ 2: ww*.pas*w*re.*om*^^1
Unknown links are censored to prevent spreading illicit content.
submitted by removalbot to removalbot [link] [comments]

The Strange Birth & History of Monero, Part III: Decentralized team

You can read here part I (by americanpegaus). This is the post that motivated me to make the part II. Now i'm doing a third part, and there'll be a final 4th part. This is probably too much but i wasn't able to make it shorter. Some will be interested in going through all them, and maybe someone is even willing to make a summary of the whole serie :D.
Monero - an anonymous coin based on CryptoNote technology
https://bitcointalk.org/index.php?topic=582080.0
Comentarios de interés:
-4: "No change, this is just a renaming. In the future, the binaries will have to be changed, as well as some URL, but that's all. By the way, this very account (monero) is shared by several user and is meant to make it easier to change the OP in case of vacancy of the OP. This idea of a shared OP comes from Karmacoin.
Some more things to come:
"
(https://bitcointalk.org/index.php?topic=582080.msg6362672#msg6362672)
-5: “Before this thread is too big, I would like to state that a bug has been identified in the emission curve and we are currently in the process of fixing it (me, TFT, and smooth). Currently coins are emitted at double the rate that was intended. We will correct this in the future, likely by bitshifting values of outputs before a certain height, and then correcting 1 min blocks to 2 min blocks. The changes proposed will be published to a Monero Improvement Protocol on github.”
(https://bitcointalk.org/index.php?topic=582080.msg6363016#msg6363016)
[tacotime make public the bug in the emission curve: token creation is currently 2 times what was intended to be, see this chart BTC vs the actual XMR curve, as it was and it is now, vs the curve that was initially planned in yellow see chart]
-14: “Moving discussion to more relevant thread, previous found here:
https://bitcointalk.org/index.php?topic=578192.msg6364026#msg6364026
I have to say that I am surprised that such an idea [halving current balances and then changing block target to 2 min with same block reward to solve the emission curve issue] is even being countenanced - there are several obvious arguments against it.
Perception - what kind of uproar would happen if this was tried on a more established coin? How can users be expected to trust a coin where it is perceived that the devs are able and willing to "dip" into people's wallets to solve problems?
Technically - people are trying to suggest that this will make no difference since it applies to reward and supply, which might be fair enough if the cap was halved also, but it isn't. People's holdings in the coin are being halved, however it is dressed up.
Market price - How can introducing uncertainty in the contents of people's wallets possibly help market price? I may well be making a fool of myself here, but I have never heard of such a fix before, unless you had savings in a Cypriot bank - has this ever been done for another coin?”
(https://bitcointalk.org/index.php?topic=582080.msg6364174#msg6364174)
-15: “You make good points but unfortunately conflicting statements were made and it isn't possible to stick to them all. It was said that this coin had a mining reward schedule similar to bitcoin. In fact it is twice as fast as intended, even even a bit more than twice as fast as bitcoin.
If you acquired your coins on the basis of the advertised reward schedule, you would be disappointed, and rightfully so, as more coins come to into existence more quickly than you were led to believe.
To simply ignore that aspect of the bug is highly problematic. Every solution may be highly problematic, but the one being proposed was agreed as being the least bad by most of the major stakeholders. Maybe it will still not work, this coin will collapse, and there will need to be a relaunch, in which case all your coins will likely be worthless. I hope that doesn't happen.”
(https://bitcointalk.org/index.php?topic=582080.msg6364242#msg6364242)
[smooth tries to justify his proposal to solve the emission curve issue: halve every current balance and change block target to 2 min with same block reward]
-16: “This coin wasn't working as advertised. It was supposed to be mined slowly like BTC but under the current emission schedule, 39% would be mined by the first year and 86% by the fourth year. Those targets have been moved out by a factor of 2, i.e. 86% mined by year 8, which is more like BTC's 75% by year 8. So the cap has been moved out much further into the future, constraining present and near-term supply, which is what determines the price.”
(https://bitcointalk.org/index.php?topic=582080.msg6364257#msg6364257)
[eizh supports smooth’s plan]
-20: “So long as the process is fair and transparent it makes no difference what the number is... n or n/2 is the same relative value so long as the /2 is applied to everyone. Correcting this now will avoid people accusing the coin of a favourable premine for people who mined in the first week.”
(https://bitcointalk.org/index.php?topic=582080.msg6364338#msg6364338)
[random user supporting smooth’s idea]
-21: “Why not a reduction in block reward of slightly more than half to bring it into line with the proposed graph? That would avoid all sorts of perceptual problems, would not upset present coin holders and be barely noticeable to future miners since less than one percent of coins have been mined so far, the alteration would be very small?”
(https://bitcointalk.org/index.php?topic=582080.msg6364348#msg6364348)
-22: “Because that still turns into a pre-mine or instamine where a few people got twice as many coins as everyone else in the first week.
This was always a bug, and should be treated as such.”
(https://bitcointalk.org/index.php?topic=582080.msg6364370#msg6364370)
[smooth wants to be sure they can’t be stigmatized as “premine”]
-23: “No, not true [answering to "it makes no difference what the number is... n or n/2 is the same relative value so long as the /2 is applied to everyone"]. Your share of the 18,000,000 coins is being halved - rightly or wrongly.”
(https://bitcointalk.org/index.php?topic=582080.msg6364382#msg6364382)
[good point made by a user that is battling “hard” with smooth and his proposal]
-28: “+1 for halving all coins in circulation. Would they completely disappear? What would the process be?”
-31: “I will wait for the next coin based on CryptoNote. Many people, including myself, avoided BMR because TFT released without accepting input from anyone (afaik). I pm'ed TFT 8 days before launch to help and didn't get response until after launch. Based on posting within the thread, I bet there were other people. Now the broken code gets "fixed" by taking away coins.”
(https://bitcointalk.org/index.php?topic=582080.msg6364531#msg6364531)
-32: “What you say is true, and I can't blame anyone from simply dropping this coin and wanting a complete fresh start instead. On the other hand, this coin is still gaining in popularity and is already getting close to bytecoin in hash rate, while avoiding its ninja premine. There is a lot done right here, and definitely a few mistakes.”
(https://bitcointalk.org/index.php?topic=582080.msg6364574#msg6364574)
[smooth stands for the project legitimacy despite the bugs]
-37: “Since everything is scaled and retroactive, the only person to be affected is... me. Tongue Because I bought BMR with BTC, priced it with incorrect information, and my share relative to the eventual maximum has been halved. Oh well. The rest merely mined coins that never should have been mined. The "taking away coins" isn't a symptom of the fix: it's the fundamental thing that needed fixing. The result is more egalitarian and follows the original intention. Software is always a work-in-progress. Waiting for something ideal at launch is pretty hopeless. edit: Let me point out that most top cryptocurrencies today were released before KGW and other new difficulty retargeting algorithms became widespread. Consequently they had massive instamines on the first day, even favorites in good standing like LTC. Here the early miners are voluntarily reducing their eventual stake for the sake of fairness. How cool is that?”
(https://bitcointalk.org/index.php?topic=582080.msg6364886#msg6364886)
[this is eizh supporting the project too]
-43: “I'm baffled that people are arguing about us making the emission schedule more fair. I'm an early adopter. This halves my money, and it's what I want to do. There's another change that needs to be talked about too: we don't believe that microscopic levels of inflation achieved at 9 or 10 years will secure a proof-of-work network. In fact, there's a vast amount of evidence from DogeCoin and InfiniteCoin that it will not. So, we'd like to fix reward when it goes between 0.25 - 1.00 coins. To do so, we need to further bitshift values to decrease the supply under 264-1 atomic units to accommodate this. Again, this hurts early adopters (like me), but is designed to ensure the correct operation of the chain in the long run. It's less than a week old, and if we're going to hardfork in economic changes that make sense we should do it now. We're real devs turning monero into the coin it should have been, and our active commitment should be nothing but good news. Fuck the pump and dumps, we're here to create something with value that people can use.”
(https://bitcointalk.org/index.php?topic=582080.msg6366134#msg6366134)
[tacotime brings to the public for first time the tail emission proposal and writes what is my favourite sentence of the whole monero history: “Fuck the pump and dumps, we're here to create something with value that people can use”]
-51: “I think this is the right attitude. Like you I stand to "lose" from this decision in having my early mining halved, but I welcome it. Given how scammy the average coin launch is, I think maximizing fairness for everyone is the right move. Combining a fair distribution with the innovation of Cryptonote tech could be what differentiates Monero from other coins.”
(https://bitcointalk.org/index.php?topic=582080.msg6366346#msg6366346)
-59: “Hello! It is very good that you've created this thread. I'm ok about renaming. But I can't agree with any protocol changes based only on decisions made by bitcointalk.org people. This is because not all miners are continiously reading forum. Any decision about protocol changes are to be made by hashpower-based voting. From my side I will agree on such a decision only if more than 50% of miners will agree. Without even such a simple majority from miners such changes are meaningless. In case of hardfork that isn't supported by majority of miners the network will split into two nets with low-power fork and high-power not-forking branches. I don't think that this will be good for anybody. Such a voting is easy to be implemented by setting minor_version of blocks to a specific value and counting decisions made after 1000 of blocks. Do you agree with such a procedure?”
(https://bitcointalk.org/index.php?topic=582080.msg6368478#msg6368478)
[TFT appears after a couple days of inactivity]
-63: “In few days I will publish a code with merged mining support. This code will be turned ON only by voting process from miners. What does it mean:
The same procedure is suitable for all other protocol changes.”
(https://bitcointalk.org/index.php?topic=582080.msg6368720#msg6368720)
[And now he is back, TFT is all about merged mining]
-67: “We don't agree that a reverse split amounts to "taking" coins. I also wouldn't agree that a regular forward split would be "giving" coins. It's an exchange of old coins with new coins, with very nearly the exact same value. There is a very slight difference in value due to the way the reward schedule is capped, but that won't be relevant for years or decades. Such a change is entirely reasonable to fix an error in a in coin that has only existed for a week.”
(https://bitcointalk.org/index.php?topic=582080.msg6368861#msg6368861)
-68: “There were no error made in this coin but now there is an initiative to make some changes. Changes are always bad and changes destroy participant confidence even in case these changes are looking as useful. We have to be very careful before making any changes in coins”
(https://bitcointalk.org/index.php?topic=582080.msg6368939#msg6368939)
[TFT does not accept the unexpected emission curve as a bug]
-72: “You are wrong TFT. The original announcement described the coin as having a reward curve "close to Bitcoin's original curve" (those are your exact words). The code as implemented has a reward curve that is nothing like bitcoin. It will be 86% mined in 4 years. It will be 98% mined in 8 years. Bitcoin is 50% mined in 4 years, and 75% in 8 years.
With respect TFT, you did the original fork, and you deserve credit for that. But this coin has now gone beyond your initial vision. It isn't just a question of whether miners are on bitcointalk or not.
There is a great team of people who are working hard to make this coin a success, and this team is collaborating regularly through forum posts, IRC, PM and email. And beyond that a community of users who by and large have been very supportive of the efforts we've taken to move this forward.
Also, miners aren't the only stakeholders, and while a miner voting process is great, it isn't the answer to every question. Though I do agree that miners need to be on board with any hard fork to avoid a harmful split.”
(https://bitcointalk.org/index.php?topic=582080.msg6369137#msg6369137)
[smooth breaks out publicily for first time against TFT]
-75: “I suppose that merged mining as a possible option is a good idea as soon as nobody is forced to use it. MM is a possibility to accept PoW calculated for some other network. It helps to increase a security of both networks and makes it possible for miners not to choose between two networks if they want both:
Important things to know about MM:
Actually the only change that goes with MM is that we are able to accept PoW from some other net with same hash-function. Each miner can decide his own other net he will merge mine BMR with.
And this is still very secure.
This way I don't see any disadvantage in merged mining. What disadvantages do you see in MM?”
(https://bitcointalk.org/index.php?topic=582080.msg6369255#msg6369255)
[TFT stands for merged mining]
-77: “Merged mining essentially forces people to merge both coins because that is the only economically rational decision. I do not want to support the ninja-premined coin with our hash rate.
Merged mining makes perfect sense for a coin with a very low hash rate, otherwise unable to secure itself effectively. That is the case with coins that merge mine with bitcoin. This coin already has 60% of the hash rate of bytecoin, and has no need to attach itself to another coin and encourage sharing of hash rate between the two. It stands well on its own and will likely eclipse bytecoin very soon.
I want people to make a clear choice between the fair launched coin and the ninja-premine that was already 80% mined before it was made public. Given such a choice I believe most will just choose this coin. Letting them choose both allows bytecoin to free ride on what we are doing here. Let the ninja-preminers go their own way.”
(https://bitcointalk.org/index.php?topic=582080.msg6369386#msg6369386)
[smooth again]
-85: “One of you is saying that there was no mistake in the emission formula, while the other is. I'm not asking which I should believe . . I'm asking for a way to verify this”
(https://bitcointalk.org/index.php?topic=582080.msg6369874#msg6369874)
[those that have not been paying attention to the soap opera since the beginning do not understand anything at all]
-86: “The quote I posted "close to Bitcoin's original curve" is from the original announcement here: https://bitcointalk.org/index.php?topic=563821.0
I think there was also some discussion on the thread about it being desirable to do that.
At one point in that discussion, I suggested increasing the denominator by a factor of 4, which is what ended up being done, but I also suggested retaining the block target at 2 minutes, which was not done. The effect of making one change without the other is to double the emission rate from something close to bitcoin to something much faster (see chart a few pages back on this thread).”
(https://bitcointalk.org/index.php?topic=582080.msg6369935#msg6369935)
[smooth answers just a few minutes later]
-92: “I'm happy the Bitmonero attracts so much interest.
I'm not happy that some people want to destroy it.
Here is a simple a clear statement about plans: https://bitcointalk.org/index.php?topic=582670
We have two kind of stakeholders we have respect: miders and coin owners.
Before any protocol changes we will ask miners for agreement. No changes without explicit agreement of miners is possible.
We will never take away or discount any coins that are already emitted. This is the way we respect coin owners.
All other issues can be discussed, proposed and voted for. I understand that there are other opinions. All decisions that aren't supported in this coin can be introduced in any new coin. It's ok to start a new fork. It's not ok to try to destroy an existsing network.”
(https://bitcointalk.org/index.php?topic=582080.msg6370324#msg6370324)
[TFT is kinda upset – he can see how the community is “somehow” taking over]
-94: “Sounds like there's probably going to be another fork then. Sigh.
I guess it will take a few tries to get this coin right.
The problem with not adjusting existing coins is that it make this a premine/instamine. If the emission schedule is changed but not as a bug fix, then earlier miners got an unfair advantage over everyone else. Certainly there are coins with premines and instamines, but there's a huge stigma and such a coin will never achieve the level of success we see for this coin. This was carefully discussed during the team meeting, which was announced a day ahead of time, and everyone with any visible involvement with the coin, you included, was invited. It is unfortunate you couldn't make it to that meeting TFT.”
(https://bitcointalk.org/index.php?topic=582080.msg6370411#msg6370411)
[smooth is desperate due to TFT lack of interest in collaboration, and he publicly speaks about an scission for first time]
-115: “Very rough website online, monero.cc (in case you asked, the domain name was voted on IRC, like the crypto name and its code). Webdesigner, webmaster, writers... wanted.”
(https://bitcointalk.org/index.php?topic=582080.msg6374702#msg6374702)
[Even though the lack of consensus and the obvious chaos, the community keeps going on: Monero already has his own site]
-152: “Here's one idea on fixing the emissions without adjusting coin balances.
We temporarily reduce the emission rate to half of the new target for as long as it takes for the total emission from 0 to match the new curve. Thus there will be a temporary period when mining is very slow, and during that period there was a premine.
But once that period is compete, from the perspective of new adopters, there was no premine -- the total amount of coins emitted is exactly what the slow curve says it should be (and the average rate since genesis is almost the same as the rate at which they are mining, for the first year or so at least).
This means the mining rewards will be very low for a while (if done now then roughly two weeks), and may not attract many new miners. However, I think there enough of us early adopters (and even some new adopters who are willing to make a temporary sacrifice) who want to see this coin succeed to carry it through this period.
The sooner this is done the shorter the catch up period needs to be.”
(https://bitcointalk.org/index.php?topic=582080.msg6378032#msg6378032)
[smooth makes a proposal to solve the “emission curve bug” without changing users balances and without favoring the early miners]
-182: “We have added a poll in the freenode IRC room "Poll #2: "Emission future of Monero, please vote!!" started by stickh3ad. Options: #1: "Keep emission like now"; #2: "Keep emission but change blocktime and final reward"; #3: "Keep emission but change blocktime"; #4: "Keep emission but change final reward"; #5: "Change emission"; #6: "Change emission and block time"; #7: "Change emission and block time and final reward"
Right now everyone is voting for #4, including me.”
(https://bitcointalk.org/index.php?topic=582080.msg6379518#msg6379518)
[tacotime announces an ongoing votation on IRC]
-184: “ change emission: need to bitshift old values on the network or double values after a certain block. controversial. not sure if necessary. can be difficult to implement. keep emission: straightforward, we don't keep change emission or block time. change final reward is simple. if (blockSubsidy < finalSubsidy) return finalSubsidy; else return blockSubsidy;”
(https://bitcointalk.org/index.php?topic=582080.msg6379562#msg6379562)
-188: “Yeah, well. We need to change the front page to reflect this if we can all agree on it.
We should post the emissions curve and the height and value that subsidy will be locked in to.
In my opinion this is the least disruptive thing we can do at the moment, and should ensure that the fork continues to be mineable and secure in about 8 years time without relying on fees to secure it (which I think you agree is a bad idea).”
(https://bitcointalk.org/index.php?topic=582080.msg6379871#msg6379871)
[tacotime]
-190: “I don't think the proposed reward curve is bad by any means. I do think it is bad to change the overall intent of a coin's structure and being close to bitcoins reward curve was a bit part of the intent of this coin. It was launched in response to the observation that bytecoin was 80% mined in less than two years (too fast) and also that it was ninja premined, with a stated goal that the new coin have a reward curve close to bitcoin.
At this point I'm pretty much willing to throw in the towel on this launch:
  1. No GUI
  2. No web site
  3. Botched reward curve (at least botched relative to stated intent)
  4. No pool (and people who are enthusiastically trying to mine having trouble getting any blocks; some of them have probably given up and moved on).
  5. No effective team behind it at launch
  6. No Mac binaries (I don't think this is all that big a deal, but its another nail)
I thought this could be fixed but with all the confusion and lack of clear direction or any consistent vision, now I'm not so sure.
I also believe that merged mining is basically a disaster for this coin, and is probably being quietly promoted by the ninjas holding 80% of bytecoin, because they know it keeps their coin from being left behind, and by virtue of first mover advantage, probably relegates any successors to effective irrelevance (like namecoin, etc.).
We can do better. It's probably time to just do better.”
(https://bitcointalk.org/index.php?topic=582080.msg6380065#msg6380065)
[smooth is disappointed]
-191: “The website does exist now, it's just not particularly informative yet. :) But, I agree that thankful_for_today has severely mislead everyone by stating the emission was "close to Bitcoin's" (if he's denying that /2 rather than /4 emission schedule was unintentional, as he seems to be). I'm also against BCN merge mining. It works against the goal of overtaking BCN and if that's not a goal, I don't know what we're even doing here. I'll dedicate my meagre mining to voting against that.
That said, you yourself have previously outlined why relaunches and further clones fail. I'd rather stick with this one and fix it.”
(https://bitcointalk.org/index.php?topic=582080.msg6380235#msg6380235)
[eizh tries to keep smooth on board]
-196: “BCN is still growing as well. It is up to 1.2 million now. If merged mining happens, (almost) everyone will just mine both. The difficulty on this coin will jump up to match BCN (in fact both will likely go higher since the hash rate will be combined) and again it is an instamine situation. (Those here the first week get the benefit of easy non-merged mining, everyone else does not.) Comments were made on this thread about this not being yet another pump-and-dump alt. I think that could have been the case, but sadly, I don't really believe that it is.”
(https://bitcointalk.org/index.php?topic=582080.msg6380778#msg6380778)
-198: “There's no point in fragmenting talent. If you don't think merge mining is a good idea, I'd prefer we just not add it to the code.
Bitcoin had no web site or GUI either initially. Bitcoin-QT was the third Bitcoin client.
If people want a pool, they can make one. There's no point in centralizing the network when it's just began, though. Surely you must feel this way.”
(https://bitcointalk.org/index.php?topic=582080.msg6381866#msg6381866)
[tacotime also wants smooth on board]
-201: “My personal opinion is that I will abandon the fork if merge mining is added. And then we can discuss a new fork. Until then I don't think Monero will be taken over by another fork.”
(https://bitcointalk.org/index.php?topic=582080.msg6381970#msg6381970)
[tacotime opens the season: if merged mining is implemented, he will leave the ship]
-203: “Ditto on this. If the intention wasn't to provide a clearweb launched alternative to BCN, then I don't see a reason for this fork to exist. BCN is competition and miners should make a choice.”
(https://bitcointalk.org/index.php?topic=582080.msg6382097#msg6382097)
[eizh supports tacotime]
-204: “+1 Even at the expense of how much I already "invested" in this coin.”
(https://bitcointalk.org/index.php?topic=582080.msg6382177#msg6382177)
[NoodleDoodle is also against merged mining]
This is basically everything worth reading in this thread. This thread was created in the wrong category, and its short life of about 2 days was pretty interesting. Merged mining was rejected and it ended up with the inactivity of TFT for +7 days and the creation of a new github repo the 30th of April. It is only 12 days since launch and a decentralized team is being built.
Basically the community had forked (but not the chain) and it was evolving and moving forward to its still unclear future.
These are the main takeaways of this thread:
  • The legitimacy of the "leaders" of the community is proven when they proposed and supported the idea of halving the balances for the greater good to solve the emission curve issue without any possible instamine accusation. Also their long-term goals and values rejecting merged-mining with a "primined scam"
  • It is decided that, as for now, it is “too late” to change the emission curve, and finally monero will mint 50% of its coin in ~1.3 years (bitcoin did it after 3.66 years) and 86% of its coins in 4 years (bitcoin does it in ~11 years) (was also voted here) (see also this chart)
  • It is decided that a “minimum subsidy” or “tail emission” to incentivize miners “forever” and avoid scaling fees will be added (it will be finally added to the code march 2015)
  • Merged mining is plainly rejected by the future “core team” and soon rejected by "everyone". This will trigger TFT inactivity.
  • The future “core team” is somehow being formed in a decentralized way: tacotime, eizh, NoodleDoodle, smooth and many others
And the most important. All this (and what is coming soon) is a proof of the decentralization of Monero. Probably comparable to Bitcoin first days. This is not a company building a for-profit project (even if on the paper it is not for-profit), this a group of disconnected individuals sharing a goal and working together to reach it.
Soon will be following a final part where i'll collect the bitcointalk logs in the current official announcement threads. There you'll be able to follow the decentralized first steps of develoment (open source pool, miner optimizations and exchanges, all surrounded by fud trolls, lots of excitmen and a rapidly growing collaborative community.
submitted by el_hispano to Monero [link] [comments]

Inconsistent download speed for full chain?

I'm spinning up a Bitcoin ABC node on a mac at home. I've noticed that when I have the app foregrounded it seems to download blocks at what I'd consider a reasonable rate. If it had carried on at the rate at which it was initially downloading it would have completed in something like 3 days.
But when I leave the computer and return a while later it has often ground to a halt. I thought at first the system was sleeping so I disabled that entirely but it is still happening.
It's been a week now and I'm only at 76%. I'm looking at it as I'm typing this and it's humming away estimating only 13 hours to go but experience says when I get home from work tomorrow evening it still won't be done.
What could be causing it to slow down? Is this a known issue with the Bitcoin-QT client? I can't imagine it's ABC- or BCH-related because I'm still pulling blocks from Jan 2017 so it's the same data the core client would be seeing at this point.
submitted by how_now_dao to btc [link] [comments]

The Monero Missives (weekly report) - September 16th, 2014

Original post is here
Monero Missives
September 15th, 2014
Hello, and welcome to our twelfth Monero Missive! This is our first Missive after a bit of a break whilst we thwarted two related blockchain attacks. Nonetheless, we have not sat by idly, we have been finalising and completing a brand new aspect of Monero designed to protect your privacy now and in the future: the Monero Research Lab
Major Updates
  1. The Monero Research Lab is an open collective and a multi-faceted academic group focused on the ongoing improvement of Monero. Membership is not fixed, and comes and goes as researchers become interested in Monero. This isn't a group focused on the addition of "features" to Monero, but rather the analysis and improvement of the underlying core of Monero to make sure that the theories and cryptography behind Monero continue to remain robust and sound. With that in mind, we are proud to announce the release of the first two publications out of the Monero Research Lab: MRL-0001 - A Note on Chain Reactions in Traceability in CryptoNote 2.0 - this is a research bulletin that investigates how a chain reaction could weaken the blockchain resistance properties of CryptoNote's ring signatures if low mixin values are consistently chosen MRL-0002 - Counterfeiting via Merkle Tree Exploits within Virtual Currencies Employing the CryptoNote Protocol - in this research bulletin we investigate how the block 202612 attack occurred and what it exploited, and also covers the permanent fix we have put in place
  2. This week Friday we're going to have our second #Monero-Dev Fireside Chat this week Friday, September 19th, 2014, at 10:00 EST which is 14:00 UTC and 16:00 UTC +2. For a full table of the time zones you can refer to this image, or you can use this online tool to add your city and make sure you have the correct starting time. Please note that this is a developer event, and so most of the focus will be from that perspective.
  3. To pick up where we left off with our last Missive, we are also happy to announce the availability of Monero merchandise on the Monero Gear store, powered by Zazzle. The advantage of us using Zazzle is that it is on-demand and we never have to worry about print runs or stock or anything. In return we get 15% of each sale as a "royalty" that will go towards enabling further Monero development, although Zazzle do not (yet!) accept Bitcoin or Monero. We hope to add new designs to the store on a regular basis. You can check the store out here: http://www.zazzle.com/monerogear* or take a peek at some of the new designs right here
  4. We are also pleased to announce the release of URS, a Monero project written in Go that allows you to sign messages using ring signatures as part of a group. The signature can be verified, but it cannot be determined which one of the signatories in the group did the actual signing (just like Monero uses for transactional unlinkability!). You can take a look at the project here: https://github.com/monero-project/urs, and the Bitcointalk thread dedicated to the project is here: https://bitcointalk.org/index.php?topic=768499.0
  5. We have a new tagged release, 0.8.8.4, available for download (binaries: Windows, Mac, Linux, FreeBSD). This adds the following features: Testnet: we now have an operating testnet. When using bitmonerod or simplewallet you can now use the --testnet flag to use testnet instead of mainnet. Feel free to run a mining node or just a testnet node, we will be setting up email alerts for testnet nodes when an update is pending (although having a few older testnet nodes on the network won't hurt testing). FreeBSD Compatability: Monero now works on FreeBSD out the box. We will add it to the ports tree soon. At the moment compilation is no different from regular Linux and Unix compilation, and the same dependencies apply. GPG commits: we have begun GPG-signing commits and merges. This is an important step in maintaining the integrity of the codebase, and will ensure that any compromise of our computers or even the github account won't allow a malicious attacker to push code to the repository without the unsigned commits being spotted. Verification can be done by running 'git log --show-signature', which will show and verify signatures. An example of what you should see can be found here Versioning: versioning is a lot easier, now, as tagged releases from 0.8.8.4 onwards will show version-final (eg. 0.8.8.4-final) as their version, and those built between tagged releases will show version-commithash (eg. 0.8.8.4-9088ea1). We expect this will greatly aid in debugging problems, as we can immediately pinpoint the actual version / commit a user is on. Logging: default log levels have been adjusted so that non-critical warnings are now relegated to log-level 1 and above. Apart from the normal reorganisation notifications, the only messages in red that should show up in the daemon are actual errors.
  6. We have slowed down development on the GUI to give us a bit more time to focus on the Monero internals. This is especially important given the recent attack. However, work has not come to a complete halt, and so we wanted to show off a couple of pages from the first start wizard. Bear in mind that these aren't mockups, this is the actual running Qt interface: http://i.imgur.com/jzUvSEP.jpg, http://i.imgur.com/Bj1PTcU.jpg, http://i.imgur.com/oirzi9n.jpg, http://i.imgur.com/ACDmOFJ.jpg
  7. Monero has been added to another exchange, Coin Swap. You can find the market here: https://coin-swap.net/market/XMBTC
Dev Diary
Core: because of all of the rapid changes that we had to merge into master to deal with the aftermath of the block 202612 attack, we have to bring the development branch in sync. At this stage the development branch should not be considered usable until the rebase is complete.
Build: the big change is FreeBSD compatibility, as mentioned above. A more subtle change is that the build will now first look for miniupnpc on the local system, and use that if found. If it fails to find miniupnpc it will fall back to the local copy.
Build: there is a new Makefile target, release-static, that builds statically linked binaries for redistribution. At this stage it forces 64-bit builds, once we have the embedded database working cleanly we can remove this.
Wallet: per-kb fees are nearly complete, and will be deployed to testnet within the next week or so. Once some thorough testing has been done on testnet we can merge this into master, and transaction fees can return to "normal".
Blockchain: this took a bit of a backseat with the blockchain attacks. Now that things are back to some semblance of normality, the first implementation can be written. We have chosen LMDB for the initial implementation, as this will allow us to rapidly write a Berkeley DB interface based off of it (they use similar APIs) and thus have a baseline for performance comparisons.
Core: all non-critical "errors" and warnings have been moved to log-level 1. As a developer, you may find it useful to run log-level 1 or 2 as your default.
Until next week!
submitted by fluffyponyza to Monero [link] [comments]

Interested in contributing to the BTC community? Here is a exhaustive manual to get you up and running. (Only takes about 20-30 minutes if you are fluent in command prompt on linux).

These instructions will work both on a VPS cloud server or a personal computer. You may find cheap VPS somewhere online for rent.
What Is A Full Node?
A full node is a program that fully validates transactions and blocks. Almost all full nodes also help the network by accepting transactions and blocks from other full nodes, validating those transactions and blocks, and then relaying them to further full nodes.
Most full nodes also serve lightweight clients by allowing them to transmit their transactions to the network and by notifying them when a transaction affects their wallet. If not enough nodes perform this function, clients won’t be able to connect through the peer-to-peer network—they’ll have to use centralized services instead.
Many people and organizations volunteer to run full nodes using spare computing and bandwidth resources—but more volunteers are needed to allow Bitcoin to continue to grow. This document describes how you can help and what helping will cost you.
Costs And Warnings
Running a Bitcoin full node comes with certain costs and can expose you to certain risks. This section will explain those costs and risks so you can decide whether you’re able to help the network.
Special Cases
Miners, businesses, and privacy-conscious users rely on particular behavior from the full nodes they use, so they will often run their own full nodes and take special safety precautions. This document does not cover those precautions—it only describes running a full node to help support the Bitcoin network in general.
Please consult an expert if you need help setting up your full node correctly to handle high-value and privacy-sensitive tasks.
Secure Your Wallet
It’s possible and safe to run a full node to support the network and use its wallet to store your bitcoins, but you must take the same precautions you would when using any Bitcoin wallet. Please see the securing your wallet page for more information.
Minimum Requirements
Bitcoin Core full nodes have certain requirements. If you try running a node on weak hardware, it may work—but you’ll likely spend more time dealing with issues. If you can meet the following requirements, you’ll have an easy-to-use node.
Note: many operating systems today (Windows, Mac, and Linux) enter a low-power mode after the screensaver activates, slowing or halting network traffic. This is often the default setting on laptops and on all Mac OS X laptops and desktops. Check your screensaver settings and disable automatic “sleep” or “suspend” options to ensure you support the network whenever your computer is running.
Possible Problems
Legal: Bitcoin use is prohibited or restricted in some areas.
Bandwidth limits: Some Internet plans will charge an additional amount for any excess upload bandwidth used that isn’t included in the plan. Worse, some providers may terminate your connection without warning because of overuse. We advise that you check whether your Internet connection is subjected to such limitations and monitor your bandwidth use so that you can stop Bitcoin Core before you reach your upload limit.
Anti-virus: Several people have placed parts of known computer viruses in the Bitcoin block chain. This block chain data can’t infect your computer, but some anti-virus programs quarantine the data anyway, making it more difficult to run a full node. This problem mostly affects computers running Windows.
Attack target: People who want to disrupt the Bitcoin network may attack full nodes in ways that will affect other things you do with your computer, such as an attack that limits your available download bandwidth or an attack that prevents you from using your full node’s wallet for sending transactions.
Linux Instructions
The following instructions describe installing Bitcoin Core on Linux systems.
Ubuntu 14.10 Instructions for Bitcoin Core 0.10.0.
If you use Ubuntu Desktop, click the Ubuntu swirl icon to start the Dash and type “term” into the input box. Choose any one of the terminals listed:
Alternatively, access a console or terminal emulator using another method, such as SSH on Ubuntu Server or a terminal launcher in an alternative desktop environment.
Type the following line to add the Bitcoin Personal Package Archive (PPA) to your system:
sudo apt-add-repository ppa:bitcoin/bitcoin
You will be prompted for your user password. Provide it to continue. Afterwards, the following text will be displayed:
Stable Channel of bitcoin-qt and bitcoind for Ubuntu, and their dependencies
More info: https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin
Press [ENTER] to continue or ctrl-c to cancel adding it
Press enter to continue. The following text (with some variations) will be displayed and you will be returned to the command line prompt:
gpg: keyring /tmp/tmpixuqu73x/secring.gpg' created gpg: keyring/tmp/tmpixuqu73x/pubring.gpg' created gpg: requesting key 8842CE5E from hkp server > > > >keyserver.ubuntu.com gpg: /tmp/tmpixuqu73x/trustdb.gpg: trustdb created gpg: key 8842CE5E: public key "Launchpad PPA for Bitcoin" imported gpg: no ultimately trusted keys found gpg: Total number processed: 1 pg: imported: 1 (RSA: 1) OK
Type the following line to get the most recent list of packages:
sudo apt-get update
A large number of lines will be displayed as different update files are downloaded. This step may take several minutes on a slow Internet connection.
To continue, choose one of the following options
sudo apt-get install bitcoin-qt
sudo apt-get install bitcoind
sudo apt-get install bitcoin-qt bitcoind
After choosing what packages to install, you will be asked whether you want to proceed. Press enter to continue.
If you’re logged in as an administrative user with sudo access, you may log out. The steps in this section should be performed as the user you want to run Bitcoin Core. (If you’re an expert administrator, you can make this a locked account used only by Bitcoin Core.)
Before using the Bitcoin Core daemon, bitcoind, you need to create its configuration file with a user name and password. First create the .bitcoin directory, create (touch) the file, and set the file’s permissions so that only your user account can read it. From the terminal, type:
mkdir ~/.bitcoin touch ~/.bitcoin/bitcoin.conf chmod 600 ~/.bitcoin/bitcoin.conf
Then you can run the command bitcoind. It will print output similar to this:
bitcoind Error: To use the "-server" option, you must set a rpcpassword in the configuration file: /home/bitcoinorg/.bitcoin/bitcoin.conf It is recommended you use the following random password: rpcuser=bitcoinrpc rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions. It is also recommended to set alertnotify so you are notified of problems; for example: alertnotify=echo %s | mail -s "Bitcoin Alert" [email protected] The “rpcpassword” displayed will be unique for your system. You can copy the rpcuser and rpcpassword lines into your configuration file using the following commands. Note that in most Ubuntu terminals, you need to press Ctrl-Shift-C to copy and Ctrl-Shift-V to paste because Ctrl-C and Ctrl-V have different meanings in a Unix-style terminal.
echo rpcuser=bitcoinrpc >> ~/.bitcoin/bitcoin.conf echo rpcpassword=XXXXXX >> ~/.bitcoin/bitcoin.conf (Warning: Don’t use XXXXXX as your RPC password. Copy the rpcpassword displayed by bitcoind for your system.)
Now you can start Bitcoin Core daemon for real. Type the following command:
bitcoind -daemon
It will print a message that Bitcoin Core is starting. To interact with Bitcoin Core daemon, you will use the command bitcoin-cli (Bitcoin command line interface). Note: it may take up to several minutes for Bitcoin Core to start, during which it will display the following message whenever you use bitcoin-cli:
error: {"code":-28,"message":"Verifying blocks..."}
After it starts, you may find the following commands useful for basic interaction with your node:
to safely stop your node, run the following command:
bitcoin-cli stop
A complete list of commands is available in the Bitcoin.org developer reference.
When Bitcoin Core daemon first starts, it will begin to download the block chain. This step will take at least several hours, and it may take a day or more on a slow Internet connection or with a slow computer. During the download, Bitcoin Core will use a significant part of your connection bandwidth. You can stop Bitcoin Core at any time using the stop command; it will resume from the point where it stopped the next time you start it.
Optional: Start Your Node At Boot
Starting your node automatically each time your computer boots makes it easy for you to contribute to the network. The easiest way to do this is to start Bitcoin Core daemon from your crontab. To edit your crontab, run the following command:
crontab -e
@reboot bitcoind -daemon Save the file and exit; the updated crontab file will be installed for you. Now Bitcoin Core daemon will be automatically started each time your reboot your computer.
If you’re an Ubuntu expert and want to use an init script instead, see this Upstart script.
You have now completed installing Bitcoin Core. If you have any questions, please ask in one of Bitcoin’s many communities, such as Bitcoin StackExchange, BitcoinTalk technical support, or the #bitcoin IRC chatroom on Freenode.
To support the Bitcoin network, you also need to allow incoming connections. Please read the Network Configuration section for details.
Network Configuration
If you want to support the Bitcoin network, you must allow inbound connections.
When Bitcoin Core starts, it establishes 8 outbound connections to other full nodes so it can download the latest blocks and transactions. If you just want to use your full node as a wallet, you don’t need more than these 8 connections—but if you want to support lightweight clients and other full nodes on the network, you must allow inbound connections.
Servers connected directly to the Internet usually don’t require any special configuration. You can use the testing instructions below to confirm your server-based node accepts inbound connections.
Home connections are usually filtered by a router or modem. Bitcoin Core will request your router automatically configure itself to allow inbound connections to Bitcoin’s port, port 8333. Unfortunately many routers don’t allow automatic configuration, so you must manually configure your router. You may also need to configure your firewall to allow inbound connections to port 8333. Please see the following subsections for details.
Testing Connections
The BitNodes project provides an online tool to let you test whether your node accepts inbound connections. To use it, start Bitcoin Core (either the GUI or the daemon), wait 10 minutes, and then visit the GetAddr page (https://getaddr.bitnodes.io/). The tool will attempt to guess your IP address—if the address is wrong (or blank), you will need to enter your address manually.
For more instruction and reviews based off BTC please follow my subreddit /BTC_Reviews
all material from this post was found here --> https://bitcoin.org/en/full-node
submitted by Mattjhagen to rBitcoin [link] [comments]

Running a full node using Bitcoin-daemon. Instructions for Linux.

These instructions will work both on a VPS cloud server or a personal computer. You may find cheap VPS somewhere online for rent.
What Is A Full Node?
A full node is a program that fully validates transactions and blocks. Almost all full nodes also help the network by accepting transactions and blocks from other full nodes, validating those transactions and blocks, and then relaying them to further full nodes.
Most full nodes also serve lightweight clients by allowing them to transmit their transactions to the network and by notifying them when a transaction affects their wallet. If not enough nodes perform this function, clients won’t be able to connect through the peer-to-peer network—they’ll have to use centralized services instead.
Many people and organizations volunteer to run full nodes using spare computing and bandwidth resources—but more volunteers are needed to allow Bitcoin to continue to grow. This document describes how you can help and what helping will cost you.
Costs And Warnings
Running a Bitcoin full node comes with certain costs and can expose you to certain risks. This section will explain those costs and risks so you can decide whether you’re able to help the network.
Special Cases
Miners, businesses, and privacy-conscious users rely on particular behavior from the full nodes they use, so they will often run their own full nodes and take special safety precautions. This document does not cover those precautions—it only describes running a full node to help support the Bitcoin network in general.
Please consult an expert if you need help setting up your full node correctly to handle high-value and privacy-sensitive tasks.
Secure Your Wallet
It’s possible and safe to run a full node to support the network and use its wallet to store your bitcoins, but you must take the same precautions you would when using any Bitcoin wallet. Please see the securing your wallet page for more information.
Minimum Requirements
Bitcoin Core full nodes have certain requirements. If you try running a node on weak hardware, it may work—but you’ll likely spend more time dealing with issues. If you can meet the following requirements, you’ll have an easy-to-use node.
Note: many operating systems today (Windows, Mac, and Linux) enter a low-power mode after the screensaver activates, slowing or halting network traffic. This is often the default setting on laptops and on all Mac OS X laptops and desktops. Check your screensaver settings and disable automatic “sleep” or “suspend” options to ensure you support the network whenever your computer is running.
Possible Problems
Legal: Bitcoin use is prohibited or restricted in some areas.
Bandwidth limits: Some Internet plans will charge an additional amount for any excess upload bandwidth used that isn’t included in the plan. Worse, some providers may terminate your connection without warning because of overuse. We advise that you check whether your Internet connection is subjected to such limitations and monitor your bandwidth use so that you can stop Bitcoin Core before you reach your upload limit.
Anti-virus: Several people have placed parts of known computer viruses in the Bitcoin block chain. This block chain data can’t infect your computer, but some anti-virus programs quarantine the data anyway, making it more difficult to run a full node. This problem mostly affects computers running Windows.
Attack target: People who want to disrupt the Bitcoin network may attack full nodes in ways that will affect other things you do with your computer, such as an attack that limits your available download bandwidth or an attack that prevents you from using your full node’s wallet for sending transactions.
Linux Instructions
The following instructions describe installing Bitcoin Core on Linux systems.
Ubuntu 14.10 Instructions for Bitcoin Core 0.10.0.
If you use Ubuntu Desktop, click the Ubuntu swirl icon to start the Dash and type “term” into the input box. Choose any one of the terminals listed:
Alternatively, access a console or terminal emulator using another method, such as SSH on Ubuntu Server or a terminal launcher in an alternative desktop environment.
Type the following line to add the Bitcoin Personal Package Archive (PPA) to your system:
sudo apt-add-repository ppa:bitcoin/bitcoin
You will be prompted for your user password. Provide it to continue. Afterwards, the following text will be displayed:
Stable Channel of bitcoin-qt and bitcoind for Ubuntu, and their dependencies
More info: https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin
Press [ENTER] to continue or ctrl-c to cancel adding it
Press enter to continue. The following text (with some variations) will be displayed and you will be returned to the command line prompt:
gpg: keyring /tmp/tmpixuqu73x/secring.gpg' created gpg: keyring/tmp/tmpixuqu73x/pubring.gpg' created gpg: requesting key 8842CE5E from hkp server > > > >keyserver.ubuntu.com gpg: /tmp/tmpixuqu73x/trustdb.gpg: trustdb created gpg: key 8842CE5E: public key "Launchpad PPA for Bitcoin" imported gpg: no ultimately trusted keys found gpg: Total number processed: 1 pg: imported: 1 (RSA: 1) OK
Type the following line to get the most recent list of packages:
sudo apt-get update
A large number of lines will be displayed as different update files are downloaded. This step may take several minutes on a slow Internet connection.
To continue, choose one of the following options
sudo apt-get install bitcoin-qt
sudo apt-get install bitcoind
sudo apt-get install bitcoin-qt bitcoind
After choosing what packages to install, you will be asked whether you want to proceed. Press enter to continue.
If you’re logged in as an administrative user with sudo access, you may log out. The steps in this section should be performed as the user you want to run Bitcoin Core. (If you’re an expert administrator, you can make this a locked account used only by Bitcoin Core.)
Before using the Bitcoin Core daemon, bitcoind, you need to create its configuration file with a user name and password. First create the .bitcoin directory, create (touch) the file, and set the file’s permissions so that only your user account can read it. From the terminal, type:
mkdir ~/.bitcoin touch ~/.bitcoin/bitcoin.conf chmod 600 ~/.bitcoin/bitcoin.conf
Then you can run the command bitcoind. It will print output similar to this:
bitcoind Error: To use the "-server" option, you must set a rpcpassword in the configuration file: /home/bitcoinorg/.bitcoin/bitcoin.conf It is recommended you use the following random password: rpcuser=bitcoinrpc rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions. It is also recommended to set alertnotify so you are notified of problems; for example: alertnotify=echo %s | mail -s "Bitcoin Alert" [email protected] The “rpcpassword” displayed will be unique for your system. You can copy the rpcuser and rpcpassword lines into your configuration file using the following commands. Note that in most Ubuntu terminals, you need to press Ctrl-Shift-C to copy and Ctrl-Shift-V to paste because Ctrl-C and Ctrl-V have different meanings in a Unix-style terminal.
echo rpcuser=bitcoinrpc >> ~/.bitcoin/bitcoin.conf echo rpcpassword=XXXXXX >> ~/.bitcoin/bitcoin.conf (Warning: Don’t use XXXXXX as your RPC password. Copy the rpcpassword displayed by bitcoind for your system.)
Now you can start Bitcoin Core daemon for real. Type the following command:
bitcoind -daemon
It will print a message that Bitcoin Core is starting. To interact with Bitcoin Core daemon, you will use the command bitcoin-cli (Bitcoin command line interface). Note: it may take up to several minutes for Bitcoin Core to start, during which it will display the following message whenever you use bitcoin-cli:
error: {"code":-28,"message":"Verifying blocks..."}
After it starts, you may find the following commands useful for basic interaction with your node:
to safely stop your node, run the following command:
bitcoin-cli stop
A complete list of commands is available in the Bitcoin.org developer reference.
When Bitcoin Core daemon first starts, it will begin to download the block chain. This step will take at least several hours, and it may take a day or more on a slow Internet connection or with a slow computer. During the download, Bitcoin Core will use a significant part of your connection bandwidth. You can stop Bitcoin Core at any time using the stop command; it will resume from the point where it stopped the next time you start it.
Optional: Start Your Node At Boot
Starting your node automatically each time your computer boots makes it easy for you to contribute to the network. The easiest way to do this is to start Bitcoin Core daemon from your crontab. To edit your crontab, run the following command:
crontab -e
@reboot bitcoind -daemon Save the file and exit; the updated crontab file will be installed for you. Now Bitcoin Core daemon will be automatically started each time your reboot your computer.
If you’re an Ubuntu expert and want to use an init script instead, see this Upstart script.
You have now completed installing Bitcoin Core. If you have any questions, please ask in one of Bitcoin’s many communities, such as Bitcoin StackExchange, BitcoinTalk technical support, or the #bitcoin IRC chatroom on Freenode.
To support the Bitcoin network, you also need to allow incoming connections. Please read the Network Configuration section for details.
Network Configuration
If you want to support the Bitcoin network, you must allow inbound connections.
When Bitcoin Core starts, it establishes 8 outbound connections to other full nodes so it can download the latest blocks and transactions. If you just want to use your full node as a wallet, you don’t need more than these 8 connections—but if you want to support lightweight clients and other full nodes on the network, you must allow inbound connections.
Servers connected directly to the Internet usually don’t require any special configuration. You can use the testing instructions below to confirm your server-based node accepts inbound connections.
Home connections are usually filtered by a router or modem. Bitcoin Core will request your router automatically configure itself to allow inbound connections to Bitcoin’s port, port 8333. Unfortunately many routers don’t allow automatic configuration, so you must manually configure your router. You may also need to configure your firewall to allow inbound connections to port 8333. Please see the following subsections for details.
Testing Connections
The BitNodes project provides an online tool to let you test whether your node accepts inbound connections. To use it, start Bitcoin Core (either the GUI or the daemon), wait 10 minutes, and then visit the GetAddr page (https://getaddr.bitnodes.io/). The tool will attempt to guess your IP address—if the address is wrong (or blank), you will need to enter your address manually.
For more instruction and reviews based off BTC please follow my subreddit /BTC_Reviews
all material from this post was found here --> https://bitcoin.org/en/full-node
submitted by Mattjhagen to BTC_Reviews [link] [comments]

Guide for first timers

I made this for my friends and family to use. Hope this heps someone. Much help!
bitcoins first: Get a wallet - just like physical money, you need a wallet to hold the money. use multibit - for a wallet - if you want options here a few http://bitcoin.org/en/choose-your-wallet go here and download this https://multibit.org/ how to backup your wallet https://multibit.org/help_backupWalletUsingPrivateKeys.html i recommend backing it up to at least 3 separate locations. example: harddrive, usb drive, encrypted dropbox folder.
go here to buy bitcoin also known as an exchange https://coinbase.com/?r=52dee75a8a2eed3e480000e5&utm_campaign=user-referral&src=referral-link
don't create wallet, click sign up button on top right. add bank information, and credit card info, and phone info - phone allows 2 factor authentication so your identity becomes much more difficult to fake and steal your money and information. I asked them to send me a SMS message instead of using app. this is the most reputable place to do this at. Never never use an online wallet!!!
buy some bitcoin on coinbase.com, and send yourself some bitcoin using your multibit wallet address(under the Request tab it shows your address there)
Now Dogecoin First get a wallet, - use the qt wallet. You can get it here for either Mac or Windows. http://dogecoin.com/ for linux use this guide - http://www.reddit.com/dogecoin/comments/1tvmnd/dogecoin_on_linux_the_complete_beginners_guide/
For a place to buy dogecoin. Use cryptsy, here is the link. https://www.cryptsy.com/users/register?refid=138894
click register new account. enter your information. go to your settings, and enable 2 factor authentication, use your cell phone number, and put in the number that they send to your phone. This makes it much more secure. you will send your bitcoins here and then buy dogecoin, then send the dogecoin to your wallet on your own computer. Backup the wallet after every purchase.
Send your Dogecoin to your own wallet. backup your wallet, at least 3 times. Use USB thumb drives. FYI, This might take away, the withdraw servers are slow as of right now. Took 3 days for me.
If you have any questions ask. Also you can buy Dogecoin or Bitcoin on ebay, do that at your own risk.
submitted by malak33 to dogecoin [link] [comments]

Need Help - Reindexing Blockchain

I need help here, for the last 5 days in a row I've been trying to download the Blockchain on Bitcoin-qt so that I can run Armory with offline transactions from my Raspberry Pi. Everything is already setup on my RPi, now I just need to download the block chain on my Online Armory client. This is proving harder than it looks…
I'm running my Online Armory client on Windows 8 OS booting from Virtualbox on my Mac OSX. The reason I have to use virtual box is the latest version of Armory for Mac glitches out and doesn't work for me.
So I've downloaded the bootstrap and placed it in the correct location and ran Bitcoin-qt, at this point (after 20-30 separate attempts) I've downloaded up to around "15 weeks behind" but once I get to around October 22nd, 2013 the blocks begin indexing extremely slow. I've tried booting the qt client with -reindex commands several times, I've tried booting qt with the -dbcache=1000 commands several times, and unfortunately I STILL have not completely downloading the block chain and I'm about to fucking murder someone because it should not be this difficult to download the block chain!!
So each time when I'm downloading the block chain it gets interrupted by one of two things. FIRST, sometimes around 15-14 weeks behind the qt client just "stops responding" and windows give me the option to close it out. After I close it and try to reboot, the database is unable to be found and I have to run the -reindex command and start all over. The SECOND thing that happens, is my Windows 8 OS running on virtual box will randomly go to a new screen that says "your product key is not correct, please enter a new one or buy another"… even though I initially entered a working product key when I first installed the OS and when I try to reenter another working product key (I've tried dozens) none of them work. So this blue screen interrupts my block chain download and at this point I haven't got past "15 weeks behind".
I've tried saving snapshots so that when the qt client stops responding or the windows 8 OS goes to that blue screen that says "reenter product key" I can restore from my last snapshot, but when i restore from an old snapshot one of those two problems continues to occur and prevents me from downloading any further than block 265502.
At this point I'm for a loss. I've done hours of searching and can't figure out how to fix this shit… can somebody help me out?
submitted by Marotta117 to Bitcoin [link] [comments]

Having trouble with the Bitcoin-QT program on Mac, can anyone help?

I have been trying to run the Bitcoin-QT wallet program for the past few days, and can't figure out whats stopping it from working.
I am using a Mac OSX (10.6.8), running Bitcoin-QT(v0.6.3-Beta)
The first time I opened the program, it began downloading transaction blocks at a slow, but steady, rate. I left the computer on overnight, hoping it would be done by morning. Alas, I awoke the next morning to find that not only had it not finished, but that it was stuck, and would download no more. On the bottom of the screen it shows that I am still "catching up", having downloaded 151291 of 185333 block transactions (%81.63, last block loaded from 313 days ago). It also shows "WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
I've tried restarting, rebooting, re downloading, all to no avail. Looking at the bitcoin website, it appears that 0.6.3 is the most recent client, so I'm not sure what I am meant to upgrade to.
If anyone can advise me on what to do, I would greatly appreciate it.
submitted by ArcaneDreamer to Bitcoin [link] [comments]

Working on an interface to Bitcoin-Qt's / bitcoind's API calls.

Right now, all it does that might be a bit handy is show you which addresses have how many bitcoins.
GitHub
Needed: python 2.7, wxPython 2.8
It is a bit rough at the moment, appearance-wise: a screenshot
I made this because the bitcoin-qt wallet does not have a way (that I've seen) to easily see all addresses, including un-labelled ones. There's the debug console, but that isn't really "easy", especially if you have a lot of addresses... I also use Armory, which will show you all addresses, but it is slow to start and a huge memory hog -- and it won't use the original client's wallet.
You'll need to set up the bitcoin.conf file to accept JSON-RPC commands (see this sample conf -- set server=1 and rpcuserpcpassword to whatever; this script will read them from the file)
It should work on Windows, *nix, and Mac, but I've only tested it in Windows.
If there's any interest, I might work on fleshing this out into a fuller interface. There's a lot of API calls that might be of use to someone.
PS: if you can think of a better name than "advbtc" please suggest it; I am terrible at naming things.
submitted by lowpass to Bitcoin [link] [comments]

Increase slow download and sync of bitcoin blockchain on Mac What is NAMECOIN BITCOIN'S First Fork - YouTube Turn key Bitcoin mining solution Ebay auction - YouTube How To Mine Bitcoin - YouTube Bitcoin Wallet Recovery

Limiting Bitcoin Bandwidth on Windows. On Windows, there are a few choices available for limiting the bandwidth of an application. Two of the more popular ones are NetLimiter ($29.95, 30-day trial) and NetBalancer (Free version with limitations, full version $49.95). The free version of NetBalancer allows the user to limit the bandwidth of up to 3 apps at once, and since we only need to limit ... I am following the instructions for the MacOS X port version to build bitcoind, but make finally cannot find a makefile to continiue the build: ginger:bitcoin sven.haiges$ ./autogen.sh autoreconf: Does Bitcoin-Qt require that I create a bitcoin.conf file in order to solo mine on my Mac? I created one after reading the wiki and placed it in Lib/AppSupp/Bitcoin but I am not sure I needed to. ... Modernise macOS cross-compilation toolchain Cherry-picked from the following upstream PRs: - bitcoin/bitcoin#13617 - Excluding the QT GUI changes. - bitcoin/bitcoin#17550 - bitcoin/bitcoin#16392 - Excluding the QT GUI changes. - bitcoin/bitcoin#18589 - bitcoin/bitcoin#19240 - bitcoin/bitcoin#19407 - bitcoin/bitcoin#17919 - Only the ancillary changes, not the `FORCE_USE_SYSTEM_CLANG` change ... Note: many operating systems today (Windows, Mac, and Linux) enter a low-power mode after the screensaver activates, slowing or halting network traffic. This is often the default setting on laptops and on all Mac OS X laptops and desktops. Check your screensaver settings and disable automatic “sleep” or “suspend” options to ensure you support the network whenever your computer is ...

[index] [40806] [20069] [38411] [14302] [37802] [18744] [43264] [37463] [18680] [37685]

Increase slow download and sync of bitcoin blockchain on Mac

What is NAMECOIN BITCOIN'S First Fork http://youtu.be/oBkhPhu3_B4 Test Scanning Stainless Steel BITCOIN WALLET view http://youtu.be/P3Cny4iX-CM Why the block... Smart Wallet BitCoin, Credit Cards BITCOIN PRICE , BITCOIN FUTURE in doubt http://youtu.be/eO-yrpQpIT8 What is NAMECOIN BITCOIN'S First Fork http://youtu.be/... How to buy Bitcoins with a paysafecard BITCOIN PRICE , BITCOIN FUTURE in doubt http://youtu.be/eO-yrpQpIT8 What is NAMECOIN BITCOIN'S First Fork http://youtu... Sign up for Private Internet Access VPN at https://lmg.gg/pialinus2 CUK USA: Powerful, attractive, and affordable, check out these gaming desktops starting a... When you are experiencing a slow download and synchronisation of the bitcoin blockchain this little tutorial might be of help. We will disable power nap feature for our system to stop macOS from ...

#