Move cache logic out of RPC and into a JS library
Open
- Dominant language
- TypeScript
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
The current design allows users to replace their RPC with a catch RPC. The issue with this is that non-cached results now return 2x slower than if the user could communicate directly with an RPC.
One possible solution is to cache in-memory in the JS code itself (via extending ethers.js or similar) and then providing public checkpoints which a user can download into their local instance of catch via ipfs and sqlite
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.