Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Create, Add content FAQs.md #31
Create, Add content FAQs.md #31
Changes from 4 commits
dcfbc7e
78002c9
ae2441c
eccf47f
8356d83
b9b0dab
b47f220
fb9f720
6df3b05
d443754
3f2e10d
8904510
84ade9a
1648e1b
c44a9dc
b1c7a9f
d9ee15d
9abe1ae
20f036c
b346fe7
65b5677
23d7c43
fa80f74
5cdfe71
fcc7697
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
this should clarify that there are different protocol state contracts depending on the data source contract's chain as well as the epoch size on that chain that is preferred by devs. An epoch size of 1 means more real time use cases, 10 would mean better suited for aggregated dataset use cases like data dashboards
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.
The PROTOCOL_STATE_CONTRACT variable serves a crucial role by specifying the address of the protocol state contract. Its configuration depends on a couple of key factors:
Data Source Contract's Chain: The specific blockchain on which the data source contract is deployed influences the protocol state contract address.
Epoch Size Preference: The epoch size, chosen based on the application’s needs, affects how data is processed and utilized:
This setup allows developers to adapt the protocol according to varying requirements and use cases, ensuring flexibility across different blockchain platforms.