-
Notifications
You must be signed in to change notification settings - Fork 35
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
pages/entropy/best-practices.mdx
Outdated
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. |
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 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.
pages/entropy/best-practices.mdx
Outdated
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. |
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.
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.
6f84c70
to
9f03689
Compare
No description provided.