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
Ernesto (DAO msig signer) pointed out that the json payloads for a new chain are very hard to verify. He suggested that we consider using solidity contracts with delegated calls.
It seems like we could actually take any tx builder jsoin that had abi data (contractInputsValues,etc), and generate a solidity script with minimal interaces from it.
Maybe the answer is to write tooling to build solidity contracts from json data?
The text was updated successfully, but these errors were encountered:
Ernesto (DAO msig signer) pointed out that the json payloads for a new chain are very hard to verify. He suggested that we consider using solidity contracts with delegated calls.
Here is Aaves multisig repo with these contracts.
Here is an example on configuring a new market.
It seems like we could actually take any tx builder jsoin that had abi data (contractInputsValues,etc), and generate a solidity script with minimal interaces from it.
Maybe the answer is to write tooling to build solidity contracts from json data?
The text was updated successfully, but these errors were encountered: