IOTA Command Line Interface
View all tagsWhen you publish or upgrade a package, its address (also known as the package ID) is tracked in the Move.lock file. This bookkeeping is done automatically so that you can avoid recording or updating hex addresses (for example, in the Move.toml file).
Learn how to build and test Move packages in IOTA with detailed instructions and examples.
Guide to connecting to an IOTA network for development and production.
How to create a Move package in IOTA
A guide to understanding and implementing secure package upgrade policies in IOTA using Move.
Learn how to use the std::debug module in Move for debugging and printing values.
Introduction
Immutable objects on IOTA cannot be mutated, transferred, or deleted once frozen. These objects are ownerless and can be used by anyone on the network.
Install the IOTA framework and required prerequisites on your system, including the IOTA command line interface to interact with the IOTA network.
IOTA provides command line tools to interact with the network, its features, and the Move programming language. Individual command groups are referred to as IOTA Client CLI, IOTA Console CLI, IOTA Keytool CLI, IOTA Move CLI, and IOTA Validator CLI.
The cheat sheet highlights common IOTA CLI commands.
The IOTA Client CLI provides command-level access to interact with the IOTA network.
The IOTA Client PTB CLI enables a user to construct a PTB and execute it from the command line or a file.
The IOTA Console CLI provides command-level access to interact with the IOTA network by wrapping the IOTA Client CLI command.
The IOTA Genesis Ceremony CLI provides commands for building a Genesis blob file.
The IOTA Keytool CLI has commands for managing and generating addresses, working with private keys, or signatures.
The IOTA CLI move command provides commands for working with Move source code directly from a terminal or console.
The IOTA CLI validator command provides command-level access to validator features of the IOTA network.
IOTA adheres to widely accepted wallet specifications in the cryptocurrency industry, including BIP-32 (and its variation, SLIP-0010) and its variation SLIP-0010, BIP-44, and BIP-39, to facilitate key management for users. At present, IOTA supports pure Ed25519, ECDSA Secp256k1, ECDSA Secp256r1, and multisig for signed transactions.
Guide to setting up and using a local IOTA network for development and testing.
IOTA supports multi-signature (multisig) transactions, which require multiple keys for authorization rather than a single, one-key signature. In technical terms, IOTA supports k out of n multisig transactions, where k is the threshold and n is the total weights of all participating parties. The maximum number of parties is 10. To learn more about the single key signatures that IOTA supports, see Signatures.
IOTA supports offline signing, which is signing transactions using a device not connected to an IOTA network, or in a wallet implemented in a different programming language without relying on the IOTA key store. The steps to implement offline signing include:
Learn how to publish your Move package on the IOTA network and interact with it using programmable transaction blocks.
A guide on how to construct, sign, and submit transactions in a Move-based blockchain.