Overview
Iagon LedgerFlow is a Cardano product that combines a batch-transfer Multisender with a Multisignature wallet for shared treasury management1. It is built within the Iagon protocol, a Cardano-native decentralized storage and compute network2. LedgerFlow targets organizations, DAOs, and teams that need to distribute assets at scale or coordinate withdrawals across multiple signatories on a single multisig wallet.
Key Features
- Batch multisender. Sends multiple native assets to multiple recipients in a single Cardano transaction, reducing total fees compared to individual transfers1.
- Address book and labels. Maintains a reusable list of recipient addresses with labels to streamline recurring payouts such as payroll or community rewards1.
- Basic multisig contract. Enforces an m-of-n signature threshold over predefined wallet addresses for adding and withdrawing ADA or digital assets from the shared vault1.
- Editable contract parameters. Supports adding or removing signatories and updating the quorum threshold through reference inputs, allowing the wallet to adapt as an organization changes1.
- On-chain and off-chain flows. Provides both off-chain signature collection for lower cost and on-chain proposal execution for stronger auditability of withdrawals and parameter updates1.
What to Expect
Creating a LedgerFlow multisig wallet involves setting up user accounts, collecting public key hashes from each signatory, and deploying a proposal, quorum, and vault contract with a minted quorum NFT that anchors state on-chain1. The deployment step uses a minting script tied to a unique policy identifier, and signatories compile the output transaction in a transaction builder before signing and submitting it. Withdrawals begin with a proposal specifying the recipient address and amount, after which other signatories attach signatures either off-chain through a stored message or on-chain through a signing transaction, and execution only releases the proposed amount to the intended recipient. Any user with the collected signatures can broadcast the final withdrawal, which prevents any single party from altering the destination or amount mid-flow.
Parameter updates follow the same proposal structure, so rotating members or changing the quorum is handled through a signed transaction rather than wallet recreation1. This makes LedgerFlow suitable for DAOs and treasuries whose signatory set evolves over time. The product also documents optional wallet integration support and an off-chain transaction history API for teams that want to embed LedgerFlow flows into their own front ends. LedgerFlow is documented as part of the Iagon product suite, with access routed through the main Iagon application2. Users should note that assets sent directly to the contract address without the correct datum may be non-recoverable, and that scheduled or automated transfers require an external trigger since Cardano smart contracts cannot self-execute. LedgerFlow fits alongside other Cardano multisig options in the wallets section of the ecosystem, targeting treasury and distribution use cases rather than personal day-to-day wallets.
