Use Bitcoin Core and access it through the JSON-RPC interface. It is just a normal HTTP API but run locally.
Oh great man. I need a payment gateway for my site which will accept bitcoin. But am not able to figure out what's necessary to make the system work. I think you could help me out in this situation. I think there is payment gateway api "bitpay" to accept payment with bitcoin. Don't hijack other people's threads with your own questions. Take it to another thread. |
|
|
|
I guess they're going to do it every day at around this time until I figure out how to stop them... I've made some progress on that front, but it's not done yet.
If anyone is an actual expert in Linux networking (ie. the term "GRE tunnel" is familiar to you), I could use your help in figuring some of this stuff out.
Instead of Cloudflare use an DDoS protected Reverse Proxy IP. The Cloudflare Free Plan is not helping at all, to stop an big attack. Edit: It seems you switched to Cloudflare and forgot to add SPF Records which fail to deliver mails to most known email provider. However, I do not receive notifications of Bitcointalk. What are you talking about? Bitcointalk doesn't use Cloudflare. The ddos is still active or what? I couldn't browse the forums in the last 30 minutes without having a connection problem, don't know if this issue happens only now or it is persistant.. Theymos please fix it  You can't stop a DDoS attack, you can only attempt to mitigate the effects of the attack. Theymos is still trying to figure out a way to mitigate the effects, but clearly networking isn't his expertise. |
|
|
|
Ok this is confusing, all I've ever done when updating/upgrading bitcoin core is download it off bitcoin.org
My coins & old addresses are always there when I open bitcoin core after updating/upgrading it.
Are you saying that with the 0.13.0 update that isn't the case.
No. All you need to do to upgrade is to download it off of bitcoin.org and install. However, if you want to take advantage of the new HD wallets, you will need to go through this process to migrate your Bitcoin. Obviously I have a back up of my wallet but speak to me like I'm 10 years old.
Back up your wallet. Make a new wallet with 0.13.0. Get addresses from that wallet. Back it up too. Restore your first backup. Send your Bitcoin from your restored wallet to the addresses that you recorded from the new wallet. Restore your new wallet backup. Your Bitcoin should have been migrated. Keep both backups just in case something bad happens. |
|
|
|
|
What wallet are you using? Which software is giving you the error, pgp or your wallet?
|
|
|
|
So I have Bitcoin Core newly installed, updated and working fine.
Opening Armory v 93 showed my wallet, and the transaction history, and I am sure that I could have sent and received coins.
I downloaded v 0.94.1, checked the Hash, and "installed" it using default actions. It deleted a bunch, then started to unpack the new files, and threw the error:
Error opening the file for writing: ArmoryQt.exe. If I ignored it (which I know wouldn't work,) there was a cascade of other files that threw the same error.
Attempting to install v94 tanked v93, so I tired reinstalling that, only to get exactly the same errors.
So right now I have a fully functional Bitcoind, but no Armory, v93 or v94.
I'm just glad I don't need to send or receive coins right now.
So Bitcoin Core is working, that's good. I recommend trying to go for a completely clean install of Armory. Find the Armory Data directory. Copy your wallet file out and back it up to a safe place. Then delete the entire folder. Reinstall Armory and try again. |
|
|
|
Sorry, I have done this in a hurry.
let's assume :
1 computer can do 10^8 hashes per second
Again, it isn't hashes. There is much more to it, please read BIP 32. There are word lookups and then multiple rounds of hashing and key stretching and other operations in order to get the private key. It isn't just hashing, so a computer will not be able to find master private keys as quickly. There are 10^7 wallets using seed of 12 words
There are 10^40 combinations of 12 words seed
1 year is 31 millions seconds
how many years it will take to this computer to test all combinations?
In one year, it can do 31* 10^6*10^8 hashes which is approximately 10^15 hashes.
dividing 10^40 by 10^15 leads to 10^25.
Thus it will take 10^25 years to tests all seeds and get all the wallets
How many years it will take to this computer to get only one wallet?
As there are 10^7 wallet with seeds and a total of 10^40 possible combinations, we can assume that 1 wallet will be hacked every 10^33 attempts which will take (10^33 divided by 10^15) 10^18 years
But what if more than one computer is used?
Do you realize how ridiculously long 10^18 years is? That is 72463768.1159 longer than the universe has even existed. Even if you used multiple computers, you would barely make a dent in that time frame. Is there not something on the algorithm that is blocking attempts when to much are made?
No because there is no central server and there is nothing you can do to block attempts when there is no central authority. |
|
|
|
|
Use Bitcoin Core and access it through the JSON-RPC interface. It is just a normal HTTP API but run locally.
|
|
|
|
|
Sounds like a service problem. People here can't help you at all whatsoever. The only people that can are Coinbase, and if they won't help, then nothing can be done.
|
|
|
|
Hi folks, really hoping you can help me cause I just created a wallet at blockchain,
but when I try to send my bitcoins to another address, it just won't let me.
And it doesn't matter how much if I type in 12 or 0.00001 BTC it's still not working..
How much Bitcoin do you have to send? What is your address? Have you tried contacting support at blockchain.info? This is a service problem, people here can't really help you. I always get the message " use total available minus fee: 0 BTC" in red text, if that would explain something?
I don't really get that because isn't there no fees when sending and receiving BTC at blockchain, or have I gotten that wrong?
You are horribly incorrect. You must remember, blockchain.info is a service, not the actual blockchain. They can't do anything with the blockchain, including transaction fees. You must send transactions with a fee if you want the transaction to confirm, regardless of the wallet you are using. |
|
|
|
You'll need more than 64 Gb to have the entire blockchain. As of right now, it's 80+ Gb. That might be your problem.
Sorry @achow101. Usb stick is 128Giga. Just edited it in the original post Ok. Can you provide the debug.log file? It should be in ~/.bitcoin/. Just copy and paste the contents into a post here. If it is too big, make a new paste at http://pastebin.com/ and post the link to that. |
|
|
|
[There is a new icon in the lower right hand corner of the window that says "HD". If it is grayed out with a slash through it, then you are not using an HD wallet. If it is not like that, then you are using an HD wallet. Mousing over that icon will also tell you whether HD is enabled or disabled for your wallet.
I have a 0.13.0 installation using a legacy (non-HD) wallet, but I don't see the icon you describe. Are you running a client built from source != to the official release? Hmm. I though that icon had made it into the release, but I guess not. I am running a build of the latest master branch. So alternatively, to check if you have an HD wallet, if you go to the Debug Console and type getwalletinfo, the output should have a field labeled "walletversion" which should be 130000. If it isn't (60000 for old wallets) then it isn't an HD wallet. |
|
|
|
|
You'll need more than 64 Gb to have the entire blockchain. As of right now, it's 80+ Gb. That might be your problem.
|
|
|
|
|
So you want the actual input to the hashing functions before the signing? Read the BIP, it explains it pretty well.
Also, can you post what you think is right so that we can see what you have done wrong?
|
|
|
|
Ah that is a cool detail. Then what I do need is I guess I need to send all my coins to the newly generated 0.13.0 wallet? How do I do this if I have to upgrade to 0.13.0 to generate the wallet first?
I don't trust other wallets other than Bitcoin Core so im not sending my coins to blockchain.info or even electrum (I store my main stack in my Core wallet.dat)
What options do I have? I have considered a paper wallet but sending all of my coins ever to the same address seems like very anti privacy practice.
So first you have to backup your original wallet. Then, move it out of the data directory and update Bitcoin Core. When you start Bitcoin Core 0.13.0, it will generate a new HD wallet for you. Grab a few addresses from that wallet and write them down somewhere. Then stop Bitcoin Core and backup the new wallet.dat file. Replace the wallet.dat file in your data directory with your old wallet. Restart Bitcoin Core, it will load the old wallet and you will see that it is non-HD. Send Bitcoin from your old wallet to the addresses that you copied down. The Bitcoin will go to the new HD wallet. Then stop Bitcoin Core again, replace the wallet.dat file in the data directory with a backup of the new one, restart Bitcoin Core, and you will be good to go. Ah I see. How many different addresses should I use for better privacy? This is what annoys me. I will spend a ton of time trying to make everything right through coin control so stuff does not get mixed in the wrong way. I wish bitcoin was really anonymous and you wouldn't have to worry about coin control etc. It depends on how much privacy you want. I suggest that, before you start, go through all of the inputs you have in coin control and figure out which ones you want grouped together so you can figure out how many addresses to use. |
|
|
|
Ah that is a cool detail. Then what I do need is I guess I need to send all my coins to the newly generated 0.13.0 wallet? How do I do this if I have to upgrade to 0.13.0 to generate the wallet first?
I don't trust other wallets other than Bitcoin Core so im not sending my coins to blockchain.info or even electrum (I store my main stack in my Core wallet.dat)
What options do I have? I have considered a paper wallet but sending all of my coins ever to the same address seems like very anti privacy practice.
So first you have to backup your original wallet. Then, move it out of the data directory and update Bitcoin Core. When you start Bitcoin Core 0.13.0, it will generate a new HD wallet for you. Grab a few addresses from that wallet and write them down somewhere. Then stop Bitcoin Core and backup the new wallet.dat file. Replace the wallet.dat file in your data directory with your old wallet. Restart Bitcoin Core, it will load the old wallet and you will see that it is non-HD. Send Bitcoin from your old wallet to the addresses that you copied down. The Bitcoin will go to the new HD wallet. Then stop Bitcoin Core again, replace the wallet.dat file in the data directory with a backup of the new one, restart Bitcoin Core, and you will be good to go. |
|
|
|
I'm using the latest version of bitcoin core, also 12W7RgjugzpULqwfq1tCzdU89LZnvVvJVw was the only key in my address book so just backing that up doesn't save my coins?
Then you should be using 0.13.0. However, you did not backup the wallet, so you did not backup the master private key. Most good wallets will not reuse the same address, and many do not tell you what the change addresses are. You *WILL* have change addresses. It is not good enough to backup the addresses that you know about because you *WILL* be using change addresses that you do not know about. You must backup the entire wallet. Since you have not, your Bitcoin is lost. There is nothing that can be done about that. what bitcoin wallet do you use?
go to blockchain.info to check your addresses on what transactions took place.
Please stop spamming and read the thread before you post. |
|
|
|
Anyway my question is... if I use my wallet.dat from the 0.12.1 version, what does this mean? I am using HD mode or im still in old format? Im just paranoid and don't want to screw things up.
You will still be using the old format. You will not be using an HD wallet. It will also tell you whether your wallet is HD. There is a new icon in the lower right hand corner of the window that says "HD". If it is grayed out with a slash through it, then you are not using an HD wallet. If it is not like that, then you are using an HD wallet. Mousing over that icon will also tell you whether HD is enabled or disabled for your wallet. |
|
|
|
What did you have to do to persuade him to change your username? I'm interested in changing my username, never thought I would be able to do it. Only know like five users that have changed their names without Donator.
I asked and he obliged. I don't really know why. Why did you decide to change it?
I thought knightdk was a pretty cool username. Sorry to question, I was just curious, I've told you before that I think you're one of the most knowledgable & helpful posters on here.
Consolidation of my identity. |
|
|
|
2. A computer cannot calculate 1015 hashes per second -- more like 108. A current ASIC device can do 1014 hashes per second.
Not only that but it isn't even just hashes being performed. There are other functions and key stretching that happens to in order to get a seed and reverse. Then to get addresses there is also some key stretching and more hashing required. The computer would be doing significantly less operations per second. |
|
|
|
I am a BTC newbie but generally tech-savy. I like the idea of a offline wallet. Why should i wait a couple of months before trying bitcoin core?
I like the idea of storing the BTC on a small thumbdrive. If i were to make a backup / copy of this thumbdrive, then use some the funds....how does the other backup know the btc is no longer in my possession?
Well... Bitcoin core is great... The downside is that you'll have to synchronise your wallet... Basically download and verify all the transactions in all the blocks. There are options to prune the blocks, in order to keep the used diskspace lower, but you'll still need several gigabytes of storage and several days to sync (if i remember correctly). Several being less than 10 Gb. It is a significant reduction from the 80+ Gb that is normally required. The sync time depends upon your network connection and computer. For example, my computer with 4 cores and 8 Gb of ram can sync the entire blockchain in less than one day. Also, bitcoin core generates random private keys, so you'll need to re-backup your wallet.dat very often, since new private keys will be added.
Not anymore. As of Bitcoin Core 0.13.0, a BIP32 HD wallet is used, so you only need to backup once. If you set a password or change on though you will need to backup again. |
|
|
|
|
Show Posts
