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
I have loved 1inch as a project. It's really simplified token trading for me. Testing it though has been a bit hard.
Per #15 there is no testnet support for 1inch. So the recommended mechanism for testing is to create a Ganache mainnet fork. I tried this approach and it didn't work so well. Every so often, I get like the following:
Transaction: 0x9121fffc83795544412e56f3e376a31ca2787e469041e2967134556310afed4a
Gas usage: 413947
Block number: 15797477
Block time: Fri Oct 21 2022 15:49:50 GMT+0000 (Coordinated Universal Time)
Runtime error: revert
Revert reason: callBytes failed: Error(LOP: bad signature)
I asked in discord what might be the cause of this error and someone responded saying that it seems that if there is a limit order in the route of the protocol then it won't work. However, there is no indication of how to turn off this routes.
So in general I would really appreciate:
Some guidance on how to turn off the limit orders
Some more general guidance on testing. I would love to know how the 1inch company tests the 1inch protocol.
Thanks again for the awesome work!
The text was updated successfully, but these errors were encountered:
Hello folks!
I have loved 1inch as a project. It's really simplified token trading for me. Testing it though has been a bit hard.
Per #15 there is no testnet support for 1inch. So the recommended mechanism for testing is to create a Ganache mainnet fork. I tried this approach and it didn't work so well. Every so often, I get like the following:
I asked in discord what might be the cause of this error and someone responded saying that it seems that if there is a limit order in the route of the protocol then it won't work. However, there is no indication of how to turn off this routes.
So in general I would really appreciate:
Thanks again for the awesome work!
The text was updated successfully, but these errors were encountered: