Permission and limits for low-frequency read-only PulseChain RPC monitoring

Web3 FlowWatch is preparing deterministic, low-frequency, read-only monitoring for PulseChain chain 369.

We have made no request to rpc.pulsechain.com and have performed no RPC, JSON-RPC, Web3 or contract calls.

Could you please direct this request to the accountable operator of rpc.pulsechain.com, or provide an official public source or dated written confirmation covering the following:

  1. Whether rpc.pulsechain.com may be used for automated, low-frequency, read-only monitoring.
  2. Whether the following methods are permitted:
  • eth_chainId
  • eth_blockNumber
  • eth_getBlockByNumber
  • eth_getCode
  • eth_call
  • eth_getTransactionByHash
  • eth_getTransactionReceipt
  1. The applicable operational limits, including:
  • rate limits;
  • concurrency limits;
  • request and response size limits;
  • timeouts;
  • batch limits;
  • retry and throttling policies.
  1. The available historical depth for:
  • block headers;
  • transactions and receipts;
  • historical state used by eth_call;
  • any applicable pruning policy.
  1. The accountable operator of the endpoint and sanitized, high-level dependency information sufficient to assess whether it can serve as an independent monitoring source.

Please do not provide credentials, private IP addresses, raw logs, customer data or confidential security information.

Public documentation or a dated written confirmation from an accountable first-party representative would be sufficient.