fix

Author: m30m

components/EntropyDeployments.tsx

@@ -255,7 +255,7 @@ export const EntropyDeployments: Record<string, EntropyDeployment> = {
   "tabi-testnet": {
     address: "0xEbe57e8045F2F230872523bbff7374986E45C486",
     explorer: "https://testnetv2.tabiscan.com/address/$ADDRESS",
-    delay: "1 block",
+    delay: "0 block",
     gasLimit: "500K",
     network: "testnet",
     rpc: "https://rpc.testnetv2.tabichain.com",
@@ -327,7 +327,7 @@ export const EntropyDeployments: Record<string, EntropyDeployment> = {
   "abstract-testnet": {
     address: "0x858687fD592112f7046E394A3Bf10D0C11fF9e63",
     explorer: "https://explorer.testnet.abs.xyz/address/$ADDRESS",
-    delay: "1 block",
+    delay: "0 block",
     gasLimit: "500K",
     network: "testnet",
     rpc: "https://api.testnet.abs.xyz",

pages/entropy/contract-addresses.mdx

@@ -17,8 +17,7 @@ import EntropyDeploymentTable from "../../components/EntropyDeploymentTable";
 **The default provider for above mainnet chains is `0x52DeaA1c84233F7bb8C8A45baeDE41091c616506`.**
 
 The default provider on mainnet has a reveal delay to avoid changes on the outcome of the Entropy request because of block reorgs.
-The reveal delay can be a number of blocks (measured from the `latest` block) or `safe` which means the reveal will be delayed until the request transaction is included in a block with `safe` tag.
-Read [here](https://www.alchemy.com/overviews/ethereum-commitment-levels) for more information on commitment levels.
+The reveal delay shows how many blocks should be produced after the block including the request transaction in order to reveal and submit a callback transaction.
 
 The default provider fulfills the request by sending a transaction with a gas limit as mentioned in above table. Entropy callbacks the consumer as part of this transaction.
 
@@ -30,12 +29,11 @@ The default provider fulfills the request by sending a transaction with a gas li
       ([k, v]) => v.network === "testnet"
     )
   )}
-  showReveal={false}
+  showReveal={true}
 />
 
 **The default provider for above testnet chains is `0x6CC14824Ea2918f5De5C2f75A9Da968ad4BD6344`.**
 
-The default provider on testnet has the same reveal delay as mainnet to provide consistent behavior and latencies for developers. The reveal delay can be a number of blocks (measured from the `latest` block) or `safe` which means the reveal will be delayed until the request transaction is included in a block with `safe` tag.
-Read [here](https://www.alchemy.com/overviews/ethereum-commitment-levels) for more information on commitment levels.
+The default provider on testnet has reveal delays identical to the corresponding mainnet chains to ensure consistent behavior across environments.
 
 The default provider fulfills the request by sending a transaction with a gas limit as mentioned in above table. Entropy callbacks the consumer as part of this transaction.