chore: remove sepolia from overview page

Author: rymcol

docs/integration/7683/solver-integration.md

@@ -61,10 +61,10 @@ Here is how you can integrate from step 1 to 5.
 
 ### 1 - Solver logins to t1 backend and streams its prices
 
-Connect to `wss://api.v07.t1protocol.com` by providing following authentication headers:
+Connect to `wss://sealedbid.api.t1protocol.com` by providing following authentication headers:
 
 ```typescript
-  const socket = new WebSocket(`wss://api.v07.t1protocol.com/`, {
+  const socket = new WebSocket(`wss://sealedbid.api.t1protocol.com/`, {
     headers: { 
       "X-Auth-Blob": { 
         username: 'your-username-for-t1-stats-recording-only',
@@ -75,7 +75,7 @@ Connect to `wss://api.v07.t1protocol.com` by providing following authentication
   });
   ```
 - `"X-Auth-Blob".username` is any string that you would like your Solver to be identified by
-- `"X-Auth-Blob".nonce` is a unique nonce tied to your login attempt. you can acquire be calling `https://api.v07.t1protocol.com/api/currentNonce?username=your-username` . This nonce is needed for security of your login - should any part intercept your signature, they are not able to use it to login.
+- `"X-Auth-Blob".nonce` is a unique nonce tied to your login attempt. you can acquire be calling `https://sealedbid.api.t1protocol.com/api/currentNonce?username=your-username` . This nonce is needed for security of your login - should any part intercept your signature, they are not able to use it to login.
 - `"X-Auth-Signature"` is a signature of a stringified `"X-Auth-Blob"` . Make sure to use the private key that will also be used to fill intents!
 
 Then stream your price list in the following format to the socket.
@@ -215,7 +215,7 @@ Location: offchain
 
 Timing: once a new `ProofOfReadRootCommitted` event has been emitted
 
-Base URL: `https://api.v07.t1protocol.com`
+Base URL: `https://sealedbid.api.t1protocol.com`
 
 Endpoint: `/api/read-proofs`
 
@@ -233,7 +233,7 @@ Method: `GET`
 **Example Request:**
 
 ```bash
-curl "https://api.v07.t1protocol.com/api/read-proofs?address=0x123...&direction=ARB_TO_BASE&page=1&page_size=100"
+curl "https://proofofread.api.t1protocol.com/api/read-proofs?address=0x123...&direction=ARB_TO_BASE&page=1&page_size=100"
 ```
 
 The HTTP call will return the following structure as a response :

docs/integration/xChainRead/overview.md

@@ -28,10 +28,10 @@ t1 runs full nodes of partner rollups inside TEEs, ensuring verifiable execution
 
 t1 currently supports the following chains:
 
-- Arbitrum Sepolia
-- Base Sepolia
+- Arbitrum
+- Base
 
-Let's use the following example to demonstrate how to use xChainRead. This example is a simplified version of the [T1ERC7683](https://github.com/t1protocol/t1/blob/canary/contracts/src/7683/T1ERC7683.sol) contract. It allows users to request a cross-chain read of the `getFilledOrderStatus` function of a 7683 contract on the Base Sepolia chain.
+Let's use the following example to demonstrate how to use xChainRead. This example is a simplified version of the [T1ERC7683](https://github.com/t1protocol/t1/blob/canary/contracts/src/7683/T1ERC7683.sol) contract. It allows users to request a cross-chain read of the `getFilledOrderStatus` function of a 7683 contract on the Base chain.
 
 ```solidity
 import "./T1XChainReader.sol";
@@ -51,7 +51,7 @@ contract IntentSettler {
         );
 
         bytes32 requestId = xChainRead.requestRead({
-            destinationDomain: 84532, // Base Sepolia
+            destinationDomain: 84532, // Base
             targetContract: 0xf96B8CcB029E0932fe36da0CeDd2b035E2c1695d,
             gasLimit: 200000,
             minBlock: 0,