Bitcoin (free) download Windows version

In early 2013, it became a common belief that new Bitcoin users should not be recommended Bitcoin-QT, the full node client. Bitcoin.org was changed to no longer exclusively recommend it. Two years later, the block size conservatives are saying the drop in full node count was due to block size

I distinctly remember that the recommending of Bitcoin-QT to new Bitcoin users became a faux pas in early 2013. It was claimed that regular people should download and install an SPV client like Multibit.
Predictably, there was a large drop in the full node count, as the wallet market became dominated by a large number of new, light clients, and the most trafficked Bitcoin website, bitcoin.org, stopped exclusively recommending people to install Bitcoin-QT.
Now, we have important developers like Luke-Jr claiming that this 95% drop in full node count can be mainly attributed to the growing size of the block chain, despite the fact that the drop began right when light clients began being recommended..
EDIT to add some data:
This is the image that GMaxwell and Peter Todd, two individuals who are conservative about the block size (in particular Peter Todd, who's been warning about increasing the 1 MB size limit since 2013), have linked to to make their point about the full node count:
http://i.imgur.com/EL0zHRe.jpg
Up until at least March 18, 2013, the only client recommended to visitors of bitcoin.org was Bitcoin-QT, and an installation link for it was provided right on the landing page:
https://web.archive.org/web/20130318211940/http://bitcoin.org/
The WayBack Machine shows that by March 25th, 2013, this had changed, and a 'Choose Your Wallet' button appeared on Bitcoin.org/:
https://web.archive.org/web/20130513214959/http://bitcoin.org/en/
From March 25th 2013 onward, the number of non-full-node wallets recommended by bitcoin.org increased, in response to a general increase in the number of high quality and/or well marketed light and mobile wallets on the market.
Now a days, Bitcoin-QT is one of twelve clients displayed on bitcoin.org's Choose Your Wallet page:
https://bitcoin.org/en/choose-your-wallet
Other than Bitcoin-QT and Bitcoin Armory, all of them are non-full-node clients.
This shift, from a wallet market where only Bitcoin-QT was available and recommended to one that is increasingly diverse and dominated by light clients, coincides with the point (Spring 2013) where we start seeing a rapid decline in the full node count.
submitted by aminok to Bitcoin [link] [comments]

Electrum 2.9.0 released

Release 2.9 - Independence (July 27th, 2017)

submitted by keystrike to Bitcoin [link] [comments]

Bitcoin wallets are inaccessible for blind people

So I am a fully blind person who uses a screen reader and every bitcoin wallet I have downloaded (Bitcoin QT, Multibit, Armory) are inaccessible to my screenreader.
This is making me very annoyed as I am a bitcoin supporter and I have acquired my own bitcoin I just cant god damn use them with out getting help from someone else. Multibit Is a java based wallet and as such, could have easily been made accessible if the Java accessibility JDk were included from the start. If we want bitcoin to truly be successful, this has to be dealt with. Any ideas outhere in the readit ethos??
Oh and by the way, when I signed up for readit, I had to fill in a visual captia (which I had to get someone to help me) and as if that was not enough, for posting in this readit forum, I have to get someone to help me fill in another visual captia before I submit. I was going to donate some bitcoin to this forum, but obviously that is a little bit hard when I cannot even really access my bitcoins from my wallet. Kind of makes me not wan to donate now.
Does anybody know of a wallet that would be accessible to screenreaders?
yIf there is not one, does any one know a developer that would take some time to build or develop one? I am sure it would not be all that hard if lets say an open source, java based wallet were redeveloped to include the accessibility JDK/API.
Thanks '
Okay I am going to append a couple of comments to this if I can figure it out:
first thanks for the amazing response!
Second, although I have been creeping the Readit Bitcoin forums for a while, I have never actually posted or interacted and have only been a member for a couple of days so I am a bit clueless as to how to engage the forum and I think I actually posted this same post (above) a fewe times by accident (sorry).
So in response to to some of the comments in general, I am a marginally technically capable blind screen reader user, and as such do not mind spending the time to learn anyway that will help me access the bitcoin technology. That being said, part of the reasoning behind making wallets accessible is so that people who are not technically inclined ( blind or not blind) will be able to more readily access Bitcoins and as such, adoption and uptake will be more fricktionless making the technology more appealing. accessibility for the blind and usability for the sighted are two sides of the same coin in that one compliments the other.
in term terms of the braille suggestions, I am interested, however I only started learning braille recently and I am only in grade one as I have been blind for only five years, so I have a ways to go in that regard.
submitted by garmondbozia to Bitcoin [link] [comments]

PSA: Clearing up some misconceptions about full nodes

It's time to clear up some misconceptions floating around about full nodes.
Myth: There are only about 5500 full nodes worldwide
This number comes from this site and it measured by trying to probe every nodes on their open ports.
Problem is, not all nodes actually have open ports that can be probed. Either because they are behind firewalls or because their users have configured them to not listen for connections.
Nobody knows how many full nodes there are, since many people don't know how to forward ports behind a firewall, and bandwidth can be costly, its quite likely that the number of nodes with closed ports is at least another several thousand.
Nodes with open ports are able to upload blocks to new full nodes. In all other ways they are the same as nodes with closed ports. But because open-port-nodes can be measured and closed-port-nodes cannot, some members of the bitcoin community have been mistaken into believing that open-port-nodes are that matters.
Myth: This number of nodes matters and/or is too low.
Nodes with open ports are useful to the bitcoin network because they help bootstrap new nodes by uploading historical blocks, they are a measure of bandwidth capacity. Right now there is no shortage of bandwidth capacity, and if there was it could be easily added by renting cloud servers.
The problem is not bandwidth or connections, but trust, security and privacy. Let me explain.
Full nodes are able to check that all of bitcoin's rules are being followed. Rules like following the inflation schedule, no double spending, no spending of coins that don't belong to the holder of the private key and all the other rules required to make bitcoin work (e.g. difficulty)
Full nodes are what make bitcoin trustless. No longer do you have to trust a financial institution like a bank or paypal, you can simply run software on your own computer. To put simply, the only node that matters is the one you use
Myth: There is no incentive to run nodes, the network relies on altruism
It is very much in the individual bitcoin's users rational self interest to run a full node and use it as their wallet.
Using a full node as your wallet is the only way to know for sure that none of bitcoin's rules have been broken. Rules like no coins were spent not belonging to the owner, that no coins were spent twice, that no inflation happens outside of the schedule and that all the rules needed to make the system work are followed (e.g. difficulty.) All other kinds of wallet involve trusting a third party server.
All these checks done by full nodes also increase the security. There are many attacks possible against lightweight wallets that do not affect full node wallets.
This is not just mindless paranoia, there have been real world examples where full node users were unaffected by turmoil in the rest of the bitcoin ecosystem. The 4th July 2015 accidental chain fork effected many kinds of wallets. Here is the wiki page on this event https://en.bitcoin.it/wiki/July_2015_chain_forks#Wallet_Advice
Notice how updated node software was completely unaffected by the fork. All other wallets required either extra confirmations or checking that the third-party institution was running the correct version.
Full nodes wallets are also currently the most private way to use Bitcoin, with nobody else learning which bitcoin addresses belong to you. All other lightweight wallets leak information about which addresses are yours because they must query third-party servers. The Electrum servers will know which addresses belong to you and can link them together. Despite bloom filtering, lightweight wallets based on BitcoinJ do not provide much privacy against nodes who connected directly to the wallet or wiretappers.
For many use cases, such privacy may not be required. But an important reason to run a full node and use it as a wallet is to get the full privacy benefits.
Myth: I can just set up a node on a cloud server instance and leave it
To get the benefits of running a full node, you must use it as your wallet, preferably on hardware you control.
Most people who do this do not use a full node as their wallet. Unfortunately because Bitcoin has a similar name to Bittorrent, some people believe that upload capacity is the most important thing for a healthy network. As I've explained above: bandwidth and connections are not a problem today, trust, security and privacy are.
Myth: Running a full node is not recommended, most people should use a lightweight client
This was common advice in 2012, but since then the full node software has vastly improved in terms of user experience.
If you cannot spare the disk space to store the blockchain, you can enable pruning. In Bitcoin Core 0.12, pruning being enabled will leave the wallet enabled. Altogether this should require less than 900MB of hard disk space.
If you cannot spare the bandwidth to upload blocks to other nodes, there are number of options to reduce or eliminate the bandwidth requirement. These include limiting connections, bandwidth targetting and disabling listening. Bitcoin Core 0.12 has the new option -blocksonly, where the node will not download unconfirmed transaction and only download new blocks. This more than halves the bandwidth usage at the expense of not seeing unconfirmed transactions.
Synchronizing the blockchain for a new node has improved since 2012 too. Features like headers-first and libsecp256k1 have greatly improved the initial synchronization time.
It can be further improved by setting -dbcache=3000 which keeps more of the UTXO set in memory. It reduces the amount of time reading from disk and therefore speeds up synchronization. Tests showed that the entire blockchain can now be synchronized in less than 3 and a half hours (Note that you'll need Bitcoin Core 0.12 or later to get all these efficiency improvements) Another example with 2h 25m
How to run a full node as your wallet.
I think every moderate user of bitcoin would benefit by running a full node and using it as their wallet. There are several ways to do this.
So what are you waiting for? The benefits are many, the downsides are not that bad. The more people do this, the more robust and healthy the bitcoin ecosystem is.
Further reading: http://www.truthcoin.info/blog/measuring-decentralization/
submitted by belcher_ to Bitcoin [link] [comments]

Secure paper wallet tutorial

This is my handout for paranoid people who want a way to store bitcoin safely. It requires a little work, but this is the method I use because it should be resistant to risks associated with:
  1. Bad random number generators
  2. Malicious or flawed software
  3. Hacked computers
If you want a method that is less secure but easier, skip to the bottom of this post.
The Secure Method
  1. Download bitaddress.org. (Try going to the website and pressing "ctrl+s")
  2. Put the bitaddress.org file on a computer with an operating system that has not interacted with the internet much or at all. The computer should not be hooked up to the internet when you do this. You could put the bitaddress file on a USB stick, and then turn off your computer, unplug the internet, and boot it up using a boot-from-CD copy of linux (Ubuntu or Mint for example). This prevents any mal-ware you may have accumulated from running and capturing your keystrokes. I use an old android smart phone that I have done a factory reset on. It has no sim-card and does not have the password to my home wifi. Also the phone wifi is turned off. If you are using a fresh operating system, and do not have a connection to the internet, then your private key will probably not escape the computer.
  3. Roll a die 62 times and write down the sequence of numbers. This gives you 2160 possible outcomes, which is the maximum that Bitcoin supports.
  4. Run bitaddress.org from your offline computer. Input the sequence of numbers from the die rolls into the "Brain Wallet" tab. By providing your own source of randomness, you do not have to worry that the random number generator used by your computer is too weak. I'm looking at you, NSA ಠ_ಠ
  5. Brain Wallet tab creates a private key and address.
  6. Write down the address and private key by hand or print them on a dumb printer. (Dumb printer means not the one at your office with the hard drive. Maybe not the 4 in 1 printer that scans and faxes and makes waffles.) If you hand copy them you may want to hand copy more than one format. (WIF and HEX). If you are crazy and are storing your life savings in Bitcoin, and you hand copy the private key, do a double-check by typing the private key back into the tool on the "Wallet Details" tab and confirm that it recreates the same public address.
  7. Load your paper wallet by sending your bitcoin to the public address. You can do this as many times as you like.
  8. You can view the current balance of your paper wallet by typing the public address into the search box at blockchain.info
  9. If you are using an old cell phone or tablet do a factory reset when you are finished so that the memory of the private keys is destroyed. If you are using a computer with a boot-from-CD copy of linux, I think you can just power down the computer and the private keys will be gone. (Maybe someone can confirm for me that the private keys would not be able to be cached by bitaddress?)
  10. To spend your paper wallet, you will need to either create an offline transaction, or import the private key into a hot wallet. Creating an offline transaction is dangerous if you don't know what you are doing. Importing to a client side wallet like Bitcoin-Qt, Electrum, MultiBit or Armory is a good idea. You can also import to an online wallet such as Blockchain.info or Coinbase.
Trusting bitaddress.org
The only thing you need bitaddress.org to do is to honestly convert the brainwallet passphrase into the corresponding private key and address. You can verify that it is doing this honestly by running several test passphrases through the copy of bitaddress that you plan on using, and several other brainwallet generators. For example, you could use the online version of bitaddress, and brainwallet and safepaperwallet and bitcoinpaperwallet. If you are fancy with the linux command line, you can also try "echo -n my_die_rolls | sha256sum". The linux operating system should reply with the same private key that bitaddress makes. This protects you from a malicious paper wallet generator.
Trusting your copy of bitaddress.org
Bitaddress publishes the sha1 hash of the bitaddress.org website at this location:
https://www.bitaddress.org/pgpsignedmsg.txt
The message is signed by the creator, pointbiz. I found his PGP fingerprint here:
https://github.com/pointbiz/bitaddress.org/issues/18
"527B 5C82 B1F6 B2DB 72A0 ECBF 8749 7B91 6397 4F5A"
With this fingerprint, you can authenticate the signed message, which gives you the hash of the current bitaddress.org file. Then you can hash your copy of the file and authenticate the file.
I do not have a way to authenticate the fingerprint itself, sorry. According to the website I linked to, git has cryptographic traceability that would enable a person to do some research and authenticate the fingerprint. If you want to go that far, knock yourself out. I think that the techniques described in this document do not really rely on bitaddress being un-corrupt. Anyway, how do we know pointbiz is a good guy? ;-)
There are a lot of skilled eyes watching bitaddress.org and the signed sha1 hash. To gain the most benefit from all of those eyes, it's probably worthwhile to check your copy by hashing it and comparing to the published hash.
"But we aren't supposed to use brainwallets"
You are not supposed to use brainwallets that have predictable passphrases. People think they are pretty clever about how they pick their passphrases, but a lot of bitcoins have been stolen because people tend to come up with similar ideas. If you let dice generate the passphrase, then it is totally random, and you just need to make sure to roll enough times.
How to avoid spending your life rolling dice
When I first started doing this, I rolled a die 62 times for each private key. This is not necessary. You can simply roll the die 62 times and keep the sequence of 62 numbers as a "seed". The first paper address you create would use "my die rolls-1" as the passphrase, the second would be "my die rolls-2" and so on. This is safe because SHA256 prevents any computable relationship between the resulting private key family.
Of course this has a certain bad security scenario -- if anyone obtains the seed they can reconstruct all of your paper wallets. So this is not for everyone! On the other hand, it also means that if you happen to lose one of your paper wallets, you could reconstruct it so long as you still had the seed.
One way to reduce this risk is to add an easy to remember password like this: "my die rolls-password-1".
If you prefer, you can use a technique called diceware to convert your die rolls to words that still contain the same quantity of entropy, but which could be easier to work with. I don't use diceware because it's another piece of software that I have to trust, and I'm just copy/pasting my high entropy seed, so I don't care about how ugly it is.
Why not input the dice as a Base 6 private key on the Wallet Details tab?
Two reasons. First of all, this option requires that you roll the die 99 times, but you do not get meaningful additional protection by rolling more than 62 times. Why roll more times if you don't have to? Second, I use the "high entropy seed" method to generate multiple private keys from the same die rolls. Using the Base 6 option would require rolling 99 times for every private key.
I'm a big nerd with exotic dice. How many times to roll?
Put this formula in Excel to get the number of times to roll: "=160*LOG(2,f)" where f = number of faces on the die. For example, you would roll a d16 40 times. By the way, somewhat unbelievably casino dice are more fair than ordinary dice
The "Change address" problem:
You should understand change addresses because some people have accidentally lost money by not understanding it.
Imagine your paper wallet is a 10 dollar bill. You use it to buy a candy bar. To do this you give the cashier the entire 10 dollar bill. They keep 1 dollar and give you 9 dollars back as change.
With Bitcoin, you have to explicitly say that you want 9 dollars back, and you have to provide an address where it should go to. If you just hand over the 10 dollar bill, and don't say you want 9 dollars back, then the miner who processes the transaction gives 1 dollar to the store and keeps the remainder themselves.
Wallet software like Bitcoin-Qt handles this automatically for you. They automatically make "change addresses" and they automatically construct transactions that make the change go to the change address.
There are three ways I know of that the change problem can bite you:
  1. You generate a raw transaction by hand, and screw up. If you are generating a transaction "by hand" with a raw transaction editor, you need to be extra careful that your outputs add up to the same number as your inputs. Otherwise, the very lucky miner who puts your transaction in a block will keep the difference.
  2. You import a paper wallet into a wallet software and spend part of it, and then think that the change is in the paper wallet. The change is not in the paper wallet. It is in a change address that the wallet software generated. That means that if you lose your wallet.dat file you will lose all the change. The paper wallet is empty.
  3. You import a paper wallet into a wallet software and spend part of it, and then think that the change is in the change address that the wallet software generated. If the transaction did not need to consume all of the "outputs" used to fund the paper wallet, then there could be some unspent outputs still located at the address of the paper wallet. If you destroyed the paper wallet, and destroyed the copy of the private key imported to the wallet software, then you could not access this money. (E.g. if you restored the software wallet from its seed, thinking all of the money was moved to the wallet-generated change addresses.)
For more on this, see here
The hot paper wallet problem
Your bitcoin in your paper wallet are secure, so long as the piece of paper is secure, until you go to spend it. When you spend it, you put the private key onto a computer that is connected to the internet. At this point you must regard your paper wallet address as hot because the computer you used may have been compromised. It now provides much less protection against theft of your coins. If you need the level of protection that a cold paper wallet provides, you need to create a new one and send your coins to it.
Destroying your paper wallet address
Do not destroy the only copy of a private key without verifying that there is no money at that address. Your client may have sent change to your paper wallet address without you realizing it. Your client may have not consumed all of the unspent outputs available at the paper wallet address. You can go to blockchain.info and type the public address into the search window to see the current balance. I don't bother destroying my used/empty paper wallet addresses. I just file them away.
Encrypting your private key
BIP 0038 describes a standardized way to encrypt your paper wallet private key. A normal paper wallet is vulnerable because if anyone sees the private key they can take the coins. The BIP38 protocol is even resistant to brute force attacks because it uses a memory intensive encryption algorithm called scrypt. If you want to encrypt your wallets using BIP38, I recommend that you use bitcoinpaperwallet because they will let you type in your own private key and will encrypt it for you. As with bitaddress, for high security you should only use a local copy of this website on a computer that will never get connected to the internet.
Splitting your private key
Another option for protecting the private key is to convert it into multiple fragments that must be brought together. This method allows you to store pieces of your key with separate people in separate locations. It can be set up so that you can reconstitute the private key when you have any 2 out of the 3 fragments. This technique is called Shamir's Secret Sharing. I have not tried this technique, but you may find it valuable. You could try using this website http://passguardian.com/ which will help you split up a key. As before, you should do this on an offline computer. Keep in mind if you use this service that you are trusting it to work properly. It would be good to find other independently created tools that could be used to validate the operation of passguardian. Personally, I would be nervous destroying the only copy of a private key and relying entirely on the fragments generated by the website.
Looks like Bitaddress has an implementation of Shamir's Secret Sharing now under the "Split Wallet" tab. However it would appear that you cannot provide your own key for this, so you would have to trust bitaddress.
Durable Media
Pay attention to the media you use to record your paper wallet. Some kinds of ink fade, some kinds of paper disintegrate. Moisture and heat are your enemies.
In addition to keeping copies of my paper wallet addresses I did the following:
  1. Order a set of numeric metal stamps. ($10)
  2. Buy a square galvanized steel outlet cover from the hardware store ($1)
  3. Buy a sledgehammer from the hardware store
  4. Write the die rolls on the steel plate using a sharpie
  5. Use the hammer to stamp the metal. Do all the 1's, then all the 2's etc. Please use eye protection, as metal stamp may emit sparks or fly unexpectedly across the garage. :-)
  6. Use nail polish remover to erase the sharpie
