You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environment:
My system is ubuntu 16.04 64, and my lavad version is v0.3.1.
details:
when my deadline is over, the node mined a new block, then the error came up. the tx 1ac00961624fe7b785cd5c2e78a30e49ccc9a85d553e11382a1ce99f70b86a7c is a firestone release tx. and here is the code about this error:
bool Consensus::CheckTxInputs(const CTransaction& tx, CValidationState& state, const CCoinsViewCache& inputs, int nSpendHeight, CAmount& txfee)
{
// are the actual inputs available?
if (!inputs.HaveInputs(tx)) {
return state.DoS(100, false, REJECT_INVALID, "bad-txns-inputs-missingorspent", false,
strprintf("%s: inputs missing/spent", __func__));
}
......
}
That means the inputs had no this related tx, but why is that?
I found the tx's prevtx hash is 029bad8e44553c1c68c5187cd4df8fb23388bd16ce467976c101de12bbff3c38, the second output of which is used here by the error tx 1ac00961624fe7b785cd5c2e78a30e49ccc9a85d553e11382a1ce99f70b86a7c.
However, at that moment, this prev tx is seems not in the inputs cache.
Anyone can help?
Hi, there is an error when my lavad created a new block after the deadline was up:
Environment:
My system is ubuntu 16.04 64, and my lavad version is v0.3.1.
details:
when my deadline is over, the node mined a new block, then the error came up. the tx
1ac00961624fe7b785cd5c2e78a30e49ccc9a85d553e11382a1ce99f70b86a7c
is a firestone release tx. and here is the code about this error:That means the inputs had no this related tx, but why is that?
I found the tx's prevtx hash is
029bad8e44553c1c68c5187cd4df8fb23388bd16ce467976c101de12bbff3c38
, the second output of which is used here by the error tx1ac00961624fe7b785cd5c2e78a30e49ccc9a85d553e11382a1ce99f70b86a7c
.However, at that moment, this prev tx is seems not in the inputs cache.
Anyone can help?
Log file
error of tx bad.log
The text was updated successfully, but these errors were encountered: