Vertical Carousel

[pbkompasz]

Resolves #196

[ubiquity-os-deployer]

5109769

fe37d8d

[github-actions]

Preview Deployment
5109769f05fffd3655e513f5a1556ec742ea0624

[Keyrxng]

@pbkompasz is this ready for review or are still to make changes?

[pbkompasz]

@Keyrxng I have to look over it again. I will let you know when it's ready.

[Keyrxng]

No worries, thanks

[pbkompasz]

@Keyrxng It's ready.

[rndquu]

There's smth strange with URLs, there're js objects and undefined values in href attribute

[pbkompasz]

@rndquu So both of those issues come from the @ubiquity-dao/rpc-handler package. There is also another issue that I ran into where the getFastestRpcProvider fails to create a provider.
Is there a way for me to take a look at the codebase? I cannot seem to find a repo only the npm package.
These bugs are also present in production

[0x4007]

I'm going to be migrating it soon to a different RPC manager. I'm still just finalizing it. You're welcome to give it a try since I'll probably need at least a few more days to get around to integrating it into this codebase. My plan was to manually copy and paste the essential files here but soon create a new npm module.

[Keyrxng]

If we standardized using blockscan.com/ instead of trying to pull explorers based on network, these href obj issues would be resolved. networks like 31337 etc may not have explorer/chains listed (even in rpc-handler v1.3 with the thousands of collected explorers it has collected). We have already relied on blockscan and it's proven v useful as it supports all 20+ Permit2 networks that we use, since we only support Permit2 networks anyway.

functions likes getNetworkExplorer() etc should just be www.blockscan.com/ not explorers[net] ?? "www.blockscan.com/"