The log files you have are old and related to my first issue, which is not present anymore.
This is the issue this topic covers, this is what I respond to. Again, you are confusing people mixing issues together. There are 2 paths to fixing a bug, you either PR code or isolate it for me to fix.
If it is a different issue - and you have a fix already - please explain what it is, otherwise your claims are as good as mine.
https://github.com/goatpig/BitcoinArmory/commit/a2a94e8419968cf8969b161614612c97a85bffe2The new issue has the same symptoms and the same solution as the issue outlined in the thread I referenced
You are conflating symptoms and causes. Minimum mempool requirements such as coin-age in relation to fee floor can change per Core sub version. You are not isolating the issue in this case.
The one way to do so would be to grab the raw tx that fails to broadcast through Armory with Core 0.14.1 and push it directly from the RPC to read the error code verbose (verbose which should be available in armorylog.txt since 0.96, so I'd like to see that).
I'm not isolating the issue to a particular section of the code because I have not the knowledge or the time to do that, as Armory's codebase is quite complicated and messy and frankly my own complicated and messy codebases are more than enough. For the same reason, a particular commit that changes a few line doesn't mean much to me.
All I said (God forbid that someone takes my words as provocation, I'm just trying to move my Bitcoin and to report back to you) is that the issue that was previously decribed is not resolved, that is presents exactly the same way, and that the same workaround still works. I'm literally saying no more than that. I'm also not implying anything else, including e.g. that the underlying cause is the same. I apologize if it came through that way.
The log simply says that the transaction times out, unless I'm missing something:
2017-05-06 14:55 (INFO) -- (PPRINT from ArmoryQt.py:3088)
01000000 0109b9db f08122b8 6bbaf955 2aff9505 e66ff6bf a7013a86 8a7aae89
36cdf58a c4000000 008b4830 45022100 90f9e43a 035a6cf1 dfb5acd2 a1d24aea
0b154a81 c8edaf0d e3d08a09 84900f5e 022025e3 b4be653a 1b438a49 14568ebd
00a2eda8 a745540c 4217f6e4 89a932ff 09410141 045ed39b a1aab680 5d9ab9ed
1a096745 e1a7bb59 667d0fed b47c7c08 7f705143 8921fd3f 55407740 a5e74614
960193d7 27bf41f1 abbf1aec 6952ca3c f9591aef edffffff ff013be5 3e050000
00001976 a914a74b 354efbe1 3422ebd6 a004d897 f274223a 53d388ac d0180700
2017-05-06 14:55 (INFO) -- (PPRINT from ArmoryQt.py:3089)
Transaction:
TxHash: b470d020049677645d5ed4024844de94eaee8ad7b682e3213662ab2c0637c2cf (BE)
Version: 1
nInputs: 1
nOutputs: 1
LockTime: 465104
Inputs:
PyTxIn:
PrevTxHash: c48af5cd3689ae7a8a863a01a7bff66fe60595ff2a55f9ba6bb82281f0dbb909 (BE)
TxOutIndex: 0
Script: (48304502210090f9e43a035a6cf1dfb5acd2a1d24aea0b154a81c8edaf0de3d0)
Sender: 1QJfNJGoP8o3U2NiXUK2gm5JtcDjiP6aUN
Seq: 4294967295
Outputs:
TxOut:
Value: 88007995 (0.88007995)
Script: OP_DUP OP_HASH160 (1GFZwbYTfHdcKDwCw6HZUXUJamnuz8EREK) OP_EQUALVERIFY OP_CHECKSIG
2017-05-06 14:55 (INFO) -- ArmoryQt.py:3094 - Sending Tx, cfc237062cab623621e382b6d78aeeea94de444802d45e5d6477960420d070b4
2017-05-06 14:55 (ERROR) -- Traceback (most recent call last):
File "qtdialogs.pyc", line 1571, in execSendBtc
AttributeError: 'DlgWalletDetails' object has no attribute 'wltAddrModel'
2017-05-06 14:55 (ERROR) -- ArmoryQt.py:3108 - Transaction was not accepted by the Satoshi client
2017-05-06 14:55 (ERROR) -- ArmoryQt.py:3109 - Raw transaction:
2017-05-06 14:55 (ERROR) -- (PPRINT from ArmoryQt.py:3110)
01000000 0109b9db f08122b8 6bbaf955 2aff9505 e66ff6bf a7013a86 8a7aae89
36cdf58a c4000000 008b4830 45022100 90f9e43a 035a6cf1 dfb5acd2 a1d24aea
0b154a81 c8edaf0d e3d08a09 84900f5e 022025e3 b4be653a 1b438a49 14568ebd
00a2eda8 a745540c 4217f6e4 89a932ff 09410141 045ed39b a1aab680 5d9ab9ed
1a096745 e1a7bb59 667d0fed b47c7c08 7f705143 8921fd3f 55407740 a5e74614
960193d7 27bf41f1 abbf1aec 6952ca3c f9591aef edffffff ff013be5 3e050000
00001976 a914a74b 354efbe1 3422ebd6 a004d897 f274223a 53d388ac d0180700
2017-05-06 14:55 (ERROR) -- ArmoryQt.py:3111 - Transaction details
2017-05-06 14:55 (ERROR) -- (PPRINT from ArmoryQt.py:3112)
Transaction:
TxHash: b470d020049677645d5ed4024844de94eaee8ad7b682e3213662ab2c0637c2cf (BE)
Version: 1
nInputs: 1
nOutputs: 1
LockTime: 465104
Inputs:
PyTxIn:
PrevTxHash: c48af5cd3689ae7a8a863a01a7bff66fe60595ff2a55f9ba6bb82281f0dbb909 (BE)
TxOutIndex: 0
Script: (48304502210090f9e43a035a6cf1dfb5acd2a1d24aea0b154a81c8edaf0de3d0)
Sender: 1QJfNJGoP8o3U2NiXUK2gm5JtcDjiP6aUN
Seq: 4294967295
Outputs:
TxOut:
Value: 88007995 (0.88007995)
Script: OP_DUP OP_HASH160 (1GFZwbYTfHdcKDwCw6HZUXUJamnuz8EREK) OP_EQUALVERIFY OP_CHECKSIG
2017-05-06 14:55 (ERROR) -- ArmoryQt.py:3113 - Failure message: tx broadcast timed out (send)
As for
"This is the issue this topic covers, this is what I respond to.", sorry for mixing things up, since you are a moderator here I'm sure you can move this to a separate topic if you think it would work out better, or I can open a new topic myself if you prefer.