Electrum
If you trust electrum you might try running it on an offline computer, and having it generate a series of private keys from a seed. I don't have experience with this software, but it sounds like there are some slick possibilities there that could save you time if you are working with a lot of addresses.
Message to the downvoters
I would appreciate it if you would comment, so that I can learn from your opinion. Thanks!
The Easy Method
This method is probably suitable for small quantities of bitcoin. I would not trust it for life-altering sums of money.
  1. Download the bitaddress.org website to your hard drive.
  2. Close your browser
  3. Disconnect from the internet
  4. Open the bitaddress.org website from your hard drive.
  5. Print a paper wallet on your printer
  6. Close your browser
submitted by moral_agent to BitcoinWallet [link] [comments]

WARNING: A fake electrum website with malware is advertising on duckduckgo and yahoo.

If you perform a search for electrum on duckduckgo or yahoo, an ad claiming to be electrum.org will be at the top.
In reality the ad links to: electrum-bitcoin org
The domain was created December 21.
This site is nearly identical to electrum.org except the download links give different files. All three of the files that can be download are much smaller than the real electrum and are most likely malware. The three files are: electrum.exe - 91136 bytes electrum.out - 60316 bytes electrum.zip - 32478 bytes
EDIT: Some Advice:
When installing software, especially something as import as wallet software, it is a good idea to verify the integrity of the download with a signature using a key that was obtained from one or more seperate sources.
I made a list of the keys used to sign popular bitcoin wallets below to act as another source to verify the integrity of those keys.
Bitcoin-Qt: Signer: Gavin Andresen [email protected] Fingerprint: 2664 6D99 CBAE C9B8 1982 EF60 29D9 EE6B 1FC7 30C1 Key ID: 1FC730C1 Key Link: bitcoin.org/gavinandresen.asc
Electrum: Signer: ThomasV [email protected] Fingerprint: 6694 D8DE 7BE8 EE56 31BE D950 2BD5 824B 7F94 70E6 Key ID: 7F9470E6 Keyserver: pool.sks-keyservers.net
Multibit: Signer: Jim Burton (multibit.org developer) [email protected] Fingerprint: 299C 423C 672F 47F4 756A 6BA4 C197 2AED 79F7 C572 Key ID: 79F7C572 Keyserver: pgp.mit.edu
Armory: Signer: Alan C. Reiner (Offline Signing Key) [email protected] Fingerprint: 821F 1229 36BD D565 366A C36A 4AB1 6AEA 9883 2223 Key ID: 98832223 Keyserver: pgp.mit.edu
The signatures provided for some of the wallets are signatures of the hash values, so be sure to verify that the hash of the downloaded file matches the hash that was signed.
EDIT: GPG Examples:
Verifying Bitcoin-Qt:
First download, import and check Gavin's key:
Download his key at bitcoin.org/gavinandresen.asc
In terminal or command line run:
gpg --import gavinandresen.asc gpg --fingerprint 
Check that the fingerprint for Gavin's key matches 01CD F462 7A3B 88AA E4A5 71C8 7588 242F BE38 D3A8.
Then download the wallet software and signature.
Verify the signature:
gpg --verify SHA256SUMS.asc 
You should see:
gpg: Good signature from "Gavin Andresen (CODE SIGNING KEY) " 
The signature for Bitcoin-Qt signs the hash values. So we must compute the hash of the downloaded software. This example is using the linux version.
gpg --print-md SHA256 bitcoin-0.8.6-linux.tar.gz 
Check that the output matches the associated hash value in SHA256SUMS.asc
Verifying Electrum:
First download, import and check ThomasV's key:
This key can be found at a keyserver.
gpg --keyserver pool.sks-keyservers.net --recv-keys 7F9470E6 gpg --fingerprint 
Check the fingerprint.
Download Electrum and the signature.
Verify the signature:
gpg --verify Electrum-1.9.6.zip.asc 
You should see:
gpg: Good signature from "ThomasV " 
For this example you do not need to compute any hash values because the signature is signing the downloaded file directly.
submitted by dcc4e to Bitcoin [link] [comments]

