Announcement: The future of automated investing is here →
It’s been a little over a week since we opened our beta to the public, and we’ve been working hard to address all the feedback and bugs that have come up. In this document, we outline all the changes we’ve made over the past week to the source code.
We’ve fixed several bugs, and prioritized many patches through the rest of the month. We appreciate all the feedback we’ve received from the community, and we’re committed to making sure that SW DAO’s user experience is the best possible experience for everyone!
We know there are still some bugs out there, and we appreciate everyone’s patience as we work through them!
We made a number of modifications to our dApp front end and back end from June 6th to June 14th. Our change log includes all the specific lines of code that were modified and pushed on our public deployment.
These changes include:
The 0x API typically only works with the most up-to-date on-chain data. Requesting historical prices is necessary for building out charts, and finding changes over time. Our in-house 0x API now has the ability to request prices for any coin, at any point in time, as long as it existed within a common liquidity pool.
24h Price change and current price now rely on live on-chain data.
Live Price change data now rely on our in-house 0x API for better performance and user experience.
OpenGraph, and partial Twitter card support. Small changes to the text.
All-in-one Docker file created for the in-house 0x API. Makes it play nice with Google Cloud, and increases portability.
Moved the Set allocations chart to a more prominent location.
Added live “Total supply”, and “market cap” on-chain data as it’s dynamically set for the TokenSets
Redundant calls were removed, and the request throttle was increased for more bandwidth.
Bug Fix for not correctly displaying 24h % change on the Product details page.
In-house 0x API optimization to avoid overloading RPC nodes.
Research into restoring the “portfolio” page, and minor fixes.
0x now automatically retries failed RPC calls.
Request throttle was increased for more bandwidth.
Settled on Alchemy as our node provider, and made adjustments to maximize compatibility with their custom implementations.
Our developers are confident that they can make the following changes over the next two weeks:
These modifications will help us better serve our clients and provide them with a more efficient experience. Thank you for your patience as we continue to work on improving our platform.
Sign up for insights on the crypto markets, delivered straight from our trading desk.