Skip to content

feat: add Ozone Chain Testnet configuration - #119

Merged
kuzdogan merged 2 commits into
sourcifyeth:mainfrom
praddoskanna:add-chain-401
Aug 6, 2026
Merged

feat: add Ozone Chain Testnet configuration#119
kuzdogan merged 2 commits into
sourcifyeth:mainfrom
praddoskanna:add-chain-401

Conversation

@praddoskanna

Copy link
Copy Markdown
Contributor

Add Ozone Chain Testnet Support

@kuzdogan

kuzdogan commented Aug 3, 2026

Copy link
Copy Markdown
Member

Thanks for the PR! The CI failure here isn't something you did wrong in the config — both of Ozone Chain Testnet's RPC endpoints are currently down, so the chain can't be verified against.

What happened, step by step:

  1. CI runs npm run generate -- --only 401, which liveness-probes the chain's RPC URLs. Both failed:
    [dead] #401 Ozone Chain Testnet — https://node1.testnet.ozonechain.io
    [dead] #401 Ozone Chain Testnet — https://node2.testnet.ozonechain.io
    1 chain(s) have no live RPC — keeping as supported:false
    
  2. With no live RPC the chain is written as supported: false, which the Sourcify server confirms:
    supportedChains=[1337,31337] | allChains=[1337,31337,401]
    
  3. Unsupported chains are filtered out of the test list, so no verification test was generated — hence the misleading "Did you forget to add a test for your new chain with the id(s) 401?" message. fix: fail generate --only when a chain has no live RPC #120 makes the "Build chains config" step itself fail in this situation, so future runs point straight at the dead RPCs instead.

Probing both endpoints directly:

  • node1.testnet.ozonechain.ioHTTP 502 Bad Gateway from nginx. The proxy is up, the node behind it isn't.
  • node2.testnet.ozonechain.ioTLS handshake fails, expired certificate:
    notAfter = Aug  3 13:41:11 2026 GMT   (Let's Encrypt)
    CI ran at  Aug  3 13:43:19 2026 GMT
    
    The certificate expired about two minutes before CI ran — auto-renewal appears not to have fired.

To move this forward, either get the cert renewed on node2 (and the backend restored on node1) and re-run CI, or point the override at a different working public endpoint if Ozone has one.

Two small nits on the diff itself:

  • The new "401" block uses mixed 3- and 4-space indentation; the rest of the file is 4-space.
  • The file still ends without a trailing newline.

Note that node1 isn't in your diff — it comes from the upstream chainid.network entry for 401 and gets merged with your override, so both get probed.

Posted with Claude Code

@praddoskanna

Copy link
Copy Markdown
Contributor Author

@kuzdogan Fix the certificate issue and lets ignore node1 as it has few other issues .

@praddoskanna praddoskanna left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rerun CI Pipeline

@kuzdogan
kuzdogan merged commit 0103ec8 into sourcifyeth:main Aug 6, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants