Skip to content
Aptos Improvement Proposals (AIPs)

Transaction Argument Support for Structs

AIP-25 - Transaction Argument Support for Structs

Section titled “AIP-25 - Transaction Argument Support for Structs”

Summary

Section titled “Summary”

We enable some select set of structs as valid parameters to entry and view functions.

Motivation

Section titled “Motivation”

So far only primitive values can be passed into entry functions. Mainly because allowing generic structs as input would invalidate important invariants, like creating Coins out of nothing.

Specification

Section titled “Specification”
  • Entry functions can take a String as input parameter. This was already a special case and continues to be supported. The string is given as a vector which has to be valid utf8 otherwise the transaction validation will fail.
  • Entry functions can take FixedPoint32, FixedPoint64 as input parameters. The value passed in is u64 or u128 respectively and represents the raw value of the fixed point value.
  • Entry functions can take an Option iff T is a valid type for an input parameter. The format is an empty vector for None and a singleton vector with element x for Some(x), where x is of type T. Vector of more than 1 element will be rejected on input validation.
  • Entry functions can take Object as input parameter. The format will be just the address of the object. The resource T must exist at said address otherwise input validation will fail.

Reference Implementation

Section titled “Reference Implementation”

Timeline

Section titled “Timeline”

Devnet: Already available for testing

Testnet: ~4/24

Mainnet: May 1st