Skip to content

Conversation

vusirikala
Copy link
Contributor

Support orderless transactions in Indexer.
To support orderless transactions, in aptos-core repo, we've added a new variant in TransactionPayload enum, to additionally store a nonce and multisig address.
Also, in aptos.transaction.v1.rs in aptos-core, we've added ExtraConfig containing nonce and multisig address.

This PR modifies the indexer to support the changes in transaction structure of UserTransaction.

@larry-aptos
Copy link
Contributor

what's the upstream change and is there an AIP to track this?

"timestamp",
"version"
"version",
"replay_protection_nonce"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we have a process to update this. https://app.clickup.com/9011498509/v/dc/8cj13gd-14211/8cj13gd-8791

our oncall might be able to help here though.

pub transaction_version: i64,
pub event_account_address: String,
pub event_creation_number: i64,
// Question: Do we need to add a replay_protection_nonce here?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no b/c it's not needed for this table anyways.

use field_count::FieldCount;
use serde::{Deserialize, Serialize};

// Question: Do we have to add a replay_protection_nonce here?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

up to you. it's useful for users but if you want it for debugging we could add it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants