It is possible to never connect the offline laptop to the internet?
Yes, in fact, it is recommended. Do I need to update win7 at all?
No. What about the bitcoin armory client? Needs updates?
There is no need to update unless there is a new feature you want or your version has a bug. Do you put these updates on a USB drive and update from it?
Yes, you can download the latest Armory client on a separate computer, and update the offline computer from a USB drive. Where do I purchase my bitcoins without compromising the security of this Armory setup?
 You've been misinformed here. Your bitcoin client does NOT need to be online in order for people to send you BTC. You just need a bitcoin address from your offline wallet. If you want to confirm you have received the coins you will need to create a watching only wallet on your online computer. |
|
|
|
A transaction can gain priority by having "aged" inputs. I've sent small (<1 btc), aged, coins without a fee and they had the greatest priority of all the transactions in the block.  Just thought I should mention this because it seems to be a commonly overlooked fact.  |
|
|
|
- snip -
laptop1 :Connected to the internet. Has Bitcoin client installed on it. Used to send /receive bitcoins but NOT to store them.
laptop2 :Used for storing bitcoins. Never connected to the internet for security reasons
The bitcoins are transfered from this laptop to a USB drive and then trasfered to laptop 1 for online bitcoin transaction.
- snip -
I think this is how the Armory wallet works, isn't it? Yes, Armory would be perfect for DAN444. |
|
|
|
|
Not sure if this helps, but you can set bitcoin to use a port other than the default one.
|
|
|
|
|
Try running it with the "rescan" option.
|
|
|
|
+1 I like the idea of a tutorial section. Would make it easier to find step by step instructions. This would be pretty nice to have and would help out developers new to Bitcoin. I would definitely spend some time there.
+1 If you could see and believe the hassle I am having handling simple? actions, this is a necessity- I hope it will happen. reg
Is English not your native language? If so I applaud you for leaning and successfully communicating in a second language. If English is your native language, well, read your posts before posting. "Cross fingers and hope their are no grammatical errors."  EDIT: I knew I recognized the posting style, I helped you try to install Bitcoin a while back. Can't believe it didn't click sooner. |
|
|
|
|
What do you mean you did a rescan? What you are describing sounds nothing like the typical meaning or running Bitcoin QT with the -rescan option.
|
|
|
|
The original post lacked info for "regular users". Here it is:
(1) If you are a "regular user" (not a miner), the best thing is to do nothing and wait a couple hours.
(2) If you are a "regular user", Upgrading, downgrading, whining, FUD, etc, will make no difference. Only miners have an incentive to do anything.
(3) Regardless of who you are, your transactions are not dead, your coins are not lost. They will just temporarily be held up. If you sent a transaction within the last few hours, it may take a few more hours before it's sorted out.
(4) If you insist on processing transactions right now it's probably best to wait 30+ confirmations. It's just due diligence though ... an attacker would still need a tremendous amount of mining power, quick thinking, and a victim willing to part with a lot of BTC.
(5) By tomorrow this will be in the past and everything will appear to be normal again. If you slept through this, you'd never know that anything happend (except for the price drop).
Let me reiterate, your coins are not at risk, your transactions are not lost. It'll just take some time for the network to "iron itself out." Everything will be okay.
Very good info. +1 The testing should have happened with the older version of Bitcoin. I don't see how testing 0.8 would fix this issue, given that 0.8 fixes the bug.
It depends on your point of view to which client has the "bug". The problem was an inconsistency with the clients, so you could say since 0.7 was already out 0.8 was the inconsistent client. |
|
|
|
|
Try moving the contents data directory to a temporary location (like your desktop) then running the bitcoin-qt client. If this works then some file in you data directory is corrupted.
P.S. How do you show hidden folders on a mac so you can reach the bitcoin data directory?
P.P.S. Where is the bitcoin data directory on a mac?
|
|
|
|
|
Assuming you have the Bitcoin-QT client, click the tab that says something like "receive coins" any addresses here are yours.
|
|
|
|
|
It is also possible for transactions to have multiple inputs. But all that wasn't really relevant to the question. I only mentioned the "change" address because I thought it might have something to do with the answer.
|
|
|
|
|
Thanks, for the fast replies and the links. This has been very helpful.
|
|
|
|
Generally when one sends coins two transactions are made, one to the desired recipient, and one to a "change" address. For example: Lets say I have 10 coins in address A. I send 7 coins to Bob. Now Bob has 7 coins, address A has zero coins, and I have a "change" address with 3 coins. So the transaction is signed with A's private key and now everyone knows the private key for address A. What happens if someone sends 10 more coins to Address A? Can anyone access the coins in address A now? Thanks for spending your time reading and hopefully answering this question!  |
|
|
|
|
Sorry to go off topic but I can't seem to find any kind of market or current exchange rate for XRP, could someone point me in the right direction?
|
|
|
|
|
16toBAHiY7H9TWhi5gzyyL25BFjsPHhon3
Thanks
|
|
|
|
|
You may be missing some coins if you outspent your keypool. If you sent >100 transactions since you backed up you wallet then you are missing some coins which went into "change" addresses.
|
|
|
|
|
Run Server1's bitcoind with the command option -detachdb. Shut down bitcoind. Move blk001.dat, blk002.dat, blk003.dat, and blkindex.dat to Server2. Run Server2's bitcoind with the command option -detachdb.
For some reason you can't transfer the blockchain files for one bitcoin client to another without using the command option -detachdb.
Note: you only need to use the command once, if you use it all the time you will notice a significant increase in the time needed to shutdown bitcoind.
|
|
|
|
Type "bitcoin-qt -loadblock=D:\Utilities\Bitcoin\bootstrap.dat" assuming this is where bootstrap.dat is located. Sorry for my poor communication skills.  Downloading version 0.8 is your choice; I personally have not chosen to do so because: A) It has not been released yet and there are still many bugs to work out. B) Since It has not been released it has not gone through extensive community use and testing. C) I've not done enough research to trust version 0.8 so I continue to use 0.7.2. However if you believe 0.8 would be easier for you go for it, but back up your wallet first!  |
|
|
|
|
Show Posts
