22 docs tagged with "Move VM"

Account Abstraction in IOTA: overview and how-to guides for Move and the IOTA SDKs

Conceptual overview of Account Abstraction in IOTA: components, authentication model, and developer guidance

The five components of Account Abstraction in IOTA and how they relate to each other

How to authenticate an account using public key verification in Move

How to create accounts that allow any member of a group to authenticate using zero-knowledge Merkle tree membership proofs

How to mitigate the risks of using shared objects as inputs to authenticator functions.

Build and deploy your first abstract account step by step, covering the authenticator function, account creation, and sending AA transactions entirely from the CLI.

How sponsor authenticators must cryptographically bind their approval to the sender's identity — the sender's authenticator function and auth digest — to prevent sender-side identity swaps after the sponsor has signed.

How to create accounts that require a weighted threshold of member approvals before a transaction can execute

How to create an account using the builder pattern in Move

How to create a basic authenticator function in Move

How to create and manage time-locked accounts with unlock time restrictions

How to properly protect authenticator input parameters with cryptographic verification to prevent input tampering attacks

Design principles for third-party developers using Account Abstraction in IOTA

How to create accounts that enforce a maximum withdrawal amount per transaction using intent-aware authentication

How to add, remove, and borrow dynamic fields on an account in Move

How to pre-authorize multiple transactions with a single signature using Merkle tree-based authentication

Learn about Programmable Transaction Blocks (PTBs) in IOTA and how they enhance smart contract efficiency.

How to control which Move functions a key can call on an account

How to rotate the authenticator function of an account in Move

How to create a sponsoring account that pays gas only for whitelisted sender authenticator functions and within per-user gas allowances

How to properly implement transaction data cryptographic protection in authenticator functions to prevent transaction tampering attacks.