final tweet on the matter and will be back at grinding: - a lot of people told us that we should not have given them the attention and rewarded them for their bad behavior. but it is something that we should highlight and it is just not cool. - they doubled down on using their misleading data (again, they are using an outdated binary) as “Jupiter”. how can you call something “Jupiter” when we the actual Jupiter don’t even know how you come up with that data? so, here are the 5 facts about them: 1. ghosted us when we tried to discuss about the matter privately. 2. doubled down on using misleading self simulated data on a sunsetted binary to continue misleading users. 3. using our hard earned brand to continue misleading their users, refused/ignored our request to correct the router name. 4. taking advantage of other’s APIs and refusing to share theirs, violating the reciprocity clause in our T&C. 5. leveraging our binary that was built for high frequency traders/oracle providers to harm our brand/reputation. again, to reiterate 2 simple things we try to ask them to do: 1. rename their the misleading “Jupiter” on their UI to “Métis Binary” since they are using the sunsetted binary and it’s not Jupiter. 2. share the API with us as highlighted in the reciprocity policy in our T&C. we have been working relentlessly over the past 5 years to build the “Jupiter” brand across different products and to contribute the free binary for the solana ecosystem to use. when we decided to pause the update on the binary (partially to stop bad player like them to exploit us), i personally had to take a lot of abuse for it (we are still trying to figure a way to continue offering the free binary without bad player like them to use it to mislead). obviously we are not perfect. we also received some feedback from some of the ecosystem players on some of the things that we can improve. and i want to address them here: - gatekeeping new AMM to be integrated into the router. there are a few reasons why integration has been slow in the past few months but now we have made many improvements both on the routing side and the resource side to accelerate this. - doubling down on making “executed price” better, it’s easy to make “quote price” look good but within the few seconds from seeing “quote price” to landing the “executed price”, many things (liquidity, price, etc) can change and affect the “executed price” badly. moving forward: other than the ultra v3 announcement last week, in next few week, we will share more on what the team has been working on. can’t wait! thanks @retiredchaddev for pointing out how we can improve.