Overview of Actions and Transactions

[martineckardt]

I prepared a few images explaining the concepts of actions, transactions and upgradeability:

Actions

From what I saw in the code and documentation I understand that actions define a set of different actions user can submit using transactions. Each Action has a ActionHandler / execute function that defines the business logic.

Transactions

What really stood out to me is the account abstraction, meaning that the sdk is very flexible how account are created. If compared to a transaction of the SubnetEVM, transactions are very light weight and flexible.

Source: ava-labs/subnet-evm, ava-labs/hypersdk

Upgradeability

Each action is scoped by block timestamps and therefore they can be replaced by newer versions or disabled.

[patrick-ogrady]

Thanks for sharing, @martineckardt!