Topic: 0.96.4 RC1 - page 6. (Read 14281 times)

Is armory 0.96.4 RC1 the same as 0.96.3.99? I can't seem to find the download for 0.96.4 RC1. Sorry for the noob question.

SegWit is off by default. Activation is detected by the node it is running against. Therefor an offline instance cannot detect SegWit activation, which is why you need to manually enable it.


Some event increased the address chain without registering the new addresses. On the next run, they have to be scanned.

Thanks. I'm surprised it needs a commandline option, given that SegWit is off by default.

Has Armory got slower to launch recently? I had it running and synced, closed it, then immediately restarted it. It's taken several minutes to build databases and now says an hour to scan transaction history. I'm sure it used to be much quicker just a few months ago.

https://github.com/goatpig/BitcoinArmory/blob/testing/changelog.txt#L9

I'm unable to set the preferred receive address type to P2SH-P2WPKH for my offline machine. I've just updated both my online and my offline to this release. My online, connected computer allows all the address types. The offline one has P2SH-P2WPKH disabled. Is there a reason for this?

PS I really think you should have a sticky post at the top of this forum pointing to https://btcarmory.com/docs/. I just tried searching ang got https://www.bitcoinarmory.com/ again. It's not clear which is the best site to use.

It seems armory does not add the amount of the original UTXO (complete, so before subtracting fees) when signing the transaction. I fixed this in a small script: https://bitcointalksearch.org/topic/script-to-spend-bch-from-armory-lockbox-2-of-3-multisig-2309673

Hi from me.
I downloaded v 096.3.99 and it was scanning transaction history forever, never seemed to end.
I downgraded back to v 96.3:  "Building Databases" finishes after a few minutes,  "synchronizing with network" [Edit] also finishes but "scanning transaction history" runs forever and never ends.

When I quit, via the menu, it gets stuck. I need to kill ArmoryQT and armoryDB from the Task Manager.


 I run QT core 0.15.1 which is fully synchronized.

Please help. I cannot access my balances anymore.

This is on a windows10  64bit machine.

The "MAX" button functionality is broken. It can calculate the exact amount but it is not possible to spend any coins.

armorylog.txt

I've seen the same error code from another user on this topic. Actually when downgrading to 0.96.3 "MAX" button is working and I'm able to spend.

Updated to this latest version of Armory. Armory won't go online and gets to 99% scanned transactions and won't budge. I really need to get to my bitcoin but can't.

Can't I use my 0.96.3 offline signer with 0.96.4 ?

Thank you! Please let us spend 0 conf someday tho, an expert setting would be perfect

I'll look into it.

I did. I got errors when both had 0.96.3.99. The above is actually just from the online machine after restoring the full wallet onto that machine. So I wasn't using an online and offline copy any more at this point.

What else do you need from me to be able to diagnose this?

Make sure you are using matching versions on the signer and the online machine.

I've been having lots of trouble creating new transactions. I've tried from 0.96.2, 0.96.3, and even 0.96.3.99. I was successfully able to send coins stored in P2PKH type addresses, but it seems that something is keeping me from creating transactions for P2SH-P2WPKH, of which I have two.

This wallet was an offline cold storage wallet. After uploading both hot and cold computers to this version, I still had these problems. When I tried to do an offline transaction, I could successfully create the transaction on the hot computer, but then the cold computer said the transaction was unrecognized.

I then moved the whole wallet to the hot computer. It's a low balance wallet I'm just using for testing so I'm not too concerned about keeping it cold. I'll create a new cold wallet once I'm ready. I now get the following in my log when attempting to create a transaction:


What can I do to get this working?

Did you update the offline side too?

I finally got around to try the RC build on my Macbook (macOS Sierra 10.12.6).  Unfortunately, it cannot broadcast transactions.

