|
You have to do a full resync by deleting all of the blk files in the data directory. One of the blocks downloaded is corrupted.
|
|
|
|
teukon has it right.
knightdk appears to be struggling to understand the concept.
A (non-coinbase) transaction has two parts pertinent to this discussion.
There are a list of inputs that provide value to the transaction. There are a list of outputs that are assigned value that must be less than or equal to the sum of the value supplied by the inputs.
A coinbase transaction also assigns value to a list of outputs. That value must also be less than or equal to some total value that is available to the coinbase transaction.
The difference is that a non-coinbase transaction gets its value from the list of inputs whereas the coinbase transaction gets its value from the block subsidy plus the sum of all transaction fees from all transactions in the block.
This means that if you sum up all the outputs of all the transactions in the block (including the coinbase output) it will be equal to the sum of all the inputs plus the block subsidy.
Therefore, every transaction in the block that left unaccounted-for value as a transaction fee essentially has that value accounted for in the output of the coinbase transaction.
So, when you follow the list back and you get to a coinbase transaction, you can't stop there. The value that you are tracing back didn't "come from" the coinbase transaction any more than it "came from" the inputs of the transaction where you started. Since the coinbase transaction got some of its value from the transaction fees (and therefore from the inputs of all the transactions that left value for transaction fees), you have to keep going with all those inputs and the transactions that created them.
And so on, and so on, until you get to coinbase transactions that came from blocks where none of the transactions in the block paid any transaction fee. At that point you'll finally be back to the point where the value first came into existence.
Ah. I see now. Thanks for explaining. |
|
|
|
Imported my backed up wallet but all the recieve addresses are gone, is there anyway to get them back? I have the key written down....
Just keep clicking the receive Bitcoins button until you start seeing addresses you don't recognize. All of your addresses should be there since armory is an HD wallet. |
|
|
|
You can create a shell script with the command you need to run Bitcoin core and then save that to the desktop. Every time you want to start bitcoin, just run that script. |
|
|
|
Of course. I didn't suggest otherwise.
Sorry, I misinterpreted your response. Now, instead of "Why stop at a coinbase transaction", I ask "Why not stop immediately"?
What do you mean by this? I think you are misinterpreting fbueller's response. He isn't saying to stop searching through the utxo list when you see a coinbase, but to keep searching through the list. For each utxo, search through its inputs and follow the chain until all coinbases in that chain are reached, then go back to the list and repeat with the next utxo. |
|
|
|
you need to use the --datadir option to point it to another directory. Your command will be pywallet.py --datadir=<path to directory> --dumpwallet > wallet.txt where <path to directory> is the path to the directory that contains the wallet.dat file. Tried doing this, and went ahead and tried uninstalling and reinstalling bitcoin core to its default directory. both times I get this message: https://i.imgur.com/61stoV6.png. My Bitcoin is currently not running, FYI. The wallet file might be corrupted and pywallet can't access it. There really isn't anything you can do to fix it. |
|
|
|
you need to use the --datadir option to point it to another directory. Your command will be pywallet.py --datadir=<path to directory> --dumpwallet > wallet.txt where <path to directory> is the path to the directory that contains the wallet.dat file. |
|
|
|
Go to https://github.com/jackjack-jj/pywallet and download the zip file. Extract the stuff to another folder. Then go to https://www.python.org/downloads/ and download python 2.7.11. Run the installer and it will install python. Make sure that when you get to the "Customize features" screen you scroll down and click the dropdown next to "Add python.exe to path" Select "Will be installed on local hard drive" then you can continue. Then go to https://pypi.python.org/pypi/zope.interface/4.1.3#downloads and select the correct file. The file you want will be either zope.interface-4.1.3-py2.7-win32.egg or zope.interface-4.1.3-py2.7-win-amd64.egg depending on if your windows version is 32 bit (the first file) or 64 bit (second file). Then download https://bootstrap.pypa.io/ez_setup.py. If that link brings you to a page of text, right click and select "save as" Go to the folder where you saved the ez_setup file and make sure that nothing is selected. Then do Shift + Right Click and in the menu that pops up select "Open command window here". In the window that pops up, type After that runs, close that window and go to the folder where you installed python. Then go to the scripts folder within that. Copy the zope interface file you downloaded to that folder. Then open the command window again. This time type easy_install.exe <zope filename> where <zope filename> is the name of the file you copied. Then go to the folder where you extracted the pywallet files and open another command window. Here just type pywallet.py --dumpwallet > wallet.txt This command will dump everything from the wallet to a file in the same folder called wallet.txt. If you have a passphrase on the wallet, add the option --passphrase <passphrase> to the command after pywallet.py and --dumpwallet. Make sure there are spaces between them all. If the directory where your wallet is located is not the Bitcoin default, then you will also need the --datadir=<path to directory> option also added in in the same manner as the passphrase. |
|
|
|
Does it mean 7Zip 9.xx is not crackable? 7Zip has several compression method with difference compression ratio. Are they all not crackable?
Compression and encryption are different things. Compression does not encrypt anything, so anyone can decompress and read the data. The encryption that 7Zip uses is AES, which is still uncracked, so yes it is uncrackable. |
|
|
|
Thank you for looking into it! How should I get the Bitcoins back in my wallet from the change address? Deleting the transaction in my wallet? I'm using an offline wallet, bitcoin-qt.
Change addresses are already in your wallet. You can spend directly from them, you own those addresses. There is nothing you need to do to spend from those addresses. |
|
|
|
|
Can you give us the debug log? Go to %APPDATA%/Bitcoin and find the debug.log file. Post the contents of that file here. If it is too big, post the last 100-200 lines.
|
|
|
|
|
18hqhj58ouipyNiNFSmNXKY8ugrx8Ewm8K is one of your change addresss. As Danny said above, the transaction spending the change from that address did not confirm and was dropped from the network.
|
|
|
|
|
Can you describe the error and post a screenshot?
|
|
|
|
I compress the wallet.dat file with 7 zip using encryption, then back up the files into usb disk. Is 7 zip encryption safe?
AFAIK, 7zip, WinRar, WinZip, etc. have all been cracked already. But as long as the wallet.dat file is encrypted you should be good. No, 7zip's encryption is not cracked. I highly doubt WinRar and WinZip's are cracked either, but I don't use them. 7zip uses AES encryption, which is still not cracked. It is the safest encryption method as of today. |
|
|
|
This "fee" shit is only getting worse, especially during extraordinarily high volume times which out the blue to started thursday nite. What happens when there are no more BTC to be mined? Also I don't understand why the block size can't be increased tramatically to fix this nonsense. The value in mining is not the fees, it's the 25 BTC.
This is nothin but slowing down adoption in a big way, especially when other crypto currencies DO NOT have this problem at all.
Increasing the block size is not trivial and there are many considerations in doing that, particularly the fact that it WILL be a hard fork. That in itself is contentious because HARD FORKS CAN BE BAD. There are no other currencies which have the same transaction volume as Bitcoin, so they aren't even comparable. If you want to compare two things, you need to eliminate all of the other variables which can affect the outcome. The must be compared ceteris paribus, all else equal. Take your off topic ranting elsewhere, we don't need it in tech support threads. And maybe learn some stuff about what you are talking about /Off Topic OP, about your question, since you were unable to set the fee, there are only a few options available to you. You could attempt a Child-Pays-For-Parent transaction in which you create a transaction that spends an output from this transaction but you pay a fee that is enough to cover both transactions. Or you can wait and hope that it confirms. Or you can wait for it to eventually (few days usually) be dropped by the network, making that transaction as if it had never happened. If that happens, then contact whoever sent you the transaction and ask them to resend it with a higher fee so that it gets confirmed. |
|
|
|
Unless we have magic, cracking SHA-256 is almost impossible. Sure, you could crack it first try, but that's like rolling 99.99 on a dice game. 1000000 times in a row.
The supercomputer would guess much faster, yes, but it will still take eons on average for it to crack a private key.
Mining/hashing? Nah. It may be a little faster than an ASIC, but it probably costs hundreds times more than an ASIC.
Private keys don't use SHA-256. It will be significantly faster to crack a private key since there are known algorithms that QCs can do faster that do prime number factorization, an important aspect in ECC which is used to create the private and public keys. Quantum computers would have an advantage over classical computers in getting private keys from public keys, but it will still take a while. But the time it takes is much much less than the time it takes for a classical computer. |
|
|
|
I just see sig campaigns requiring an avatar That's because there are no longer any open avatar campaigns that are not also sig campaigns. They don't all require sigs, but all of those are sig campaigns with the avatar as an afterthought. |
|
|
|
(1) Register on an API
(2) Take an address you're interested in
(3) Request all utxos on the address
(4) Lookup txid on the API.
If coinbase: stop here.
Otherwise: look at inputs, and repeat this step.
At the end you'll have a rather large list of blocks.
Why stop at a coinbase transaction? Coinbase outputs contain the fees of transactions included in its block. Surely we should repeat the iteration with each one of the block's fee-paying transactions. Fees aren't outputs. Fees are the difference between the sum of the inputs and the sum of the outputs of a transaction. There is nothing that links fees back to the transaction that they belong to. Really what they are are coins that disappear into thin air and then are regenerated in the block reward. |
|
|
|
Most likely not. If you have some idea of what the password is, you can attempt to brute force it and recover the password. You could try doing it yourself or asking the guy who runs http://www.walletrecoveryservices.com/. The site is trusted and the owner is a trusted person on the forums. |
|
|
|
|
Show Posts