My first experience with bitcoin was NOT positive :( + Questions

After seeing an interesting comment on /funny in which bitcoin currency is used to make tips across reddit I started to investigate and learn about the Bitcoin. I had heard about it before but I didn't know how it worked or what I had to do in order to use it.
A dozen Bitcoin Wiki entries later I download bitcoin-qt and create my first wallet. The system seemed very easy and straightforward and I had already started to apply for "free starter bitcoins" when I met "synchronization".
Now synchronization is not necessarily a deal breaker but it was annoying as hell. I'm using an old computer and it seemed as if it would take at least a day if not more to complete the whole process... and during that time my computer was getting slow as hell.
Now I'm quite a tech savy person and I know why in this P2P based system this is important, but for anyone else this would be unacceptable. Imagine elder people or not so tech savy persons trying out the system for the first time and noticing that they can't use it without occupying 2+ GiB of their HardDrive and having to wait a lot.
I did not complete the sync and tried to use the multibit instead. But since I had already applied to the Free starter bitcoins on some websites I wanted to keep my old wallet. I try to look for an import/export button but it seems that Bitcoin-qt doesn't support exportation and I needed to use a third party application called pywallet (command line!) to export my wallet and convert it into another plaintext format since the format used by bitcoin-qt was not supported by multibit.
And one would assume that the first thing you do when creating such a currency is to define a standard for the wallet and the applications. Again, I know how to use the command line but anyone who doesn't and who just wants to try out the system for the first time would be inmediately turned off by this limitation.
These are all issues that need to be fixed and addressed. Also, at the current situation it is much more comfortable and easier to set up an e-wallet than using standalone software on my computer. And if you ask me, it beats the purpose of creating a decentralized currency when in the end the most popular e-wallet services are going to hold most bitcoins and suppose a great security risk.
So I ask you: do you know any solutions to the above mentioned problems? Is there any way to reduce the impact by those hindrances?
And now to the questions:
Since I'm a very inquisitive mind and I'm still very much interested in bitcoins I would like to ask some questions I couldn't find properly answered in the wiki about the nature of the bitcoin system and how exactly it works.
I'd be very grateful if you could answer any of the following questions:
1. What exactly is a bitcoin? A string of text? A hash? A file with a string of text?
2. If I'm not mistaken, a bitcoin wallet is made of a public key and a private key. If I want to transfer my wallet from one program to another or a piece of paper... would I need to export or print out the strings of text that form the bitcoins itself or do I just need those two keys?
3. How does the bitcoin system know how much balance is inside an wallet/account. Does it typically ONLY check it against the chainblock or does it also make use of any bitcoin strings stored inside the wallet?
4. Cryptographically speaking... what happens when I transfer bitcoins?
Thank you!
*Please don't downvote me just because my first experience was negative. I'm still very interested and would like to learn a lot more. *
Edit: Thank you very much for all your answers! I can't reply to all of you (mainly because it's very late over here) but I feel that I understand the concept much better and also feel much more comfortable knowing that the only thing I ever need is my private and public key. It makes me care much less about software and wallet.data files, knowing that I can have everything I need written on piece of paper or saved in an encrypted file of my own. Then, when I need to spend bitcoins or check my balance I can use whatever software I deem best at the moment.
Thank you!
submitted by DanielTaylor to Bitcoin [link] [comments]

