Skip to content

ledger command should include CTID for expanded transactions (Version: 2.6.1) #5885

@mDuo13

Description

@mDuo13

Summary

The CTID (compact transaction identifier) is a helpful field for identifying validated transactions independent of network, but the ledger method does not include CTIDs in the response when you get an expanded list of transactions in the ledger.

For consistency with transaction formatting elsewhere, it should.

Test Case / How to Reproduce

Example request

Solution

I would expect each member of the transactions array in the response to have a ctid field at the top level, for consistency with the format used in the tx command.

The CTID can be calculated from other information already known in this context, but it would be much easier for API users to supply one pre-calculated.

Metadata

Metadata

Labels

API ChangeFeature RequestUsed to indicate requests to add new featuresTriagedIssue/PR has been triaged for viability, liveliness, etc.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions