Expand description
Library for deploying and using Starknet account contracts.
Re-exports§
pub use single_owner::ExecutionEncoding;
pub use single_owner::SingleOwnerAccount;
Modules§
- single_
owner - Module containing types for using an account contract with only one signer.
Structs§
- Account
Deployment V3 - Abstraction over
DEPLOY_ACCOUNT
transactions for account contract deployment. This struct uses v3DEPLOY_ACCOUNT
transactions under the hood, and hence pays transaction fees in STRK. - Argent
Account Factory AccountFactory
implementation for deployingArgent X
account contracts (v0.4.0).- Declaration
V3 - Abstraction over
DECLARE
transactions from accounts for invoking contracts. This struct uses v3DECLARE
transactions under the hood, and hence pays transaction fees in STRK. - Execution
V3 - Abstraction over
INVOKE
transactions from accounts for invoking contracts. This struct uses v3INVOKE
transactions under the hood, and hence pays transaction fees in STRK. - NotPrepared
Error - Error when calling
prepared()
on a type when not all fields are populated. - Open
Zeppelin Account Factory AccountFactory
implementation for deployingOpenZeppelin
account contracts.- Prepared
Account Deployment V3 RawAccountDeploymentV3
but with a factory associated.- Prepared
Declaration V3 RawDeclarationV3
but with an account associated.- Prepared
Execution V3 RawExecutionV3
but with an account associated.- RawAccount
Deployment V3 AccountDeploymentV3
but withnonce
and other transaction fee options already determined.- RawDeclaration
V3 DeclarationV3
but withnonce
and other transaction fee options already determined.- RawExecution
V3 ExecutionV3
but withnonce
and other transaction fee options already determined.
Enums§
- Account
Error - Errors using Starknet accounts.
- Account
Factory Error - Errors using Starknet account factories.
Traits§
- Account
- The standard Starknet account contract interface. It makes no assumption about the underlying
signer or provider. Account implementations that come with an active connection to the network
should also implement
ConnectedAccount
for useful functionalities like estimating fees and sending transactions. - Account
Factory - Abstraction over different ways of deploying account contracts using the
DEPLOY_ACCOUNT
transaction type. - Connected
Account - An
Account
implementation that also comes with aProvider
. Functionalities that require a connection to the sequencer or node are offloaded to this trait to keep the baseAccount
clean and flexible. - Execution
Encoder - An abstraction over different ways to encode
Vec<Call>
intoVec<Felt>
.