Bitcoin-QT freezes when I try to run it with the -rescan command...
It takes a long time to run, it can look like it locked up since there is no progress bar or such. You can also start Bitcoin-Qt with the -salvagewallet option just for another round of validation. |
|
|
|
In the case of starsoccer9, it absolutely did fool the "system" (which used to say that an empty unboxing video was sufficient proof of seller fraud). Bitmit attempted to revise history and claim this was never their policy, and effectively said that the tracking number alone was more proof that the item was delivered, than the unboxing video with the label still on, showing the seller & buyers' name/address, and tracking #, tape being cut away, revealing an empty box. This is why the only effective escrow to mediate the meeting of scam buyers and scam sellers is full escrow. Buyer sends escrow agent the money, seller sends escrow agent the merchandise, who verifies its legitimacy and authenticity to the conditions set forth by the buyer. Only when both money and merchandise are escrow-agent-approved are they released to the parties. This is of course impractical for many items, requires time and a trustworth escrow agent, and would require double-shipping and appropriate fees, but would guarantee that no scammer gets away with their scam. This is why Christie's makes $17 million for selling one painting. |
|
|
|
Any idea? Am I doing something wrong?
I have no explanation; maybe move your original found-key file to a simple directory name such as C:\WALLET along with the script, specify the max size, etc. Here is the command line I just used with pywallet in the same directory as the keyfile: pywallet-keyskip2.py --recover --recov_device recovered-wallet.dat --recov_size 1Mio --recov_outputdir . |
|
|
|
Ok, reupped, after actually running the code and recovering some real keys off my own hard drive: C:\pywallet>diff.exe pywallet.py pywallet-keyskip.py
4910,4911c4910,4919
< importprivkey(db, sec, "recovered: %s"%sec, None, True)
< importprivkey(db, sec+'01', "recovered: %s"%sec, None, True)
---
> try:
> importprivkey(db, sec, "recovered: %s"%sec, None, True)
> except RuntimeError, e:
> print "%s error importing key %s" % (e, sec)
> continue
> try:
> importprivkey(db, sec+'01', "recovered: %s"%sec, None, True)
> except RuntimeError, e:
> print "%s error importing key %s" % (e, sec)
> continue
|
|
|
|
Now I get this error:
Traceback (most recent call last):
File "C:\Users\Name\AppData\Roaming\Bitcoin\pywallet.py", line 27, in <mo
dule>
pyw_filename = os.path.basename(__file__)
NameError: name 'os' is not defined
The code (in)validator appears to have removed the os,sys import. Grr, I guess I'll just text-edit the python to patch it, and keep the tabs instead of using my IDE which bitches about the tabs and won't even let me type them. Sorry about all that... |
|
|
|
Thanks alot! I really appreciate it! I get a syntax error at line 4261, "table in =", an arrow is pointing at the "=". Typo?  Ooops, looks like I randomly hit "enter" in the middle of the file, fixed and reupped. I also ran it thru a code validator which removed some imports and reformatted the python. |
|
|
|
Thanks for the advice! I tried running pywallet --recover on just the "recovered-wallet.dat" file. It actually finds 306 keys, but it stops at importing 20/306. Importing key 20/306:
Traceback (most recent call last):
File "C:\Users\Name\AppData\Roaming\Bitcoin\pywallet.py", line 4910, in <
module>
importprivkey(db, sec, "recovered: %s"%sec, None, True)
File "C:\Users\Name\AppData\Roaming\Bitcoin\pywallet.py", line 2622, in i
mportprivkey
pkey = EC_KEY(str_to_long(sec.decode('hex')))
File "C:\Users\Name\AppData\Roaming\Bitcoin\pywallet.py", line 1056, in _
_init__
self.pubkey = Public_key( generator, generator * secret )
File "C:\Users\Name\AppData\Roaming\Bitcoin\pywallet.py", line 1000, in _
_init__
raise RuntimeError, "Generator point has x or y out of range."
RuntimeError: Generator point has x or y out of range. The dat file with only 19 keys actually works loading with the bitcoin client. Is there anyway to check if it contains any money without having to sync the bitcoin client? It doesn't just "stop" importing, it has a catastrophic failure with the value of one key being invalid as a elliptical curve private key. Likely there was a KeyA or other data prefix surrounding an area of a hard drive that made it look like a potential key, but the data was all 00s or all FFs, which would cause this error. Either the key will need to be edited out of the recovered-wallet, by hex editing the wallet to make that particular data a real (but no money) key, or fixing pywallet so it evaluates and skips invalid private keys. |
|
|
|
I succeded in making a little money today by selling 7.5 bitcoins and then buying 7.5 bitcoins at a lower price (I traded on coinbase.com).
But I had to tie up several thousand dollars for several days to do it.
You just made 2.5x what holding a 1-year CD at a bank will earn you in those few days. In a market with 5% volatility in hours you can make this much pretty easily as long as you recognize the risk of getting locked in for a potentially long time if your BTC position goes down. |
|
|
|
|
At least edit the first post subject to "Buying BTC local in Sacramento CA" or such... so 99.9% of users don't have to click to see something irrelevant to them.
|
|
|
|
Title pretty much says it all. Which operating systems and versions/distros do you use?
I can answer this question for all forum users. As could be predicted, the most used here is Win7 x64. Here's the OS part of the user agent for one day of web hits to this image, which is in some thread on this forum:  Android 2.3.6; Linux; Opera Mobi/ADR-1309251116
Android; Mobile; rv:25.0
compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0
iPad; CPU OS 5_1_1 like Mac OS X
iPad; CPU OS 5_1_1 like Mac OS X
iPad; CPU OS 6_1_2 like Mac OS X
iPad; CPU OS 7_0_3 like Mac OS X
iPhone; CPU iPhone OS 7_0 like Mac OS X
iPhone; CPU iPhone OS 7_0 like Mac OS X
iPhone; CPU iPhone OS 7_0_2 like Mac OS X
iPhone; CPU iPhone OS 7_0_3 like Mac OS X
iPhone; CPU iPhone OS 7_0_3 like Mac OS X
iPhone; CPU iPhone OS 7_0_3 like Mac OS X
Linux; Android 4.1.1; HTC6435LVW Build/JRO03C
Linux; Android 4.2.2; Galaxy Nexus Build/JDQ39E
Linux; Android 4.2.2; HTC One Build/JDQ39
Linux; Android 4.3; Nexus 4 Build/JWR66Y
Linux; U; Android 4.1.1; en-ca; HTC One S Build/JRO03C
Linux; U; Android 4.2.2; de-de; Nexus 7 Build/JDQ39
Linux; U; Android 4.2.2; de-de; Nexus 7 Build/JDQ39
Linux; U; Android 4.3; en-us; Galaxy Nexus Build/JWR66Y
Macintosh; Intel Mac OS X 10.7; rv:17.0
Macintosh; Intel Mac OS X 10.8; rv:24.0
Macintosh; Intel Mac OS X 10_6_8
Macintosh; Intel Mac OS X 10_6_8
Macintosh; Intel Mac OS X 10_6_8
Macintosh; Intel Mac OS X 10_7_5
Macintosh; Intel Mac OS X 10_7_5
Macintosh; Intel Mac OS X 10_7_5
Macintosh; Intel Mac OS X 10_7_5
Macintosh; Intel Mac OS X 10_7_5
Macintosh; Intel Mac OS X 10_8_4
Macintosh; Intel Mac OS X 10_8_5
Macintosh; Intel Mac OS X 10_8_5
Macintosh; Intel Mac OS X 10_9
Macintosh; Intel Mac OS X 10_9
Macintosh; Intel Mac OS X 10_9_0
Macintosh; Intel Mac OS X 10_9_0
Macintosh; Intel Mac OS X 10_9_0
Macintosh; Intel Mac OS X 10_9_0
Macintosh; Intel Mac OS X 10_9_0
Macintosh; Intel Mac OS X 10_9_0
Macintosh; Intel Mac OS X 10_9_0
Macintosh; Intel Mac OS X 10_9_0
Windows NT 5.1
Windows NT 5.1
Windows NT 5.1
Windows NT 5.1; rv:25.0
Windows NT 6.0
Windows NT 6.1
Windows NT 6.1
Windows NT 6.1
Windows NT 6.1
Windows NT 6.1
Windows NT 6.1
Windows NT 6.1; rv:25.0
Windows NT 6.1; rv:25.0
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64
Windows NT 6.1; WOW64; rv:24.0
Windows NT 6.1; WOW64; rv:24.0
Windows NT 6.1; WOW64; rv:24.0
Windows NT 6.1; WOW64; rv:24.0
Windows NT 6.1; WOW64; rv:25.0
Windows NT 6.1; WOW64; rv:25.0
Windows NT 6.1; WOW64; rv:25.0
Windows NT 6.1; WOW64; rv:25.0
Windows NT 6.1; WOW64; rv:25.0
Windows NT 6.1; WOW64; rv:25.0
Windows NT 6.1; WOW64; rv:25.0
Windows NT 6.1; WOW64; rv:25.0
Windows NT 6.1; WOW64; rv:25.0
Windows NT 6.1; WOW64; rv:25.0
Windows NT 6.1; WOW64; rv:25.0
Windows NT 6.2; WOW64
Windows NT 6.2; WOW64
Windows NT 6.2; WOW64
Windows NT 6.2; WOW64
Windows NT 6.2; WOW64
Windows NT 6.2; WOW64
Windows NT 6.2; WOW64
Windows NT 6.2; WOW64
Windows NT 6.2; WOW64; rv:25.0
Windows NT 6.3; WOW64
Windows NT 6.3; WOW64
Windows NT 6.3; WOW64
Windows NT 6.3; WOW64
Windows NT 6.3; WOW64
Windows NT 6.3; WOW64
Windows NT 6.3; WOW64; rv:25.0
Windows NT 6.3; WOW64; rv:25.0
Windows NT 6.3; WOW64; rv:25.0
X11; Linux i686
X11; Linux i686; rv:17.0
X11; Linux i686; rv:25.0
X11; Linux x86_64
X11; Linux x86_64
X11; Linux x86_64
X11; Linux x86_64
X11; Linux x86_64
X11; Linux x86_64
X11; Linux x86_64
X11; Linux x86_64
X11; Linux x86_64
X11; Linux x86_64
X11; Linux x86_64
X11; Linux x86_64; rv:25.0
X11; Linux x86_64; rv:25.0
X11; Linux x86_64; rv:25.0
X11; U; Linux x86_64; en-US; rv:1.9.2
X11; Ubuntu; Linux x86_64; rv:25.0
X11; Ubuntu; Linux x86_64; rv:25.0
Windows NT 6.0 = Windows Vista or SBS 2008 Windows NT 6.1 = Windows 7 Windows NT 6.2 = Windows 8 Windows NT 6.3 = Windows 8.1 Macs in second place, with Linux, iPads and iPhones, and Android also a putting in a good showing. Yes, I know who you are (see the quote in my signature); I actually can't disable logging on my webhost. If you don't like being tracked by third-parties everywhere you go on the web, you should install RequestPolicy. |
|
|
|
Asked both of them now. Awaiting response  The second that you say the word "format" or "repartition", the only hope is to yank the drive from service and scan the whole surface for any recoverable private keys. Data likely will no longer be where it should be, recovery software will find junk in the sectors where "wallet.dat" is indicated to have been. After IMMEDIATELY discontinuing use of any drive with possibly-recoverable bitcoins on it, you need to boot another operating system off another drive, and use software that will mount and scan the entire original drive by raw disk sector to discover any recoverable private key data that could be left on the drive. Get a second hard drive to run off of or bootable USB with a linux distro on it, and get pywallet running on it: https://bitcointalk.org/index.php?topic=34028.0Then use the command below, pointed to the appropriate device corresponding to the old hard drive and the correct drive size/area to scan, pywallet will go through these steps: 1. read every byte on the disk to look for keys 2. create a recovery file of private keys which enables 3. attempt recovery of password-encrypted keys using possible phrases python pywallet.py --recover --recov_device /dev/sdb --recov_size 120GB --recov_outputdir ~/foundkeys It takes about 10 hours to fully 0-wipe a 2TB hard drive, expect longer for key recovery just to read and process the whole drive. Several threads are around discussing this, but there is not one that is at "master tutorial" level. |
|
|
|
The fact that RippleLabs keeps a fraction and can move the price is EXACTLY the same thing that Satoshi and others early miners hold a huge amount of bitcoins => not a big deal. (But knowing if the 100 billion number is fixed or not is a big deal).
99 Billion of 100 Billion is a fraction? For the peons that have been given minute amounts and the "friends" of Ripple that have been given millions, the exchange rate is currently 40,000/BTC. That's the equivalent of saying that there is a legitimate reason for the company's premined XRP to be worth $900,000,000, which is ludicrous. Even if Satoshi were to emerge and dump all his coins, there are book orders on exchanges wanting to buy several times more bitcoins than will ever exist. Bitcoin has value that cannot be diluted, Ripple has value only until Ripple the company decides to dilute it. |
|
|
|
One question about collectible value of the casascius coins
How much of a price premium people pay for a 1, 10, ... physical bitcoins versus the BTCUSD rate?
Remember that the coins sold for 1.20-1.25 BTC, but have 1BTC of digital currency. One would expect a coin to retain this value when resold. Spending the coin likely destroys the price premium paid for it (e.g., is a spent coin worth 0.25 BTC?). This question is whether a $400 1.00 BTC coin is still worth 0.25 BTC mint cost, a premium of $100. I think it has been established that the numismatic value at least has maintained the original BTC premium, but it is still market/buyer dependent. A coin with money added is worth just the money added; anybody can add money to a coin. Maybe it even removes utility from the coin, since it can't be handed over at face value any more. |
|
|
|
I will attempt to find out but will it help retrieve the coins or are they completely gone?
Tymer, stop with the bullshit posts and go back to playing with your 0.0056BTC
If this was a payment to you by a third party, you can make the case to them that their payment to you was never received. However, you should not have completed a sale or accepted the payment as legitimate until you saw it had confirmations - there is a likelihood that it was intentionally constructed from other bad transactions in a way that would never confirm. (hrm... the forum red-text alerting of another thread post while you were responding isn't working or was removed...) |
|
|
|
... why does the client have a drop-down box to set a fee if the fee changes all the time?
The fee doesn't change all the time, the minimum fee has been reduced twice in the history of Bitcoin to keep it in parity with market valuation of currency. The minimum fee is a mechanism to prevent frivolous transactions or network spam. If all transactions were free, it would be trivial to send many tiny transactions over and over simply to cause network disruption. The inclusion of a transaction in the blockchain by miners, making them recognized and permanent, is based on many rules, but equivalent transactions are served in a first-come basis. You can encourage prompt blockchain inclusion by offering more in fees than other transactions, which is adjustable in your client. The Bitcoin software that miners use promotes priority inclusion of transactions when they include more than the minimum fee. |
|
|
|
|
Bitcoin is money. It has opportunities because it is the currency of the internet and transcends banks and international borders, and includes its own money-transfer mechanism. It is up to you to figure out what those opportunities are.
|
|
|
|
It is strange that QT attempted to send the tx without it confirming! very unusual! This ability is needed because of change, if you had to wait for your change to confirm before you could send another transaction from Bitcoin, you would be limited to one transaction per block. Bitcoin considers all money you've received as spendable, it is up to you to use the information about number of confirmations to see if you should be spending amounts that need the unconfirmed coins. ...
How is this going to help? I'm posting because I have assistance to offer, not for a bounty. Adding a bounty to a tech support thread attracts others that want a bounty but do not offer assistance. |
|
|
|
Just deleted tx's through pywallet, done bitcoin -rescan and balance shows 0 confirmed and 0 unconfirmed.
Looks like this might be showing the correct balance, based on the input above! |
|
|
|
|
Show Posts
. 
