UST1CMM.com stats after second day!
2.7 million USTC sent to the CMM Treasury.
2.1 million USTR minted.
279 swaps used a referral code.
43 referral codes have been used at least once.
Dont forget to check the leaderboard to see the top performing referral codes! ust1cmm.com/referral

Its been about a month since I worked on the CL8Y Bridge, and its critical for the next phase of CL8Y governance, USTR, and our gamefi plans. So, Im doing a code review and a gap analysis to see where we're at and what realistic schedule can be made to finally get the release set. We had testnet transactions working before I moved to other work, so I expect a positive outcome.

Additionally, I will be releasing a new security module for CL8Y to track high risk wallets, especially exchange wallets, and flag wallets engaged in suspicious behavior with high risk wallets. When the risk thresholds are triggered, this will prevent hackers or malicious bots from using CL8Y on exchanges to manipulate the markets or dump.

RiskFlagAuto is now deployed! It will be automatically flagging high risk transactions associated with exchange accounts holding CL8Y, as historically these have been the target of 2 hacks in just the 9 months of CL8Y's history. If you frequently withdraw CL8Y from exchange accounts, drop me a message & Ill make sure you're whitelisted. Dont worry if you get flagged - its just a freeze, so once the transaction passes review, the CL8Y will be released as its solely to mitigate malicious bot transactions, laundering, hackers, and other malicious activity. Currently its managed by the CZODIAC multisig, and once CL8Y's governance nodes are live they will also take over this and the other Guardian Modules that are currently active.

Im working on tooling to reduce my AI inference costs and increase speed by batching coding tasks to my GPU and only using SOTA models for architecture, planning, and work assignment. The tool is called WorkSplit, I've spent 2 days and appears to be able to get at least a 50% reduction in cost but has some bugs. Im going to give this effort until end of January, if I can get it working by then we will be able to have a more aggressive release schedule without needing funding. However this is high risk tech because of how new it is, which is why if I dont get it fully functional by end of month I will go back to my legacy workflow (mid tier models + manual coding) although it takes about 10x longer.

I've finished WorkSplit, which is a way to reduce ai inference cost if you have access to a powerful local llm via Ollama. I'll be using this for future code updates, it can have substantial cost reductions for complex projects where lots of files need to be created or edited. However, for very simple tasks, it is more expensive. And, currently the only model reliably able to run WorkSplit consistently is Opus 4.5. If you try it out, lmk if you run into any issues! You will need to already have ollama and an llm model, ideally thinking with 32k context window, available (tho smaller models might work). https://github.com/PlasticDigits/WorkSplit

P2B has informed us they will not allow cl8y withdrawals unless we compensate them 99,526 CL8Y for their loss in the hack. Accordingly, please prepare for reduced market making support and potential delisting.

I am also investigating Ascendex regarding a lack of 1:1 cl8y backing of tokens on their exchange. Please be prepared for issues there, but unlike p2b withdrawals are active.

MasterChef lens for better bot discovery of TidalDex farms has been deployed to 0x8ec52A7DC3cFD72f271357c7Dfbe22EEABc07088. This will empower bots to have a standard interface for interacting with the farms and discover them via onchain interface searches.

CL8Y whitepaper updated to better cover our ecosystem plans, as our community is moving away from being just a memecoin. https://cl8y.com/cl8y_whitepaper

https://fund.cl8y.com will be raising privately via donations to fund my AI Dev Cluster. This will massively accelerate our roadmap and development timeline. Participation is restricted to the CL8Y Strategy Group due to regulatory compliance.

I have strong suspiciouns and circumstantial evidence that AscendEX is not backing CL8Y 1:1 on their exchange, based on onchain data. If you are holding CL8Y on AscendEX, I recommend you either withdraw or sell it immediately.

First private funding tranche for AI Dev Cluster is complete. Thank you everyone who participated, this is greatly going to accelerate the release of new dapps!

https://ust1cmm.com/treasury is now live, where you can see USTR issuance, Treasury assets, contract address, and ratios.

End to End automated testing for the CL8Y bridge is a critical feature, because it allows LLM to write scripts to check everything works as expected - and write red team tests that attempt to hack the bridge, including via fuzz tests that try thousands of different attack values. To do so requires a fast, terraclassic image that can be quickly turned on/off. I've built it today and released at github.com/PlasticDigits/localterra-cl8y. You can also see how its currently being user in the cl8y-bridge-monorepo on my github.

E2E tests are now working on local devnet for transfers between TerraClassic<>EVM, with both the Operator service and the Canceler service correctly releasing valid transfers and identifying invalid ones. Next steps include expanding the E2E tests to more scenarios, improved insight via Prometheus and Grafana, better dashboards. That will be followed by red team tests, internal audits, and finally testnet release.

Thanks to USTRIX for the generous donation! To show their support for USTR, the USTRIX community has donated 2% of the USTRIX supply to the UST1CMM.com/treasury. https://x.com/BurnixToken/status/2018645637160677855

E2E testing for local devnet terraclassic<>evm transfers has been migrated from scripts to Rust, due to increasing complexity as a lot of suprising technical issues have been uncovered during e2e testing, requiring more integration tests especially for crosschain hashing. The results have been greatly sped up e2e testing and rapid discovery of new bugs & issues on devnet.

More issues found and fixed during E2E testing for thr CL8Y bridge, specifically for the operator detecting and activating transfers.

On our CL8Y Bridge, while we got ahead of schedule during implementation, testing and integration is behind schedule, but not yet over our token budget. Im still finding and fixing bugs in E2E, if not complete today I'll take a more efficient approach by reducing our feature set and using more manual testing workflows. However, its much, much better to get full E2E as it allows any future updates (such as cl8y bridge v2, which will include things like automatic token swaps and registration) to be implemented much faster without compromising security.

A major challenge found in E2E testing is proper crosschain address encoding. Previously, we were using ASCII encoding as a simple strategy, however it quickly runs into issues due to the byte size in storage causing a wide variety of errors. I'm migrating our bridge to instead have a address encoding implementation that can easily handle any chain.

I uncovered that multichain library is necessary, and that there are not good existing libraries for multichain handling both terraclassic and evm - or in fact generally theres a lack of multichain libraries. Since we have operators, cancelers, and e2e tests all of which are packages that need to integrate with multichain, I've added a mulltichain-rs package to the cl8y bridge, greatly improving code quality and consistency in behavior across the project. This sets us back 1-2 days for the CL8Y Bridge V1 release, but is a key technical discovery.