User Story
<aside>
📜 As a Safe Signer, I would like to sign off on a limit order transaction to be scheduled later, so that I don’t have to deal with transacting on a DEX one transaction at a time.
</aside>
<aside>
📜 As a Safe Signer, I want to limit the scope and conditions for the transaction to be executed later, so that I can continue to limit my trust assumptions and save time
</aside>
<aside>
📜 As a Safe Signer, I would like to not pay gas, manage nonce or deal with intricacies of a swap transaction, so that I can focus on higher level organization goals
</aside>
User Interaction Flow
Design Goals
- Unburden Gnosis Safe users from the complexity of time sensitive operations, gas management, nonce management, and swap configurations- handle all of the following operations for users without sacrificing controls
- Inherit and build on the security of the Gnosis Safe’s
M-of-N
threshold signatures assumption instead of compromising the contract with the module’s own security model.
- The module stays non-custodial - the delegate address (the backend service agent executing the transaction) does not have the ability to execute transactions without the valid signatures.
- Introduce a new model for asynchronous-atomic transactions instead of synchronous-sequential transactions
- Give Gnosis Safe signers the ability to opt-out of any inflight transaction they have committed to
- Orders are 100% private and will only be revealed atomically as the transaction gets settled
Smart Contracts
https://github.com/exponent-cx/async-kit