Skip to content

Add WelshDAG public RPC for BlockDAG Network (1404) - #2981

Open
Welshdag wants to merge 1 commit into
DefiLlama:mainfrom
Welshdag:codex/add-welshdag-rpc-1404
Open

Add WelshDAG public RPC for BlockDAG Network (1404)#2981
Welshdag wants to merge 1 commit into
DefiLlama:mainfrom
Welshdag:codex/add-welshdag-rpc-1404

Conversation

@Welshdag

@Welshdag Welshdag commented Jul 28, 2026

Copy link
Copy Markdown

Summary

Adds the WelshDAG-operated public RPC endpoint for BlockDAG Network, chain ID 1404, using the current extraRpcs.js schema.

  • RPC: https://rpc.welshdag.trade
  • Chain ID: 1404
  • Hex chain ID: 0x57c
  • Operator: WelshDAG
  • Transport: HTTPS through Cloudflare

The endpoint is marked tracking: "limited" because Cloudflare and WelshDAG infrastructure may log IP addresses, RPC methods, timestamps, and request metadata for rate limiting, abuse prevention, security, and service reliability. The published data-handling terms are linked in the RPC entry.

Link the service provider's website (the company/protocol/individual providing the RPC):

https://welshdag.trade

Provide a link to your privacy policy:

https://welshdag.trade/rpc-privacy/

The policy explains the RPC's limited operational logging, purposes, service providers, retention criteria, user choices and contact route.

If the RPC has none of the above and you still think it should be added, please explain why:

This community-operated endpoint provides an additional independent public RPC for BlockDAG users. It requires no API key, supports browser CORS, and is intended to remain publicly available.

Validation

Public checks completed on 28 July 2026:

  • RPC HTTP status: 200
  • CORS: Access-Control-Allow-Origin: *
  • eth_chainId: 0x57c
  • eth_blockNumber: returned a valid current block height
  • No API key required
  • Privacy policy: HTTP 200 across repeated cache-busted requests
  • Privacy policy is linked from the WelshDAG homepage

Repository checks:

  • node --check constants/extraRpcs.js — passed
  • git diff --check — passed
  • Two focused commits and one changed file
  • The 1404 RPC is appended at the end of the extraRpcs object
  • The tracking details include the published privacy-policy URL

The repository test script reproduces three existing failures on the untouched upstream baseline: octal-escape parsing in extraRpcs.js and chainIds.js, plus duplicate chain key 4663. This change introduces no duplicate 1404 key.

@Welshdag

Copy link
Copy Markdown
Author

Hi maintainers — this RPC submission is ready for review. The endpoint, CORS, chain ID and published privacy policy have been verified, and the repository validation check passes. Please let me know if any changes are required. Thank you.

@Define101

Copy link
Copy Markdown
Member

#2980

merged this one, thanks
can i close this one?

@Welshdag

Copy link
Copy Markdown
Author

#2980

merged this one, thanks can i close this one?

no, these are two different RPC. you have listed the other one please list this one also.

@Define101

Copy link
Copy Markdown
Member

@lukepashill-cyber please add it under the current 1404: {
rpcs: [ and dont make a new one

Addresses review feedback: adds the RPC to the existing 1404 entry
instead of declaring a duplicate 1404 key.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@Welshdag
Welshdag force-pushed the codex/add-welshdag-rpc-1404 branch from f883cad to 14ee6f2 Compare August 7, 2026 19:49
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.

3 participants