When I load a transaction that I signed offline, I cannot broadcast it.  The usual dialog comes up, I load the transaction from file, the usual gibberish appear in the window, but Broadcast and Copy Raw Tx (Hex) buttons remain gray.  And the green text "All Signatures Valid" does not appear.  Instead, a number of exceptions appear in the log: https://pastebin.com/7pv6U5iE

I have now reverted to the previous version and have broadcasted my transaction, but I am ready to try again (and to patch the Python code to test solutions).

EDIT: It is a BCH transaction, signed with the BCH signer.

I fail to send BCH from a lockbox. I am connected to my node (Bitcoin ABC), started the Armory DB from scratch, selected the BCH signer, and disabled RBF. When I send a transaction (either directly in the dialog, or after exporting -> exporting as hex -> importing on http://blockdozer.com/insight/tx/send) I get the error that SIGHASH_FORKID is not used.

Bitcoin ABC:
2017-10-09 18:39:50 Misbehaving: 127.0.0.1:43462 peer=0 (0 -> 100) reason: mandatory-script-verify-flag-failed (Signature must use SIGHASH_FORKID) BAN THRESHOLD EXCEEDED

Blockdozer:
64: non-mandatory-script-verify-flag (Signature must use SIGHASH_FORKID). Code:-26

2017-10-09 20:39:50 (INFO) -- (PPRINT from /usr/bin/../lib/armory/ArmoryQt.py:3118)

  01000000 025661a7 bba1588e 2085052f be725eeb e0afb382 d152ffd4 7aafa8e9
  a831bf82 81000000 00fd5c01 00473044 02203fb9 6d77b6ee e47c82a1 55dfc3c4
  7b89cfc9 17c469d8 85c83c16 f1320c0a f8940220 7ed35215 d943badc 28c5e15e
  b01a001a 1a624d1d f44b4fff 333358b9 25cdb042 01473044 02203852 5fc553a8
  d134f200 9d520bf2 9c87b096 7cfaea7c db043a0d 0f6b135b f7140220 26315e4d
  88edabc7 6b39241e 6f7ea4bd 95af0c8a 31c6c497 9006724a bed70450 014cc952
  410434be 1ffcac1c fdea8f80 01e31af2 75a2b2b1 2c00461d 2727fc30 ef025116
  ba918c78 31d23bb5 bb52ef60 d098b82c d9275391 934e2fa7 24f641b5 a8f51549
  2c8d4104 a3b81cc8 fde26d66 5c11133f a6e0e562 c80122d0 fd6d25b7 9cc1478a
  7ad77d06 b403565b 0a016a6b 971c664d 686bd590 f1bd4d08 982909b1 3d45128c
  39e22bbd 4104ce75 f88b933d 0cdc647a 28d24547 0481a6b3 8caa1720 ba143fe8
  94d49c54 6a4eecc8 5b5e817a 1dda3fbb fbe5dbb7 0b83294c c9c617cd 27f1eff3
  e50ef043 0c0453ae ffffffff 2c5ce43c 90a0a120 2196b660 d48b5085 70ff1e8a
  b5ac03fd 4864cb77 8a09d3b3 00000000 fd5e0100 48304502 2100c808 7a7e467e
  3c10faef a32fd620 67ab5003 ff0bfc1f eceecb38 e6906277 eb2b0220 7b28db72
  7a1fe783 f15a5b04 93c49391 990017fb 88d9a7d5 d2498c27 c71ac6d6 01483045
  022100ff c7d05f2f e891cde2 06d5e725 8505cc2c 995eaccb f7791e07 5846e8b4
  931d2402 20158177 42b8d1b5 f1abe051 21ca5abd 390b2e82 9b3d9af5 3ed9240e
  7f307937 d9014cc9 52410434 be1ffcac 1cfdea8f 8001e31a f275a2b2 b12c0046
  1d2727fc 30ef0251 16ba918c 7831d23b b5bb52ef 60d098b8 2cd92753 91934e2f
  a724f641 b5a8f515 492c8d41 04a3b81c c8fde26d 665c1113 3fa6e0e5 62c80122
  d0fd6d25 b79cc147 8a7ad77d 06b40356 5b0a016a 6b971c66 4d686bd5 90f1bd4d
  08982909 b13d4512 8c39e22b bd4104ce 75f88b93 3d0cdc64 7a28d245 470481a6
  b38caa17 20ba143f e894d49c 546a4eec c85b5e81 7a1dda3f bbfbe5db b70b8329
  4cc9c617 cd27f1ef f3e50ef0 430c0453 aeffffff ff014277 fb040000 00001976
  a9141a33 d9d2aa52 d4ff6425 f9e98f5f c6686588 6a6588ac bd8a0700
2017-10-09 20:39:50 (INFO) -- (PPRINT from /usr/bin/../lib/armory/ArmoryQt.py:3119)
Transaction:
   TxHash:    1eb2421b07620977a49c2b2a9ab1ac4dbb4f057b1424bfdf84f9b50cf40a1ba8 (BE)
   Version:   1
   nInputs:   2
   nOutputs:  1
   LockTime:  494269
   Inputs:
      PyTxIn:
         PrevTxHash: 8182bf31a8e9a8af7ad4ff52d182b3afe0eb5e72be2f0585208e58a1bba76156 (BE)
         TxOutIndex: 0
         Script:     (0047304402203fb96d77b6eee47c82a155dfc3c47b89cfc917c469d885c83c16)
         Sender:     33Rsw83aYK9ChQx68C1aXxaJb5j5LzyLhw
         Seq:        4294967295
      PyTxIn:
         PrevTxHash: b3d3098a77cb6448fd03acb58a1eff7085508bd460b6962120a1a0903ce45c2c (BE)
         TxOutIndex: 0
         Script:     (00483045022100c8087a7e467e3c10faefa32fd62067ab5003ff0bfc1feceecb)
         Sender:     33Rsw83aYK9ChQx68C1aXxaJb5j5LzyLhw
         Seq:        4294967295
   Outputs:
      TxOut:
         Value:   83588930 (0.8358893)
         Script:  OP_DUP OP_HASH160 (13PYgef5Lsbhnk2D3W6z8zHiHiaAeHRdyp) OP_EQUALVERIFY OP_CHECKSIG

2017-10-09 20:39:50 (INFO) -- ArmoryQt.py:3124 - Sending Tx, a81b0af40cb5f984dfbf24147b054fbb4dacb19a2a2b9ca4770962071b42b21e
2017-10-09 20:39:50 (INFO) -- ArmoryQt.py:3138 - Failed to broadcast Tx through P2P
2017-10-09 20:39:50 (ERROR) -- ArmoryQt.py:3159 - Transaction was not accepted by the Satoshi client
2017-10-09 20:39:50 (ERROR) -- ArmoryQt.py:3160 - Raw transaction:
2017-10-09 20:39:50 (ERROR) -- (PPRINT from /usr/bin/../lib/armory/ArmoryQt.py:3161)

  01000000 025661a7 bba1588e 2085052f be725eeb e0afb382 d152ffd4 7aafa8e9
  a831bf82 81000000 00fd5c01 00473044 02203fb9 6d77b6ee e47c82a1 55dfc3c4
  7b89cfc9 17c469d8 85c83c16 f1320c0a f8940220 7ed35215 d943badc 28c5e15e
  b01a001a 1a624d1d f44b4fff 333358b9 25cdb042 01473044 02203852 5fc553a8
  d134f200 9d520bf2 9c87b096 7cfaea7c db043a0d 0f6b135b f7140220 26315e4d
  88edabc7 6b39241e 6f7ea4bd 95af0c8a 31c6c497 9006724a bed70450 014cc952
  410434be 1ffcac1c fdea8f80 01e31af2 75a2b2b1 2c00461d 2727fc30 ef025116
  ba918c78 31d23bb5 bb52ef60 d098b82c d9275391 934e2fa7 24f641b5 a8f51549
  2c8d4104 a3b81cc8 fde26d66 5c11133f a6e0e562 c80122d0 fd6d25b7 9cc1478a
  7ad77d06 b403565b 0a016a6b 971c664d 686bd590 f1bd4d08 982909b1 3d45128c
  39e22bbd 4104ce75 f88b933d 0cdc647a 28d24547 0481a6b3 8caa1720 ba143fe8
  94d49c54 6a4eecc8 5b5e817a 1dda3fbb fbe5dbb7 0b83294c c9c617cd 27f1eff3
  e50ef043 0c0453ae ffffffff 2c5ce43c 90a0a120 2196b660 d48b5085 70ff1e8a
  b5ac03fd 4864cb77 8a09d3b3 00000000 fd5e0100 48304502 2100c808 7a7e467e
  3c10faef a32fd620 67ab5003 ff0bfc1f eceecb38 e6906277 eb2b0220 7b28db72
  7a1fe783 f15a5b04 93c49391 990017fb 88d9a7d5 d2498c27 c71ac6d6 01483045
  022100ff c7d05f2f e891cde2 06d5e725 8505cc2c 995eaccb f7791e07 5846e8b4
  931d2402 20158177 42b8d1b5 f1abe051 21ca5abd 390b2e82 9b3d9af5 3ed9240e
  7f307937 d9014cc9 52410434 be1ffcac 1cfdea8f 8001e31a f275a2b2 b12c0046
  1d2727fc 30ef0251 16ba918c 7831d23b b5bb52ef 60d098b8 2cd92753 91934e2f
  a724f641 b5a8f515 492c8d41 04a3b81c c8fde26d 665c1113 3fa6e0e5 62c80122
  d0fd6d25 b79cc147 8a7ad77d 06b40356 5b0a016a 6b971c66 4d686bd5 90f1bd4d
  08982909 b13d4512 8c39e22b bd4104ce 75f88b93 3d0cdc64 7a28d245 470481a6
  b38caa17 20ba143f e894d49c 546a4eec c85b5e81 7a1dda3f bbfbe5db b70b8329
  4cc9c617 cd27f1ef f3e50ef0 430c0453 aeffffff ff014277 fb040000 00001976
  a9141a33 d9d2aa52 d4ff6425 f9e98f5f c6686588 6a6588ac bd8a0700
2017-10-09 20:39:50 (ERROR) -- ArmoryQt.py:3162 - Transaction details
2017-10-09 20:39:50 (ERROR) -- (PPRINT from /usr/bin/../lib/armory/ArmoryQt.py:3163)
Transaction:
   TxHash:    1eb2421b07620977a49c2b2a9ab1ac4dbb4f057b1424bfdf84f9b50cf40a1ba8 (BE)
   Version:   1
   nInputs:   2
   nOutputs:  1
   LockTime:  494269
   Inputs:
      PyTxIn:
         PrevTxHash: 8182bf31a8e9a8af7ad4ff52d182b3afe0eb5e72be2f0585208e58a1bba76156 (BE)
         TxOutIndex: 0
         Script:     (0047304402203fb96d77b6eee47c82a155dfc3c47b89cfc917c469d885c83c16)
         Sender:     33Rsw83aYK9ChQx68C1aXxaJb5j5LzyLhw
         Seq:        4294967295
      PyTxIn:
         PrevTxHash: b3d3098a77cb6448fd03acb58a1eff7085508bd460b6962120a1a0903ce45c2c (BE)
         TxOutIndex: 0
         Script:     (00483045022100c8087a7e467e3c10faefa32fd62067ab5003ff0bfc1feceecb)
         Sender:     33Rsw83aYK9ChQx68C1aXxaJb5j5LzyLhw
         Seq:        4294967295
   Outputs:
      TxOut:
         Value:   83588930 (0.8358893)
         Script:  OP_DUP OP_HASH160 (13PYgef5Lsbhnk2D3W6z8zHiHiaAeHRdyp) OP_EQUALVERIFY OP_CHECKSIG

2017-10-09 20:39:50 (ERROR) -- ArmoryQt.py:3164 - Failure message: mandatory-script-verify-flag-failed (Signature must use SIGHASH_FORKID)
2017-10-09 20:39:50 (WARNING) -- ArmoryQt.py:4111 - Called updateSyncProgress while not sync'ing

post dbLog.txt

Hi , I am using this version of release and my my blockchain is completely downloaded and then my scanning transaction history comes to like 98% and gets stuck , it has been running for 2 days now and still stuck at the same time , when i export the log file it says :
:22:08 (INFO) -- ArmoryQt.py:1687 - Changing usermode:
2017-10-02 18:22:08 (INFO) -- ArmoryQt.py:1688 -    From: Advanced
2017-10-02 18:22:08 (INFO) -- ArmoryQt.py:1696 -      To: Advanced
2017-10-02 18:22:08 (INFO) -- ArmoryQt.py:1825 - startBitcoindIfNecessary
2017-10-02 18:22:08 (INFO) -- ArmoryQt.py:1861 - setSatoshiPaths
2017-10-02 18:22:08 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2017-10-02 18:22:08 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-10-02 18:22:08 (INFO) -- SDM.pyc:173 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-10-02 18:22:08 (INFO) -- SDM.pyc:337 - Called startBitcoind
2017-10-02 18:22:08 (INFO) -- ArmoryUtils.pyc:667 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Users\\Morpheus\\AppData\\Roaming\\Bitcoin\\']
2017-10-02 18:22:09 (INFO) -- SDM.pyc:450 - PID of bitcoind: 12828
2017-10-02 18:22:09 (INFO) -- SDM.pyc:451 - PID of armory:   6092
2017-10-02 18:22:09 (INFO) -- ArmoryUtils.pyc:667 - Executing popen: ['.\\guardian.exe', '6092', '12828']
2017-10-02 18:22:12 (INFO) -- ArmoryQt.py:1861 - setSatoshiPaths
2017-10-02 18:22:12 (WARNING) -- SDM.pyc:403 - Spawning DB with command:./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\Morpheus\AppData\Roaming\Bitcoin\" --datadir="C:\Users\Morpheus\AppData\Roaming\Armory\" --dbdir="C:\Users\Morpheus\AppData\Roaming\Armory\databases"
2017-10-02 18:22:12 (INFO) -- ArmoryUtils.pyc:667 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="C:\\Users\\Morpheus\\AppData\\Roaming\\Bitcoin\\"', '--datadir="C:\\Users\\Morpheus\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\Morpheus\\AppData\\Roaming\\Armory\\databases"']
2017-10-02 18:22:15 (INFO) -- ArmoryQt.py:1813 - Connecting on port 54321
2017-10-02 18:22:15 (INFO) -- ArmoryQt.py:1913 - Setting netmode: 1
2017-10-02 18:22:15 (INFO) -- ArmoryQt.py:1895 - loadBlockchainIfNecessary
2017-10-02 18:22:15 (ERROR) -- ArmoryQt.py:1194 - 19 attempts to load blockchain failed.  Remove mempool.bin.
2017-10-02 18:22:15 (ERROR) -- ArmoryQt.py:1199 - File mempool.bin does not exist. Nothing deleted.
2017-10-02 18:22:15 (INFO) -- ArmoryQt.py:1913 - Setting netmode: 1
2017-10-02 18:22:15 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-10-02 18:22:15 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-10-02 18:22:15 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-10-02 18:22:15 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-10-02 18:22:16 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-10-02 18:22:16 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-10-02 18:22:16 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-10-02 18:22:16 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-10-02 18:22:17 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode