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

IO to get state of another contract #204

Open
Tracked by #208
steinerkelvin opened this issue Oct 28, 2022 · 3 comments
Open
Tracked by #208

IO to get state of another contract #204

steinerkelvin opened this issue Oct 28, 2022 · 3 comments
Assignees

Comments

@steinerkelvin
Copy link
Contributor

Allows to get and process the dup of the stored state of another contract.

Useful for native code that process the state and extract new info of contracts that don't have an action to return it's entire state without having to process it externally.

cc @VictorTaelin

@steinerkelvin steinerkelvin added enhancement New feature or request discussion labels Oct 28, 2022
@steinerkelvin steinerkelvin self-assigned this Oct 31, 2022
@steinerkelvin steinerkelvin changed the title Primitive to get state of another contract IO to get state of another contract Oct 31, 2022
@steinerkelvin steinerkelvin removed the enhancement New feature or request label Oct 31, 2022
@developedby
Copy link
Contributor

If anyone can put the state behind dups, won't they be able to increase the cost of accessing that memory? This would increase the cost of using a contract for anyone else that comes after.

@steinerkelvin
Copy link
Contributor Author

Top-level dups are resolved before the result is persisted.
I'm not sure what would happen on nested dups.

@steinerkelvin
Copy link
Contributor Author

I have an idea of how this would work as intended, but I need to first polish my thoughts and document the solution to the general "storing lazy state" problem, as this is very related to it.

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

No branches or pull requests

2 participants