What

A small change to include the ledger sequence number, and the ledger status of the fetched tx.

❯ stellar tx fetch result --hash a5527a54978bc1ebfc9bfa56f7c11149060eea009c39baff8af98fc7f60bc688 --network local --output json-formatted

Transaction Status: SUCCESS
Transaction Ledger: 91
{
  "fee_charged": "41727",
  "result": {
    "tx_success": [
      {
        "op_inner": {
          "invoke_host_function": {
            "success": "df071a249d03fc2f22313f75c734a254bbea03124cea77001704db0670b2fc02"
          }
        }
      }
    ]
  },
  "ext": "v0"
}

This is only included when the output if json-formatted, or on the fee table.

Dependent on: stellar/rs-stellar-rpc-client#48

Why

While I was looking into fetching events, I realized that the ledger information is not included on the tx and thought that this would be helpful information.

We could alternatively embed this in the json with a custom type, but I wanted to make sure that the returned json could be decoded into an easy-to-access type (xdr::TransactionEnvelope, xdr::TransactionResult or xdr::TransactionMeta) so that scripts could use this if needed.

Known limitations

Cargo deny failure should be fixed when the associated rpc client PR is merged, and released.