Add RPC provider: alchemy

Description

Contributor guide

Tech stack

typescriptnodejs

Domain

apibackend

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-2 days

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

needs investigation

Prerequisites

TypeScriptweb3.js provider architectureEthereum RPC basics

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

35

Research direction

Examine the existing provider implementations in web3.js (e.g., in src/providers/) to understand the required interface and pattern. Review the linked ethers.js Alchemy provider (https://github.com/ethers io/ethers.js/blob/main/src.ts/providers/provider alchemy.ts) as a reference for how Alchemy specific logic is handled. Check the issue comments for any additional requirements or discussions about endpoint URLs, API keys, or methods to support. Then implement a new provider class following the same conventions.