You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At first, it looks like every new version of the Safe contracts includes a new version for each contract (GnosisSafe, MultiSend, DefaultCallbackHandler, etc.) .
GnosisSafe v1.1.1 uses MultiSend v1.1.1
GnosisSafe v1.3.0 uses MultiSend v1.3.0
However, this is not always true. A specific version of the GnosisSafe contract might use a contract with a lower version number.
GnosisSafe v1.2.0 uses MultiSend v1.1.1 (MultiSend v1.2.0 does not exist)
It would be useful to get the specific contract used by a given GnosisSafe version by adding a new filter with the GnosisSafe version to the DeploymentFilter.
The text was updated successfully, but these errors were encountered:
germartinez
changed the title
Improve querying (get all contracts given a specific GnosisSafe version)
Improve querying (get all contracts used by a given GnosisSafe contract version)
May 7, 2021
germartinez
changed the title
Improve querying (get all contracts used by a given GnosisSafe contract version)
Improve querying (get a contract filtering by the GnosisSafe version that uses it)
May 7, 2021
At first, it looks like every new version of the Safe contracts includes a new version for each contract (GnosisSafe, MultiSend, DefaultCallbackHandler, etc.) .
v1.1.1
uses MultiSendv1.1.1
v1.3.0
uses MultiSendv1.3.0
However, this is not always true. A specific version of the GnosisSafe contract might use a contract with a lower version number.
v1.2.0
uses MultiSendv1.1.1
(MultiSendv1.2.0
does not exist)It would be useful to get the specific contract used by a given GnosisSafe version by adding a new filter with the GnosisSafe version to the DeploymentFilter.
The text was updated successfully, but these errors were encountered: