The catbuffer schemas repository defines how each transaction type should be serialized. In combination with the catbuffer-generators project, developers can generate builder classes for a given set of programming languages.
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 (
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.
|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.|
Did you find what you were looking for? Give us your feedback.