-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EVM: Add an FRC42 endpoint for EVM calls #1256
Comments
So, this is also important for off-chain calls. Right now, we use method 2 which will produce not-so-great errors. Ideally, we'd:
|
This is also an issue for on-chain calls. Right now, we just invoke method 2 without really thinking about it, which will likely cause issues in the future. We should implement this now. |
Specifically:
|
This also re-numbers all the other method numbers, because we're removing method 2. This is going to be annoying... but it's better to do this now than to have a dead method. fixes filecoin-project/ref-fvm#1256
This also re-numbers all the other method numbers, because we're removing method 2. This is going to be annoying... but it's better to do this now than to have a dead method. fixes filecoin-project/ref-fvm#1256
This also re-numbers all the other method numbers, because we're removing method 2. This is going to be annoying... but it's better to do this now than to have a dead method. fixes filecoin-project/ref-fvm#1256
Closing this after since filecoin-project/builtin-actors#1021 is merged (not sure why the automation didn't do it) |
I'm a bit concerned that users will start hard-coding the current InvokeContract method number, making it difficult for "native" actors to implement EVM calling. We can likely punt on this, but that should be an explicit decision.
The text was updated successfully, but these errors were encountered: