Signed transaction not broadcast to the network

[btcArmory user]

I have a file that I intended to send to the network. My bitcoin core was not synced at the time when I attempted it. The file format is not in a standard HEX format. How can I broadcast it to the network using the Armory SENT file?

[Timelord2067]

You can either post your RAW transaction in this thread or yours ^{(preferably using the code BBCode tag)}, or, you can head over to [Guide] Broadcast Your RAW Transaction (Push TX) BTC & Alts coins and follow the links to post the RAW transaction yourself.

I don't mind rebroadcasting it for a couple of days in either event.

[btcArmory user]

I don't know how to identify a RAW transaction. Is it in HEX, or can it include other characters?

The characters in the file are not all HEX numbers. I can't say that I have a sent transaction in RAW HEX format. Can somebody tell me what it is? the characters include upper and lower case letters from throughout the alphabet.


https://bitcointalk.org/index.php?topic=245910.msg2607452#msg2607452
There are posts from 2013 and 2014. Is there a more current update?

[nc50lc]

If your Armory is now online, all you have to do is to click "Offline Transactions", "Sign and/or Broadcast Transaction", "Load File..." (load the signed transaction file), then "Broadcast", review the transaction's details displayed and lastly "Send".

[btcArmory user]

It should be possible to broadcast the transaction to the network from within armory. How is this done?

I'm still syncing headers. It's been quite a process. The indications are that there were issues with the path after the upgrades to bitcoin core 0.20.1 and armory 0.96.5. that shouldn't matter, though.

[nc50lc]

It should be possible to broadcast the transaction to the network from within armory. How is this done?
-snip-

My previous reply is the workflow in Armory (GUI) if you want to broadcast a signed transaction,
that's if the "file" that you've mentioned in the OP is an offline signed transaction, usually named as "armory_xxxxxxxx_.signed.tx".

If it's a txt file with RAW TX in HEX, you can send it through any push/broadcast service or through Bitcoin core.

[btcArmory user]

I apologize for my confusion. This is the format that the file name takes:

armory_nnnnnnnn_.SENT.tx

Due to the fact that the contents include a lot of additional chars besides HEX numbers, I don't know what I have. I don't know for sure that it's raw HEX.

[nc50lc]

armory_nnnnnnnn_.SENT.tx

Okay, so that transaction was previously attempted to send to the network due to the 'SENT' in the name.
Anyways, you can still load it the same way as loading a signed transaction as long as the contents are correct.

it should look like this (sample from RegTest, do not send):

Code:

=====TXSIGCOLLECT-A18o4Vub======================================
AQAAAPq/tdoAAAAAAf1KAQEAAAD6v7XaUuSqnL4H/60mkZwkX0bK+lzGXN4/WIfy
lS5JEAycAFkAAAAAiQIAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAD/////BQLuAAEB/////wIA+QKVAAAAABl2qRSaeagGpmxRpBHwRq3jAcH0TDdX
LYisAAAAAAAAAAAmaiSqIant4vYcP3HR3v0/qZnfo2lTdVxpBol5mWK0i+vYNpdO
jPkAAAAAAAAA/f///wFBBG5ESjXsiMapztTiRSZLK29j/nf2VZIOg5ZQteyu5ilF
8ngMFMsUNw63Ai9/6azxhswfWhdaE85QBWU2QMPHZ0tIMEUCIQDVB/guWpaec11W
KIvB6OLJm30RVkMA9TgBPhdsN4UqMwIgATVQcYk8hpxTh/Ux5SP1RjRqEmJfjBm8
tSbytiY+u2YBAAI0AQAAAPq/tdoZdqkUBWpodCNcs3fR5VYrwA4l1f7hwoKIrNAG
ApUAAAAAAAAETk9ORQAAADQBAAAA+r+12hl2qRTXni1+BSytzhAiNMwNP1X4Yrgl
AYisECcAAAAAAAAAAAROT05FAAAAPQkAACAGTGVnYWN5MIoBAAAAPQkAABAAAAAA
ATQAAf3///8GJFLkqpy+B/+tJpGcJF9GyvpcxlzeP1iH8pUuSRAMnABZAAAAAAD5
ApUAAAAAAiLQBgKVAAAAABl2qRQFamh0I1yzd9HlVivADiXV/uHCgoisIhAnAAAA
AAAAGXapFNeeLX4FLK3OECI0zA0/VfhiuCUBiKw=
================================================================

If you don't want to wait for Armory, you can send it now to the network using any "push/broadcast service" by copying the RAW Transaction in HEX.
You can get it by following my previous reply until "load file", but instead of broadcast, click the text in blue: "Click here for more information about this transaction", then "Copy Raw Tx (HEX)".
That should be compatible with broadcast services like https://blockstream.info/tx/push.

Lastly, Armory should be in "Advanced User" mode or higher for the buttons to appear.

[btcArmory user]

I don't have Armory online. There is probably a pathing issue, the way it looks. The new versions of bitcoin core and armory didn't come up together and work normally after the upgrade. I have been running the same installation since early 2014, upgrading when needed.