Quote from: harlequininja on November 26, 2021, 07:48:16 PM

This is were Armory connects to the WAN I guess.

This isn't a WAN connection. This is ArmoryQt (the GUI) connecting to ArmoryDB (the blockchain service) on 127.0.0.1:50559

Quote

Can you point me somewhere where I can find an explanation how to broadcast an armory-transaction directly with Core?

Getting the raw tx

A. If a transaction fails to broadcast, it should dump the tx in hex in your logs.

B. Or, go through the unsigned tx flow instead of signing and broadcasting from the send dialog (on an online node). You would:

a) Create the transaction as unsigned. This will give you a text blob you can save to a file or copy paste around.
b) Load this blob via the offline transaction dialog (the sign/broadcast option). This stuff is available to both offline and online nodes, just make sure you've set the user mode to expert.
c) From this dialog, you will first sign the transaction. This will update the blob with the signatures.
d) From this same dialog (if you're doing this from an online wallet), or after loading the blob on your online instance, you can either broadcast the transaction, or copy the raw hex tx. Choose the latter.

Broadcasting the raw tx

You can broadcast transactions in hex format from the Core RPC using the sendrawtransaction command. There are 2 ways to do this:

A. If you're using the bitcoin-core-qt (the GUI), this is as simple as going to the console tab, writing sendrawtransaciton then pasting the hex tx in quotes. If you can't see that tab in the GUI, restart it with -disablewallet.

B. You can also do this from any terminal/command line prompt by sending the same command within a JSON packet to Core's RPC. This is a somewhat involved process, so I'll let you search for a guide to walk you through the steps (they're not that hard to find).