We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The only features ewasm would need to expose are:
useGas
calldatacopy
calldatasize
return
revert
This could be a way to get wasm VMs implemented and experimented with in a more controlled environment on the main chain.
It is not clear whether the precompiles would have "magic gas calculation rules" or just use "a metering process" on them.
The text was updated successfully, but these errors were encountered:
BTW, can you pass reference to calldata buffer directly to the contract main function?
Sorry, something went wrong.
Sample precompile in Rust: https://github.com/ewasm/ewasm-precompile-sha256/blob/master/src/lib.rs
Great idea. More generally, we can discuss how to constrain Wasm and EEI to get nice properties, such as allowing "magic gas calculation".
Proposal to expose these functions from the EEI:
getCallDataSize
callDataCopy
getCaller
getTxOrigin
getCallValue
No branches or pull requests
The only features ewasm would need to expose are:
useGas
calldatacopy
/calldatasize
)return
/revert
This could be a way to get wasm VMs implemented and experimented with in a more controlled environment on the main chain.
It is not clear whether the precompiles would have "magic gas calculation rules" or just use "a metering process" on them.
The text was updated successfully, but these errors were encountered: