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

[iota-rest-api] Add new endpoint to execute transaction for optimistic indexing purposes #5669

Open
tomxey opened this issue Feb 27, 2025 · 0 comments
Assignees
Labels
infrastructure Issues related to the Infrastructure Team

Comments

@tomxey
Copy link
Contributor

tomxey commented Feb 27, 2025

Created as a continuation of #5151

To ease introduction of optimistic indexing of transactions in indexer, we will require a new endpoint in the node that will execute a transaction and return all data required by the indexer.

The endpoint is meant to be called by the indexer, not the end users. The end users should still use the old endpoint.

Apart from normal tx execution response, the response should contain full transaction information in CheckpointTransaction format:

pub struct CheckpointTransaction {

The current standard execute_transaction_block endpoint (
async fn execute_transaction_block(
) contains all necessary data (ExecuteTransactionResponseV1 and ExecuteTransactionRequestV1) to construct CheckpointTransaction.

The logic from execute_transaction_block can be a good base to create the new endpoint.

In case it would happen to be an issue, the response format could be based on

async fn get_checkpoint_full(
(which is returning CheckpointData, which contains CheckpointTransaction internally)

@tomxey tomxey added the infrastructure Issues related to the Infrastructure Team label Feb 27, 2025
@kodemartin kodemartin changed the title [iota-json-rpc] Add new endpoint to execute transaction for optimistic indexing purposes [iota-rest-api] Add new endpoint to execute transaction for optimistic indexing purposes Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure Issues related to the Infrastructure Team
Projects
None yet
Development

No branches or pull requests

1 participant