# Arc technical feedback

The following items are reproducible documentation observations captured in `PULSE_ARC_TECHNICAL_FEEDBACK_EVIDENCE_V1.md`. They are not claims of protocol failure.

## RPC hostname consistency — confirmed documentation issue

At capture time, first-party Arc pages showed both `https://rpc.testnet.arc.io` and `https://rpc.testnet.arc.network`, while both endpoints returned chain ID `5042002` to read-only `eth_chainId`. A builder can therefore receive inconsistent endpoint guidance.

Reproduction: inspect the linked official endpoint/wallet/gas documentation, POST read-only `eth_chainId` to each hostname, and record the UTC timestamp and response. Suggested improvement: designate one canonical hostname and document any alias or migration status.

## Chain-ID representation — confirmed documentation issue

The captured wallet documentation showed a decimal/hex pair that did not encode the same value as live Arc Testnet. Live RPC returned decimal `5042002` (`0x4CEF52`).

Reproduction: compare every displayed decimal and hexadecimal EIP-3085 chain ID with a read-only `eth_chainId` response. Suggested improvement: keep the representations mathematically equivalent and include a release timestamp.

These observations were not submitted to Arc in this local package. Documentation can change; re-capture current pages before external reporting.