Spending Limits

[lukasschor]

Dependency

Smart Contract Module still needs to be deployed and audited.

What is this about?

As Safe owner(s) I/we want to set rules for specific beneficiaries to access funds on the Safe so that I/we don’t have to collect all signatures for smaller / recurring payments.

Why do we do this?

Some (potential) users miss the Daily Limit feature implemented in the old Gnosis Multisig. This Allowance feature covers those use cases and adds other usecases such as:

• Give allowance to mobile device
• Give allowance to external people
• Give allowance to employees (without making them owners of the Multisig)

Sub-tickets

• Display allowances in settings
• Set / remove allowances
• Execute allowances as an owner of a Safe (non-owner executions are not part of the first implementation)
• Show allowance transfers in the transaction list

Designs

All Screen designs are on Zeplin.

Startscreen

New Allowance

Transaction List

Remove Allowance

Send Funds

As non-owner

Contract:

https://rinkeby.etherscan.io/address/0xCFbFaC74C26F8647cBDb8c5caf80BB5b32E43134#code

Updates

• Oct 26, Tobi: Add contract address

[fernandomg]

I have a few questions, out of ignorance mostly, related to Modules and this functionality.

1. Allowance feature will be implemented as a Module? That means no new mastercopy version, but a new Allowance contract deployed and somehow enabling it in our safe?
   1.1. If that's the case, then we must add a Settings' section to enable/disabled Gnosis approved modules. Am I right?
2. Somehow, the Safe-app will need to know that a particular Module is enabled, and feature-flag some functionalities across the app. For instance [Spending Limits] Send funds #693
3. Implementation-wise questions:
   3.1. To enable a module, we need to create a new Safe Transaction, calling enableModule, passing the address of the "to be enabled" module. So the address is going to be an env variable?
   3.2. Then the sApp will interact with the module's ABI, and implementing all its features.

[fernandomg]

Probably #934 is the answer to 1.1, right? (@lukasschor)

[lukasschor]

Yes, this will eventually solve this.

1. Yes, it's just a module, no mastercopy change needed
2. This information should be accessible on the blockchain. If the module is not enabled or if no allowances are set, it should just always show the intro / explanation screen.
   3.1. Yes, enabling a module is just part of the multisend transaction of setting the first allowance, sho
   3.2. Exactly