Why don't more people use electrum?

Is it just me or do not many people use this client? I love it because after writing down the seed, I never have to worry about "losing" my keys. It's also extremely lightweight, really easy to set a password, and the UI looks pretty good.
My question is: why do people generally prefer using bitcoin-QT, which requires a full download of the block chain, or Multibit, which didn't make it easy to encrypt for a long time?
Edit: here is a link to the client site where you can learn more and download it: http://electrum.org/
Basically, it's a bitcoin client like bitcoin qt but your keys are deterministic ally generated from a seed AND the client sends transactions to servers instead of processing transactions itself (all encrypted), obviating the need to download the whole block chain. The benefit of generating keys from a seed is that remembering a seed is all that's necessary to back up the wallet. Want to run it on another computer? Just download electrum, input the seed, and all your bitcoins will be there ready to spend instantly.
submitted by iamn to Bitcoin [link] [comments]

Bitcoin Wallets are not accessible for blind people

So I am a fully blind person who uses a screen reader and every bitcoin wallet I have downloaded (Bitcoin QT, Multibit, Armory) are inaccessible to my screenreader.
This is making me very annoyed as I am a bitcoin supporter and I have acquired my own bitcoin I just cant god damn use them with out getting help from someone else. Multibit Is a java based wallet and as such, could have easily been made accessible if the Java accessibility JDk were included from the start of development. If we want bitcoin to truly be successful, this has to be dealt with. Any ideas outhere in the readit ethos??
Oh and by the way, when I signed up for readit, I had to fill in a visual captia (which I had to get someone to help me) and as if that was not enough, for posting in this readit forum, I have to get someone to help me fill in another visual captia before I submit. I was going to donate some bitcoin to this forum, but obviously that is a little bit hard when I cannot even really access my bitcoins from my wallet or even read the captias. Kind of makes me not wan to donate now.
Does anybody know of a wallet that would be accessible to screenreaders?
If there is not one, does any one know a developer that would take some time to build or develop one? I am sure it would not be all that hard if lets say an open source, java based wallet were redeveloped to include the accessibility JDK/API.
Thanks
submitted by garmondbozia to Bitcoin [link] [comments]

opening an old wallet.dat

I had about $8 USD worth of bitcoin in a wallet, and I backed up the wallet.dat to my dropbox. According to the modified date of the file this was in April 2013, so it was probaby from bitcoin qt version 0.8.1, or maybe a little earlier.
I basically left it there and haven't done anything with bitcoin since then. Since it is worth probably at least $100 now I decided to check the exact amount.
I downloaded the latest version of bitcoin core, added the wallet.dat file to the data directory, started it with -rescan, and waited almost a month (!) for the blockchain data to get up to date. The balance showed as 0 the whole time. I thought it would update once the blockchain was totally downloaded, but it still just says 0.
Is this a problem with old vs new versions? Did I do something wrong? Next time, should I expect the balance to show a non-zero amount even if I haven't downloaded the whole blockchain yet?
Update: ok, I feel kind of dumb, turns out the transaction was made in a multibit wallet, not a bitcoin qt wallet, but I still have a copy of that too. I opened the wallet in the latest version of multibit classic, and it has the receiving address in question, and checking the address on blockchain.info I can see that it received the transaction... but the transaction and the balance both don't show in the program. I wonder if I need the same multibit version I had before? the transaction was made in feb 2014
Update 2: was able to use the private key to sweep the balance into electrum
submitted by valanbrown to Bitcoin [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]

Difficult to purchase doge in my local currency so this is what I'm gonna do

