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

Create, Add content FAQs.md #31

Closed
wants to merge 25 commits into from
Closed

Conversation

havealakshya
Copy link
Contributor

Created Faq questions & added content to it.

Created Faq questions & added content to it.
@havealakshya havealakshya self-assigned this Apr 22, 2024
@havealakshya havealakshya added the documentation Improvements or additions to documentation label Apr 22, 2024
Spelling, Grammar fixes
@kanikamishra kanikamishra requested review from xadahiya and removed request for 0xpg, xadahiya, muku314115, Seth-Schmidt and iamvijaysaran April 22, 2024 12:38
Copy link
Contributor

@kanikamishra kanikamishra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I checked the doc for spelling and grammar.

@kanikamishra kanikamishra removed the request for review from xadahiya April 23, 2024 11:07
@havealakshya
Copy link
Contributor Author

docs/build-with-powerloom/devnet/FAQs.md Outdated Show resolved Hide resolved
### Can we run the setup on different languages?
Yes, you can run the setup in different languages. The Snapshotter node is a complex system with multiple components written in different languages. Pooler is a Python program, while Audit Protocol is coded in Go. Since Pooler and Audit Protocol communicate via RabbitMQ, either component can be ported to different languages, making the Snapshotter node accessible to developers unfamiliar with Python or Go.

### What is the purpose of the PROTOCOL_STATE_CONTRACT variable?
Copy link
Member

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

Copy link
Contributor

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:

  • Epoch Size of 1: Ideal for real-time use cases where immediate data processing is crucial.
  • Epoch Size of 10: Better suited for use cases that involve aggregated data sets, like data dashboards, where data can be compiled and reviewed over a set period.

This setup allows developers to adapt the protocol according to varying requirements and use cases, ensuring flexibility across different blockchain platforms.

docs/build-with-powerloom/devnet/FAQs.md Outdated Show resolved Hide resolved
@kanikamishra kanikamishra self-requested a review April 24, 2024 13:44
@havealakshya
Copy link
Contributor Author

The FAQ docs reviews have been resolved.

This is ready for its final checks

docs/build-with-powerloom/devnet/FAQs.md Outdated Show resolved Hide resolved
docs/build-with-powerloom/devnet/FAQs.md Outdated Show resolved Hide resolved
### If you are a new Snapshotter,
Enter the ChatID when prompted on the terminal during the node setup.

### If you are an existing Snapshotter,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not about being a 'new snapshotter' or 'existing snapshotter'. It is about whether they have a previously existing installation.

updated rpc section & added link to the compute & config docs.
@SwaroopH SwaroopH closed this Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants