Skip to content

fix(dos): correct metadata for DOS Chain (7979) and DOS Testnet (3939)#8096

Open
JOY wants to merge 1 commit intoethereum-lists:masterfrom
JOY:fix/dos-chain-metadata
Open

fix(dos): correct metadata for DOS Chain (7979) and DOS Testnet (3939)#8096
JOY wants to merge 1 commit intoethereum-lists:masterfrom
JOY:fix/dos-chain-metadata

Conversation

@JOY
Copy link

@JOY JOY commented Feb 24, 2026

Summary

  • Fix infoURL from doschain.io to doschain.com for both mainnet (7979) and testnet (3939)
  • Fix testnet shortName from dost to dos-test
  • Fix testnet RPC URL trailing slash
  • Fix testnet infoURL protocol from http to https
  • Add EIP1559 feature flag — DOS Chain is subnet-evm based (Avalanche L1), supports EIP-1559
  • Add "active" status for both chains
  • Add dedicated DOScan explorer icon (doscan.json) — SVG uploaded to IPFS

Changes

File Change
eip155-7979.json Fix infoURL, add features/status, explorer icon → doscan
eip155-3939.json Fix infoURL/shortName/RPC, add features/status, explorer icon → doscan
icons/doscan.json New — dedicated DOScan block explorer icon (SVG on IPFS)

Verification

  • doschain.com resolves correctly
  • main.doschain.com RPC responds
  • test.doschain.com RPC responds
  • doscan.io explorer live (EIP3091)
  • test.doscan.io explorer live (EIP3091)
  • IPFS icon accessible: ipfs://bafkreigebmjtun75zmpgtywve6za5bobpxwtw7k7qme7iauod7bumq7ply

- Fix infoURL from doschain.io to doschain.com (both mainnet 7979 and testnet 3939)
- Fix testnet shortName from "dost" to "dos-test"
- Fix testnet RPC trailing slash
- Fix testnet infoURL protocol from http to https
- Add EIP1559 feature flag (subnet-evm based chain)
- Add "active" status for both chains
- Add dedicated DOScan explorer icon (SVG on IPFS)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions
Copy link

You successfully submitted a PR! Due to the amount of PRs coming in: we will only look at PRs that the CI is happy with. We can also not hold your hand getting the CI green - just look how others that where merged did it and RTFM. So as long as there is any CI check that reports an error - no human will look at this. You might be able to ask for some support after supporting the project - e.g. by sending funds to lists.eth. When you fixed things after a requested change - then you also need to (re-)request a review.

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.

1 participant