-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Add EIP-5219: Contract Resource Requests #5219
Conversation
All tests passed; auto-merging...(pass) eip-5219.md
(pass) assets/eip-5219/IDecentralizedApp.sol
|
Co-authored-by: Micah Zoltu <micah@zoltu.net>
Re-trigger CI |
The commit f875cde (as a parent of 3354320) contains errors. Please inspect the Run Summary for details. |
Head branch was pushed to by a user without write access
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.
It is unclear to me how exactly this solves the problems you proposed. We already have a mechanism for calling functions against Ethereum contracts and getting responses, along with an enchoding scheme for all of that (the solidity function call ABI). I don't understand what we gain by having a function with an abstract function calling mechanism in it.
Think about this EIP as standardizing a way for smart contracts to become websites. HTTP just happens to be the current standard for that, and so this EIP tries to mimic that. |
Head branch was pushed to by a user without write access
The commit fda819c (as a parent of 49d6bbe) contains errors. Please inspect the Run Summary for details. |
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.
LGTM
* Add eip-dhttp * Self-assign EIP number * I can't believe I somehow missed that * Update EIPS/eip-5219.md Co-authored-by: Micah Zoltu <micah@zoltu.net> * Add actual solution to problem * Formatting * Update discussions-to link * It worked locally though! * Add extra newline * Remove EIP-20 reference * Add field that I missed * Change the name to Contract REST & make a few more changes * Move text from abstract to motivation * Make suggested changes * Remove EIP-165 * Alternative mechanism described * Get rid of all EIP references * Extremely slim down the spec * Make the EIP motivation a bit more clearer throughout * Change name to "Contract Resource Requests" * Fix typos Co-authored-by: Micah Zoltu <micah@zoltu.net>
When opening a pull request to submit a new EIP, please use the suggested template: https://github.com/ethereum/EIPs/blob/master/eip-template.md
We have a GitHub bot that automatically merges some PRs. It will merge yours immediately if certain criteria are met: