Transaction Authentication
This section introduces transaction authentication on Sui, covering keys, addresses, signatures, key derivation (BIP-32, BIP-44, BIP-39), and signature requirements, and links to the subtopics that detail each one.
Sui supports multiple transaction authentication methods, from standard cryptographic key pairs (Ed25519, ECDSA Secp256k1/r1) to multisig wallets, zkLogin for OAuth-based authentication, and passkeys for biometric signing.
Signing and Sending Transactions
Understanding cryptographic keys, addresses, and signatures on Sui. Sui supports multiple cryptography algorithms and primitives with rapid switching between them.
Multisig Authentication
Learn how Sui multisig authentication works, including k-of-n thresholds, per-key weights, mixing Ed25519 and ECDSA key schemes, and how to create and submit a multisig transaction using the Sui CLI.
Intent Signing
Intent signing provides a compact domain separator to data signed by both user and authority signatures. Data that each signature commits to is called an intent message, which all signatures on Sui must include.
Offline Signing
Offline signing can be used to sign a Sui transaction when a device is not connected to a Sui network, or if the signing wallet uses a different programming language than that of the transaction being signed.
Address Aliases
Address aliases can be used to configure the set of keys that are allowed to sign transactions for a particular address on the Sui network.