StarkNet account interface

A StarkNet account contract must include the following two functions:

  • __validate__

  • __execute__

These serve distinct purposes to ensure that only the account owner can initiate transactions and that fees can be charged for the resources you use.

StarkNet’s account type is inspired by Ethereum’s EIP-4337, where instead of EOAs, you now use smart contract accounts with arbitrary verification logic.

Through the use of smart contracts, you are provided with complete flexibility within your account implementation.

While not mandatory at the protocol level, a richer standard interface for accounts was developed by the community. This standard was developed by OpenZeppelin, in a close collaboration with wallet teams and other Core StarkNet developers. You can see the IAccount interface here.

Replay protection

In StarkNet, similar to Ethereum, every contract has a nonce. This nonce is sequential; when a transaction is sent from an account, its nonce must match the account’s nonce and it’s incremented after the transaction is executed (whether or not it was reverted).

Note that, similar to Ethereum, only the nonce of account contracts (that is, those adhering to the above structure) can be non-zero.

A nonce serves two important roles:

  • It guarantees transaction hash uniqueness (this is important for good UX)

  • It provides replay protection to the account (since the signature refers to a particular nonce, the transaction can’t be replayed by a malicious party)

As seen above, StarkNet currently determines the nonce structure (sequential) at the protocol level. In the future, StarkNet will consider a more flexible design, extending account abstraction to nonce management (previously referred to as "nonce abstraction").