OK, when I was scouring the RPC help of the list of methods, I did not consider sendrawtransaction because I was looking for RPCs that took a txid (quite literally "txid" as that is how the parameters are labelled in the short description).
But what if I'm using an air-gapped wallet that doesn't provide a raw transaction, but just a txhash? Perhaps the hexstr argument of sendrawtransaction can be amended to take the txhash as an alternative? This is the only way I think this funcionallity an be inserted if another RPC call cannot be created.
I know its already returned as the result, but it's not possible to obtain the raw transaction bytes in all wallets.
You should be able to. Txhash doesn't provide sufficient information for you to broadcast anything. You need the raw transaction, not just the txhash to broadcast the transaction. But what if I'm using an air-gapped wallet that doesn't provide a raw transaction, but just a txhash? Perhaps the hexstr argument of sendrawtransaction can be amended to take the txhash as an alternative? This is the only way I think this funcionallity an be inserted if another RPC call cannot be created.
I know its already returned as the result, but it's not possible to obtain the raw transaction bytes in all wallets.
If you can somehow rebroadcast using the Txid, then chances are your transaction is already propagated.
