docs(entropy): update testnet block delays to match mainnets and remove safe block references

[devin-ai-integration]

Update Entropy documentation to reflect current mainnet configurations

Summary

This PR updates the Entropy documentation to align with recent Fortuna configuration changes:

1. Removed safe block status references - The system now only uses latest block status
2. Updated testnet documentation - Clarified that testnet block delays are now identical to mainnet chains for consistent behavior
3. Updated table configuration - Enabled reveal delay display for testnet deployments to show the matching delays

Changes Made

/pages/entropy/contract-addresses.mdx

• Mainnet section: Removed references to safe block status and the explanation about safe vs latest blocks
• Testnet section: Updated description to clarify that testnet delays now match mainnet chains instead of having no delays
• Table configuration: Changed showReveal={false} to showReveal={true} for testnet table to display the delay values

Background

These changes reflect the current Fortuna implementation where:

• Only latest block status is used (no more safe block references)
• Testnet reveal delays now match their corresponding mainnet configurations for consistency
• The EntropyDeployments.tsx component already contains the correct delay values matching the Fortuna config

Verification

• ✅ Documentation builds successfully (npm run build)
• ✅ Linting passes (npm run lint)
• ✅ All safe block status references removed
• ✅ Testnet documentation updated to reflect matching delays
• ✅ Table configuration updated to show reveal delays for both mainnet and testnet

Related

• References mainnet configurations from pyth-network/deployments
• Addresses feedback from PR #1994 in the deployments repository

---

Link to Devin run: https://app.devin.ai/sessions/687c9433a1864a30a48e90df9297cc01

Requested by: Amin Moghaddam (amin@dourolabs.xyz)

[devin-ai-integration]

🤖 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

[vercel]

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:38pm
documentation	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 10, 2025 4:38pm