Strict proposal enforcements about zodiac-module-reality

[rmeissner]

You can find an example how to build multisend calls in the safe contract tests: https://github.com/gnosis/safe-contracts/blob/bace2dadf7e0675cec5c5c5d29e3fcb0adb6d31f/test/utils/multisend.ts#L18

We will improve the documentation around that and are working on a sdk that should make this easier.

[rmeissner]

To enforce atomic execution you would use a multisend that contains your atomic transactions as a single transaction. The only use case where you would want to use multiple transactions is to spread them over multiple blocks. (We should probably add this to the readme).

As your proposal contains a hash of the hashes of all tx that should be executed and the hash of a tx contains the operation (call or delegatecall) there is a strict enforcement on what operation is valid to be used.

[CalabashSquash]

To confirm my understanding, would the appropriate method for this use case be to make a proposal that executes Multisend.multiSend?