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
(Capturing some of our discussion)
Exo's use Endo Patterns to validate arguments. M.string() has a default length limit of 100k.
M.string()
Chain storage is implemented as an Exo and thus any string value passed to it over 100k throws.
The market items collection currently serializes into one storage node.
Store each item in its own storage node.
When a market item is no longer for sale, the node is deleted. How to delete: Agoric/agoric-sdk#8063 (comment)
Note that it requires the node be created with sequence: false option. That inherited through the node hierarchy and our bootstrap root node is sequence: true. So your core proposal should override that with sequence: false and then all the contract's nodes will be configured that way.
sequence: false
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
(Capturing some of our discussion)
Background
Exo's use Endo Patterns to validate arguments.
M.string()
has a default length limit of 100k.Chain storage is implemented as an Exo and thus any string value passed to it over 100k throws.
Problem
The market items collection currently serializes into one storage node.
Solution
Store each item in its own storage node.
When a market item is no longer for sale, the node is deleted. How to delete: Agoric/agoric-sdk#8063 (comment)
Note that it requires the node be created with
sequence: false
option. That inherited through the node hierarchy and our bootstrap root node is sequence: true. So your core proposal should override that withsequence: false
and then all the contract's nodes will be configured that way.The text was updated successfully, but these errors were encountered: