error broadcasting tx: status not ok: 400 Bad Request (-25: Missing inputs)

[placer14]

We've had reports on both BCH and LTC where a transaction was attempted and resulted in a 400 Bad Request with Blockbook reporting the tx error as {"error":"-25: Missing inputs"}.

In one example payload, the structure appeared like this:

{
	"version": 1,
	"locktime": 0,
	"ins": [
		{
			"n": 0,
			"script": {
				"asm": "<encodingremoved>",
				"hex": "<encodingremoved>"
			},
			"sequence": 0,
			"txid": "<hashremoved>",
			"witness": []
		},
		{
			"n": 0,
			"script": {
				"asm": "<encodingremoved>",
				"hex": "<encodingremoved>"
			},
			"sequence": 0,
			"txid": "<hashremoved>",
			"witness": []
		},
		{
			"n": 0,
			"script": {
				"asm": "<encodingremoved>",
				"hex": "<encodingremoved>"
			},
			"sequence": 0,
			"txid": "<hashremoved>",
			"witness": []
		},
		{
			"n": 0,
			"script": {
				"asm": "<encodingremoved>",
				"hex": "<encodingremoved>"
			},
			"sequence": 0,
			"txid": "<hashremoved>",
			"witness": []
		},
		{
			"n": 1,
			"script": {
				"asm": "<encodingremoved>",
				"hex": "<encodingremoved>"
			},
			"sequence": 0,
			"txid": "<hashremoved>",
			"witness": []
		},
		{
			"n": 1,
			"script": {
				"asm": "<encodingremoved>",
				"hex": "<encodingremoved>"
			},
			"sequence": 0,
			"txid": "<hashremoved>",
			"witness": []
		}
	],
	"outs": [
		{
			"script": {
				"addresses": [
					"1addr"
				],
				"asm": "OP_DUP OP_HASH160 <hashremoved> OP_EQUALVERIFY OP_CHECKSIG",
				"hex": "<hashremoved>"
			},
			"value": ...
		},
		{
			"script": {
				"addresses": [
					"1addr"
				],
				"asm": "OP_DUP OP_HASH160 <hashremoved> OP_EQUALVERIFY OP_CHECKSIG",
				"hex": "..."
			},
			"value": 123
		}
	],
	"hash": "...",
	"txid": "..."
}