Backup has been restored and 43.xxxBTC sitting in wallet.
The address holding is: 16sfAJDmdEZahYva5YWa3RZ7FF6BMzU4Hj which says 0BTC is held at this address... :/
Just thought I would also add that 6.02 and 0.28 tx's are still showing as unconfirmed in the wallet too.
A wallet has many addresses, most of which are not shown to you. Much of your balance will be in "change" addresses if you have used your wallet to send payments. |
|
|
|
Just deleted tx's through pywallet, done bitcoin -rescan and balance shows 0 confirmed and 0 unconfirmed.
I have no idea what is going on but I hope I haven't just watched $19k go down the drain.
If you have your original wallet.dat backup containing the keys to spend your bitcoins, and haven't forgotten the password, then your money is always recoverable and spendable. What we are doing is attempting to remove the "reservation" of coins your wallet thinks you spent, but have never been included in a block. The -rescan command looks through all blocks you have downloaded one-by-one to update your balance, adding payments to you and deducting payments you have sent. What you should see after a rescan is that the transactions tab shows all transactions this wallet has ever made, but with the unconfirmed ones removed. Bitcoin-Qt needs to have completed downloading all blocks before you will see an accurate balance though. You should have the "up-to-date" checkmark in the lower right of your client before wondering WTF. If pywallet seemed to operate normally, there are a few things that may have gone wrong: - the rescan option might not have been called correctly (it needs a single hyphen for -rescan when you type it), this must launch a new copy of Bitcoin (it wasn't already running), and you should see the rescan dialog take considerable time when Bitcoin starts. - was Bitcoin running when you ran pywallet? Bitcoin must be completely closed before anything accesses wallet.dat or you attempt to make a backup. In options, be sure "Start Bitcoin on system login", "minimize on close", and "minimize to the tray" (or whatever equivalent OSX options there are) are unchecked, and restart your computer to be sure Bitcoin-Qt is absolutely not running, - pywallet didn't do what it was supposed to. Perhaps berkeley database libs were the wrong version or not installed correctly, or other unanticipated problems, - you are not starting Bitcoin under your user name from the command prompt, which would create a new wallet for whatever user that was (root, etc), - you didn't run pywallet under your username. File permissions or ownership may be incorrect, or it didn't find your wallet or save changes correctly, - OSX Bitcoin-qt client is known for having blockchain database problems more often than it should (some bug that hasn't been identified yet), this could have happened coincidentally, making your blockchain or it's index un-scannable. If you are sure the rescan was performed, looks like we need to try again. I would rename the non-working wallet.dat, and restore your wallet.dat backup (which, for that much in BTC, it should be backed up in multiple places) to the ~/.bitcoin data directory. Everything should be like it was before when you run Bitcoin, including your unconfirmed transactions, confirming that your coins are still there and your backup is good. Then meticulously follow the remove-transaction steps again, with a restart first to be sure Bitcoin isn't locking the wallet file. The file names in the pywallet "delete" tab are filled in correctly on most operating systems, but be sure they reference the correct full home directory path with your user name. If you really need wallet recovery, I could do this for you, but would have you phone call me personally to communicate a strong password to 7zip up your wallet backup when sending it, etc. It would take about 5 minutes since I already have pywallet working. I could send send back the balance-restored original wallet.dat, or transfer all bitcoins to a brand new wallet you create and we pre-verify with test transactions is working 100%. Edit: see that you got money transferred out of wallet. |
|
|
|
|
The default minimum per-kB fee was reduced a few months ago to 0.0001 bitcoins. You don't need to specify a larger fee that 0 in the Bitcoin-Qt options unless you want to be generous or want to pay for higher priority processing than default. The minimum fee will be calculated and added automatically when required.
Completely emptying a wallet can take several attempts to discover the correct amount before sending. First try to send the full balance, and see what the fee is. Then reduce the amount you are sending by this fee. When you attempt to send again, see if amount + fee is sending your whole wallet balance.
It is probable that no fee would have been required if you were completely sending all 25BTC at once (with no 0.001 change back to your wallet) if the coins had sat in your wallet for a day.
|
|
|
|
|
In computing, having an undetermined machine state is bad. If there wasn't a limited amount of Bitcoin that will be produced, the size of the variable holding it would eventually overflow, memories would overflow, etc. A compiler can see that if mining were to continue forever there would be more bitcoins than molecules in the universe, and optimize out the indeterminate state by removing mining entirely. It is easier to program without bugs when there is a maximum number of Bitcoin base units, we know how many digits need to be shown in the user interface and such.
As for why this particular curve? It's better than 50 BTC for 8 years and then no rewards after. In hindsight, the halving times should have been longer so that half the currency wasn't already mined before it really became popular, but you could not have anticipated the adoption rate of the currency - it could still be a few cryptographer's experiment, or it could have gone gangbusters the first year.
|
|
|
|
I wish I knew how to code
Everyone should! 1. Go here: http://logo.twentygototen.org/ZkRilu2Y2. Type in the right-side box: CIRCLE 20 COLOR [255 0 0] CIRCLE 50 3. The commands you type are executed when you press 'run', and draw the circles you asked for. 4. Can you figure out how to make a circle of radius 100? A blue circle? If you can, you are writing commands that make a computer do what you want, you're a programmer! I hope you're a programmer, and not an idea guy, because this thread is a stupid idea. http://logo.twentygototen.org/ZkRilu2YCrawling BitTorrent DHTs for Fun |
|
|
|
Another way to do this, for "perfect" entropy calculation is to roll six-sided dice and write down bits. Then convert those directly to a private key...
Bleah, I coded some python to turn any-sided dice into a full-strength private key, no hashes. The answer is it takes a LOT of dice rolling, less than 100 d6's is not a full-strength key. I quit at an unencoded 64 byte hex key, you can convert it to an importable key/address with http://bitaddress.org or such. **Dice to Bitcoin private key generator**
>How many sides on your dice?:6
Need 100 rolls of 6-sided dice. (258.496250072 bits)
Number of dice rolls so far: 0, need 100 more.
input dice rolling results, no space between rolls:)
>22222222222222333333333333333
Number of dice rolls so far: 29, need 71 more.
input dice rolling results, no space between rolls:)
>2222222222244444444444
Number of dice rolls so far: 51, need 49 more.
input dice rolling results, no space between rolls:)
>2222222222333333333
Number of dice rolls so far: 70, need 30 more.
input dice rolling results, no space between rolls:)
>1
Number of dice rolls so far: 71, need 29 more.
input dice rolling results, no space between rolls:)
>55555555555
Number of dice rolls so far: 82, need 18 more.
input dice rolling results, no space between rolls:)
>333333
Number of dice rolls so far: 88, need 12 more.
input dice rolling results, no space between rolls:)
>55555555
Number of dice rolls so far: 96, need 4 more.
input dice rolling results, no space between rolls:)
>222222222
raw private key: 218c3c240686849676c9828fc5fd8749860365a0ed82ebe3e601a2b9a039f333
Or if you want to see what it looks like with bits or coin flips: **Dice to Bitcoin private key generator**
>How many sides on your dice?:2
Need 256 rolls of 2-sided dice. (256.0 bits)
Number of dice rolls so far: 0, need 256 more.
input dice rolling results, no space between rolls:)
>1111111111111111111111111111111122222222222222222222222222222222111111111111111 1111111111111111122222222222222222222222222222222
Number of dice rolls so far: 128, need 128 more.
input dice rolling results, no space between rolls:)
>1111111111111111111111111111111122222222222222222222222222222222111111111111111 1111111111111111122222222222222222222222222222222
raw private key: ffffffff00000000ffffffff00000000ffffffff00000000ffffffff00000000 import math
keyval = 0
sides = ''
roll_list = []
maxkey = int('FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364141', base=16)
while not sides.isdigit() or int(sides) < 2:
sides = raw_input('**Dice to Bitcoin private key generator**\n>How many sides on your dice?:')
sides = int(sides)
rolls = int(math.ceil(math.log(maxkey, sides)))
print "Need %s rolls of %s-sided dice. (%s bits)" % (rolls, sides, math.log(math.pow(sides, rolls), 2))
while len(roll_list) < rolls:
print "Number of dice rolls so far: %s, need %s more." % (len(roll_list), rolls-len(roll_list))
if sides < 10:
rollinput = raw_input('input dice rolling results, no space between rolls:)\n>')
rollinput = list(rollinput)
else:
rollinput = raw_input('input dice rolling results,separated by spaces:)\n>')
rollinput = rollinput.split()
add_rolls = []
for inputitem in rollinput:
if not inputitem.isdigit() or int(inputitem) < 1 or int(inputitem) > sides:
print "**invalid dice roll detected: '%s', discarding all input " % inputitem
break
add_rolls.append(int(inputitem))
roll_list.extend(add_rolls)
for i in range(rolls):
keyval += (roll_list[i]-1) * sides ** i
hexkey = "{0:064x}".format(keyval)[-64:] # truncate to 64 bytes hex
if int(hexkey, base=16) > maxkey or int(hexkey, base=16) < 1:
raise Exception('Wow, invalid key, try again!')
print "raw private key: ", hexkey Not a problem to roll that many dice if you've got a dice-o-matic, though. |
|
|
|
Am I talking to myself here? http://bitcoincharts.com/charts/btcnCNY#rg360ztgSzm1g10zm2g25It looks like you have a big gap in data from Aug to Oct, perhaps created by an older sierrachartfeed with a limit on the number of days to resume. That cannot be easily repaired. After getting the latest sierrachartfeed, posted above, I would delete the btcnCNY.scid file and get the whole thing again using the command line options: sierrachartfeedUTC-0.6.023.exe --history=700 --symbols=btcnCNY(set history to how may days you really need; this exchange has data from July 2011.) If all exchange data has such a gap in recorded dates, extract my scid 7zips to your sierrachart data directory to save some time. |
|
|
|
save the *.py to your home directory. Double-click.
-or-
You should be familiar with the shell, ...
Changed both those lines and ran pywallet.py --web through terminal as root and get this error; SyntaxError: unexpected character after line continuation character You do not need or want to be root. Especially with code you cannot understand off the Internet. Root has a different wallet in a different home directory than you, anyway. Note the subtle "-or-" above; you don't need to do both things I described. It sounds like you edited more than you needed to, causing the syntax error. Re-download pywallet.py to your home directory and run it with the terminal if you have figured that out. |
|
|
|
You can edit the pywallet.py file so it starts the web interface by default. Change the first line to the correct shebang for OSX: Change line 4792 from: help="run pywallet web interface") to help="run pywallet web interface", default=True) Do not alter the indenting. save the *.py to your home directory. Double-click. -or- You should be familiar with the shell, though (command prompt, terminal, console, etc), to do other actions such as using the Bitcoin command line options. Here's how I would expect you to run it: finder -> go -> utilities -> terminal type python pywallet.py --web |
|
|
|
You should not be hashing anything multiple rounds that needs to maintain entropy. SHA256 probably isn't a random oracle, but the entropy loss is small. If it was a random oracle, the entropy loss would be 36%. I retort, and say why isn't everything done with cryptographically strong random numbers? Because we must let people be stupid? |
|
|
|
|
There are a few cases where this will work as expected, like if you were to spend your entire wallet balance exactly including fees, then all wallet inputs will be spent as you specify. Otherwise, Bitcoin will compose a transaction from available inputs in a way that minimizes change, but spending an amount where the change is zero, given the automatic inclusion of unpredictable fees, is hard.
see coin control.
|
|
|
|
Ok, thanks I will try that. How do I store the processed blocks on my flash drive so each time I put it in a new computer, the client doesn't have to sync the entire block history?
Instead of copying the wallet.dat file from the bitcoin data directory, copy the entire directory contents except wallet.dat (around 13.5GB now). This can be restored to any computer you wish to run Bitcoin on to avoid the complete re-downloading of the blockchain; only the wallet.dat file contains the personal information about your addresses. It is not a good idea to use the same wallet.dat on multiple computers, they will go out-of-sync after many transactions or as soon as you start adding labels. A good way to lose money, as eventually one wallet won't have addresses that are in the other. |
|
|
|
|
Please don't waste your time attempting to mine without specialized ASIC hardware. The difficulty is too damn high for anything but dedicated mining-only hardware. Even with a $200+ ATI GPU particularly suited for mining, you will make less than 0.0005 BTC/day.
|
|
|
|
Looks like they're mostly hosted at your-server.de
Whoever is doing this, please set your subVer field appropriately. Otherwise it just makes you look like a DoS attacker ....
The same hosting IP space of bitcoincharts/bitcoinwatch... |
|
|
|
I found a small weakness in Electrum's key stretching algorithm: The seed-key is only hashed twice.
You should not be hashing anything multiple rounds that needs to maintain entropy. As 256 bits of possible input do not map to a full 256 bits of output (for every two inputs that have a duplicate hash there must be a non-possible hash), repeated hashing reduces entropy further. "Infinity" rounds of hashing may even converge on a vastly reduced output set, but mathematical proof would be a challenge. |
|
|
|
You should really understand the algorithm that calculates when fees are required and what they are in the Bitcoin source code before attempting to roll your own transactions, otherwise you will likely duplicate blockchain.info wallet fail where they send transactions without adequate fee or non-standard transactions that will never confirm. https://en.bitcoin.it/wiki/Transaction_feeA safe minimum is 0.0001 BTC per 1000 bytes (rounding up transaction size) for any transaction, if you want timely processing. If this BTC amount were to be adjusted, you would find it on line 50 of https://github.com/bitcoin/bitcoin/blob/master/src/main.cppOne caveat is that this calculation must be correct for the final transaction that is broadcast. Adding a fee can change the payment inputs that are used and the size of the transaction. |
|
|
|
|
Please follow my instructions on page 1. This will return the full available balance to the wallet. After balance recovery, it would be wise to create a new wallet and send the balance there, since you have mishandled wallet privacy by uploading private key data over interceptable Internet connections to third parties.
|
|
|
|
|
Betteridge's Deepceleron's law of headlines: The answer to fucking lying inflammatory headlines is no.
|
|
|
|
Retransmitting the transaction or publishing transaction information the user may wish to keep private does not accomplish the goal he wishes to reach. See: would like to know a way to restore these coins back to my wallet.
|
|
|
|
|
Bankers funnel millions into the coffers of lawmakers and lobbyists to do their bidding and get laws written that are favorable to them. There are many companies that use Bitcoin as a foundation of their business, and consumers that do not want to have banking extract wealth from them by inserting itself into their money storage and payments, and it is reasonable for a lobbying group to exist that can collectively represent their interests too.
|
|
|
|
|
Show Posts
