I attempted to download the bitcoind blockchain from scratch and kept getting a database error after a few hours even with the -reindex switch to which I find odd since I have been running bitcoin 0.13.0 for over a year on this SSD without issue . I ended up restoring a backup copy of the blockchain that I have and bitcoind was stable and synchronizing. Then I removed and re-installed Armory 0.93.3 and in about an hour or so, Armory rebuilt its' database successfully and it is fully functional. The blockchain I have works fine with Arnory 0.93.3 but won't work with 0.94.1. So, I think I am going to try Armory 0.95 when its out and see if it works with my system next. I seriously doubt that I have corruption on this SSD.
That's quite interesting. You can try out the latest testing build from https://github.com/goatpig/BitcoinArmory/releases/tag/v0.94.99.1-testing. This one is basically the final version as we have fixed all of the previous bugs and issues and haven't found anymore. We also need people to test it  |
|
|
|
|
Bitcointalk was hacked in May 2015. This exposed usernames, email addresses, etc. That's how spammers got your email.
|
|
|
|
Do exactly this from the Bitcoin source dir. cd depends
make
cd ..
./autogen.sh
./configure --prefix=`pwd`/depends/x86_64-pc-linux-gnu
make
The binaries produced should work across platforms. |
|
|
|
|
You should use the depends system and compile the libs. Then you can build with those and it would work.
|
|
|
|
|
As an extra precaution, the Admins have temporarily banned goatpig's account from posting and sending PMs.
|
|
|
|
When calculating SHA256 on the first 80 bytes I get:
a2cca229c9e96b9b71b1507e8f71631da7840c750a94c3c199a0ce371f51caa0
But the “proof of work hash” that I want to generate is:
0000000000000000047db8fc3e7265104fd042697b8cc25d66f7fedc5ce572d9
What am I doing wrong?
First of all, you have to hash it as byte data. You have hashed it as string. Secondly, the hash is actually SHA256 Double, so you need to hash it, then take that hash and hash it again, both times as byte data. The result should be the block hash in reverse byte order (it's one of the endians, I can't remember which). |
|
|
|
Ok so i have followed the Procedure above, but no where does my wallet show HD i thought i heard that it was to have an HD bottom right corner? also should i not have a seed of words?
The HD thing at the bottom is in the next version. Apparently it didn't make it into 0.13.0. Bitcoin Core does not support BIP39 Mnemonics, so no seed words. |
|
|
|
Actually - one more question: If a miner does not specify the full miners' fees they are entitled to are the BTC lost?
I'm guessing the answer is no as the next block would be entitled to pick up these missing BTC, as long as it doesn't exceed the total permitted BTC for that block depth?
IIRC if the miner does not specify the full reward (subsidy and fee) then whatever they missed will be lost. This has happened before; a miner (midnightmagic I think) missed one satoshi in the rewards so now that satoshi is permanently lost. |
|
|
|
|
Start Bitcoin Core with the -reindex option.
|
|
|
|
Apps for this forum are currently hard to do. I wrote a basic one for the forum: https://github.com/achow101/BitcointalkForum but I have since stopped working on it. If anyone wants to continue work on that, then feel free. The issue with writing apps for the forum is the lack of an API. Right now everything must be done by scraping HTML and then figuring out the correct HTTP requests in order to post. This takes a lot of time and it isn't optimal. When the new forum comes out, it should be mobile friendly and have an API so apps will be easier to write. |
|
|
|
|
Are you fully synced? Do you see any transactions that are marked as "conflicted" in the transactions list?
|
|
|
|
The reason i asked this question is i saw a newbie member wearing avatar in his/her profile and other members noticed it too but can't locate the thread where i saw the post to share the link here.
Anyway, not a big deal though. Thanks for all the input!
-WK
A few years ago everyone could have avatars. Then there was some security bug found and some spamming happened so Theymos restricted avatars to Full Member and above. However any Newbie, Jr. Member, or Member who had an avatar at the time of that change could still have their avatar. They just couldn't change it otherwise they would also have to wait until they were Full Members. |
|
|
|
If 20 years old person wan to use BTC and ETH cryptocurrencies to store main part of his/her life savings for next 60 years, how big risk is there the developers of the cryptrocurrency will steal his money
Very low. The developers of the reference implementation (i.e. consensus rules) cannot steal your Bitcoin without a hard fork. That hard fork would require that the miners agree to that change. If the developers did something malicious or suspicious, they would no longer be the developers of the reference implementation because the software labeled as the reference implementation would be changed. or cryptocurrency will "bankrupt" some way so his json wallet key file will become useless?
It is entirely possible for a cryptocurrency to be abandoned and be "dead". This happens to a lot of altcoins but it is unlikely to happen to Bitcoin. |
|
|
|
|
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.
|
|
|
|
|
Show Posts
