|
Well it means that has failed to load the blockchain before, which is usually indicative of some corruption in the blockchain.
|
|
|
|
|
I get the feeling that something is amiss with it skipping that many bytes..
I'm not sure what is wrong here. Redownloading the blockchain would most likely fix your issue. You could also try running the next testing version for 0.95 which should be out in a day or so (or run the one that is already released).
|
|
|
|
|
Can you post the cpplog file too? That's somewhat important, it's where all the db stuff happens.
|
|
|
|
|
Try disabling the auto-managed bitcoind and run Bitcoin Core manually.
|
|
|
|
Guys ? I've got a problem  "Please wait for your previous request to finish and try again" But last time I did a request was quite a long time ago :/ If your IP address is shared (or you are using a proxy), then someone else with that IP may have recently made a request. The site uses IPs to check that. I'm still having the problem, I'm now on my phone and still have the problem :/ I'm pretty sure that nobody else using this connection is using the price so I don't know how to get out of it What is your IP address? I can look it up in the database and see if it is associated with a request currently there. |
|
|
|
as I am using xapo for my transactions so heard for the first time about that when a fees is given less than the require then it will be cancelled. Now I learned that why some services and some people do not progress in deal when the transaction get at least 1 confirmation. Is there any calculator with which we will find that how much will we pay the fees for any amount of transaction?
Fees are not dependent on the amount being transacted by the size of the transaction in bytes. It all depends on how many inputs and outputs your transaction has. Most modern wallets will dynamically calculate fees for you by analyzing the blockchain. This site: http://bitcoinfees.21.co/ does a pretty good job too of a satoshi per byte breakdown of fees. |
|
|
|
For me that is a great tool to check the parameters to my account and to check the activity status of my account but sometimes it show 1 or 2 posts less than what the total of mine. so I go to the catche and clear the catche then come back and find everything working better. can I know why it happens?
Interesting. Your browser might be caching previous results so you aren't actually seeing what is newly generated. |
|
|
|
No one can accurately estimate how long a confirmation will take. Your fee is too low, at ~20 satoshis per byte. According to https://bitcoinfees.21.co/#delay it can take you anywhere from 4 blocks to 22 blocks (or even higher) to get a confirmation. |
|
|
|
Also will i have to set a new password or encrypt the wallet ?
Yes. Nothing is carried over from the old wallet. |
|
|
|
|
If you upgraded to 0.94.1 (which I hope you did), then there isn't a setBlocking method. You don't need it.
|
|
|
|
It is a common misconception that the hash has to start with a number of zeroes. It actually doesn't. The hash has to be a number less than the target, and it just so happens that hash will have a lot of zeroes, but the zeroes aren't actually counted or anything like that. The block header is the first 80 bytes of the block. You can get it by getting the hexdump of a block. In Bitcoin Core, you run where <hash> is the block hash. This will get you the hex of the block. Just take the first 80 bytes and you will have the block header. There is a field in the header called nBits. This is a compact form of the target. Follow the instructions at https://bitcoin.org/en/developer-reference#target-nbits to convert that into the target. Then just check that the block hash is less than that target. If it is, then that hash satisfies the proof of work. |
|
|
|
|
Log files please.
Try running a rescan. Go to Help > Rescan Databases and then restart Armory.
|
|
|
|
Great set of instructions thank you  , i think to be safe i will just the funds to another wallet i have in the mean time. so a few question's, - will following this procedure allow me to keep all my old addressess ?
No. This moves all of your fund to a new wallet with new addresses. You should move the old one out and put the new one in. Hold onto the old one as your backup of the old one. |
|
|
|
Follow these instructions very carefully. Make sure you backup. - Start with Bitcoin Core stopped
- Move your wallet.dat file out of the Bitcoin datadir
- Start Bitcoin Core. It should create a new HD wallet
- Get an address from the wallet. Copy it somewhere safe.
- Stop Bitcoin Core. Backup the new wallet file in the Bitcoin datadir
- Move that wallet.dat file out of the datadir to a safe location
- Move your old wallet.dat file back into the datadir
- Start Bitcoin Core
- Send all of your Bitcoin to the address you copied down earlier. Wait for a few confirmations
- Stop Bitcoin Core
- Move your new wallet.dat file back into the datadir
- Start Bitcoin Core. You should see the Bitcoin in your wallet now.
|
|
|
|
|
Doesn't the newTheBDM call have to happen inside of the init? Otherwise it won't run?
Don't make a duplicate thread just because you aren't getting an answer within an hour. Be patient. People don't live on this forum, and Armory is a somewhat niche software. There are only a few people who can actually answer your questions.
|
|
|
|
|
You have to call newTheBDM first in order to setup the TheBDM so that there is actually an object associated with TheBDM.
|
|
|
|
Ok I am trying to extract the raw transaction from the blockchain, and I am running into a problem:
AttributeError: 'BlockDataManager' object has no attribute 'setBlocking'.
Can you show us your code? Yes I am using armory 0.93.3, how does that make a difference, and I have already compiled c++ files in cppForSwig, even than I am running into this problem, can anyone explain me why?
Thanks in advance
It matters because things have been improved in the newer versions. Your database will be significantly smaller (in MBs instead of GBs). Some optimizations have been made. In general though, it should not affect how you interact with the BDM though. |
|
|
|
|
Try going to File > Settings and uncheck the box for "Let Armory run Bitcoin Core in the background". Then Stop Armory and start Bitcoin Core manually. Make sure it is fully synced. That start Armory and see if that works.
|
|
|
|
|
Show Posts
