[1.3.7] transaction spends a nonexisting siacoin output
Now, I've seen this issue float around here before, but mine is a bit different, since I don't actually use a wallet. I have a cold storage wallet that also can create a sign a transaction, using functions straight from Sia source.
The main source of the issue I have seen is that it might be due to having 2 or more wallets with the same seed, but that does not apply to my situation.
Here is the parent transaction that I'm trying to spend (tx id: 8b342aa656b4400f86cf95a6f03cc169c4370febc43b6c936406fbf5032e65a7
):
{
"siacoininputs": [
{
"parentid": "6c3bfa5e883b27b09b98f43da877de94a421ce26edeeb9b2def4863493975480",
"unlockconditions": {
"timelock": 0,
"publickeys": [
{
"algorithm": "ed25519",
"key": "jazrNg9VpZpE5U5DHyzF3q+TCppkDGGmLTuDTWvcshk="
}
],
"signaturesrequired": 1
}
}
],
"siacoinoutputs": [
{
"value": "10000000000000000000000000",
"unlockhash": "95b9155247f30b90ce1c9f99940133e07a27e28f99ff973d82190ecf2537f2e7d4de6c70a6c1"
}
],
"filecontracts": [],
"filecontractrevisions": [],
"storageproofs": [],
"siafundinputs": [],
"siafundoutputs": [],
"minerfees": [
"63600000000000000000000"
],
"arbitrarydata": [],
"transactionsignatures": [
{
"parentid": "6c3bfa5e883b27b09b98f43da877de94a421ce26edeeb9b2def4863493975480",
"publickeyindex": 0,
"timelock": 0,
"coveredfields": {
"wholetransaction": true,
"siacoininputs": [],
"siacoinoutputs": [],
"filecontracts": [],
"filecontractrevisions": [],
"storageproofs": [],
"siafundinputs": [],
"siafundoutputs": [],
"minerfees": [],
"arbitrarydata": [],
"transactionsignatures": []
},
"signature": "BnqIogJXN5Kn+ggo9idDofsttkZciD2EAB9aKN/H9QXDd3XRADnENiGcE0PYt0scY8ONQcUspYgq2Wiv7thqDQ=="
}
]
}
And here is the transaction that I generated and attempting to broadcast:
{
"siacoininputs": [
{
"parentid": "8b342aa656b4400f86cf95a6f03cc169c4370febc43b6c936406fbf5032e65a7",
"unlockconditions": {
"timelock": 0,
"publickeys": [
{
"algorithm": "ed25519",
"key": "45/JD9y1POhN51heUkQKS9Bq3NbunbUO5eiBpXL2d5Y="
}
],
"signaturesrequired": 1
}
}
],
"siacoinoutputs": [
{
"value": "9936400000000000000000000",
"unlockhash": "7b3a2893a0c8ef19ff25f8aaa2a1193fde8d307e5dad3bdde258acd0121a6ef903cad88bf621"
}
],
"filecontracts": null,
"filecontractrevisions": null,
"storageproofs": null,
"siafundinputs": null,
"siafundoutputs": null,
"minerfees": [
"63600000000000000000000"
],
"arbitrarydata": null,
"transactionsignatures": [
{
"parentid": "8b342aa656b4400f86cf95a6f03cc169c4370febc43b6c936406fbf5032e65a7",
"publickeyindex": 0,
"timelock": 0,
"coveredfields": {
"wholetransaction": true,
"siacoininputs": null,
"siacoinoutputs": null,
"filecontracts": null,
"filecontractrevisions": null,
"storageproofs": null,
"siafundinputs": null,
"siafundoutputs": null,
"minerfees": null,
"arbitrarydata": null,
"transactionsignatures": null
},
"signature": "MRF431hiR3B11L+SAWIXXBenGsEAscU1XzGCxqpdZFYp1ESVTjzCQE8NIiD9qvfbjM9jVomGBy58Jknkt8IRAA=="
}
]
}
Also I do check the validity using the StandaloneValid
function, so the signatures are most likely ok.
So I'm not sure what is causing this.