[OPDATA-4082] Add Coinpaprika State adapter

[paul-chain]

Description

Adds a new Coinpaprika State external adapter that streams state_price via Server-Sent Events (SSE).
See package README for full details

Changes

• New package: @chainlink/coinpaprika-state-adapter
• Endpoint: coinpaprika-state (alias: state)
• Transport: single-connection SSE with:
  • pair batching & dynamic reconnect on pair-set change
  • JSON parsing with malformed-event tolerance
  • graceful shutdown & reconnection backoff with jitter

Sample Input and Output

Sample Input

{
  "data": {
    "base": "LUSD",
    "quote": "USD",
    "endpoint": "coinpaprika-state"
  }
}

Using the alias state

{
  "data": {
    "base": "LUSD", 
    "quote": "USD",
    "endpoint": "state"
  }
}

Without endpoint (uses default)

{
  "data": {
    "base": "LUSD",
    "quote": "USD"
  }
}

Sample Output

{
  "data": {
    "result": 1.000979,
    "timestamp": 1758888503
  },
  "statusCode": 200,
  "result": 1.000979,
  "timestamps": {
    "providerDataRequestedUnixMs": 1758888508939,
    "providerDataReceivedUnixMs": 1758888508939,
    "providerIndicatedTimeUnixMs": 1758888503000
  },
  "meta": {
    "adapterName": "COINPAPRIKA_STATE",
    "metrics": {
      "feedId": "{\"base\":\"lusd\",\"quote\":\"usd\"}"
    }
  }
}

Example cURL Requests

Using the primary endpoint coinpaprika-state

curl -X POST http://localhost:8080 \
  -H "Content-Type: application/json" \
  -d '{"data":{"base":"LUSD","quote":"USD","endpoint":"coinpaprika-state"}}'

Using the alias state

curl -X POST http://localhost:8080 \
    -H "Content-Type: application/json" \
    -d '{"data": {"base": "LUSD", "quote": "USD", "endpoint": "state"}}'

Without endpoint (uses default)

curl -X POST http://localhost:8080 \
  -H "Content-Type: application/json" \
  -d '{"data": {"base": "LUSD", "quote": "USD"}}'

Steps to Test

1. Navigate to the root of the external-adapters-js repo
2. Build the adapter: yarn workspace @chainlink/coinpaprika-state-adapter build
3. Run tests:

• Integration test: yarn test packages/sources/coinpaprika-state/test/integration/adapter.test.ts
• Unit test: yarn test packages/sources/coinpaprika-state/test/unit/sse.test.ts

Quality Assurance

• If a new adapter was made, or an existing one was modified so that its environment variables have changed, update the relevant infra-k8s configuration file.
• If a new adapter was made, or an existing one was modified so that its environment variables have changed, update the relevant adapter-secrets configuration file or update the soak testing blacklist.
• If a new adapter was made, or a new endpoint was added, update the test-payload.json file with relevant requests.
• The branch naming follows git flow (feature/x, chore/x, release/x, hotfix/x, fix/x) or is created from Jira.
• This is related to a maximum of one Jira story or GitHub issue.
• Types are safe (avoid TypeScript/TSLint features like any and disable, instead use more specific types).
• All code changes have 100% unit and integration test coverage. If testing is not applicable or too difficult to justify doing, the reasoning should be documented explicitly in the PR.

[changeset-bot]

🦋 Changeset detected

Latest commit: 83913f6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@chainlink/coinpaprika-state-adapter	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[karen-stepanyan]

any reason why this is not a new endpoint on existing coinpaprika EA ?

[paul-chain]

Updated to use existing EA with new endpoint

[alejoberardino]

saw this pr randomly, there's an sse transport in the framework, what's the particular reason this adapter needs a custom one?

[paul-chain]

@alejoberardino I investigated SseTransport but found it's designed around the usual EventSource/GET model (and optional separate sub/unsub/keepalive calls). The current design of Coinpaprika State API instead opens a single SSE connection via POST with a JSON body containing all pairs and expects reconnects when the pair set changes. Given that shape, SubscriptionTransport is a cleaner fit for batching pairs and managing one shared connection + reconnection logic.

[mmcallister-cll]

Just noting an assumption on this SSE transport: We assume each valid streamed message will contain 1 event and 1 data field. Changes to the data provider API message schema (multi-responses or otherwise) are not expected to work out of the box and would require further code changes.