Skip to content

docs(entropy): update testnet block delays to match mainnets #713

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

devin-ai-integration[bot]
Copy link
Contributor

Update testnet block delays to match mainnets

Summary

This PR updates the Pyth Network documentation to reflect that testnet block delays are now identical to mainnet block delays, based on changes made in pyth-network/deployments PR #1994.

Changes Made

1. Updated EntropyDeployments.tsx

Updated all testnet entries to show proper block delay values instead of empty strings, matching their mainnet counterparts:

  • lightlink-pegasus: 1 block (matches lightlink-phoenix)
  • chiliz-spicy: 12 blocks (matches chiliz)
  • mode-sepolia: 2 blocks (matches mode)
  • sei-evm-testnet: 1 block (matches sei-evm)
  • arbitrum-sepolia: 6 blocks (matches arbitrum)
  • blast-testnet: 1 block (matches blast)
  • optimism-sepolia: 2 blocks (matches optimism)
  • base-sepolia: 1 block (matches base)
  • zetachain-testnet: 0 block (matches zetachain)
  • taiko-hekla: 1 block (matches taiko)
  • merlin-testnet: 1 block (matches merlin)
  • etherlink-testnet: 1 block (matches etherlink)
  • kaia-testnet: 1 block (matches kaia)
  • berachain-bepolia: 1 block (matches berachain)
  • monad-testnet: 2 blocks (based on PR #1994)
  • story-testnet: 0 block (matches story)
  • And other testnet entries updated accordingly

2. Updated contract-addresses.mdx

Updated the testnet section documentation to reflect that:

  • Testnets now have the same reveal delay as mainnets
  • This provides consistent behavior and latencies for developers
  • Added reference to Ethereum commitment levels documentation

Background

PR #1994 in the deployments repository changed testnet block delays from 0 to match their mainnet equivalents to provide "similar latencies and behavior" for developers. This documentation update ensures that developers reading the docs understand the current behavior rather than the outdated information that testnets have no reveal delays.

Testing

  • ✅ Linting passes (npm run lint)
  • ✅ Documentation builds successfully (npm run dev)
  • ✅ All testnet entries now display proper delay values in the documentation tables

Link to Devin run

https://app.devin.ai/sessions/d8669a9901594479aeba21d316c7b08d

Requested by: Jayant Krishnamurthy (jayant@dourolabs.xyz)

- Update testnet delay values in EntropyDeployments.tsx to match mainnet counterparts
- Update contract-addresses.mdx to reflect that testnets now have reveal delays
- Based on changes in pyth-network/deployments PR #1994

All testnet entries now show proper block delay values instead of empty strings:
- lightlink-pegasus: 1 block (matches lightlink-phoenix)
- chiliz-spicy: 12 blocks (matches chiliz)
- mode-sepolia: 2 blocks (matches mode)
- sei-evm-testnet: 1 block (matches sei-evm)
- arbitrum-sepolia: 6 blocks (matches arbitrum)
- blast-testnet: 1 block (matches blast)
- optimism-sepolia: 2 blocks (matches optimism)
- base-sepolia: 1 block (matches base)
- zetachain-testnet: 0 block (matches zetachain)
- taiko-hekla: 1 block (matches taiko)
- merlin-testnet: 1 block (matches merlin)
- etherlink-testnet: 1 block (matches etherlink)
- kaia-testnet: 1 block (matches kaia)
- berachain-bepolia: 1 block (matches berachain)
- monad-testnet: 2 blocks (based on PR #1994)
- story-testnet: 0 block (matches story)
- And other testnet entries updated to match their mainnet equivalents

Co-Authored-By: Jayant <jayant@dourolabs.xyz>
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

Copy link

vercel bot commented Jun 10, 2025

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

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 10, 2025 4:43pm
documentation ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 10, 2025 4:43pm

- Update abstract mainnet delay from 1 block to 0 block to match fortuna config
- Update unichain mainnet delay from 0 block to 1 block to match fortuna config
- Ensures documentation accurately reflects actual deployment configurations

Co-Authored-By: Jayant <jayant@dourolabs.xyz>
@@ -255,7 +255,7 @@ export const EntropyDeployments: Record<string, EntropyDeployment> = {
"tabi-testnet": {
address: "0xEbe57e8045F2F230872523bbff7374986E45C486",
explorer: "https://testnetv2.tabiscan.com/address/$ADDRESS",
delay: "",
delay: "1 block",
Copy link
Contributor

Choose a reason for hiding this comment

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

revert this one

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.

1 participant