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
Thinking of how to improve UX, one sucky thing about the current system is that doing the configuration makes me pretty anxious and likely other devs as well.
So thinking around how to make it simpler, consider an Plug that needs to be deployed on both arbi and opti.
We can write a connectionHelper plug that plugs your plugs in.
Your plug will have a boolean called "helperMode" that will be turned off by default
Owner can turn it on/off
easyConnect() that only local connectionHelper contract can call + this function trips helperMode to off before finishing execution
On the source chain, on connectionHelper pass it "integrationType",localPlug and siblingPlug address
It calls connect on localPlug and then sends a message to remote ConnectionHelper who then does the same for its localPlug via easyConnect() on destination chain.
As soon as this tx is done, your connection is done.
The text was updated successfully, but these errors were encountered:
Thinking of how to improve UX, one sucky thing about the current system is that doing the configuration makes me pretty anxious and likely other devs as well.
So thinking around how to make it simpler, consider an Plug that needs to be deployed on both arbi and opti.
As soon as this tx is done, your connection is done.
The text was updated successfully, but these errors were encountered: