Add Stork, Scry Protocol, SEDA to the oracles.csv file

[Adisaok]

Summary

Type of change

• Add data rows
• Update data rows
• Remove data rows
• Schema change
• Documentation/metadata only

Scope

• Networks affected:

• Categories affected:

• Additional notes, additional context / screenshots:

Links

• Related issue(s)/ DB Improvement Proposal (if schema-related):

Validation checklist

• I followed the Style Guide and Column Definitions. I'm aware of what is !provider syntax, and that entities in /networks sub-folders inherits records from /providers folder
  • Style Guide: https://github.com/Chain-Love/chain-love/wiki/Style-Guide
  • Column Definitions: https://github.com/Chain-Love/chain-love/wiki
• I personally opened and verified every new link I'm adding. I can confirm, that all the links I'm adding are valid.
• If I added new entries - I personally confirmed that the provider I'm adding (modifying) currently supports the adjusted network(s). I've also verified that value in every cell I'm changing is correct according to my best understanding
• This PR is not a blind AI-generated submission

Optional

• Rewards address (for data patching rewards):
• Twitter (X) post link (for +10% of rewards to this PR):

[USS-Supervisor]

Hi @Adisaok - this PR is stale, and review should wait until required CI is passing. Current status: no checks reported on the 'patch-834717' branch. Could you please fix or trigger CI and update the PR?

[Adisaok]

Hi @Adisaok - this PR is stale, and review should wait until required CI is passing. Current status: no checks reported on the 'patch-834717' branch. Could you please fix or trigger CI and update the PR?

Hi @eugene17kotov, please, what is left for me to fix on this PR?

[USS-Supervisor]

Hi @Adisaok - this PR is stale, and review should wait until required CI is passing. Current status: no checks are currently reported on the patch-834717 branch. Could you please fix or trigger CI and update the PR when ready?

[USS-Supervisor]

Hi @Adisaok - this PR is stale, and review should wait until required CI passes. Current status: no checks reported. Could you please fix or trigger CI and update the PR when ready?

[github-actions]

Summary

Status	Count
🔍 Total	33
🔗 Unique	30
✅ Successful	33
⏳ Timeouts	0
🔀 Redirected	4
👻 Excluded	0
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	0

Full Github Actions output

[USS-Supervisor]

Verdict: REQUEST_CHANGES
Risk: MEDIUM
Summary: CI and the latest link-check are green, and the CSV structure/references parse cleanly, but the PR adds or touches network-specific SEDA oracle listings that I could not verify against SEDA's official supported EVM/prover deployment source. Please either remove those rows or add official SEDA evidence for those exact target networks.
Findings:

• [MEDIUM] listings/specific-networks/ethereum/oracles.csv:16, listings/specific-networks/filecoin/oracles.csv:5, listings/specific-networks/polygon/oracles.csv:7, listings/specific-networks/somnia/oracles.csv:10 - These rows list !offer:seda for Ethereum mainnet, Filecoin mainnet, Polygon mainnet, and Somnia mainnet. SEDA's official Prover Contract Deployments table lists ArbitrumOne and several other networks, but not these target networks, and the SEDA agent guidance says to stop if the target chain is not listed. For network-specific listings, please remove unsupported rows or provide an official SEDA source showing SEDA support for each exact network/chain value. Source: https://docs.seda.xyz/home/technology/seda-network-architecture/seda-core/seda-core-infrastructure-overview/prover-contract-deployments.md and https://docs.seda.xyz/home/for-agents/agent-modules/prover-contract-deployments.md
• [LOW] references/offers/oracles.csv:21 - The new scry-protocol offer row leaves a single-space value in the final tag column (...,,, ). Please make that field truly empty.
  Confidence: HIGH

[github-actions]

Summary

Status	Count
🔍 Total	33
🔗 Unique	30
✅ Successful	33
⏳ Timeouts	0
🔀 Redirected	4
👻 Excluded	0
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	0

Full Github Actions output

[USS-Supervisor]

Verdict: APPROVE
Risk: LOW
Summary: The follow-up commit removes the unsupported SEDA rows from Ethereum, Filecoin, Polygon, and Somnia, and fixes the blank tag field in references/offers/oracles.csv. CSV shape, duplicate checks, offer references, provider logo paths, and the remaining network rows all check out; SEDA remains only on ArbitrumOne, Stork has exact contract-address coverage for the changed networks, and Scry is documented as EVM-focused/permissionless oracle infrastructure. Required validation passes on a976391, and fresh link-check run 30086879486 reports 33/33 successful links with 0 errors/timeouts.
Findings: None.
Confidence: HIGH