Skip to content
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

what's the plan about ext_storage_proof_size_storage_proof_size_version_1? #1833

Closed
xlc opened this issue May 16, 2024 · 3 comments · Fixed by #1834
Closed

what's the plan about ext_storage_proof_size_storage_proof_size_version_1? #1833

xlc opened this issue May 16, 2024 · 3 comments · Fixed by #1834

Comments

@xlc
Copy link
Contributor

xlc commented May 16, 2024

AcalaNetwork/chopsticks#754

not sure if there is already an issue about it but looks like more teams are using this feature

@tomaka
Copy link
Contributor

tomaka commented May 16, 2024

Well, I was vehemently against RFC 43.

In the discussion, I explained that in my opinion this function isn't implementable because generating a proof is currently an implementation detail. @bkchr and @skunert on the other hand claim that they could properly write a spec of how proof generation works should work deterministically. If such a spec appears, I can implement it, otherwise I won't.

@bkchr
Copy link

bkchr commented May 16, 2024

You can just provide the host function and return 0.

@tomaka
Copy link
Contributor

tomaka commented May 16, 2024

I went with the solution of tossing the hot potato to the API user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants