Multi-Signature provides enhanced security by requiring multiple signatures to execute transactions. Create multi-signature accounts, generate transactions, and manage signatures collaboratively.

Multi-Signature — Kabila Tools

What is Multi-Signature?

Multi-Signature (multisig) is a security mechanism that requires more than one private key to authorize a transaction. Instead of a single person having full control, multiple parties must approve an action before it can be executed.

Available Operations

1. Create Multi-Signature Account

Create a new Hedera account with multiple signing keys:

• Key configuration — Add 1 to 10 public keys or Account IDs
• Threshold — Define how many signatures are required to execute transactions (defaults to all)
• Key generator — Generate secure ED25519 key pairs
• Validation — Threshold cannot exceed the total number of keys

Security levels:

• High: threshold ≥ 70% of total signatures
• Medium: threshold ≥ 50% of total signatures
• Low: threshold < 50% of total signatures

2. Create Transaction

Create transactions from multi-signature accounts for others to sign. 5 transaction types available:

Transfer HBAR

Transfer HBAR from the multi-signature account to other accounts.

Transfer Fungible Tokens

Transfer fungible tokens (FTs) from the multi-signature account. Validates that the recipient has the token associated.

Transfer NFTs

Transfer NFTs (maximum 10 per transaction) from the multi-signature account. Select the collection and specific serial numbers.

Associate Token

Associate tokens with the multi-signature account to be able to receive them.

Update Account Keys

Update the key configuration of the multi-signature account:

• Change number of signatures and threshold
• Replace or add public keys
• Requires additional signatures equal to the new number of keys

3. Sign Transaction

Sign transactions created by others using your private key:

• Input — Transaction bytes in base64 format
• Output — Signed transaction in publicKey:transactionBytes format
• Partial signing — Supports adding signatures incrementally

4. Execute Transaction

Execute transactions once the required signature threshold is reached. Validates all signatures before execution.

Workflow

Key Features

• Shared control — Multiple team members share control over token operations
• Enhanced security — Reduces the risk of unauthorized transactions
• Flexible threshold — Define how many signatures are required (from 1 to all)
• Partial signing — Supports adding signatures incrementally
• Multiple transaction types — Supports 5 different transaction types
• Key generator — Generate secure ED25519 key pairs
• Real-time validation — Validates accounts, keys, and configurations

Use Cases

• Team treasuries — Require multiple founders to approve token transfers
• Collection management — Shared control over NFT collection operations (minting, burning, updating)
• Token operations — Multi-party approval for sensitive operations like pausing or freezing tokens
• Organizations — Shared custody for corporate digital assets

Limits and Considerations

• Maximum keys: 10 per account
• Maximum NFTs per transaction: 10
• Transaction expiration: 3 minutes from creation
• Threshold: Must be ≤ total number of keys
• Account update: Requires threshold + number of new public keys

Pricing

Hedera network fees apply additionally.

---

Want to check pricing for all tools? Visit the Pricing page.