commonprefix / commonprefix/patronum
Allow for passing multiple RPC URLs
- Dominant language
- TypeScript
- Stars
- 24
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the Verifying provider is booted up with just one provider. This provider can be malicious in such a case the current system simply throws an error and fails.
Allow for passing a set of RPC URLs ordered by the most trusted one first. Gracefully try other provider URLs sequentially
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how the Verifying provider is initialized with its single provider and where provider errors are handled. Check the existing RPC proxy flow before deciding how the ordered URLs are passed. Done means the most trusted URL is tried first, failures are handled gracefully, and later URLs are tried sequentially.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100