Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Object transaction history RPC #5039

Open
mvadari opened this issue Jun 5, 2024 · 0 comments
Open

Feature request: Object transaction history RPC #5039

mvadari opened this issue Jun 5, 2024 · 0 comments
Labels
API Change Feature Request Used to indicate requests to add new features Food for Thought Ideas, moonshots, etc. Stuff to think about broadly. Not necessarily directly actionable.

Comments

@mvadari
Copy link
Collaborator

mvadari commented Jun 5, 2024

Summary

It would be really nice to have an RPC that provides you a list of chronological transactions that have affected a certain object.

Motivation

Object history can be important; for example, to get a list of all offers that filled another offer, track edits to a DID, or get the transaction that created a certain object.

Solution

This RPC, tentatively named object_tx, could just iterate through the PreviousTxnIDs of a transaction in reverse chronological order and use PreviousTxnLgrSeq to determine how far back to go to get the previous PreviousTxnID of the transaction.

Paths Not Taken

You can theoretically do this right now with tx and ledger_entry, using the ledger_index parameter, but it would be nicer if there were a method to do this automatically.

@mvadari mvadari added Feature Request Used to indicate requests to add new features API Change Food for Thought Ideas, moonshots, etc. Stuff to think about broadly. Not necessarily directly actionable. labels Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Change Feature Request Used to indicate requests to add new features Food for Thought Ideas, moonshots, etc. Stuff to think about broadly. Not necessarily directly actionable.
Projects
None yet
Development

No branches or pull requests

1 participant