Hopefully this is clear. Is code OK or would a pastebin link be better next time?
I'd rather you use pastebin. What is your issue besides the illegal instructions issue? (Use clang to build if you want to avoid that one.) Hi. it seems that armory is always loosing and re-establishing connection to Bitcoin core as the rellevant system notification is flashing all the time. So it takes for ages for Armory to prepare databases (after only 5 days rest). It shows 0% for more than an hour. Figures near the relevant band are changing sometimes, 18, 21 ...31 .. 29 ...37..46 ..83...81...79...again 81.. and so on (What do those figures mean? They are changing in not predictable manner) . How to fix the issue of database building reluctancy ? (the latest Armory, 0.14.1 core + Win 10 pro, 16 Gb RAM. i7)
Start BitcoinQt manually and let it sync before starting Armory. |
|
|
|
Would make sense to allow Segwit generation also in the offline version.
Minor annoyance -- Offline Armory appears unable to sign transactions from SegWit addresses unless manually put into Expert mode and select C++ signer.
Specifically, from a SegWit UTXO to two SegWit addresses plus an OP_RETURN
That's semi by design, don't want it to be too easy to shoot one's self in the foot yet. Will remove the limitations in the next point release. |
|
|
|
|
Afaik, the encrypt suffix is added when you create an encrypted copy of an otherwise unencrypted wallet. The UI has been changed along the years to reduce the changes people would just create uncreated wallets by default (like while restoring from a paper backup).
If you're concerned your wallet is not encrypted, load it into Armory and check for yourself. If it is not, sweep the funds away asap.
|
|
|
|
0.96.2 is out. The use of SegWit has been enabled on the mainnet starting this release. SegWit availability is checked through your node's WITNESS service bit, i.e. connecting Armory to a node that does not advertise this bit will disable SW in the GUI. Changes: == Added ==
- Enabled SegWit on the mainnet. Running against a node with WITNESS service bit flagged will allow you to create SegWit addresses.
- Improved DB scan speed (~80% faster) and stability.
- Reduced DB memory usage (~20% less).
- Supernode DB mode. This isn't optimized for consumer grade computers, use at your own risk.
- The MAX button in the Send dialog has been changed to a checkbox, effect is now binding.
Maximum value will be calculated on any change.
- You can now create OP_RETURN outputs from the Send dialog. This feature is only available in Expert mode.
- You can now pick the signer of your choosing in Expert mode.
- Added BCH on top of the legacy and 0.96 C++ signer.
- Improved verbose on ZC broadcast failure.
== Fixed ==
- Fixed benchmark timers on POSIX systems.
- Fixed several Linux build configure bugs.
- Properly update RPC state in GUI on connect/disconnect events.
- Various zero conf bugs.
- Scan progress notification.
- Properly display comments for non legacy addresses.
- Digital exports will be saved under the proper file extention in Windows.
== Removed ==
- Removed armoryd from the repository. armoryd was moved to its own repository (https://github.com/goatpig/armoryd)
Binaries: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.2Note: OSX and offline RPi packages are on the way. |
|
|
|
First I sent you what I thought was the relevant part of armorylog and then sent you the full logs twice...
Didn't realize that. /edit: I even tried running armorydb manually with these switches: --db-type=DB_BARE --ram-usage=1 --thread-count=1
https://github.com/goatpig/BitcoinArmory/blob/master/changelog.txt#L235You need to wipe your DB to use DB_BARE, the db mode is permanent once set. Basically, you need to create a fresh with DB_BARE once, and that will fix your issue. |
|
|
|
How are the new builds coming? Itching to get started using SegWit, and compiling for windows is a pain.
Sometimes today maybe. Creating offline packages is a pain. |
|
|
|
|
I've tried to reproduce this several times in the past and still can't.
You need to give me more details:
- What fee did you pay?
- Is there change?
- Is the tx RBF?
- How many coins did you select?
- Are the only coins you have left to spend change?
- Does this happen while the tx is unconfirmed? Does it goes back to normal after confirmation
- There's no evidence in your log that you broadcast anything. How did you push this tx?
- Need to see the DB log as well.
Anything you can think of can be a clue. Also make use of paragraphs, it's hard to read a unified blob of text.
|
|
|
|
|
update to 0.96.1 and try again
|
|
|
|
It would probably be useful if the old site was taken down or a notice put up or a redirect put in... but I suspect it never happened because "reasons"...  I don't own it and have no control over it. ATI wants to keep their brand alive, therefor they keep running this page, and search engines just see that. |
|
|
|
|
Sure, flesh it out with a troubleshooting FAQ and I'll sticky it.
|
|
|
|
|
There's no support for the BCH signer with lockboxes because lockboxes are not covered by the new C++ wallet interface. I'd have to do that first to even look at the signer part.
|
|
|
|
|
You're using python3, armory uses python2.
|
|
|
|
|
I've spent my BCH accross hitbtc, changelly, shapeshift, poloniex and bittrex. They all worked ok. Changelly was the least annoying.
|
|
|
|
|
Update to 0.96.1 and try again.
|
|
|
|
|
Show Posts
