OffchainLabs / OffchainLabs/arbitrum-sdk
Enable getting getL2Network via an rpc url
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 275
- Forks
- 217
- PR merge metrics
- No merged PRs in 30d
Description
A general pattern I think all rollups should land on as we move to a multi rollup world is the ability to get the rollup config on chain. This way you can bootstrap the arbitrum sdk with only the rpc url even if the rollup config hasn't been added to this sdk yet.
e.g.
const l2Network = await getL2NetworkFromRpc(
l2RpcUrl /** <-- rpc url of target Arbitrum chain */
)
This allows us to more easily make tooling work for all chains without needing to specify the config within the library first or needing to tediously craft your own config
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the SDK's existing getL2Network functionality and the entry point represented by getL2NetworkFromRpc. Determine how an RPC URL could provide the on-chain rollup configuration, then verify that the resulting l2Network can bootstrap the SDK without a pre-added chain configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100