zZangzZang

As we approach $250,000 in total platform volume just 7 days into our open Beta, we want to prioritize our commitment to the community and ecosystem that we are building. With that, we have begun our revenue powered buy-backs. We have high hopes in regards to creating meaningful platform incentives, rewarding beta users, and creating an ecosystem where every user feels valued as we would not be here without them. We look to continue utilizing our platform revenue to provide value to our users and supporters. Thank you to all users that have provided feedback, support, and encouragement. We look forward to delivering the best product possible! More to come! $Polyblock

As promised, I quit my job. I’m dedicated to making this work. In the last 48 hours, we’ve been grinding non stop. I’m going to keep giving you guys these frequent updates as I know you like to know what progress is being made and it helps us stay accountable for the progress we make. Between the two of us, we’ve had around 10 hours sleep and a LOT of caffeine over the past couple of days. B has been staring at the Auto Trader data for past trades across all timeframes and assets and identified some golden patterns where our win rates are consistent and high (60-75% with 200-300% profit factors) along with looking at the same consistencies across losses. Using this data, we now direct Claude not to trade in specific situations which almost always result in a loss, which should increase win rate. From looking at all of our stored order book history and comparing it to our previous entry prices, Claude found significant areas where we can place our buy orders at lower prices, which means we now acquire more shares for the same price, increasing profit margins for every trade. Our win rate has increased since applying these changes, but of course we need more data to be sure. Claude now has access to every trade we’ve ever made too, and heavily considers past performance in the same conditions. It won’t take the trade if the win rate is low for previous trades with the same market conditions. As mentioned in the quoted post below, my number one priority has been workflow between us two devs and ensuring the platform’s foundation is built for sustainability. We didn’t have either of these locked in 12 hours ago. Since then, we’ve changed our system to ensure we backup every single change and can both work on implementing new functions or fixing bugs at the same time. This has already significantly improved our output. A common problem for every developer is that when we make one fix, it breaks something else. With this new system, we back up our server after every change and can easily revert back to previous logic with the click of a button and then re-attempt the fix, making sure we don’t break a function that is responsible for important processes on the server. This will also save us hours of work when something breaks that worked previously. We had a major problem with our server load and CPU usage causing the server to crash, restart and completely shut down multiple times per day, you may have noticed prices not showing or markets not loading for short periods of time. We were previously manually restarting the server as a temporary fix while we had other bugs to iron out. Personally, i’ve spent the past 6-10 hours really digging into the code, core functions and systems that run frequently to find the root cause. I’m confident that our server now operates how it should. We’ll need to continue monitoring in order to ensure we have completely resolved the problem but we’ve had 0 restarts in the last 3 hours and our metrics look much better. As we’ve been working through this, we’ve been responding to you guys reaching out in our support chat whenever we get a moment. We’re happy to help with anything you need, so feel free to reach out. We’ll implement email notifications soon so you don’t miss a reply from us. More on this soon. We had a bug with 15m markets disappearing in the last 5 minutes of the market. This has been resolved now. Also made some minor improvements to the home page, making it more attractive. My next concern is the information we show to users in analytics and trade history. We are aware everyone is seeing incorrect statistics and we have identified that the root cause of this issue is likely unclosed trades. We’ll look at automated processes that close every position, updating all data correctly. Please remember that we didn’t even have a working product 9 days ago when the token was launched. We’ve many sleepless nights since launch date, dedicated every minute of every day to fast forward our development and bring you something we are proud of. So far we’ve accomplished that. If you have any issues, please open a ticket in our docs page where you can chat directly with me while I resolve your issue for you. Thank you for your endless support! We’re so close to being able to focus on UI and new features. I’m excited for what the future holds!

100%, it's on the list! We have a to-do list we reference everyday. It's there, and don't worry, the buyback funds are safe and ready to blast when the setup is complete. This takes a little extra development to make it automatic when bridging from Polygon to Solana and then buying $Polyblock.

Here’s the second medium-severity issue flagged in the okxlabs/DEX-Router-Solana-V1 audit. Unwrap misuse inside the wrap_unwrap_v3.rs flow. This pattern shows repeated unchecked operations inside a core instruction. If any of these values come in malformed or unexpected, the program can panic, halt execution, or create inconsistent account states. These are the kinds of logic paths Chain-Fox is designed to surface early — before they turn into outages or exploitable behavior.