-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Levana Geoblocked Request is not cached locally [200 USDC Reward!] #3356
Comments
I'm not sure if this can be really implemented. How would the browser know the current IP? To go by location, you'd need to ask for location permissions, but that is based on the user's consent only. |
@UkuLoskit you could use something like @UkuLoskit how about this, could you run some benchmarking between |
Very simple benchmark:
I intentionally did not use something like wrk or ab, so as to replicate making a request to new connection on initial page load (TCP handshake, no keepalive). The results are comparable (geoblock is slightly faster), so there is not time to be saved by making this extra request. |
@UkuLoskit I missed this. Thanks for doing the research. If you message finance@osmosis.team they can help with the bounty |
π Bug Bounty: Tree Shaking Optimization Needed! π οΈ
Reward: π 200 USDC π
We are thrilled to announce a special bug bounty for proficient third-party developers! This is an opportunity to showcase your expertise, make a significant impact, and earn a substantial reward.
Issue Description π
Cache Levana Geoblocking Request
Current Behavior β
Try refreshing the frontend a few times with the cache enabled. You will see that the levana geoblocked request is not cached, and is remade on every request. This should ideally hit a local cache for the same input country code if you are coming from the same IP.
Expected Behavior π‘
On page refresh from the same IP address, the levana geoblocking request should not be rerun but instead be fetched from the cache
Requirements for the Bounty π
Submit a pull request with a verified solution to optimize tree shaking.
Demonstrate a measurable decrease in the bundle size as a result of your optimization.
Ensure the fix does not introduce any new bugs or vulnerabilities.
Adhere to our project's coding style and contribution guidelines.
Your solution will undergo a thorough review by our team, and the bounty will be awarded upon approval.
How to Claim Your Bounty π°
Fork our repository.
Create a new branch dedicated to your optimization fix.
Submit a pull request to our main branch with comprehensive details of your optimization strategy and evidence of the reduced bundle size.
Upon review and approval, the 200 USDC will be transferred to your wallet.
Please Note: All bounty claimants must undergo a KYC (Know Your Customer) process with our finance team to receive the reward. This is a mandatory step to ensure compliance with financial regulations.
We eagerly await your innovative solutions and thank you for contributing to the efficiency and performance of our project!
The text was updated successfully, but these errors were encountered: