Skip to content

feat(entropy): More best practices #337

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

Merged
merged 4 commits into from
Jun 13, 2024
Merged

feat(entropy): More best practices #337

merged 4 commits into from
Jun 13, 2024

Conversation

m30m
Copy link
Contributor

@m30m m30m commented Jun 12, 2024

No description provided.

Copy link

vercel bot commented Jun 12, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
documentation ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 13, 2024 8:12am

Since the entropy providers limit the gas usage on the callbacks,
it is important to keep the callback function as simple as possible
so that the gas usage is predictable and below the limits.
This will ensure consistent performance and avoid potential issues with the callback.
Copy link
Member

Choose a reason for hiding this comment

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

This first paragraph can be rephrased like

Keeping the callback function simple is crucial because the entropy providers limit gas usage. This ensures gas usage is predictable and consistent, avoiding potential issues with the callback.

either ask users to submit more transactions after the callback to continue the flow or run a background crank service
to submit the necessary transactions.

You can see the gas limits for each chain in [this](./contract-addresses) page.
Copy link
Contributor

Choose a reason for hiding this comment

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

I suggest linking to pages using the page title, so like "The gas limits for each chain are listed on the Contract Addresses page."

that way the reader can find this info from the index if they're looking for it later.

@m30m m30m force-pushed the more-best-practices branch from 6f84c70 to 9f03689 Compare June 13, 2024 08:10
@m30m m30m merged commit 7e593f5 into main Jun 13, 2024
3 of 4 checks passed
@m30m m30m deleted the more-best-practices branch June 13, 2024 08:11
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 this pull request may close these issues.

3 participants