Use Multisend to batch transactions for Safes

[gravenp]

Description Safe smart accounts can accept & sign batched transactions. With the implementation of #400 & #401 in the March Safe hackathon, we will assume that all Cadastre users have this setup. All land market transaction windows should batch the required transactions for a single action button UX.

Requirements

• Consolidate transactions required for claiming/bidding on/editing parcels into a single button that triggers a Multisend batch

• Add a link & module for (advanced) users to optionally preview their transaction bundle

  • Include contract addresses, function names, & tx details

• Until ETHx is able to be used to pay gas fees via Gelato's SyncFee, wrap ETH to ETHx incrementally with each batch transaction. Wrap the lesser of:

  • Required ETHx transfer (claim payment/bid collateral/+ buffer deposit) + For Sale Price*.1 (1 year worth of streamed network fees) = minimumEthXForTransfer
  • ETH Balance - .002 (i.e. leave .002 ETH for gas) = ethBalanceSubGasBuffer
  • If this value is equal to or less than the Required ETHx Transfer, then the "Insufficient Funds" error message should be shown and the claim button should be greyed out (i.e. they at least need to be able to pay upfront costs) ethBalanceSubGasBuffer <= minimumEthXForTransfer = Error: Insufficient Funds

• Bundle composition for users with ETHx less than the above threshold

  • Wrap 100% of the ETH to ETHx
  • Post hackathon, we'll consider Safes that are used for more than just the Geo Web and conditional or manual wrapping amount
  • Authorize the appropriate ETHx ERC-20 transfer amount
  • Authorize the appropriate ETHx stream amount
  • Claim the parcel/place the bid/change the price

• Bundle composition for users with enough ETHx for the transaction:

  • Authorize the appropriate ETHx ERC-20 transfer amount
  • Authorize the appropriate ETHx stream amount
  • Claim the parcel/place the bid/change the price

• Utilize Gelato’s SyncFee for users to pay for their batch transaction gas fees with ETHx https://docs.gnosis-safe.io/learn/safe-core-account-abstraction-sdk/relay-kit

  • Note: The Safe, not the EOA/signer, should pay the gas fees associated with the batch from its balance

[gravenp]

Note: For the Safe hackathon, we won't be setting the content fields because it will require a new approach for the management of Ceramic streams. We can leave the Name & Link fields on the UI, but don't bother trying to submit that info with the Claim batch.

[gravenp]

Closed with #413 merged into the Safe branch. Will open a ticket for merging any changes to develop & production when appropriate.