Content
@
0 reply
0 recast
2 reactions
Jem
@jem
I made what feels like a breakthrough yesterday. It's typically been quite difficult to do fork testing of new contracts for the Olympus protocol, as installation/activation/configuration is done by a multi-sig (and now some of that is performed by OCG).
1 reply
0 recast
0 reaction
Jem
@jem
The multi-sig batches and OCG proposals are written as forge scripts, and there didn't appear to be a way to have forge broadcast as another address when operating on a fork.
1 reply
0 recast
0 reaction
Jem
@jem
Enter the Tenderly Transaction API. https://media.tenor.com/ifV30YPLRW0AAAAM/friends-friends-tv.gif
1 reply
0 recast
0 reaction
Jem
@jem
It turns out that this API doesn't require transactions to be signed, which means we can execute the scripts as if they were coming from the MS/OCG itself. I've modified our scripts to execute MS batches and OCG proposals on a fork if `TESTNET=true`.
1 reply
0 recast
0 reaction
Jem
@jem
... which means we can do better testing of the outcome of multi-sig batches and OCG proposals! Currently, this is tied closely to the Olympus tooling and is not generalisable, but I hope to make it so in the future.
0 reply
0 recast
0 reaction
