Aggregate Transaction

Aggregate transactions merge multiple transactions into one, allowing trustless swaps, and other advanced logic. Catapult does this by generating a one-time disposable smart contract.


Example of an AggregateTransaction between two participants

When all involved accounts have cosigned the AggregateTransaction, all the inner transactions are executed at the same time.

Catapult’s public network supports aggregate transaction containing up to 1,000 inner transactions involving up to 25 different cosignatories. Other aggregate transactions are not allowed as inner transactions.

Aggregate complete

An AggregateTransaction is complete when all the required participants have signed it.

The cosigners can sign the transaction without using the blockchain. Once it has all the required signatures, one of them can announce it to the network. If the inner transaction setup is valid, and there is no validation error, the transactions will get executed at the same time.

Aggregate complete transactions enable adding more transactions per block by gathering multiple inner transactions.

Aggregate bonded

An AggregateTransaction is bonded when it requires signatures from other participants.


Before announcing an AggregateBondedTransaction, an account must announce and get confirmed a HashLockTransaction locking 10 symbol.xym.

Once an aggregate bonded is announced, it reaches partial state—where it can live up to 2 days—and notifies its status through WebSockets or HTTP API calls.

Every time a cosignatory signs the transaction and announces an aggregate bonded cosignature, the network checks if all the required cosigners have signed. When all signatures are acquired, the transaction changes to unconfirmed state until the network includes it in a block.


AggregateBondedTransaction cycle


Sending multiple transactions together

Dan announces an AggregateTransaction that merges two transfer transactions.

As Dan is the only required signatory, the transaction is considered complete after he signed. After announcing it to the network, Alice and Bob will receive the mosaics at the same time.


Sending payouts with aggregate complete transactions

Multi-asset escrowed transactions

In this example, Alice is buying tickets with currency.euro mosaic. When the ticket distributor cosigns the AggregateTransaction, the swap will happen atomically.


Multi-Asset Escrowed Transactions

Paying for others fees

Alice sends 10 currency.euro to Bob using an app to make payments. But Alice doesn’t own symbol.xym to pay the transaction fee.

By creating an AggregateBondedTransaction, Alice can convert currency.euro to symbol.xym to pay the fee. Now, Alice and Bob can use Catapult’s public blockchain without ever having to buy or hold symbol.xym units.

Since the app creator can put their own branding on the open source payment app, Alice and Bob may not even know they are using blockchain technology.


Paying for others fees


Transaction schemas


Announce an AggregateTransaction to combine multiple transactions together.

Version: 0x01

EntityType: 0x4141 (complete), 0x4241 (bonded)



Property Type Description
transactionsHash Hash256 Aggregate hash of the aggregate transaction.
payloadSize uint32 Transaction payload size in bytes. In other words, the total number of bytes occupied by all inner transactions.
aggregateTransactionHeader_Reserved1 uint32 Reserved padding to align end of AggregateTransactionHeader on 8-byte boundary.
transactions array(Transaction, size=payloadSize) Array of inner transactions. Other aggregate transactions are not allowed as inner transactions.
cosignatures array(Cosignature, __FILL__) Array of transaction cosignatures. Fills the remaining body space after transactions.


Cosignature transactions are used to sign announced AggregateBondedTransactions with missing cosignatures.


Property Type Description
parentHash Hash256 AggregateBondedTransaction hash to cosign.


Property Type Description
signerPublicKey Key Cosigner public key.
signature Signature Transaction signature.


Alias: LockFundsTransaction

Lock funds for a certain amount of blocks with a HashLockTransaction before sending an AggregateBondedTransaction. This transaction prevents spamming the partial cache with transactions that never will complete. The lock duration is allowed to lie up to 2 days, being this value configurable per network.

After enough funds are locked (10 symbol.xym by default), the AggregateTransaction can be announced and added into the partial transactions cache.


It’s not necessary to sign the aggregate and its HashLockTransaction with the same account. For example, if Bob wants to announce an aggregate and does not have enough funds to announce a HashLockTransaction, he can ask Alice to send the hash lock funds transaction for him by sharing the signed AggregateTransaction hash.

Upon completion of the aggregate, the locked funds become available in the account that signed the initial HashLockTransaction. If the AggregateBondedTransaction duration is reached without being signed by all cosignatories, the locked amount becomes a reward collected by the block harvester at the height where the lock expires.

Version: 0x01

EntityType: 0x4148


Property Type Description
mosaic UnresolvedMosaic Locked mosaic.
duration BlockDuration Number of blocks for which a lock should be valid.
hash Hash256 AggregateBondedTransaction hash that has to be confirmed before unlocking the mosaics.

Continue: Account Restrictions.