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
RSKIP197 - Fix Precompile Calls Not Conforming With CALL Semantics #197
RSKIP197 - Fix Precompile Calls Not Conforming With CALL Semantics #197
Conversation
834c529
to
58fc3bb
Compare
I've just reopened this RSKIP with the specification @SergioDemianLerner @nagarev , any comments? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I understand this change, the RSKIPS should have a single line and nothing more:
"Add REVERT capability to pre-compiled contracts"
That's all that is needed to understand the change. There is no need for examples.
I'm still trying to understand why this is a consensus change. The only reason I found is that this change might bring some unintended side-effects, so we synchronize the activation of this change with the Iris upgrade. |
Thats right, we are trying to synchronize some unexpected behavior from rskj that might affect a transaction final state. Do you think there's no need to include it as RSKIP? Maybe we can do some sync-tests to validate a safe upgrade |
here is a much simplified version of this RSKIP, a oneliner |
fbfd08c
to
45a340f
Compare
45a340f
to
78e580a
Compare
Introducing a new mechanism to handle errors on failed precompiled calls