-
Notifications
You must be signed in to change notification settings - Fork 5
[BUG?] Look Into Optimizing Loading Speed for Web3 #65
Comments
@AlphaSerpentis I saw your gitcoin posts on the various page re-designs. Improving Performance
If your are interested in this improvement, I'd be happy to take ownership of it if you create a small gitcoin bounty. |
Heya! Thanks for stopping by and giving some pointers. We're actually planning to rewrite the website entirely from the ground-up soon which may or may not help in terms of performance, but helps with trying to make our frontend code easier to read and work with for future contributors. If we spot performance issues still, I'll def. consider providing a Gitcoin bounty on this |
Awesome! Thanks for getting back to me so quickly 🙏 |
No worries! If you're looking for frontend stuff, we're currently in the process of the aforementioned redesign and rewrite, so I would maybe wait until that code is pulled into this repo and decently fleshed out. I might be looking for someone familiar with ethers.js (or web3.js) since frontend is not my cup of tea, so in the future to plug the components with the web3 libraries when the redesign is complete. If you're into Solidity, v0.2 (our Venus upgrade) branch has the updated contracts that you could look through, but I'm already in the process of writing v0.3 (Earth upgrade) at its most basic framework to experiment and test with. We haven't deployed v0.2 on any prod. network due to financial constraints and technical constraints (ETH L1 too expensive, Arbitrum having timestamp inaccuracies which prevents AirSwap from operating which we depend on) If you'd like to remain communications with us, feel free to join https://discord.optional.finance |
File(s): frontend/???
Test Files Required?: No
What Testing Should Include:
Currently, it may take between 10 - 15 seconds to load the vaults completely (with 400 Mbps down). This delay is somewhat a nuisance and not ideal. Look into figuring out ways to optimize loading speeds.
The text was updated successfully, but these errors were encountered: