Instance
Starknet.js Architecture
Create an account
Since there are no Externally Owned Accounts (EOA) in Starknet, all Accounts in Starknet are contracts.
Estimate fees
By default, all non-free Starknet commands (declare, deploy, invoke) work without any cost limits.
Signature
You can use Starknet.js to sign a message outside of the network, using the standard methods of hash and sign of Starknet. In this way, in some cases, you can avoid paying fees to store data in-chain; you transfer the signed message off-chain, and the recipient can verify (without fee) on-chain the validity of the message.
Post-quantum signature (Falcon-512)
Starknet.js can sign the transactions of a Falcon-512 account. Falcon is a signature scheme designed to resist quantum computers. This page explains why it matters, how to use it, and its limits.
Execute calls using Paymaster
Overview
WalletAccount
Use wallets to sign transactions in your DAPP.
Outside Execution (SNIP-9)
Outside Execution, also known as meta-transactions, allows a protocol to submit transactions on behalf of a user account, as long as they have the relevant signatures. This feature is implemented according to SNIP-9.
Proofs (SNIP-36)
SNIP-36 lets you run a Cairo transaction off-chain, generate a STARK proof of its execution, and submit only the verified result on-chain.