Skip to content

Add Valve RPC for Ethereum (1), PulseChain (369) and PulseChain Testnet v4 (943)#2938

Open
valvecitydev wants to merge 3 commits into
DefiLlama:mainfrom
valvecitydev:valve-rpc-privacy-none
Open

Add Valve RPC for Ethereum (1), PulseChain (369) and PulseChain Testnet v4 (943)#2938
valvecitydev wants to merge 3 commits into
DefiLlama:mainfrom
valvecitydev:valve-rpc-privacy-none

Conversation

@valvecitydev

@valvecitydev valvecitydev commented Jul 15, 2026

Copy link
Copy Markdown

Adds Valve's public RPC endpoints for Ethereum mainnet, PulseChain mainnet, and PulseChain Testnet v4:

  • https://rpc.valve.city/v1/vk_demo/evm/1 (chain 1)
  • https://rpc.valve.city/v1/vk_demo/evm/369 (chain 369)
  • https://rpc.valve.city/v1/vk_demo/evm/943 (chain 943)

All three are marked tracking: "none". This is accurate for the public endpoint:

  • No request logs are written and no client IP is stored — access logging is disabled for the public key path.
  • Per-request analytics record no IP address.
  • Per-IP rate-limiting uses ephemeral, salted-hashed counters (auto-expiring; no raw IP at rest).
  • No wallet↔IP correlation, no third-party analytics, no data sale.

Privacy policy: https://valve.city/#/privacy

Notes:

  • CORS is enabled (verified Access-Control-Allow-Origin reflected for https://chainlist.org).
  • Full/archive nodes served from Valve's own infrastructure.

…v4 (943)

Valve runs a privacy-respecting public RPC. For the shared public
endpoint we retain no request logs and store no client IP addresses:
access logging is disabled for the public key, request analytics record
no IP, and per-IP rate-limiting uses ephemeral, salted-hashed counters
(no raw IP at rest). No wallet<->IP correlation, no third-party
analytics, no data sale — so tracking is "none".

  https://rpc.valve.city/v1/vk_demo/evm/1    (Ethereum mainnet)
  https://rpc.valve.city/v1/vk_demo/evm/369  (PulseChain mainnet)
  https://rpc.valve.city/v1/vk_demo/evm/943  (PulseChain Testnet v4)
@valvecitydev
valvecitydev force-pushed the valve-rpc-privacy-none branch from 4c0d20a to 3f39184 Compare July 15, 2026 15:37
@valvecitydev valvecitydev changed the title Add Valve RPC for Ethereum (1) and PulseChain (369) Add Valve RPC for Ethereum (1), PulseChain (369) and PulseChain Testnet v4 (943) Jul 15, 2026
Valve now serves JSON-RPC over WebSocket at the same path as HTTP, over wss://
(key-authed, metered per call). Add a wss:// entry alongside each existing
https:// Valve endpoint, same no-log privacy statement.
@valvecitydev

valvecitydev commented Jul 19, 2026

Copy link
Copy Markdown
Author

Update: Valve now serves JSON-RPC over WebSocket, and I consolidated all entries onto the single canonical host one.valve.city (same host + path form documented on learn.valve.city). Each chain now has an HTTP and a WebSocket entry:

  • chain 1: https://one.valve.city/rpc/vk_demo/evm/1 · wss://one.valve.city/rpc/vk_demo/evm/1
  • chain 369: https://one.valve.city/rpc/vk_demo/evm/369 · wss://one.valve.city/rpc/vk_demo/evm/369
  • chain 943: https://one.valve.city/rpc/vk_demo/evm/943 · wss://one.valve.city/rpc/vk_demo/evm/943

WebSocket is the same URL as HTTP over wss:// — key-authed and metered per call, single + batch. Same no-log privacy policy as the HTTP entries.

Consolidate the HTTP and WebSocket entries (chains 1, 369, 943) onto the
canonical one.valve.city/rpc/<key>/evm/<chainId> surface — the same host and
path form documented on learn.valve.city — instead of the rpc.valve.city/v1
variant. Both forms hit the same nodes; one host keeps the listing consistent.
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