Description
Is your feature request related to a problem? Please describe.
The different between a transaction and a subscription as defined by the current data structures is rather discrete.
Abstracting the concepts back a little, what is really defined is a transaction with meta data that when coupled with defined logic enables the subscriptions intended functionalities.
Describe the solution you'd like
I would like to see a way where the structures are abstracted apart and the meta data is stored and then keyed to the transactions, downside is this breaks the current functionality on any application that already supports the Gnosis multi sig, as the transaction structure is going to be different.
Argument can be made that we care not about what other people have done for the gnosis wallet and push this as the new implementation that we want to use.
Describe alternatives you've considered
Subscriptions become mirrored of Transaction with the addition of meta data and build the entire new functionality of the 948 work into its own contract that inherits 1:1 the gnosis multisignature and overrides method that need adjusting to be compliant.