config: Update page configuration

analytics/ hypeburn.json

@@ -0,0 +1,11 @@
+{
+    "entity": "Hypeburn",
+    "dashboards": [
+      {
+        "name": "HYPE Burn",
+        "url": "https://www.hypeburn.fun/",
+        "description": "Hyperliquid token accrual and builder revenue data.",
+        "type": "custom"
+      }
+    ]
+  }

analytics/hypeflows.json

@@ -0,0 +1,11 @@
+{
+    "entity": "Neutrl Labs",
+    "dashboards": [
+      {
+        "name": "HypeFlows",
+        "url": "https://hypeflows.com/",
+        "description": "The best place to track Hyperliquid's trading stats against Centralized Exchanges.",
+        "type": "custom"
+      }
+    ]
+  }

analytics/hyperdash.json

@@ -0,0 +1,11 @@
+{
+  "entity": "HyperDash",
+  "dashboards": [
+    {
+      "name": "HyperDash",
+      "url": "https://hyperdash.info/",
+      "description": "Analytics and insights for the Hyperliquid ecosystem.",
+      "type": "custom"
+    }
+  ]
+}

analytics/hyperdata.json

@@ -0,0 +1,11 @@
+{
+    "entity": "Hyperdata",
+    "dashboards": [
+      {
+        "name": "Hyperdata",
+        "url": "https://hyperdata.info/",
+        "description": "Real-time Hypercore analytics.",
+        "type": "custom"
+      }
+    ]
+  }

apis/blocksense.json

@@ -0,0 +1,9 @@
+{
+  "entity": "Blocksense",
+  "apis": [
+    {
+      "name": "Blocksense Price Feed API",
+      "url": "https://coda.io/@georgi-zlatarev/blocksense-hyperevm-price-feeds"
+    }
+  ]
+} 

apis/enso.json

@@ -0,0 +1,9 @@
+{
+  "entity": "Enso",
+  "apis": [
+    {
+      "name": "Shortcuts API",
+      "url": "https://docs.enso.build/pages/build/get-started/overview"
+    }
+  ]
+} 

apis/sim.json

@@ -0,0 +1,9 @@
+{
+  "entity": "Sim",
+  "apis": [
+    {
+      "name": "Sim API",
+      "url": "https://sim.dune.com/"
+    }
+  ]
+} 

explorers/README.md

@@ -20,6 +20,14 @@ Each explorer should create one JSON file named `<entity-name>.json` with the fo
 - **url** (required): The explorer website URL
 - **description** (required): Brief description of what your explorer offers
 
+## Best Practices
+
+1. **Performance**: Ensure fast loading times and responsive UI
+2. **Features**: Provide comprehensive blockchain data (blocks, txs, validators)
+3. **Search**: Implement robust search functionality
+4. **Mobile**: Optimize for mobile devices
+5. **API**: Consider offering an API for programmatic access
+
 ## Examples
 
 ### Basic Explorer
