feat: Dynamic rpc handler

[Keyrxng]

Resolves ubiquity/rpc-handler#3

• Implemented a successful RPC cache
• Included a 5-visit refresh (for cases where only 2 or 3 RPCs make it through the first time it might be a good idea to give them another try later)
• Uses the cancelToken feature of axios to cancel any calls upwards of 500ms (this does log a (cancelled) failure reason but that can be a hit and a miss with one rpc being really quick from one call to the next) and the original flickering issue the "blacklist" resolved has been resolved included in this pr
• merged main into this which is based off the current sync-erc-permits pr and validated everything is working

In the RPC video I'm using mainnet as an example as that has far more failed calls

claiming.mp4

rpc_dynamic_handling.mp4

[ubiquity-os-deployer]

75cb97a

[Keyrxng]

Seems to be working well

Gnosis permit for Anvil

https://eee30fb3.pay-ubq-fi-bxp.pages.dev/?claim=W3sidHlwZSI6ImVyYzIwLXBlcm1pdCIsInBlcm1pdCI6eyJwZXJtaXR0ZWQiOnsidG9rZW4iOiIweGU5MUQxNTNFMGI0MTUxOEEyQ2U4RGQzRDc5NDRGYTg2MzQ2M2E5N2QiLCJhbW91bnQiOiIxMDAwMDAwMDAwMDAwMDAwMDAwIn0sIm5vbmNlIjoiNTIxNDg5OTMxOTcyNDE0NDI4ODMzMDM1NTYwMTQyOTUzMzIxOTcwMTc1OTU0MjQ0NTIyNDc0NzY1NjA5MzY2OTQwNTExODIyMDY4ODEiLCJkZWFkbGluZSI6IjExNTc5MjA4OTIzNzMxNjE5NTQyMzU3MDk4NTAwODY4NzkwNzg1MzI2OTk4NDY2NTY0MDU2NDAzOTQ1NzU4NDAwNzkxMzEyOTYzOTkzNSJ9LCJ0cmFuc2ZlckRldGFpbHMiOnsidG8iOiIweGYzOUZkNmU1MWFhZDg4RjZGNGNlNmFCODgyNzI3OWNmZkZiOTIyNjYiLCJyZXF1ZXN0ZWRBbW91bnQiOiIxMDAwMDAwMDAwMDAwMDAwMDAwIn0sIm93bmVyIjoiMHg3MDk5Nzk3MEM1MTgxMmRjM0EwMTBDN2QwMWI1MGUwZDE3ZGM3OUM4Iiwic2lnbmF0dXJlIjoiMHg5YjgyN2Y0MTA2ZTU0OGRlZTkyM2NlN2VhYTk2MWE5YmY2ZjkwYjE2NTlmZDU1NDkxYjZhNTNjZTdlZmEwZTkwNTg3NGQ2ODdhMTZmMTc0ZDE0YzAyNjdkOTY1MTdkYjhmMWQ0ODY1NTRmN2M2NjRlNTlmNmYzZTdkNDM1ODYyNjFjIiwibmV0d29ya0lkIjoxMDB9LHsidHlwZSI6ImVyYzIwLXBlcm1pdCIsInBlcm1pdCI6eyJwZXJtaXR0ZWQiOnsidG9rZW4iOiIweGU5MUQxNTNFMGI0MTUxOEEyQ2U4RGQzRDc5NDRGYTg2MzQ2M2E5N2QiLCJhbW91bnQiOiI5MDAwMDAwMDAwMDAwMDAwMDAwIn0sIm5vbmNlIjoiMTAzOTM3OTAzMTcxNDg5NzUyMDE2NTQ2NDI4NTY3ODg5NDM4NTQyMDgxNjk5MTE4MDk3NjU5NTAzNjk3NDc2NzIzMjgyMjM3MzQxNDEiLCJkZWFkbGluZSI6IjExNTc5MjA4OTIzNzMxNjE5NTQyMzU3MDk4NTAwODY4NzkwNzg1MzI2OTk4NDY2NTY0MDU2NDAzOTQ1NzU4NDAwNzkxMzEyOTYzOTkzNSJ9LCJ0cmFuc2ZlckRldGFpbHMiOnsidG8iOiIweGYzOUZkNmU1MWFhZDg4RjZGNGNlNmFCODgyNzI3OWNmZkZiOTIyNjYiLCJyZXF1ZXN0ZWRBbW91bnQiOiI5MDAwMDAwMDAwMDAwMDAwMDAwIn0sIm93bmVyIjoiMHg3MDk5Nzk3MEM1MTgxMmRjM0EwMTBDN2QwMWI1MGUwZDE3ZGM3OUM4Iiwic2lnbmF0dXJlIjoiMHhkYWIyOTE1Y2M0OTM4ZDdkNDg0ZDVmNDQxYWNmYjJmYmMyNGJjNTFkYzJkMmYwOTUwZjY5MzM1ZGQ4ZGYxZTBhMzY0YmIxNmE5Y2MxNDkyMjQyZjI4ODkyMzRlZGFlNDYyODFjMDhiYWQ3MzM0ZGQzZmFlNmE3NjRlMzAwZGMwYjFjIiwibmV0d29ya0lkIjoxMDB9XQ==

