feat: add support for starknet network

[wa0x6e]

Toward https://github.com/snapshot-labs/workflow/issues/562

This PR will add support for starknet network.

Tests

query {
  blocks (where: { ts: 1640000000, network_in: ["0x534e5f4d41494e", "1"] }) {
    network
    number
  }
}

This should return

{
  "data": {
    "blocks": [
      {
        "network": "1",
        "number": 13841761
      },
      {
        "network": "0x534e5f4d41494e",
        "number": 407
      }
    ]
  }
}

• starknet: https://starkscan.co/block/407
• ethereum: https://etherscan.io/block/13841761

It is returning blocks, matching the timestamp (Monday, December 20, 2021 11:33:20 AM)

Note

Depends on snapshot-labs/snapshot.js#1155

[Copilot]

Pull Request Overview

Adds support for the Starknet network to the block‐fetching utilities, refactors the cache helpers to use the new util, and provides integration tests plus a dedicated test script.

• Introduce getBlockNumber/interpretResult with Starknet‐specific field mapping
• Refactor getBlock/getRange in cache.ts to leverage getBlockNumber
• Add integration tests for getBlockNumber and a test:integration npm script

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
test/integration/helpers/utils.test.ts	New integration tests for getBlockNumber, including Starknet
src/helpers/utils.ts	Implements getBlockNumber and interpretResult logic
src/helpers/cache.ts	Refactors cache functions to call getBlockNumber
package.json	Adds test:integration script and updates the main test command

Comments suppressed due to low confidence (3)

test/integration/helpers/utils.test.ts:44

• Only the first Starknet network ID is tested. Add a case for the second ID (0x534e5f5345504f4c4941) to ensure full Starknet coverage.

it('should handle starknet specific block', async () => {

src/helpers/cache.ts:5

• [nitpick] The name starts is vague. Consider renaming to startBlockByNetwork for clarity.

const starts: Record<string, number> = {};

src/helpers/cache.ts:10

• [nitpick] blocks could be misread. Rename to blockCache or similar to reflect its purpose as a timestamp‐indexed cache.

const blocks: Record<string, Record<string, number>> = {};

[wa0x6e]

Will wait for snapshot-labs/snapshot.js#1165

[ChaituVR]

Updated blockfinder #484

[ChaituVR]

Something weird in my local, i tried above request but it give me 0 block instead of 407
I also tried same time for 1000 block = 1644428894 it still give me 0 🤔 is it same for you?

[ChaituVR]

Also it is returning latest if i pass latest timestamp, is it expected?

[wa0x6e]

Also it is returning latest if i pass latest timestamp, is it expected?

You get the same latest result, even on network 1, when the ts is very close to the current time.

Starknet block takes a little more time than eth

[wa0x6e]

After a few refresh, it finally returns a block number, it can take up to 1 min

[ChaituVR]

tAck