I don't really intent to moderate the gh-pages beyond the regular sanity checks. It's really intended as a community maintained page, expected me to be much laxer with PRs to that branch than any actual code branch.
That is good to know, thanks. Grabbed the repo and had a play around - I had some rather annoying issues getting Jekyll going, but I can't remember a time that ruby (with native gems) has been a smooth experience on Windows! I'll see about making some PRs to give the site some TLC as a starting point. |
|
|
|
So it seems to me that I have to find the "original" legacy (P2PKH) address that Armory used to generate a segwit address? But I couldn't find it anywhere within Armory.
Right, but that isn't how Armory generates the addresses nor, as far as I know, how the standard works. There isn't normally a corresponding legacy address for each segwit address. Core's addwitnessaddress is a bit of a stopgap until proper support is there, which may only be a few weeks away. Happy to be corrected here. Are you wanting to move your coins and are basically stuck without a working Armory setup currently? |
|
|
|
|
I take it you've tried using the output address from the import as the address for addwitnessaddress?
Unless I've done something wrong while testing that, that doesn't work either. Core's segwit support in 0.15.x is not quite ready yet from what I've read - Going on discussion from their github I'm pretty sure 0.16 will offer compatibility with standard P2SH-P2WPKH, though.
|
|
|
|
ok - so went back to o.96.3 and splash screen is ok there is now some movement as well on the progress bars "building databases"... the target field is currently: "C:\Program Files (x86)\Armory\ArmoryQt.exe" and i tried "C:\Program Files (x86)\Armory\ArmoryQt.exe --satoshi-datadir=D:/BitcoinCore" and got an error. "BitcoinCore" is what i named the folder on the SSD which logs exactly should i post? also, no privacy risk with posting logs  ? "C:\Program Files (x86)\Armory\ArmoryQt.exe" --satoshi-datadir=D:\BitcoinCore Note where I've moved the second " and using a backslash rather than a forward slash. If your external SSD is D:\ then that should do the job. Some privacy loss with logs. Username and CPU info mostly. See whether the above helps or not first. |
|
|
|
|
How many BTC are you trying to send?
|
|
|
|
Steady now, people are busy over the holiday period. Provided you know the password for your wallet and the wallet definitely contains that address, your coins are not lost. Gotta work with us, though - if you don't give us the info and follow the instructions given it is going to be an awful lot more difficult to help you. Have you actually downloaded and installed Armory 0.96.4 RC1/ 0.96.3.99 as instructed? Report back once you've done that, okay? |
|
|
|
I downloaded 0.96.3.991 - thanks Unfortunatly, I wasnt able to solve the problem using the fix you suggested. I recived an error message saying: "The name specified in the target box .... is not valid. make sure the path and file name are correct" - can you please show me EXACTLY what the "target" field is supposed to show? also, now when i try to launch Armory it freezes on the splash screen, "ArmoryQT.exe is not responding" I imagine these two issues are related ...  clarification - I am only storing the Bitcoin Core info on the SSD (D:). Armory and Bitcoin Core program are on C: help? The freezing on the splash screen is a known issue with RC2 on Windows. Either grab RC1, use the workaround in the pinned RC2 thread, or wait until goatpig can fix it. As for your actual issue: Where exactly has bitcoin core downloaded the blockchain? You said on an external SSD, but need more info than that. Can't tell you exactly what it should look like because your setup will be different to mine. You can paste here what your target field looks like (with your attempted change) and we can help point out what might be wrong. Probably the most important thing here is to post your log files on pastebin.com or another service and add the link here so we can see what is going wrong. |
|
|
|
I wish things were that simple. My understanding is that the old site is going to be maintained, even if the maintainers insist on uploading only major versions. It's not my call. The best I can do is try to spread the word. I have some ideas regarding how to do that, but even then, I don't control goatpig's site (i.e., I can only do so much).
That is a strange arrangement, but I guess it is what it is. Yeah, at the end of the day goatpig still needs to approve the PRs for the gh-pages branch too and of course that is at his discretion. Thanks for the info and the FAQ  |
|
|
|
Please mate could you point me to some literature about these?
TIA
Not sure what kind of literature you are after. A changelog? Or did you mean the issues with RC2 I mentioned? Latter is in the pinned thread. What's the difference? That's what I was going to do originally, but I was unsure about sending funds from one address to another in wallets in the same instance of Armory. Then it seemed that sweeping was the "correct" way to do that.
Sweeping is the convenient way. It stops being convenient as soon as something about your setup decides it should charge you 2 BTC in fees! Under the hood, sweeping will still create a transaction. Just send the coins like a normal transaction to the new wallet. There is no problem sending to and managing multiple wallets in one instance of Armory. |
|
|
|
|
Look at the pinned threads by goatpig in this forum.
|
|
|
|
Make sure ArmoryDB.exe isn't running.
Delete this folder:
C:\Users\x\AppData\Roaming\Armory\databases
I downloaded version 0.96 and having this problem as well. I followed the path mentioned above but the furthest I can get to us "Users". Any other way? Oof, old thread - Go grab 0.96.3 at least if you haven't. You are looking for your username rather than "x", right? Another way is by typing in explorer to get you to C:\Users\x\AppData\Roaming\ |
|
|
|
Hang on, do you mean BTG (Bitcoin Gold) or BCH (Bitcoin Cash)? Bitcoin Cash. I'm not familiar with Gold yet. I assume that's yet another fork... I'm not sure what to do about the sweep. Is there a prebuilt binary of the Armory RC? I'm not set up to build from source. I'm running Core 0.15. Armory can be frustrating. 0.96.3 is certainly the most stable version I've seen in a long time, but it still seems to have a hard time staying connected to bitcoind and I have to restart it more than once before it comes up and stays up as "online". Okay. Yeah, gold is another fork. Worth about what BCH was worth early on. Have you had a look at the pinned BCH thread? Binaries are up on github. Some issues with RC2 on Windows, FYI. As for sweeping, you may not have to immediately. Since you can sign the BCH transaction in Armory itself, you won't expose the private keys in a less trusted wallet. You will expose your public keys for your BTC. This is a problem, but not on the same scale as private keys. You should still move your coins, but to me it isn't the same "Oh god the building is on fire" state of urgency as potentially leaking private keys. Relevant info from goatpig in the BCH thread: Whether you have sent your coins to a KYC exchange or not, you want to cycle your wallets on the other chain afterwards, i.e. if you dumped BCH, you want to move all these coins on BTC chain to a fresh wallet.
The reason for this is that your public keys will be exposed on at least one chain. One of the security layers of Bitcoin is that public keys are behind hashes up until you spend the coin. Once you sign coins on one of the chains, you lose this layer. This is a major reason why you do not reuse addresses in Bitcoin. This is particularly relevant if you have coins in long term cold storage: cycle them if you touch the keys! Trade security for convenience and vice versa. Up to you to decide on that one. |
|
|
|
No, just trying to play with BTH (in a different wallet, in a VM on a different machine). My understanding is that I should transfer my existing BTC to a new address before importing the private key to the BTH wallet.
Not sure how I should proceed here.
Ah, then yes - moving it first is good advice - Don't risk ~$28k for the sake of ~$500. That said, Goatpig is working on a BTG signer for Armory, but no ETA or any promises there. If you're willing to sit tight you could wait for that and you won't expose your private keys. If not, then you'll need to send to your new wallet. Get it setup to receive at a P2SH-P2WPKH (segwit) address, then figure out what fee you're willing to pay/how long you're willing to wait for the BTC tx to get confirmed. Core 0.15 & the current RC of Armory have a smart estimation feature that might help you decide, but there are all sorts of charts/ graphs online - I can definitely say you don't want to pay 2 BTC in transaction fees. Right now... somewhere in the region of 100-300 satoshi per byte possibly. Edit: All of this is still a lot of greek to me. I don't know what a "segwit" address is.
Segwit, also known as segregated witness, is a fancy name for an address format that basically makes transactions smaller, thus reducing transaction costs for you. Instead of addresses looking like 1blahblah, they look like bc1blahblah or in Armory's case 3blahblah. You don't have to use it, but unless you are in a rush it'd make sense to read up on it. Edit2: Hang on, do you mean BTG (Bitcoin Gold) or BCH (Bitcoin Cash)? Just realised a one letter typo would get you to both. |
|
|
|
Yeah, that looks bad. The fee is the miner processing fee, and in BTC from what I can tell: 0.0271717 + 2.1533283 = 2.1805 Normally you'd hope that the fee would be the smaller number  Something strange in the estimation there if you really only have two transactions. Should be safer to do a manual send from old wallet -> new wallet. You may want to look at sending to a segwit address too to save you fees down the line too. Are you worried that the original wallet is compromised? |
|
|
|
Meant to report back on this. I think Armory is hanging when starting the db process with with popen. 2017-12-29 19:09:36 (WARNING) -- SDM.pyc:396 - Spawning DB with command: ./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="L:\BC\blocks" --datadir="C:\Users\PhoenixFire\AppData\Roaming\Armory\" --dbdir="L:\ArmoryBC\databases"
2017-12-29 19:09:36 (INFO) -- ArmoryUtils.pyc:679 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="L:\\BC\\blocks"', '--datadir="C:\\Users\\PhoenixFire\\AppData\\Roaming\\Armory\\"', u'--dbdir="L:\\ArmoryBC\\databases"'] Logs stops there and no DB process starts at all. That said, I can spawn ArmoryDB manually like so: start ArmoryDB.exe --db-type=\"DB_FULL\" --cookie --satoshi-datadir=\"L:\BC\blocks\" --datadir=\"C:\Users\PhoenixFire\AppData\Roaming\Armory\\\" --dbdir=\"L:\ArmoryBC\databases\" And then run ArmoryQt and everything works fine. "start" not required, just a preference. Edit: Got it to create the log in the install dir: (ERROR) ArmoryUtils.pyc:3723 - Unsupported language specified. Defaulting to English (en)
(WARNING) SDM.pyc:396 - Spawning DB with command: ./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="L:\BC\blocks" --datadir="C:\Users\PhoenixFire\AppData\Roaming\Armory\" --dbdir="L:\ArmoryBC\databases"
Exception WindowsError: (6, 'The handle is invalid') in <bound method Popen.__del__ of <subprocess_win.Popen object at 0x0000000004A5FEB8>> ignored
Edit2: I can start Qt, let it hang, then start ArmoryDB manually. Qt then wakes up and loads the wallets just fine. |
|
|
|
Looks good, droark. I was going to fill in the "Why is Armory bugging me about backups" question, but tbh borrowing and paraphrasing etotheipi's pinned post would probably go a long way towards it? Not really for the FAQ, but on the list of things that'd help reduce repetition in the forums: As I understand it, goatpig has no control/access to the old Armory site? If so, need to shout loudly that btcarmory.com is the right one - still seeing a surprising amount of people grabbing 0.96.0 from the old site and then hop onto the forums when it doesn't work, and saying they have the "latest". I'd say a pinned thread for just that info but there are already quite a few. Unfortunately bitcoinarmory.com seems to be higher in the search rankings - More content might help that but a redirect from old -> new would have been ideal. I can't really help with python or C, but I can certainly volunteer to help with the website side of things. In that vein, and again not necessarily a part of the main FAQ, but common troubleshooting information and some sort of support template thread that can be used to help users provide info when having problems e.g. Armory and Bitcoin version and (possibly) how to find the version numbers. OS version too, probably. How to find logs and where to upload them so devs can see them. Stuff like that - sound sane? |
|
|
|
Strange... I've rolled back to RC1 for now which is still fine, so not the end of the world. Did some digging, this could be relevant: https://github.com/giampaolo/psutil/issues/811 (I'm running Win7 so it shouldn't be the outdated OS side of the issue) If I get desperate I'll try getting a Windows build env setup and giving that a whirl. Have a happy new year, both of you! |
|
|
|
Thanks, Goatpig. Grabbed the installer for Win64. Got an error about write permissions for a log file in Armory's install dir, then ran as admin to allow that to work. Got a fatal error at that point: Traceback (most recent call last):
File "ArmoryQt.py", line 38, in <module>
File "psutil\__init__.pyc", line 139, in <module>
File "psutil\_pswindows.pyc", line 16, in <module>
File "psutil\_psutil_windows.pyc", line 12, in <module>
File "psutil\_psutil_windows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found. I do have a (new?) file named "psutil._psutil_windows.pyd" - no similar problem with RC1. |
|
|
|
EDIT3: Looking at the logs, this is what is says:
"Log file opened at 23:30:55.000: C:\Users\Bla\AppData\Roaming/Armory/dbLog.txt
-INFO - 23:30:55.000: (..\main.cpp:32) Running on 8 threads
-INFO - 23:30:55.000: (..\main.cpp:33) Ram usage level: 50
-INFO - 23:30:55.000: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 9001
-ERROR - 23:30:55.016: (..\BDM_Server.cpp:1270) There is already a process listening on 127.0.0.1:9001
-ERROR - 23:30:55.016: (..\BDM_Server.cpp:1272) ArmoryDB cannot start under these conditions. Shutting down!
-ERROR - 23:30:55.016: (..\BDM_Server.cpp:1273) Make sure to shutdown the conflicting processbefore trying again (most likely another ArmoryDB instance)."
Have you set Armory to specifically use port 9001? Mine uses a random-ish high port each launch and I'm fairly sure that is the default. Either way, something is listening on port 9001, and ArmoryDB is trying to use that port too. As it says, it could be another ArmoryDB process that you would need to kill, or another program entirely. If it is ArmoryDB, it is possible that it is choking on a bad DB, depending on which version you upgraded from, which is usually resolved with a rebuild and rescan. EDIT2: I'm also using bitcoin core 0.13.1, should I update?
Probably, yeah. I think Core will need to update the DB format so be prepared for that to take a little while. Hello ConnyH,
Bitcoin Core will never ever follow the BCH chain (no matter which version). Replace Bitcoin Core temporarily with Bitcoin ABC and let that work as backend to Armory. Then you will be getting there.
EDIT1: And then move your BCH funds to a new wallet you create in a wallet that intends to support the future hard forks of BCH (e.g. Bitcoin ABC). Goatpig has made it clear, that he will not support Altcoins in Armory other than moving your hard-fork funds out of Armory wallets.
Depends on how they intend to split the BCH and the situation with UTXOs, but ABC isn't always required. All covered in the BCH thread, though. |
|
|
|
From the thread just below yours: |
|
|
|
|
Show Posts
