Msig configuration for Cow TWAP feature

[petrovska-petro]

No description provided.

[petrovska-petro]

fallback handler

it can be changed by design to support features not natively supported by safe, such as erc1271 signatures, which its the signature type leverage in the composable cow orders. Without its support the safe is limited to read/automate the twap intents.

erc1271 is read only type of verification, so no concerns in regards to funds getting away in an expected manner. only the settlement sc has ability/permission for the swap

requires calling setFallbackHandler to upgrade to the extensible fallback handler instead of default

twap sc requires implementing isValidSignature(bytes32,bytes), where bytes32 is the EIP-712 digest of the GPv2Order.Data. This already is handled by their ui while creating the twap orders

extensible fallback handler in a nutshell

allows a safe to validate a EIP-1271 signature and allows delegating an EIP-712 domain to a custom contract

ComposableCoW therefore will process ALL EIP-1271 signatures for the GPv2Settlement.domainSeparator() EIP-712 domain.

how orders are indexed?

two events are being tracked from the watchtower:

1. ConditionalOrderCreated
2. MerkleRootSet

technical resources to dive deeper

• https://hackmd.io/@mfw78/ByFP7Iazn
• https://hackmd.io/@mfw78/HyuvoGt9h
• https://blog.cow.fi/all-you-need-to-know-about-cow-swaps-new-safe-fallback-handler-8ef0439925d1
• https://help.safe.global/en/articles/40838-what-is-a-fallback-handler-and-how-does-it-relate-to-safe