migrate blast v3/v4 subgraphs to new account

[mzywang]

Alchemy is migrating a set of its subgraphs to a new account to split the indexing load. We need to migrate the v3/v4 subgraphs in routing to query from the new subgraph. We are starting with blast as it is one of the lower-traffic chains. Follow-up PRs will be filed for the remaining chains.

I added a new secret to the Pipelines account, and made sure to update the ACL so that the routing account will be able to see it.

This PR also removes the decentralized API key as it didn't look to be used anymore.

Tested locally:
V3 Logs:

-25T18:53:06.559Z","v":0}
{
  "name": "RoutingLambda",
  "hostname": "169.254.75.251",
  "pid": 11,
  "level": 30,
  "msg": "Got 3125 V3 pools from the subgraph. 95 after filtering",
  "time": "2025-02-25T18:53:06.970Z",
  "v": 0
}
{
  "name": "RoutingLambda",
  "hostname": "169.254.75.251",
  "pid": 11,
  "level": 30,
  "msg": "Got 95 V3 pools from the subgraph for 81457. Saving to poolCacheGzip.json-81457-V3",
  "time": "2025-02-25T18:53:06.970Z",
  "v": 0
}
{
  "name": "RoutingLambda",
  "hostname": "169.254.75.251",
  "pid": 11,
  "level": 30,
  "result": {
    "Expiration": "expiry-date=\"Sat, 24 Feb 2035 00:00:00 GMT\", rule-id=\"MGRmMzJjNDgtMjA3Yi00ODAzLWE1MjctNzk4ZDQ1YTgyYjFl\"",
    "ETag": "\"74d6056f08a99ef696600ce76394f3ca\"",
    "ServerSideEncryption": "AES256"
  },
  "msg": "Done V3 for 81457",
  "time": "2025-02-25T18:53:07.104Z",
  "v": 0
}
{
  "name": "RoutingLambda",
  "hostname": "169.254.75.251",
  "pid": 11,
  "level": 30,
  "msg": "Successfully cached 81457 V3 pools to S3 bucket routingapistack-routingca-poolcachebucket3c1337d0e-zustlam1u50d",
  "time": "2025-02-25T18:53:07.104Z",
  "v": 0
}
{
  "name": "RoutingLambda",
  "hostname": "169.254.75.251",
  "pid": 11,
  "level": 30,
  "msg": "compression ratio for 81457 V3 pool file is 26332:6800",
  "time": "2025-02-25T18:53:07.104Z",
  "v": 0
}

V4 Logs:

{
  "name": "RoutingLambda",
  "hostname": "169.254.46.109",
  "pid": 11,
  "level": 30,
  "msg": "Got 7 V4 pools from the subgraph. 7 after filtering",
  "time": "2025-02-25T18:54:32.830Z",
  "v": 0
}
{
  "name": "RoutingLambda",
  "hostname": "169.254.46.109",
  "pid": 11,
  "level": 30,
  "msg": "Got 7 V4 pools from the subgraph for 81457. Saving to poolCacheGzip.json-81457-V4",
  "time": "2025-02-25T18:54:32.831Z",
  "v": 0
}
{
  "name": "RoutingLambda",
  "hostname": "169.254.46.109",
  "pid": 11,
  "level": 30,
  "result": {
    "Expiration": "expiry-date=\"Sat, 24 Feb 2035 00:00:00 GMT\", rule-id=\"MGRmMzJjNDgtMjA3Yi00ODAzLWE1MjctNzk4ZDQ1YTgyYjFl\"",
    "ETag": "\"87788015cb2c21c5dab58a98050cf469\"",
    "ServerSideEncryption": "AES256"
  },
  "msg": "Done V4 for 81457",
  "time": "2025-02-25T18:54:32.905Z",
  "v": 0
}
{
  "name": "RoutingLambda",
  "hostname": "169.254.46.109",
  "pid": 11,
  "level": 30,
  "msg": "Successfully cached 81457 V4 pools to S3 bucket routingapistack-routingca-poolcachebucket3c1337d0e-zustlam1u50d",
  "time": "2025-02-25T18:54:32.905Z",
  "v": 0
}
{
  "name": "RoutingLambda",
  "hostname": "169.254.46.109",
  "pid": 11,
  "level": 30,
  "msg": "compression ratio for 81457 V4 pool file is 2621:658",
  "time": "2025-02-25T18:54:32.905Z",
  "v": 0
}

[mzywang]

• migrate blast v3/v4 subgraphs to new account #1031 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[graphite-app]

Graphite Automations

"Request reviewers once CI passes on routing-api repo" took an action on this PR • (02/25/25)

1 assignee was added and 5 reviewers were added to this PR based on Siyu Jiang (See-You John)'s automation.

[jsy1218]

nit: add ALCHEMY_QUERY_KEY_2 into the README

[mzywang]

@jsy1218 i also updated the 1pass env entry for routing api