@@ -40,6 +48,18 @@ Each explorer should create one JSON file named `<entity-name>.json` with the fo
 }
 ```
 
+## Common Features
+
+Good explorers typically include:
+- Block details and history
+- Transaction search and details
+- Address/account information
+- Validator information and voting power
+- Network statistics
+- Token transfers and balances
+- Smart contract verification
+- API documentation
+
 ## Contributing
 
 1. Fork

guides/bedlam.json

@@ -0,0 +1,12 @@
+{
+    "entity": "Bedlam Research",
+    "guides": [
+      {
+        "title": "The Design Space for Builder-Deployed Perps.",
+        "description": "A comprehensive analysis of the design space for builder-deployed perps.",
+        "url": "https://www.bedlamresear.ch/posts/builder-deployed-perps/",
+        "difficulty": "intermediate",
+        "topics": ["hip-3", "builder codes", "defi"]
+      }
+    ]
+  }

guides/felix.json

@@ -0,0 +1,41 @@
+{
+    "entity": "Felix",
+    "guides": [
+      {
+        "title": "Builder Codes and the Future of Hyperliquid as Infra",
+        "description": "A breakdown of the emerging builder code ecosystem.",
+        "url": "https://x.com/0xBroze/status/1938603649917153661",
+        "difficulty": "beginner",
+        "topics": ["builder codes", "defi", "trading"]
+      },
+      {
+        "title": "Explain the Unit Guardian System Like I’m 5: BTC on Hyperliquid",
+        "description": "A simple explanation of the Unit Guardian System.",
+        "url": "https://x.com/0xBroze/status/1890761476501131353",
+        "difficulty": "beginner",
+        "topics": ["defi", "unit"]
+      },
+      {
+        "title": "Unlocking Efficient Liquidations: The Power of HyperCore<>HyperEVM Composability",
+        "description": "The power of composability between HyperCore and HyperEVM.",
+        "url": "https://x.com/0xBroze/status/1900525372707574012",
+        "difficulty": "intermediate",
+        "topics": ["hypercore", "defi"]
+      },
+      {
+        "title": "How Hyperliquid’s Precompile Architecture Enables Real Time Awareness",
+        "description": "How precompiles unlock real time awareness on Hyperliquid.",
+        "url": "https://x.com/emaverick90/status/1924805040121815399",
+        "difficulty": "intermediate",
+        "topics": ["precompiles", "defi"]
+      },
+      {
+        "title": "Plug-and-Play Perps Exchange : Launch in Hours w/ Builder Codes & HIP3",
+        "description": "How exchanges can launch overnight with deeper books than Tier-1 CEXs.",
+        "url": "https://x.com/emaverick90/status/1920080068388294942",
+        "difficulty": "beginner",
+        "topics": ["hip-3", "builder codes"]
+      }
+
+    ]
+  }

guides/hyperdrive.json

@@ -0,0 +1,10 @@
+{
+  "entity": "Hyperdrive",
+  "guides": [
+    {
+      "title": "The Not-So-Definitive guide to Hyperliquid Precompiles.",
+      "description": "Imagine if Binance allowed smart contract developers to deploy on the Binance order books… this is what Hyperliquid enables.",
+      "url": "https://medium.com/@ambitlabs/the-not-so-definitive-guide-to-hyperliquid-precompiles-f0b6025bb4a3"
+    }
+  ]
+}

indexers/goldsky.json

@@ -0,0 +1,10 @@
+{
+  "entity": "Goldsky",
+  "indexers": [
+    {
+      "name": "Goldsky HyperEVM Indexer",
+      "url": "https://docs.goldsky.com/chains/hyperevm",
+      "description": "Goldsky offers real-time and historical indexing infrastructure for HyperEVM, enabling developers to build fast and reliable on-chain data services."
+    }
+  ]
+} 

indexers/sqd.json

@@ -0,0 +1,10 @@
+{
+  "entity": "SQD",
+  "indexers": [
+    {
+      "name": "SQD Hyperliquid Support",
+      "url": "https://docs.sqd.ai/hyperliquid-support/",
+      "description": "SQD provides decentralized data indexing for Hyperliquid, allowing customizable and scalable subgraph-like data querying."
+    }
+  ]
+} 

rpcs/README.md

@@ -1,6 +1,6 @@
 # RPC Endpoints
 
-Public RPCs for interacting with HyperEVM.
+Public RPCs for interacting with HL.
 
 ## File Format
 
@@ -86,25 +86,7 @@ Which provides:
 - Geographic routing for optimal latency
 - Health monitoring and automatic exclusion of failing endpoints
 
-## Rate Limiting
-
-Providers can specify rate limits in their endpoint configuration. Our load balancer will enforce these limits per end-user (WIP).
-
-### L7 Proxy Considerations
-
-Our load balancer operates as a Layer 7 proxy, terminating client connections and establishing new ones to upstream providers. This means:
-- All requests to your RPC will originate from our load balancer IPs
-- The original client IP is preserved in the `X-Forwarded-For` header
-- To properly rate limit individual users (not our proxy), configure your infrastructure to evaluate limits based on `X-Forwarded-For`
-
-### Load Balancer Origins
-
-When implementing `X-Forwarded-For` based rate limiting, whitelist these hosts:
-- `us-east.rpc.hyperliquid.directory`
-- `eu.rpc.hyperliquid.directory`
-- `tyo.rpc.hyperliquid.directory`
-
-Feel free to [ping us](https://t.me/murakamikaze) for support on this
+## Contributing
 
 ## Contributing
 

tools/biconomy.json

@@ -0,0 +1,12 @@
+{
+  "entity": "Biconomy",
+  "tools": [
+    {
+      "name": "MEE",
+      "description": "Biconomy's Modular Execution Environment",
+      "url": "https://docs.biconomy.io/new/getting-started/getting-started",
+      "type": "sdk",
+      "language": "Solidity"
+    }
+  ]
+} 

tools/copypaste.json

@@ -0,0 +1,12 @@
+{
+  "entity": "Copypaste",
+  "tools": [
+    {
+      "name": "Ferrofluid",
+      "description": "High Performance Hyperliquid Rust SDK",
+      "url": "https://github.com/ControlCplusControlV/ferrofluid",
+      "type": "sdk",
+      "language": "Rust"
+    }
+  ]
+} 

tools/debridge.json

@@ -0,0 +1,12 @@
+{
+  "entity": "DeBridge",
+  "tools": [
+    {
+      "name": "DeBridge Messaging Protocol",
+      "description": "Cross-chain messaging and asset bridging for Hyperliquid.",
+      "url": "https://docs.debridge.finance/the-debridge-messaging-protocol/deployed-contracts#evm-chains",
+      "type": "sdk",
+      "language": "Solidity"
+    }
+  ]
+} 

tools/gelato.json

@@ -0,0 +1,12 @@
+{
+  "entity": "Gelato",
+  "tools": [
+    {
+      "name": "Gelato Web3 Services",
+      "description": "Automation and execution tooling for smart contracts.",
+      "url": "https://docs.gelato.cloud/Web3-Functions/Introduction/Overview",
+      "type": "sdk",
+      "language": "TypeScript"
+    }
+  ]
+} 

tools/hyperlane.json

@@ -0,0 +1,12 @@
+{
+  "entity": "Hyperlane",
+  "tools": [
+    {
+      "name": "Hyperlane Messaging",
+      "description": "Permisionless Hyperlane cross-chain messaging.",
+      "url": "https://docs.hyperlane.xyz/docs/reference/developer-tools/cli",
+      "type": "sdk",
+      "language": "Solidity"
+    }
+  ]
+} 

tools/hyperliquid.json

@@ -0,0 +1,12 @@
+{
+  "entity": "Hyperliquid",
+  "tools": [
+    {
+      "name": "Hyperliquid Python SDK",
+      "description": "Python SDK example for interacting with HyperEVM.",
+      "url": "https://github.com/hyperliquid-dex/hyperliquid-python-sdk/blob/master/examples/basic_evm_use_big_blocks.py",
+      "type": "sdk",
+      "language": "Python"
+    }
+  ]
+} 

tools/layerzero.json

@@ -0,0 +1,12 @@
+{
+  "entity": "LayerZero",
+  "tools": [
+    {
+      "name": "LayerZero Messaging",
+      "description": "Crosschain messaging protocol integrated with Hyperliquid.",
+      "url": "https://docs.layerzero.network/v2/deployments/deployed-contracts?chains=hyperliquid",
+      "type": "sdk",
+      "language": "Solidity"
+    }
+  ]
+} 

tools/perpflow.json

@@ -0,0 +1,12 @@
+{
+  "entity": "Perpflow",
+  "tools": [
+    {
+      "name": "Trace‑X Call Trace Visualizer",
+      "description": "Paste calldata and run Trace‑X to visualize HyperEVM transaction call traces for debugging.",
+      "url": "https://trace-x.xyz/",
+      "type": "client",
+      "language": "JavaScript"
+    }
+  ]
+} 

tools/proof-of-play.json

@@ -0,0 +1,12 @@
+{
+  "entity": "Proof of Play",
+  "tools": [
+    {
+      "name": "VRNG",
+      "description": "Verifiable Random Number Generator for smart contracts.",
+      "url": "https://docs.proofofplay.com/services/vrng/about",
+      "type": "sdk",
+      "language": "Solidity"
+    }
+  ]
+} 

tools/pyth.json

@@ -0,0 +1,12 @@
+{
+  "entity": "Pyth",
+  "tools": [
+    {
+      "name": "Pyth Price Feeds",
+      "description": "Real-time oracle feeds for EVM including Hyperliquid.",
+      "url": "https://docs.pyth.network/price-feeds/contract-addresses/evm",
+      "type": "sdk",
+      "language": "Solidity"
+    }
+  ]
+} 

tools/redstone.json

@@ -0,0 +1,12 @@
+{
+  "entity": "Redstone",
+  "tools": [
+    {
+      "name": "Redstone Feeds",
+      "description": "Popular oracle data feeds for EVM networks including HyperEVM.",
+      "url": "https://app.redstone.finance/app/feeds/?page=1&sortBy=popularity&sortDesc=false&perPage=32&networks=999,998",
+      "type": "sdk",
+      "language": "Solidity"
+    }
+  ]
+}