0.96.2 Bump Fee not working | Bitcointalksearch.org

Brangdon

sr. member

Activity: 365

Merit: 251

Quote from: calebcjh on December 17, 2017, 09:17:32 PM

My transaction has been visible in blockchain.info for a week though. So I think our problems are different. I just need instructions on how to broadcast manually.

I now have the same problem, but with a transaction that has been broadcast. Bump Fee does nothing, and writes nothing to the logfile. I tried deleting geometry entries in the settings file, but it made no difference.

I have tried using Send Coins > RBF Control. It sets source to the right transaction. I have set a new receive address in my wallet, and set Amount to Max. However, I am getting Size: N/A, Fee: N/A, and Preview Transaction says it has an Invalid spend value. Using other amounts makes no difference.

I'm really not sure what I am supposed to do here. Is there any documentation on this I can read? Armory doesn't seem to have a help file.

calebcjh

newbie

Activity: 16

Merit: 0

Quote from: goatpig on September 18, 2017, 10:35:29 AM

Will look into it. For now, you can grab the output through the RBF coin control dialog and bump yourself.

How do I do what you suggested?

goatpig

legendary

Activity: 3794

Merit: 1375

Armory Developer

You can't, fees are covered by the signature. You have to reconstruct tx with a higher fee and sign that.

calebcjh

newbie

Activity: 16

Merit: 0

Yes, but how do I modify the fees in the raw Hex?

gangtraet

full member

Activity: 159

Merit: 100

To broadcast a transaction manually, load it into the window where you sign or broadcast it (I only sign offline, but I assume it looks the same way if you do it all on one line). There, you can click on the button "copy as hex". You can paste the transaction into this web page to broadcast:

https://pool.viabtc.com/tools/BTC/broadcast/

calebcjh

newbie

Activity: 16

Merit: 0

My transaction has been visible in blockchain.info for a week though. So I think our problems are different. I just need instructions on how to broadcast manually.

Brangdon

sr. member

Activity: 365

Merit: 251

I have a similar issue. When I right-click and select Bump Fee, nothing seems to happen. No dialog appears, and nothing extra is written in File > Export Log File....

The transaction has 1 input and 1 SegWit output. It looks like it never got propagated to the network - there was a warning about P2P/RPC when I created it, and Blockchain Info says "Transaction not found" more than half an hour later. I'm using Armory 0.96.3.99, and Core 0.14.1. So it may be that this behaviour is as designed; if so, the user experience is not great.

Later: I used Help > Clear All Unconfirmed to get rid of it. Resending with a higher fee had the same problem. I'm going to try updating core to 0.15.1. If my node isn't well-connected enough, is there anything I can do to improve that?

calebcjh

newbie

Activity: 16

Merit: 0

It is still not working (using armory_0.96.3.99-gcc4.7-noasm_amd64.deb). Also, what is the RBF coin control dialog? No dialog shows up when bump fee is selected.

I am considering clearing unconfirmed and making a few tx, any concerns there?

goatpig

legendary

Activity: 3794

Merit: 1375

Armory Developer

Will look into it. For now, you can grab the output through the RBF coin control dialog and bump yourself.

tandyuk

newbie

Activity: 28

Merit: 0

With 0.96.2, I sent a transaction with a low fee.
It says 'Right click to bump fee', but when I do so, nothing happens.

This is the log of the original tx, and my attempt to bump the fee:

Code:

2017-09-18 13:38:04 (INFO) -- TxFrames.pyc:727 - Change address behavior: NewAddr
2017-09-18 13:38:20 (INFO) -- (PPRINT from ArmoryQt.py:3118)

  01000000 013c0da7 aae5ca8c e6190a75 7f38cf83 8b96a8cf 589255bb d1978cb9 
  f48922ae 9d010000 008b4830 45022100 f7bbe930 12b3bd1f 206e418c a672bad0 

  00001976 a914d9d0 32d542ed de06a5d1 59a6da53 c6cc98c9 9cb788ac c0568d01 
  00000000 1976a914 0456126c 17301d0e 8383054f a723c6fe ec68bf39 88ac006a 
  0700 
2017-09-18 13:38:20 (INFO) -- (PPRINT from ArmoryQt.py:3119)
Transaction:
   TxHash:    3c4faaffb3640e3a9566ca310b6bc6a1c174e38cc7812573d757e97037d3c29d (BE)
   Version:   1
   nInputs:   1
   nOutputs:  2
   LockTime:  485888
   Inputs: 
      PyTxIn:
         PrevTxHash: 9dae2289f4b98c97d1bb559258cfa8968b83cf387f750a19e68ccae5aaa70d3c (BE)
         TxOutIndex: 1
         Script:     (483045022100f7bbe93012b3bd1f206e418ca672bad07092cd405435e5827d34)
         Sender:     154Enja33FvFaRT6QtqgXiWd7D2K6KNddy
         Seq:        4294967293
   Outputs: 
      TxOut:
         Value:   300000000 (3.0)
         Script:  OP_DUP OP_HASH160 (1Lrh3WzuXJhFLKdahccsFtv5j7Fq62qZZa) OP_EQUALVERIFY OP_CHECKSIG
      TxOut:
         Value:   26040000 (0.2604)
         Script:  OP_DUP OP_HASH160 (1Pvp9paFSV7y3fhSk4AFyLHu8XeqJd3vS) OP_EQUALVERIFY OP_CHECKSIG

2017-09-18 13:38:20 (INFO) -- ArmoryQt.py:3124 - Sending Tx, 9dc2d33770e957d7732581c78ce374c1a1c66b0b31ca66953a0e64b3ffaa4f3c
2017-09-18 13:38:20 (INFO) -- ArmoryQt.py:5343 - Bitcoins Sent!
Amount:  3.00036 BTC
From:    Wallet "Michael 2017" (2WCFZkJXR)
To:      1Lrh3WzuXJhFLKdahccsFtv5j7Fq62qZZa
2017-09-18 13:38:27 (INFO) -- ArmoryQt.py:4944 - New Block! : 485889
2017-09-18 13:38:27 (INFO) -- ArmoryQt.py:4952 - Current block number: 485889
2017-09-18 13:46:52 (ERROR) -- Traceback (most recent call last):
  File "ArmoryQt.py", line 3409, in showContextMenuLedger
  File "ArmoryQt.py", line 5913, in bumpFee
  File "armoryengine\PyBtcWallet.pyc", line 1818, in getCommentForAddress
  File "CppBlockUtils.pyc", line 4083, in getScriptHashVectorForIndex
RuntimeError: invalid asset index

Topic: 0.96.2 Bump Fee not working (Read 440 times)