[0x4007]

Please rebase to a later commit. It makes it more difficult than it needs to be when we see commits that are already merged in.

[molecula451]

if it's going to be removed i think we can leave it as a comment or add it to the readme for others dev to be aware

[Keyrxng]

I'm going to close this PR and open a fresh one

• I've built the npm module which is in it's own repo ofc so where should I PR against, will someone make a repo for it? Currently working in the browser and via jest (node) at least locally, going to publish and then use the package in the UI code

• I assume that I'll build the package but it will be hosted under @ubiquity? So for QA I'll just import my own package and then once the ubq package is published it can be swapped

[molecula451]

I've built the npm module which is in it's own repo ofc

what is your repo's link

[Keyrxng]

I've built the npm module which is in it's own repo ofc

what is your repo's link

https://github.com/Keyrxng/web3-rpc-racer/tree/master

It'll be my first NPM package, esm and cjs builds for fe and be. Everything needed exported properly ( at least locally (i don't see why tht would change pulling it from npm but yet to test that))

[molecula451]

It'll be my first NPM package, esm and cjs builds for fe and be. Everything needed exported properly ( at least locally (i don't see why tht would change pulling it from npm but yet to test that))

but looks crude, at least at first sight, you are planning to add more changes on PR opening or is ready to just PR and review?

If it's a npm package i think a good move it's first upload to npm, as npm can also be remove, for then to test as a package itself

[Keyrxng]

It'll be my first NPM package, esm and cjs builds for fe and be. Everything needed exported properly ( at least locally (i don't see why tht would change pulling it from npm but yet to test that))

but looks crude, at least at first sight, you are planning to add more changes on PR opening or is ready to just PR and review?

That's the plan once I test pulling from npm if everything works then refactor where needed

It's commonplace to have to import from the specific build dirs isn't it? So running jest I'm importing diretly from the cjs module and in the UI importing directly from the esm one

If it's a npm package i think a good move it's first upload to npm, as npm can also be remove, for then to test as a package itself

Exactly, so my PR to the UI code will be removing the logic and adding my test package which can be replaced when the UBQ one is hosted? or the pr will prove it works and the ubq can be published and I'll swap them before merge

[molecula451]

That's the plan once I test pulling from npm if everything works then refactor where needed

It's commonplace to have to import from the specific build dirs isn't it? So running jest I'm importing diretly from the cjs module and in the UI importing directly from the esm one

I think you are in route, yes, perhaps first local testing with npm link

Context: https://chat.openai.com/share/92e44b12-cb21-42a1-a2cc-b3deb5c0909f

but if you going to close this PR then open an issue where you could add more context

[Keyrxng]

That's the plan once I test pulling from npm if everything works then refactor where needed
It's commonplace to have to import from the specific build dirs isn't it? So running jest I'm importing diretly from the cjs module and in the UI importing directly from the esm one

I think you are in route, yes, perhaps first local testing with npm link

Context: https://chat.openai.com/share/92e44b12-cb21-42a1-a2cc-b3deb5c0909f

but if you going to close this PR then open an issue where you could add more context

everything working with local yarn link my friend yes

Pav changed the original spec of the issue, this is the correct place for it but there's no repo to push the code for the npm module to

[molecula451]

That's the plan once I test pulling from npm if everything works then refactor where needed
It's commonplace to have to import from the specific build dirs isn't it? So running jest I'm importing diretly from the cjs module and in the UI importing directly from the esm one

I think you are in route, yes, perhaps first local testing with npm link
Context: https://chat.openai.com/share/92e44b12-cb21-42a1-a2cc-b3deb5c0909f
but if you going to close this PR then open an issue where you could add more context

everything working with local yarn link my friend yes

Pav changed the original spec of the issue, this is the correct place for it but there's no repo to push the code for the npm module to

so you're plan it's to PR a fresh ubq-repo for the npm package to then add more changes + submit to the npm repositories?

[Keyrxng]

I'll test npm before I open the new PR but if you could create a repo for me to fork and port the code into that would be sweet

[molecula451]

I'll test npm before I open the new PR but if you could create a repo for me to fork and port the code into that would be sweet

send the PR against this branch only https://github.com/ubiquity/web3-rpc-racer/tree/web3-rpc-racer-npm-branch and open an issue only to add more context

I'm going to close this PR and open a fresh one

closing now