Skip to content

[AA] Handle MoveAuthenticator inputs the same as a the TX inputs #8908

@miker83z

Description

@miker83z
  • Pre-consensus: input objects are read from the MoveAuthenticator in the same way any other input object is read from a TX/PTB. If validation fails, do NOT bump the sequence number, just drop everything. (This is in line with current implementation).
  • Post-consensus: input objects are read from the MoveAuthenticator in the same way any other input object is read from a TX/PTB. If validation fails, bump the sequence number of all input objects (coming from MoveAuthenticator and TX), deduct the validation gas computation from the TX gas object and return a TX execution error “Validation failed post-consensus“.
  • Additionally, check any time tx.shared_input_objects() is invoked from the TransactionData and adapt this call to support MoveAuthenticator inputs when needed.

Metadata

Metadata

Assignees

Labels

vm-languageIssues related to the VM & Language Team

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions