Fix: handle NOT_VALIDATED status in ledger.Status()

[atharrva01]

Problem

I noticed that ledger.Status() in the FabricX package doesn’t handle the NOT_VALIDATED state. When a transaction is still waiting to be committed (which can happen during normal block processing or orderer delays), it falls into the default case and gets marked as Invalid , even though it hasn’t failed.

// Before - NOT_VALIDATED falls into default
switch protoblocktx.Status(tx.ValidationCode()) {
case protoblocktx.Status_COMMITTED:
    return driver.Valid, nil
default:
    return driver.Invalid, nil
}

Interestingly, the finality service in the same package already handles this correctly:

case protoblocktx.Status_NOT_VALIDATED:
    return fdriver.Unknown

So right now two parts of the system interpret the same state differently.

---

Impact

• Pending transactions may be reported as Invalid even though they are still in-flight
• The consistency checker could potentially raise warnings like “transaction record is valid for vault but not for the ledger” for transactions that haven’t finalized yet
• Callers of Ledger.Status() might interpret the result as a failure, even though the transaction is simply not validated yet

---

Fix

I added the missing NOT_VALIDATED case so pending transactions return Unknown. It’s a small change but keeps ledger.Status() consistent with the finality service and avoids false failure signals.

[atharrva01]

hi @adecaro I noticed ledger.Status() didn’t handle the NOT_VALIDATED state, which could cause pending transactions to be reported as Invalid. This adds the missing case so they return Unknown, matching the behavior of the finality service.

[adecaro]

Hi @atharrva01, nice catch. I'll review ASAP. Thanks for submitting this.

[adecaro]

LGTM. Thanks 👍