Background: I used to be able to acquire doge relatively easily in local currency (Malaysian Ringgit) from local sellers like lincoln_lava (hey sister shibe, where are you nowadays? no news mate?) and from localdogecoin. It was a great experience to use local bank transfer instead of PayPal or Skrill. The fun at localdogecoin was short-lived as all the local sellers slowly left the market possibly due to the declining price of doge. See for yourself, it’s empty offering in localdogecoin https://www.localdogecoin.com/eng/buy/MY ughhh!
My plan to buy doge:
Buy BTC in local currency bank account
Deposit BTC to prelude.io
Exchange BTC to doge at prelude.io (preferably at 100 Satoshi, yummy!)
Withdraw doge from prelude.io to my wallet-qt
The edits below will document each step until I finally get my doge love!
EDIT 1: About a week ago, Numoni Pte Ltd (a Singaporean company), has installed a BTC ATM at Bangsar Shopping Centre. It is about an hour drive from my place. The ATM launching appeared in some local media (read here: http://www.lowyat.net/2014/03/first-bitcoin-vending-machines-appear-in-malaysia). So yesterday, I braved the horrendous traffic and paid expensive parking to go to this so-called high-end shopping mall. I made my way to the advertised shop, which seems like a mobile/PC hardware selling stuff. No BTC ATM there! The staff said Numoni took it away a few days ago sigh. Given that the ATM launching was around 3/27, it was probably taken away about 2-3 days after going live, ughh! Anyway, I’ve posted on Numoni’s FB page and currently waiting for their definitive answer. On the bright side, Chili’s quesadilla and nachos at the mall were all good. Burppp! Oh yes!
EDIT 2: As the ATM route was bust, I checked out localbitcoins. It seems more promising as there are plenty of local sellers that will accept fiat from my local bank accounts. I’ve raised BTC purchase request and am currently waiting for the seller to respond. It is midnight here so nothing much to do until tomorrow. Grrr! OK, I've gotten my BTC, yay! Time to hit prelude.io
EDIT 3: Nothing yet but hopefully this is the part where I receive my BTC to my light wallet (Hive? Electrum? Multibit? Any suggestion?) I've downloaded electrum. Nice, clean interface. But man, BTC does take sometime to be moved to and fro. Grrr! (again!)
EDIT 4: Nothing yet but hopefully this is the part where I trade all BTC to doge at prelude.io and transfer my baby doge to my local wallet After 1.5hrs, my BTC finally appears on prelude.io, well, still faster than international wire, right? Time to embrace those doge! Put buy order at 107 (I know I said 100 satoshis above but who am I kidding, LOL). Order went through easily! Great job moolah_
EDIT 5: Nothing yet but hopefully I won’t have to use this edit section. It can’t be that complicated, right? (-vvv-) It's time to transfer these baby doge to my wallet-qt. WOW, such easy!
OK, time to summarize:
Maybe some of you shibes will ask why I don’t register my local bank account with kraken, prelude, VOS, etc. I believe the verification will take some time (well, I’m not American, Canadian or European) and the international wire transfer is both expensive and time-consuming. I hope my assumption is correct on this one, though. TOO THE MOON!
submitted by xixabangma to dogecoin [link] [comments]

Frustrated with wallets - could THIS be the stake through the heart of Bitcoin?

Actually, that should be "with wallets and fees." Both are causing some grief right now.
While in the process of building a new computer, I'm getting increasingly frustrated with Bitcoin's complexity, especially around the notion of wallets.
The Bitcoin-QT wallet becomes part of the network. Lovely, if you have a huge chunk of disk space to devote. I happen to be running a very lightweight pure SSD system, so onwards I look.
Hmm. Armory? Well, it sits on top of the QT client, so no.
How about Electrum? Not bad, but I'd rather NOT have my wallet stored elsewhere, encrypted or not. If I'm going to do that, I might as well just use a web wallet.
Multibit? Ah, here we go! Local storage, no downloading of the entire block chain, and...you can't alter the transaction fee! I wasn't going to stress out over that because as many people have said, "what's $0.25" (or .40 or .06, or whatever people claim the trivial fee is)?
But when I went to transfer my bitcoins from the old computer to the new one (because of course the wallet formats are incompatible between wallets), it came up with a fee of just under 0.05 BTC! I understand why fees are going to become important, but really - twenty bucks to transfer my own bitcoins from one computer to another, with the promise of more fees down the line.
This is not a good system; and the fact that everyone who wants to use bitcoin has to go through pages of documentation to get some vague understanding of why they have to pay nondeterministic fees sometimes and not other times.
Just venting here. This won't be the future of currency until it works as easily as currency.
submitted by swordgeek to Bitcoin [link] [comments]

Accepting bitcoin for my online business, do I need full validation for pre-generated addresses?

So, I've had the multibit client for a while, and I used to use bitpay as a payment gateway that funneled funds to one address. Now I'm revisiting accepting bitcoin through some websites.
As far as I can tell it's a bad idea to receive funds on one address, is this negated by the way bitpay works?
If I was to go down the route of pre-generating addresses do I need a different wallet as I can't see a way of importing pre-generated addresses into my wallet, or am I wrong? Do I need a wallet with full validation to do this?
I originally had the QT wallet but downloading the blockchain was a pain, and unless I kept the wallet online updating took a while also. Any wallets that anyone could recommend would be appreciated.
submitted by me__uk to Bitcoin [link] [comments]

Importing Private keys into a QT based wallet, how is it done?

Before the fork I had been storing my tokens in MultiBit. I saw no need to incur a transaction fee to transfer those tokens into a QT compatible wallet format prior to the fork. So now I am here with multiple files that contain the private key(s) from those wallets.
I now need to import these keys into both my Bitcoin (Cash) and Bitcoin (Settlement) QT clients. What are the steps necessary to accomplish this?
I did find https://bitcointalk.org/index.php?topic=336404.0
Is this a safe method in which to perform the activity? I will be importing to Bitcoin ABC v0.14.6 & Bitcoin Unlimited v1.0.3.0
  1. Export private key from MultiBit without password (Done)
  2. edit file with some editor like Notepad++ (I'll probably just use Notepad, unless that is a bad idea?)
  3. copy only key - this is row without # ,and you must copy only key - no date and another symbols , (row indicates that it might be better to import to a spreadsheet?)
  4. then in BitCoin-Qt open from Help->Debug window ->Console (I am able to navigate to where the Console is not located)
  5. importprivkey [label] [rescan=true]
(Where is the information I copied from step 3? and also without the '<>')
(where label is name of owner - your name.; is this necessary? Do I need to provide a label? Can I leave it blank? And if I can leave it blank would I simply omit that the '[label]' argument?)
  1. And when press enter the your address with coins will appear in your addresses and in your balance.
Additionally, can this activity take place on a computer that is not connected to the applicable network? I am still waiting (1 year 40 weeks behind) for the Bitcoin (Settlement) wallet to download the chain (for some reason copying over of the pre-fork blocks did not take and now that the fork has occurred I do not want to try to start over or run the risk of re-installing).
Thank you for your assistance.
submitted by PilgramDouglas to btc [link] [comments]

mSigna unsent transaction (lost funds?)

I am having a problem with my first transaction with Msigna and am looking for help. I have been unable to find an answer by searching the internet so I am writing this post. I sent a transaction to an address I wish to send funds to but the confirmation status is “unsent” after several hours of waiting. I am running Bitcoin-Qt and the blockchain is completely downloaded and synced. The icon in Msigna is a green circle with a check in it and it is connected. However the funds seem to be stuck locally and have not appeared in blockchain.info. I have installed the latest version and imported my vault (and updated schema) but the status remains the same. Am I doing something wrong? How do I recover my un-sent funds? How do I export the private keys so that I can import into another wallet like Multibit or Armory? Any help would be greatly appreciated… Thanks!!
submitted by waybackwhen007 to Bitcoin [link] [comments]

GPG instructions and public key list for verifying Bitcoin clients.

I have noticed their is a growing problem of fake bitcoin clients, and I expect the frequency and elaboratness of these fake clients to increase.
Verifying the signatures for these clients will detect if you are receiving anything other than what the signer the of the software signed. The exception to this is if the attacker acquires the signer's private key, which should be a lot more difficult than tricking users to visit the wrong site or hacking servers. This can also be addressed by using multiple signatures per client.
An important part of this process is acquiring the public keys for the sofware signers in a secure manner.
To help with this I have included a signed list of fingerprints and where to acquire the public keys to act as another source to verify the keys used to sign bitcoin clients.
I have also included instructions for verifying the fingerprint list and bitcoin clients.
To deal with the issue that posts and comments on Reddit can be easily modified I suggest other users (especially well known ones) post a signature of the fingerprint list in a comment in this thread, or at least a hash of the fingerprint list (not as secure but still better than nothing).
List of Fingerprints:
+++ Bitcoin-Qt: Signer: Gavin Andresen (CODE SIGNING KEY) [email protected] Fingerprint: 2664 6D99 CBAE C9B8 1982 EF60 29D9 EE6B 1FC7 30C1 Key ID: 1FC730C1 Key Link: bitcoin.org/gavinandresen.asc
Electrum: Signer: ThomasV [email protected] Fingerprint: 6694 D8DE 7BE8 EE56 31BE D950 2BD5 824B 7F94 70E6 Key ID: 7F9470E6 Keyserver: pool.sks-keyservers.net Signer: Animazing [email protected] Fingerprint: 9914 864D FC33 499C 6CA2 BEEA 2245 3004 6955 06FD Key ID: 695506FD Keyserver: pool.sks-keyservers.net
Multibit: Signer: Jim Burton (multibit.org developer) [email protected] Fingerprint: 299C 423C 672F 47F4 756A 6BA4 C197 2AED 79F7 C572 Key ID: 79F7C572 Keyserver: pgp.mit.edu
Armory: Signer: Alan C. Reiner (Offline Signing Key) [email protected] Fingerprint: 821F 1229 36BD D565 366A C36A 4AB1 6AEA 9883 2223 Key ID: 98832223 Keyserver: pgp.mit.edu +++
My Key:
-----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.4.12 (GNU/Linux) mQINBFLB9nUBEAC/klZvqQkWP/NUD0pT09PzhKh0xIQ0XM7MxqUZLa1OytF3iUCX /fNwQD5OnSFQoEg1O4bGzrrRb+PiuKCvH19dp7sFVj3q7Dhwfb6EvsX39xqzxCr6 2AQFQ3esz4nNodnQWa48t2ujihaf/vpTn6n7+jCl6a124r+U4wNGiNIEWxLLUNNb ec8S1RcjtTp6Ue/yRpThgJN9e4rj19+vJMqKCiqL03NBZWVoCEkL6iIdjwlQK8/r CpP9m5yAsc8wkelRkZvuLmjJ1GgSFrO0WteGnURMshy59LetaSRyiIDeHaPdV5rk /n3mBv8hsK/39O6H7fYWDx/ZLnZE4rMghcndexIFLhsuPx6FJNATqQ2gHT4ijb8K NlwZ0LatlXyUEMKfC1aroa3/9RkQSf0y0GKS0XrvUWGVRn/X7gk1DRhuaHWuacCf k3w0XZOA2WpWw1w/rjZSeHbKG1w4B2/kWH3K4sXsfcLltlY85zH03HUYSx+leMFc yxiHz60ZfuV2aGjYFPL8dzF6DS106lHz51j608OZkAEO8Xssincii1k/PR1h1y2P AqgrEADzgl52iBbNw+tdnxSAIy/asEyxU/VwkUFjOzSyP7ZmBxg8ss966w2Kl6WE o9R5tkVuUG8WTMTnF0FeMxO9YOqx4KhN9bhP7RjBL7BFTvRXYVVJUGabIQARAQAB tBVkY2M0ZSA8ZGNjNGVAZ214LmNvbT6JAj4EEwECACgFAlLB9nUCGwMFCQlmAYAG CwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJECO6L0dAOWOhsNIQAKUN9Z4e0hM3 DbaUjYJx93JGdJArLmz+Ko10N/lGcao4lCNVA+xM73Ga1GBnPlhPFW9iD2VQocOv tY2PYNsPrHgGlzyMKAMSpZ8364wVEyCHdJVKFORUjhyuJGYfyhDt2iZuzQwxWbmQ 1gmlbiGvxRysmaSW5+M8CDhja/fI8+EOp5NbH/EvHJClul3cO72UBUXBPxRv4Eb+ j8k0Uozob70A3bD894F8bJ9wZ3XBX/9DEkAbvDyW7CxIZwUiCeYTQylH++8S91A1 wL3z35ELdOLzGqwetYY6gSZRwY/W+rewEfPfBDSRjXKOBfhraMBYV1Sdg0IUj10W 2XVAzkqmqaej0T/xTt6aNjFtiH1u18BUpYIcCAAZ6TJ7325bnqnI+0xWFdonyggL +AIX1nzhx5niw8ZkCX0/jlJAx3TXAuxX/Tfy7cVSVi33v0fiwoDb8ZIDBzg0P2uc PUpR13B3AevFpxuAuAFPWfTDOJQmZyn9YNswVOhNb9rfq5bkmaSBlMRefTtUKIjW XjrRhSULPJ73H+R1DNL1Y0vhclnkOVCFRB+VPChkO+6RitGQDTg/Z60fBHpnYiDz sysnsoojLwBGanHO5mZMprxADc9CmeRGRmfHwvx7eJvW1HqN+5JR3Ai+JDlT+IxX RNUQxUbOry4D8TwRn9nBEtumNyNQcBmUuQINBFLB9nUBEACyRFYCrOXxC8yWm92U qPPNa3YC+W17O4rHW/thKTze1/TeZAKTNaIMPCS7iSVBBRbuijG+8NsgFd6W9acC ihMD4VUdFhVPjRGM3HmqzsxudVI4kGlQl8w86pYZu8ceGB4LQcoUFbPmWgXDIszH NV7kIFO/2oCRJ7VIBllUMP97RRdIfDND7EZMWvDveZ40BZCBLfnD9f6VSs4Lgn2C ow/ko01ijnvUxA/BGPJKI7JTLJHbdL//RQwT3AacLSc/etIurY2Ef926XbYYI1gi qboCU/dYUkGG2D+BDcGdukwpksdZZSXPyNhkZQAPPViHuFFtHI3C+FNb5L+lnC0h /dfF73U1lN3jp/VX11U1tIsHJyPjs8aael2UJO7Qy3vgVRM6KOywNNjVRv79Z/rF YHkNzBwXrGKdwV16SdRWjgkzkB4JeNQME096SqrwAEj/j5fwMqHjR8dKqWKDT6s9 V2Z83go3n9kI8JWFh33OksBh/qpKghhwtGWrUsbVcEDOVmUn2ozXvARDzqnNw3DN PcQvzUtasD8hxGHo7fW4TczdtgS3b/DfU2VJo68Fmo1C4eqYX+Ixx05khFCtP7d0 POqX6jIIQqZq8NTea8/M8Xx1YGhR5RpA4vZe7bCLgD2VUXHL43Npmq2nuZ0/7AwY H0hc/y/T+SU70xn28XyWHHLkCwARAQABiQIlBBgBAgAPBQJSwfZ1AhsMBQkJZgGA AAoJECO6L0dAOWOhIcgP/ioKYiJFAsolS4ep1PenCPvQFjvZTq4xJnsubEJ/ERU8 zdgET0Rh5jcCLqRAxQbGW3lVsewR3N+S9Rt3zHApqfZBFg5XJkZxsk0u+0qGPHWA 4oC7U3E4ZwMfVzUDcfKrzD1h0JaiSW1+1qgCh9/YVCUYakR1n/9LgzPP8ekQLTeb nWE+ZQQfeTDgoTNFWZvUlEbh4zcHLvcay78PnK3uT3UbWPyltSxon/eD47s1dt03 P/8nqaXCZhhRZ9N3EbJyudLBgA3ctySSJJSKKQHYynH5qUQqKp4Wq1KY80161xvW FqKwN/Jr4tTpRVZPu8P82cxhwrWJdf1U3/M2F2aIgXbGS4fHbzsLZ+6zZ3AuT4D8 auW55GOrnoF9XzZV6IavtluILUXMjVzF13slo5PKzS8yyJRNxE22krbeEyUum4Zu dDiERxIB6B+RDMM9qvV9svGJoEXG+4ugwkA3R7a6LWApmkvH3eXpULfDN2g5eNcr 5efFMrI/myxmpsP3nUp5EZFJyp8+ZSzIMJ1jSzXH8mHajIGTG49xDyZGpbog3wd2 7aQf5D9WOuKfYZM9MU9PBF+ZgtNrAxWuYJcCOr4WEd/2IjayMWvLxNA/RVW66oVj puaaDc3m3hXg1fwUWv9ZJyMUv7NARLgig3KEMVZiVzos7ZMn9mZNrOk2fnkKpVJB =ufyu -----END PGP PUBLIC KEY BLOCK----- 
Signature for fingerprint list:
-----BEGIN PGP MESSAGE----- Version: GnuPG v1.4.12 (GNU/Linux) owGFk31QFGUcx48XIU/KU0YSZOhHToraHeze3u4tqd2+HZ6g4ks6ZBTLsXdud7eH ewtCV4mp4/hGKmlTQbyEkgoZxpg6kReML0RWaoohOWWN0mhK4WSZje0Zxw0zzfTP 7rPf5zfP7/N8nn22PRyliYyYfDQ9y0La6yNaotYW6hyi5BTkYlmUFJ9BKVMWdZyu mDFjhpYWFbtXlPQLlUztYtEpCXImZPGlogSUVCQLPkGCNGYBy8FiW9Z82/wsyOby poEzWMEPFVicHl50G+xeD1jDXTIBxXEMcJYkgaEpDhiSNgNCmlHgrHgGoCRLAsfh NCBWhgBjBoNos4VysLGZD5LhIEeUXJlQ+C+nwSs700d0N/A+u5ZzC3ZFLvGE97Bk hdfD+5aC8uBdiqiQZYYiQTuCEMdJDFizujuC5swqjQkHI0JzwJImlZBmTWBGMRoI q1pHZHD4MGEwCQU+QS4Ntiz2et0Gn8und4Uyn0ESlGEkShI9/Etqf5jJh4Zhd7NH opEkgoEZx1iwMkYjYCTJAM5QKADNcRSgKGZSnWWogkmTCTJwKzvMFkxCwf+xzStx K6LqNixurugBukRWvOrBe4Zmg9ahSCgV3N5iQZ4GL4oeHDFbHLxPGcI3lLhG8qNB YAw1qtQEagWMsKoGTTgFOE1hwCAkASjFsUCQVgIYE4GG1apJKBjGdxYbPCqHUFSi pWSPVy4PA1NuXgLGAIsEUf2GtAUOh1sdQXA+KFtdZhrwapFl6B/iHywQdD4S2Ywi VkBQlAQjTrPAmnBVMa4iM0b1gVE0AjiluifNZqN6AKhxGDmYhIL/Qg5etI2RydGa iEhNzKjI4N3TaEfrQjf0brJOs692U9vbzb2jMs51uP1Jl/6KXf7NoTEHolxXvvRf SjzbEylrjFvH1jXefbJxd9/tK8u8SVdLC9yv5N88N/v1Cyu7N1deXDPJMeVs8obj b9zvtW84sv9OWeJJ8tXyPX2/N+zqGn+ZnxCdGz++QXqzYGzthSRE7JJaflRu4/01 jqsFuat62ifvHujc8ZhupW1P59OBjoMtgz+crx08mdN/sDkwtUmfLecN2Hb8duuz Lxq6Aztjz3RsWV1d3TJBc4D86cbfuqjvn0iJemqvfk1/ToHQFZhtWrT555eZwh45 +vNj/jX7Fubnd/3adNxf+EhF7sWmMX+Q184dSvygFdFXBF6b2m1KjLvnoKanzEp0 2cWqgX7L2biU8/2xt5LudZ4g4pawCZVpv6T7q1JfaN9Q1xFxP2Z55fiPuo7tvXdd v6m3vrLt+Tk12bGzDn/rr8+puxl4vLsqrnPKmPg51xUZo+tiXKuf2XZ44DLd8t7N weL21tONnY2jKy+MSzi1/1o8sWrQPPPTd1tteW/tTct6fyO2NNWUJ6wT6mPWx9fz 31ml53QTe75a+2HbumVuvZCcC33V0/fFpM07wkRYUh9a0LxzK6mrOuqYChWT6u4M oGkJS2vmNkWdmdWcP5le4ulLbr+Ws+IysX37OyfSt4y70St8vLov9dE/k3Y1zNy4 SyrY/fWzvRMLP8mNrjh1eFvtznXt/wA= =5zDz -----END PGP MESSAGE----- 
Hashes for fingerprint list:
SHA-256: 7A6B9841 355B1127 E5639A9D 7040D81C F395D382 884376C2 31829C63 6FCF1B80
SHA-512: 04A49A60 A1645479 ED0B3CE9 AE32E156 E9768CC2 0D4EF393 814162BE BFA6FAF5 6C520769 C654467F 6B61EBD4 4A5A5C93 9DF81B7D AA468A50 2DD7FFF3 F637A49C
Verifying the fingerprint list:
Save fingerprint list, from the first plus to the last plus, to a text file called fingerprints.txt
Next save my key to a file called dcc4e.asc and my signature to a file called fingerprints.txt.asc
In terminal or command line run:
gpg --import dcc4e.asc gpg --verify fingerprints.txt.asc 
You should see:
Good signature from "dcc4e " 
GPG examples for verifying Bitcoin clients:
Verifying Bitcoin-Qt:
First download, import and check Gavin's key:
Download his key at bitcoin.org/gavinandresen.asc
In terminal or command line run:
gpg --import gavinandresen.asc gpg --fingerprint 
Check that the fingerprint for Gavin's key matches 01CD F462 7A3B 88AA E4A5 71C8 7588 242F BE38 D3A8.
Then download the wallet software and signature.
Verify the signature:
gpg --verify SHA256SUMS.asc 
You should see:
gpg: Good signature from "Gavin Andresen (CODE SIGNING KEY) " 
The signature for Bitcoin-Qt signs the hash values. So we must compute the hash of the specific downloaded software manually. This example is using the linux version.
gpg --print-md SHA256 bitcoin-0.8.6-linux.tar.gz 
Check that the output matches the associated hash value in SHA256SUMS.asc
Verifying Electrum:
First download, import and check ThomasV's key:
This key can be found at a keyserver.
gpg --keyserver pool.sks-keyservers.net --recv-keys 7F9470E6 gpg --fingerprint 
Check the fingerprint.
Download Electrum and the signature.
Verify the signature:
gpg --verify Electrum-1.9.6.zip.asc 
You should see:
gpg: Good signature from "ThomasV " 
For this example you do not need to manually compute any hash values because the signature is signing the downloaded file directly instead of signing a list of hashes.
submitted by dcc4e to Bitcoin [link] [comments]

[Guide] How to transfer your wallet from your computer to android.

I got tired of waiting and waiting for the whole blockchain to sync so I decided to move my dogecoins to my phone since the app does not need to download the whole chain. (Luckily there is a bounty for a electrum equivalent that will hopefully arrive soon.)
It is much much easier if you just transfer some funds to a new address on your android phone, but this tutorial is for those people like me who can't even get the dogecoin app to sync.
Surprisingly the whole process was very simple. Don't be put off by all the text or all the talk about security. I just want things to be accessible to beginners and to practice good habits. Root is not required.
Note: I am assuming you are using the official dogecoin-qt app and the Dogecoin Wallet app by langerhans.
Disclaimer: This will involve having your private key stored in plaintext. Proceed with caution and treat that file like you would a password. Do not share your private key with anyone.

Getting your private keys

A wallet comprises of public keys and private keys. Public keys are the addresses that you share, you can only use them for viewing. Private keys let you actually make transfers and are what makes you the owner of the wallet. Today we will be transferring those private keys to your phone. They will still be present on your computer unless you delete them, so keep that in mind security-wise.
You will have to replace everything in '<>' with your own values.
  1. Open the desktop app
  2. Open the wallet console by going to: Help -> Debug Window -> Console
  3. If your wallet is locked with a password, you'll need to unlock it by typing: "walletpassphrase 120".
  4. Get the private key for an address by typing: "dumpprivkey "
  5. Save the private key to a file.
  6. Repeat this for each address that you want to transfer over.
Please think about how much dogecoins you want to transfer over. Brarsh:
Do you need that much? What if you lose your device? Just like only keeping a small amount of cash in your wallet and most safe in the bank, only carry what you could conceivably use for that time without access to your main wallet.

Creating a backup file

Next we need to create a backup file so that we can import our addresses into the android app. The android app uses the same format for its backup files as MultiBit (A popular bitcoin app). A typical file looks like the following:
# KEEP YOUR PRIVATE KEYS SAFE! Anyone who can read this can spend your Bitcoins. Kwmxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2013-06-22T18:36:35Z L1Sxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2013-05-04T22:47:32Z Kxwxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2013-05-08T00:58:28Z 
What we want to do is put our private keys in the following format: key date-of-address-creation, where the date is in the format YYYY-MM-DDTHH:MM:SSZ. Note the T and the Z. The android app needs the date so it knows how far back into the blockchain it needs to sync.
If you can't remember when you created the address, visit http://dogechain.info/address/YOURADDRESS and get the date of the earliest transaction. It says that the dates are approximate, so I'd just put 00:00:00 for the time.
You should now have a valid unencrypted backup of your wallet.

Importing the backup

  1. Transfer the backup to your android phone, placing it in your Download folder. It has to be put in the Download folder or else the dogecoin app won't find the backup. Make sure it has a name you'll remember later.
  2. Open the dogecoin app and click on: Back Up Keys -> Restore private keys. Click on the name of the backup and from the list that shows up, look for your backup, which should be unencrypted. Click Restore.
  3. Delete the backup in your Downloads folder. Remember, your private key is stored in plaintext in there, so it is important that you delete it. Delete the backup on your computer if it is there also.
  4. Wait for the app to sync completely. Your addresses will be added to the addresses that were already in the app, and your transactions should show up. If they do not, make sure that the date you put was correct and early enough.
  5. Go to Back up Keys > Back up private keys and create a backup. This time it will be encrypted with a password :). If you do not have a backup, you could lose all your coins if you lose your phone or the data on it.
  6. To the moon!

Terminology

I just got into dogecoin two days ago so correct me if any of this is wrong. Same thing with anything in the post :).
Blockchain/Dogechain: The blockchain is a ledger (record) of all the dogecoin transactions that have ever taken place. As of writing it is larger than 1GB in size. The blockchain is needed to find out how many funds you have in your wallet.
Wallet: A wallet is the digital equivalent of a real life wallet. It is where your money is tied to (It doesn't contain actual dogecoins, but someone else could explain that better than me). The wallet contains your addresses and your private keys, both which are needed to receive and send dogecoins respectively.

Sources

Getting your private key
Importing the key into the android app
submitted by cooper12 to dogecoin [link] [comments]

Clearing up some misconceptions about full nodes | Chris Belcher | Feb 10 2016

Chris Belcher on Feb 10 2016:
I've been asked to post this to this mailing list too. It's time to
clear up some misconceptions floating around about full nodes.
=== Myth: There are only about 5500 full nodes worldwide ===
This number comes from this and similar sites: https://bitnodes.21.co/
and it measured by trying to probe every nodes on their open ports.
Problem is, not all nodes actually have open ports that can be probed.
Either because they are behind firewalls or because their users have
configured them to not listen for connections.
Nobody knows how many full nodes there are, since many people don't know
how to forward ports behind a firewall, and bandwidth can be costly, its
quite likely that the number of nodes with closed ports is at least
another several thousand.
Nodes with open ports are able to upload blocks to new full nodes. In
all other ways they are the same as nodes with closed ports. But because
open-port-nodes can be measured and closed-port-nodes cannot, some
members of the bitcoin community have been mistaken into believing that
open-port-nodes are that matters.
=== Myth: This number of nodes matters and/or is too low. ===
Nodes with open ports are useful to the bitcoin network because they
help bootstrap new nodes by uploading historical blocks, they are a
measure of bandwidth capacity. Right now there is no shortage of
bandwidth capacity, and if there was it could be easily added by renting
cloud servers.
The problem is not bandwidth or connections, but trust, security and
privacy. Let me explain.
Full nodes are able to check that all of bitcoin's rules are being
followed. Rules like following the inflation schedule, no double
spending, no spending of coins that don't belong to the holder of the
private key and all the other rules required to make bitcoin work (e.g.
difficulty)
Full nodes are what make bitcoin trustless. No longer do you have to
trust a financial institution like a bank or paypal, you can simply run
software on your own computer. To put simply, the only node that matters
is the one you use.
=== Myth: There is no incentive to run nodes, the network relies on
altruism ===
It is very much in the individual bitcoin's users rational self interest
to run a full node and use it as their wallet.
Using a full node as your wallet is the only way to know for sure that
none of bitcoin's rules have been broken. Rules like no coins were spent
not belonging to the owner, that no coins were spent twice, that no
inflation happens outside of the schedule and that all the rules needed
to make the system work are followed (e.g. difficulty.) All other kinds
of wallet involve trusting a third party server.
All these checks done by full nodes also increase the security. There
are many attacks possible against lightweight wallets that do not affect
full node wallets.
This is not just mindless paranoia, there have been real world examples
where full node users were unaffected by turmoil in the rest of the
bitcoin ecosystem. The 4th July 2015 accidental chain fork effected many
kinds of wallets. Here is the wiki page on this event
https://en.bitcoin.it/wiki/July_2015_chain_forks#Wallet_Advice
Notice how updated node software was completely unaffected by the fork.
All other wallets required either extra confirmations or checking that
the third-party institution was running the correct version.
Full nodes wallets are also currently the most private way to use
Bitcoin, with nobody else learning which bitcoin addresses belong to
you. All other lightweight wallets leak information about which
addresses are yours because they must query third-party servers. The
Electrum servers will know which addresses belong to you and can link
them together. Despite bloom filtering, lightweight wallets based on
BitcoinJ do not provide much privacy against nodes who connected
directly to the wallet or wiretappers.
For many use cases, such privacy may not be required. But an important
reason to run a full node and use it as a wallet is to get the full
privacy benefits.
=== Myth: I can just set up a node on a cloud server instance and leave
it ===
To get the benefits of running a full node, you must use it as your
wallet, preferably on hardware you control.
Most people who do this do not use a full node as their wallet.
Unfortunately because Bitcoin has a similar name to Bittorrent, some
people believe that upload capacity is the most important thing for a
healthy network. As I've explained above: bandwidth and connections are
not a problem today, trust, security and privacy are.
=== Myth: Running a full node is not recommended, most people should use
a lightweight client ===
This was common advice in 2012, but since then the full node software
has vastly improved in terms of user experience.
If you cannot spare the disk space to store the blockchain, you can
enable pruning as in:
https://bitcoin.org/en/release/v0.11.0#block-file-pruning. In Bitcoin
Core 0.12, pruning being enabled will leave the wallet enabled.
Altogether this should require less than 1.5GB of hard disk space.
If you cannot spare the bandwidth to upload blocks to other nodes, there
are number of options to reduce or eliminate the bandwidth requirement
found in https://bitcoin.org/en/full-node#reduce-traffic . These include
limiting connections, bandwidth targetting and disabling listening.
Bitcoin Core 0.12 has the new option -blocksonly, where the node will
not download unconfirmed transaction and only download new blocks. This
more than halves the bandwidth usage at the expense of not seeing
unconfirmed transactions.
Synchronizing the blockchain for a new node has improved since 2012 too.
Features like headers-first
(https://bitcoin.org/en/release/v0.10.0#faster-synchronization) and
libsecp256k1 have greatly improved the initial synchronization time.
It can be further improved by setting -dbcache=6000 which keeps more of
the UTXO set in memory. It reduces the amount of time reading from disk
and therefore speeds up synchronization. Tests showed that the entire
blockchain can now be synchronized in less than 3 and a half hours
(See
https://github.com/bitcoin/bitcoin/pull/6954#issuecomment-154993958)
Note that you'll need Bitcoin Core 0.12 or later to get all these
efficiency improvements.
=== How to run a full node as your wallet ===
I think every moderate user of bitcoin would benefit by running a full
node and using it as their wallet. There are several ways to do this.
(https://bitcoinarmory.com/) or JoinMarket
(https://github.com/AdamISZ/JMBinary/#jmbinary)
Multibit connecting only to your node running at home, Electrum
connecting only to your own Electrum server)
So what are you waiting for? The benefits are many, the downsides are
not that bad. The more people do this, the more robust and healthy the
bitcoin ecosystem is.
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-February/012435.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

I downloaded bootstrap.dat from torrent but still bitcoin-qt won't synchronize !

I tried to run bitcoin-qt but the synchronization was taking FOREVER (4days running and green bar was less than 10%)
So I downloaded bootstrap.dat on torrent and now the green bar is 50% but now bitcoin-qt is synchronizing with network which take FOREVER, even in 100years it won't be synched at this rate.
Where can I get a bootstrap.dat UP TO DATE, or how can I make bitcoin-qt synchronize faster .
Please don't tell me to use multibit or whatever, I know it exists but I don't know how secure it is since there is no bootstrap.dat, just answer my question how can I make bitcoin-qt work I can find no solution on the internet which is crazy.
THANK YOU
submitted by Wicelo to Bitcoin [link] [comments]

Using Multibit wallets in other software

So I've been using Multibit, and I enjoy its GUI and ease of use. Problem is, from what I understand there's no way to remove the transaction fees.
Thing is, I'd like to be able to transfer BTC between my own wallets without being dinged every time with transaction fees. I downloaded Bitcoin-QT on the suggestion of a professional associate, but I can't figure out how to import wallets from Multibit.
Are the wallets I opened in Multibit tied specifically to Multibit or can I open them using other software? If they are, is there any way to get my BTC out of Multibit without suffering the transaction fees?
For bonus marks, are there any other wallet programs you recommend other than Bitcoin-QT or Multibit which allows you to manage multiple wallets easily and without any mandatory transaction fees?
submitted by Fuquawi to BitcoinBeginners [link] [comments]

OLD-FAIL: Remember when people counted Bitcoin-QT downloads as the bitcoin adoption metric?

Just recounting some old fail and old things we used to have to debate about.
Remember when people counted Bitcoin-QT downloads as THE bitcoin adoption metric?
Completely ignoring how cumbersome that is to use and is the worst wallet software for casual users to download, not even including download estimates for much more convenient wallet software like Electrum, or Multibit or the android apps and eventually iphone apps
submitted by 1blockologist to Bitcoin [link] [comments]

Had to update to Multibit 0.5.19 to get my Bitcoin to show Bitcoin.pl Poradnik #2 : Instalacja klienta Multibit Multibit wallet download Download the Multibit.org Bitcoin Wallet (subtítulos en español) BitCoin - YouTube

Download Bitcoin Core Neueste Version: 0.20.1 Download Bitcoin Core Bitcoin Core 0.20.1. Überprüfen Sie Ihre Bandbreite und den freien Speicherplatz. Die Erstsynchronisierung von Bitcoin Core dauert sehr lange und lädt eine große Menge Daten herunter. Sie sollten sicherstellen, dass Sie ausreichend Bandbreite und Speicherplatz für die volle Größe der Blockchain (über 350GB) zur ... Download MultiBit Wallet: GitHub: DOWNLOAD MultiBit HD Wallet MEGA: DOWNLOAD MultiBit HD Wallet MultiBit was designed to be as easy to use as possible, but Bitcoin itself may require some getting used to. These articles are intended to provide useful explanations of the common problems that people face. MultiBit HD Designed to be easy to […] Bitcoin-QT is slower than Multibit because Bitcoin-QT is a thick client(it downloads the entire blockchain,) whereas Multibit is a thin client(it does not download the full blockchain.) share improve this answer follow answered Jun 11 '13 at 15:44. DrAwesome DrAwesome. 135 4 4 bronze badges. Are there benefits of a thick client? – stommestack Jun 11 '13 at 17:38. 4. Thin clients do not ... To install Bitcoin-Qt, simply download and install Bitcoin Core (Bitcoin-Qt). On first launch of Bitcoin-Qt, it may takes days for this Bitcoin client to do the initial sync the full blockchain, block by block, with the network to your local drive under a Bitcoin-Qt data directory, which is time consuming that usually takes days. 2. Download blockchain file via Torrent The complete blockchain ... Bitcoin-Qt ist ein Open-Source-Projekt und derzeit einer der sichersten Vertreter unter den Mining-Clients. Hier müssen Sie sich nicht um eventuelle Angriffe auf Ihr virtuelles Geld sorgen. Ebenfalls Open-Source und vertrauenswürdig ist Electrum.Das Tool punktet mit einer 2-Faktor-Authentifizierung, dem Support von Add-ons und der Möglichkeit, Ihre Keys jederzeit in andere Bitcoin-Clients ...

[index] [31481] [24457] [11342] [48361] [44430] [43977] [16463] [22271] [13799] [50783]

Had to update to Multibit 0.5.19 to get my Bitcoin to show

BREAKING: Institutions Pay a WHOPPING 287% INCREASE for Ethereum! Wall Street FOMO! Bitcoin & Google - Duration: 25:18. Digital Asset News 6,863 views. New Bitcoin.pl Poradnik #2 : Instalacja klienta Multibit ----- Nasz poradnik w prosty i zrozumiały sposób przedstawi Ci wszystkie kroki potrzebne do zainstalowania klienta transakcji Multibit, oraz ... made with ezvid, free download at http://ezvid.com made with ezvid, free download at http://ezvid.com Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

#