From d0689d80b0c9e86b20735d548cf6d609dc27505b Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Thu, 30 Oct 2025 15:46:50 +0000 Subject: [PATCH] docs: add reference to Setting Custom Gas Limits guide in Entropy best practices Co-Authored-By: Jayant --- pages/entropy/best-practices.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/entropy/best-practices.mdx b/pages/entropy/best-practices.mdx index 16fb54eb..90119f8e 100644 --- a/pages/entropy/best-practices.mdx +++ b/pages/entropy/best-practices.mdx @@ -13,7 +13,7 @@ Multiple solutions are possible to address this problem. You can store the rando 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. -The gas limit for each chain is listed on the [contract addresses](./contract-addresses) page. +The gas limit for each chain is listed on the [contract addresses](./contract-addresses) page. If your callback function requires more gas than the default provider limit, you can request a higher gas limit using the [Setting Custom Gas Limits](./set-custom-gas-limits) guide. ## Handling callback failures