|
Double check your firewalls and any port forwarding.
|
|
|
|
Getting error "DB version Mismatch use another dbdir" Any help is appreciated.
Go to the armory data directory (os dependent) and delete the "databases" folder. Then start Armory. |
|
|
|
I tried doing a clean install of 0.95.1 and follow the post above, but no luck. Still stuck on build databases and doesn't build the database.
It only works if I start bitcoin-qt and Armory separately.
Do you see the progress bar move at all or does it stay stuck at something like 1%? hi there,
reddit pointed me to the updated armory, so glad it's still going! I've been trying to upgrade from .93 and bitcoin .11 to the latest version .95.1 and the latest core 13.1
I've had a problem whereby it's trying to scan the blockchain (I know it's up to date), and saying 1 second on scanning transactions and not going further. I tried to rescan and rebuild databases, and nothing happens when I reboot (although I did get the pop up welcome message).
I'm going to try and reinstall completely to see if that fixes it, but if I'm doing something obviously wrong, please let me know.
Thanks
Jamie
First, you need to delete the entire folder named "databases" inside of armory's datadir. Then try again. If you do not see any of the progress bars moving and stuck at 1%, that usually means that the ArmoryDB isn't running or crashed. Stop Armory and make sure that there are no processes named ArmoryDB running. Then try again. |
|
|
|
Hi folks,
Will segwit soft fork require any changes in mining software for solo mining?
Thanks.
If you want to mine segwit blocks, then yes. If you are using GBT, checkout BIP 145 which specifies GBT changes for segwit. Otherwise, no. |
|
|
|
|
The dumpwallet rpc command exports all of the keys to a human readable text file. You can then use a script to import all of those private keys into your new wallet.
|
|
|
|
|
Nope, someone just turned on a lot of mining power onto testnet briefly. This tends to happen since the difficulty is so low. At one point I remember there being several blocks being mined every second.
|
|
|
|
|
Option 1 is what most services do. You give out a new address for each deposit and just calculate the balances of the user as they deposit and store that somehwere.
|
|
|
|
Anyway, I'll leave with a final question. How reverse compatible might Armory be? I was wondering whether anyone has had more success in retrieving their savings by running an older version. The one I originally used seemed flawless as far as I can remember. Or would it not work with recent updates to bitcoin core etc?
The wallet files are backwards compatible, but not necessarily everything else. For one thing, various changes on the network have made versions older than 0.93.3 not likely to be able to successfully send transactions. The databases have been upgraded. There was a massive change from 0.93.3 to 0.94 which drastically improved performance. 0.95 also changed the databases again, which is what is causing your problems. This also increases performance. Most of the issues that we see people hit are with Windows (because windows is stupid sometimes) and Macs (because goatpig doesn't know much about Macs). Also, once segwit is activated, all versions prior to 0.95 will not work if you use Bitcoin Core 0.13.1+. Your problem should be solved by deleting ~/.armory/databases again and letting it rebuild. It is not like 0.93.3 which could take ages to build, it should only take ~20 minutes, maybe an hour at most. If the progress bar doesn't move, then usually that means that ArmoryDB did not start. |
|
|
|
This time the port was clear and ArmoryDB was not running, but after a few minutes I got,
The DB has returned the following error:
DB version mismatch. Use another dbdir!
Armory will now shutdown
Delete ~/.armory/databases and try again. I'm going to see if I can import my walled private keys rather than continue down this bug ridden armory route.
Do you realize that there is only one full time developer on Armory, with the occasional contribution from some other people (including myself)? Testing is very hard to do with such a limited amount of man power, so of course there will be bugs. We have worked to address all the bugs that come up, but very few people actually help us test and we can't possible hit every single edge case that people somehow come up with. |
|
|
|
thanks for the reply. sorry its datestamp. ok so i can recover the wallet. what about the bitcoins?i can recover that? I use multibit
Install the latest MultiBit HD. When you start it, choose the option to recover a wallet and just follow the instructions. |
|
|
|
Segregated Witness (segwit) is a soft fork which defines a new set of output scripts which will have their signatures located in a new witness part of the transaction. That witness area is not used for calculating the transaction id, thus completely removing transaction malleability. Segwit also defines a new sighashing algorithm for determining the data that is signed for those new output types. This new algorithm makes sighashing linear instead of quadratic. Segwit also replaces the maximum block size with a maximum block weight, which is similar to block size. The witness part of the transaction is given a weight factor of one while the rest of the transaction receives a weight factor of 3. Read this: https://bitcoincore.org/en/2016/01/26/segwit-benefits/ for more information If you want the full technical details, read BIPs 141, 143, and 144. |
|
|
|
|
Unless there is a significant increase in usage, I will be shutting down the site on December 1st.
|
|
|
|
I have deleted that file .lock
But now bitcoin doesn't start at all anymore
That's interesting. How does it not start? Does it give you an error or does nothing happen? Can you post the debug.log file? |
|
|
|
When i click on the link with my left button i get this error
"kan geen lock krijgen op gegevensmap F:Bitboin. Bitcoin core draait waarschijnlijk al. Toegang geweigerd."
I think this means in english
can not get a lock on map F:Bitcoin. Bitcoin core is probably already running. Access denied.
Ok.. Go to the folder containing data directory. Make sure that the properties of the data directory give your user full permissions. Then go inside the data directory. Make sure that Bitcoin Core is not running. If you see a file named .lock, delete it. Then try starting Bitcoin Core again. |
|
|
|
I have doen this, but when i want to start up bitcoin with my link on my taskbar, i Always have an error. I do Always have to start with clinking right and than choose "als administrator uitvoeren" (this is in my language). Than i can open my wallet.
In my debug is see the following lines :
2016-11-05 13:01:02 Default data directory C:\Users\Hoofdgebruiker\AppData\Roaming\Bitcoin
2016-11-05 13:01:02 Using data directory F:\bitcoin
2016-11-05 13:01:02 Using config file F:\bitcoin\bitcoin.conf
I have moved everything from my C-drive to my external harddisk F.
Is there a way so that when i click on my link, i go directly to my F and i don't have to use the link "als administrator uitvoeren" (this is in Netherlands, don't know how it is called in english.
I imagine that means something like "run as administrator", right? That means that there is a permissions problem. Right click on your drive and look at it's properties. Make sure that you are allowed to read and write to the drive. |
|
|
|
It seems to be slower than 0.94.
It synchronised with the network in a few seconds, but has made no notable progress on 'Build Databases' and 'Scan Transaction History' in two hours. Oddly, the 'Scan Transaction History' on 0% says, '1 second'.
I think I'm going to have to figure out how to extract my private keys from the wallets to import into BitcoinQt.
Stop Armory. Make sure that there is no process running named ArmoryDB. Make sure that nothing is using port 9001. Then try again. What happened was that the backend database engine failed to start. |
|
|
|
Those are spam nodes. You should just ban them. Is there an easy way to ban multiple connections from the same IP, without say, doing something drastic like blacklisting AWS IP addresses.
Not really. |
|
|
|
I saw from the 'Armory 0.95 is out' thread that allot of people were having problems so I've been sticking with 0.94.1. I'll try it though. Um, I couldn't find installation instructions sudo apt-get install armory_0.95.1_amd64.deb won't do it. 0.95.1 fixes 0.95 issues (which were mostly windows only). The command to install should be dpkg -i armory_0.95.1_amd64.deb
At least I have my formed wallets, which had taken weeks to achieve. I'll have to redo one of them as it kept telling me that I had the wrong password for it, but I'll be trying to import the wallets into Bitcoin-Qt as soon as it has caught up with the blockchain.
Well you will need to delete the databases folder inside ~/.armory since the database format has changed. Luckily the new databases are much faster than the old one so it will go much faster. |
|
|
|
do you agree pools should not be 100% trusted to not make bad data
do you agree pools should not be 100% trusted to not be malicious
meaning nodes have a real reason to FULLY validate
do you agree that orphans do happen and while nodes cannot FULLY validate a transaction as not being malicious/ bad more orphans can occur
and while not all pools are uptodate there is a heightened risk even further
do you agree that nodes should not 100% trust data they receive
do you agree that nodes should 100% independently and FULLY data they receive
overall do you agree that for those not upgrading.. they should be more wary of risk
Yes. anyone can steal someones chequebook and right a destination an acceptable date and an acceptable amount.. but the cheque is not valid unless its fully validated.
any banks cashing a cheque without the signature risks a double spend. and should "accept" the cheque and let it pass on to other more uptodate banks to validate the cheque using uptodate technology before its then deemed safe
Please stop with your analogies. They are usually incorrect. I know exactly how Bitcoin works; just because my opinion differs from yours does not mean that I am wrong nor that I don't understand how it all works. again wait a few confirmations to ensure it doesnt orphan because bad data and malicious intent is and always will be a risk and thats why nodes are important
Yes. Why are you asking all of these questions? They are irrelevant to the point at hand. At no point in time have I ever said that fully validating was bad and that miners were trustable. All I was trying to do was to point out that the statement "non-upgraded nodes just blindly accept segwit transactions" is incorrect. You have taken this and spun it way out of control. Just stop. |
|
|
|
Yes. You can copy the entire Bitcoin Core datadir from your internal drive to the external drive. You will have to always start Bitcoin Core with the -datadir option so that it knows where to look for the datadir though.
What do you mean with the datadir? I am not familiar with all these therms. The datadir is the data directory. It is where your wallet, the blockchain, and other files that Bitcoin Core needs. It does not contain the binaries to run Bitcoin Core though. That is in the installation directory. To find your datadir, open Bitcoin Core and go to Help > Debug Window. In the Information tab, you should see a field labeled "datadir" and a file path next to it. That path points to the datadir. Cut and paste that folder to your external drive. Then stop Bitcoin Core and start it with the -choosedatadir option. See https://achow101.com/2016/07/Bitcoin-Core-Troubleshooting#option-startup for help with that. That option will open up a dialog for you to choose your datadir. Choose wherever you put the datadir and you should be good to go. Starting with that option only needs to be done once. |
|
|
|
|
Show Posts
