Verify that Spark Checker can retrieve content announced by Curio to IPNI

[bajtos]

• TODO: How to find a payload ID to test? Inspect piece-indexer Redis state?
• See also Support retrievals from multiaddrs with http-path segment filcdn/roadmap#239
• bafkreih74ljilat42tptlywlnuejfkyigun6ahor5gmkxemqkvvdftasg4 could be a good one to use. However, at the time of writing this comment, the SP was advertising an incorrect retrieval address. (cid.contact query, correct retrieval address).

This requires other tasks listed in filcdn/roadmap#231 to be implemented first.

Blocked by CheckerNetwork/spark-deal-observer#117
Blocks #113

[juliangruber]

This requires other tasks listed in filcdn/roadmap#231 to be implemented first.

@bajtos which of them?

[juliangruber]

For now, I'm assuming it's all of them (except the announcement)

[bajtos]

• bafkreih74ljilat42tptlywlnuejfkyigun6ahor5gmkxemqkvvdftasg4 could be a good one to use. However, at the time of writing this comment, the SP was advertising an incorrect retrieval address. (cid.contact query, correct retrieval address).

The problem has been fixed by now and the IPNI retrieval providers show correct multiaddr now.

For example: https://http.f02620.devtty.eu/ipfs/bafkreih74ljilat42tptlywlnuejfkyigun6ahor5gmkxemqkvvdftasg4

[bajtos]

Based on a recent chat in the Filecoin Slack, here are two miner IDs that are running Curio and adding new DDO deals:

• f01857342
• f01992431

We can use them to verify that Spark can test DDO deals on Curio.

/cc @NikolasHaimerl

[NikolasHaimerl]

Results

I tested the miner ID f01857342.
First, I queried the Peer ID for this miner: 12D3KooWLarn89SZrkN45rGJdwnorARFxhTzqkAKcCCyxsqS2qpk
Then I checked the redis database for entries that contain piece-payloads with this peer ID:

127.0.0.1:16379> SCAN 0 MATCH piece-payload:12D3KooWLarn89SZrkN45rGJdwnorARFxhTzqkAKcCCyxsqS2qpk* COUNT 100
1) "0"
2)  1) "piece-payload:12D3KooWLarn89SZrkN45rGJdwnorARFxhTzqkAKcCCyxsqS2qpk:baga6ea4seaqac57djuykcotytntrdjkf24fxxi5aaisu4u5faq5qvclfhvmt2mq"
...

I then fetched the payload CID for the the first key:

127.0.0.1:16379> SMEMBERS piece-payload:12D3KooWLarn89SZrkN45rGJdwnorARFxhTzqkAKcCCyxsqS2qpk:baga6ea4seaqac57djuykcotytntrdjkf24fxxi5aaisu4u5faq5qvclfhvmt2mq
1) "bafkreiebx67xy2jbcosfdk3ukmerwyvachnrmwwisfyd345smiltfkfgki"

Using the manual check from spark-checker I then searched for the CID bafkreiebx67xy2jbcosfdk3ukmerwyvachnrmwwisfyd345smiltfkfgki and the miner ID f01857342.

// The task to check, replace with your own values
const task = {
  cid: 'bafkreiebx67xy2jbcosfdk3ukmerwyvachnrmwwisfyd345smiltfkfgki',
  minerId: 'f01857342',
}

The result was:

nhaimerl@archlinux ~/C/W/S/spark-checker (main)> ./zinnia run manual-check.js
Calling Filecoin JSON-RPC to get PeerId of miner f01857342
Using PeerID from the smart contract.
Peer ID fetched from smartContract.
Found peer id: 12D3KooWLarn89SZrkN45rGJdwnorARFxhTzqkAKcCCyxsqS2qpk
Querying IPNI to find retrieval providers for bafkreiebx67xy2jbcosfdk3ukmerwyvachnrmwwisfyd345smiltfkfgki
IPNI returned 4 provider results
Fetching: https://deals.future-tech-holdings.com/ipfs/bafkreiebx67xy2jbcosfdk3ukmerwyvachnrmwwisfyd345smiltfkfgki?dag-scope=block
Testing HEAD request: https://deals.future-tech-holdings.com/ipfs/bafkreiebx67xy2jbcosfdk3ukmerwyvachnrmwwisfyd345smiltfkfgki?dag-scope=block
Measurement: {
  cid: "bafkreiebx67xy2jbcosfdk3ukmerwyvachnrmwwisfyd345smiltfkfgki",
  minerId: "f01857342",
  indexerResult: "OK",
  statusCode: 200,
  byteLength: 1048674,
  providerId: "12D3KooWLarn89SZrkN45rGJdwnorARFxhTzqkAKcCCyxsqS2qpk",
  protocol: "http",
  providerAddress: "/dns/deals.future-tech-holdings.com/https",
  startAt: 2025-04-08T13:58:16.007Z,
  carChecksum: "12206e745511f94f59fb602f34e0919590b42e7cc7772b9dc96a659f53e8128cc2e2",
  endAt: 2025-04-08T13:58:17.837Z,
  headStatusCode: 405
}