CompX

@nextblockexpo gold partner @sealedchannel presenting their post quantum secure communication suite.... looks like it is based on #Algorand .

@CometaHub Sames. Welcome back.

@Compxlabs deprecating fast, shipping faster. respect 🤝

Lending updates: After a small configuration issue was found with the original v2 contracts for lending we have deployed new v3 contracts and deprecated the old ones. $wBTC and $wETH are deprecated and no longer on the UI. $USDC is marked deprecated as it still contains deposits. Please move all deposits to v3 markets. Additionally, welcome $GOLD and $SILVER markets!

@FlawdaFrog Yeah, token streams are still available on v1 - v1.compx.io and they’ll be migrated over to v2 by the end of the month

@Compxlabs I had some CompX tokens locked up before the transition from v1 to v2. Will these tokens be returned?

@BonezAlgo @CometaHub DM sent, all sorted, pool is live

If no answer im more than sad 🫤 @CometaHub @Compxlabs cmon algorand community i should have to pay to be noticed. Both LP staking needs approval.

Now that the first phase of CompX v2 is out we're looking at the next pieces of the puzzle. clAMM - The beta for the clAMM has had a UI update on testnet - we're still a few days from operational testing but you can start to see how it's coming together. Stable.X - Our new stablecoin protocol is taking a pivot into the agentic economy first with a big focus on automnomous agents for both stability and utility. We'll be updating both of these features rapidly, so please do check them out.

CompX V2 is live on mainnet! 1. Lending for $wBTC, $wETH and $USDC 2. Permissionless staking pools 3. Repayment pools for those affected by the Orbital exploit. We've got a 10M $COMPX LP staking pool for @tinymanorg $COMPX / $ALGO LP for starters from @Xxiled1 Repayment pools are still being added to in terms of final numbers and users, with the majority of $ALGO staking still to be added this week. First payments will be out next week. Next up: clAMM and Governance V3

Going to be taking an extra few days to get CompX v2 full operational. Lending and staking are ready but some refinements still needed for repayments.

Mainnet inbound! Tomorrow we’ll start to deploy our new contracts and v2 platform to mainnet. Lots of work this past month on security, automated maintenance and fail safes. CompX V2 will launch with lensing for wBTC, wETH and USDC with Gold and Silver to come. Fully Permissionless staking will go online at the same time allowing any user to create their own single or LP token staking pools. Repayment pools will brought online allowing for repayment overtime for users directly affected by the Orbital exploit last month. 70% of fees from CompX V2 will go directly to repayment pools and you’ll be able to track progress of repayments on our public dashboards. We’ll also be pushing our current build of the clAMM to testnet which you’ll be able to interact with and give feedback on. We can’t wait to get back to mainnet.

CompX V2 on Testnet: v2.compx.io

CompX V2 is now live on Testnet. This marks a new era for CompX focussed on security and sustainability. This current version v0.1 features two main DeFi primitives. Lending - Our Orbital lending contracts have been re-worked. Deposits, borrowing, liquidations and buyouts remain the same but migrations, single points of admin failure have been removed. No single admin account can access user funds, each contract has 3 admin wallets - for parameter updates, for withdrawing platform fees and for initialisation. Permissionless Staking - What was going to be our platform, Delta, has been rolled into the main CompX app. Users can create staking pools for single or LP tokens, add rewards and set start and end dates. We've kept things with the staking pools as simple as possible. Each pool has 2 admin wallets - one is the creator who can add/top up rewards and the second is for CompX to withdraw platform fees. We've completely redone the UI and gone with a more serious and modern feel while having the same responsive UX as we had in Orbital. The phases: 0.1: Staking and Lending 0.2: Repayment pools for users affected by the Orbital Lending exploit. -- Push to Mainnet -- 0.3: Governance V3 0.4: Payments and token streams - taking advantage of our upgraded Waypoint codebase. -- Push to Mainnet -- 0.5: clAMM - a new liquidity source for Algorand. -- Push to Mainnet -- 0.6: Stable.X - A massive upgrade from xUSD with price stabilisation via redemptions - USD.X, GBP.X and EURO.X -- Push to Mainnet -- With the above plan we hope to regain trust, provide best in class DeFi on Algorand and make our users whole. CompX V2 on testnet now - link below 👇

V2 coming along well. Will be available testing soon.

Working on our new CompX V2 - we expect testnet version for lending and staking available end of this week. Repayment contracts are underway and will be available for testing the week after. clAMM design is complete and will begin build - contracts and UI - at the end of this month with a release in March/April

We are currently working on a plan for moving forward - including repayment for those that were affected by the issues this past Friday on Orbital. In the immediate term we're working to clean up the core application : We will be turning rewards off for all staking pools. All pools can be withdrawn from barring the ALGO pool - for simplicity the ALGO pool will be removed from the UI. We ask all users in those pools to remove their stake - details of the stakers in the cALGO pool have already been noted.

An update regarding the exploit on Orbital Lending. - Details have been passed to Cloudflare and Indonesian police - Reports to local police here in the UK will be done tomorrow. - Huge thanks to @d13_co for helping compile the data for these reports. - We remain hopeful that we can recover the stolen funds. In the meantime, and if that were not to be successful we at CompX are committed to ensuring that all tokens stolen from depositors are restored back to their rightful owners. We have all accounts affected and the exact amounts deposited and in the coming weeks we will present a solution to pay back the lost tokens over time. We are still here, we will make this right.

To the owner of A42D42ZGP73HHZR3DTF6DBYW2GBAANMIU7232IB6T4GD3ODJ545JHIFQTU Kamu lupa menggunakan proxy pada transaksi pertamamu. Kamu bisa menyimpan 10% dan hidup tenang, atau menyimpan semuanya di penjara. Kami akan menunggu 1 jam sebelum pergi ke Bareskrim dan Telkom. Jangan hancurkan masa depanmu. We have your IP details - please get in touch within the next hour. We will do what we can to get our user funds returned.

Orbital Update The cause of the of the issue: We had to build a small service to migrate the box data for our ALGO market to the new contract as there were over 500 entries. The admin account for Orbital is the only account that can do that so we used that in our backend code to make the transactions. To do that, the seed phrase is added to .env file for the application - this file is only stored locally and does not go into GitHub or other source control. This pattern is used for other sensitive information. On our hosting platform these values are encrypted. What happened today was purely human error, the seed phrase was accidentally added to the env.example file in error - this was subsequently not deleted, and then subsequently checked in to GitHub where it was then publicly viewable. There's no excuse or additional reasoning that can be given - a mistake, a very costly mistake. We understand there will be anger, disappointment and questions you may all have - @Xxiled1 will be in the discord to answer any you may have at this time. Again, our absolute and sincerest apologies to those affected.

Important Update. At 9.26pm (GMT) this evening the admin account for Orbital markets was rekeyed to the account: A42D42ZGP73HHZR3DTF6DBYW2GBAANMIU7232IB6T4GD3ODJ545JHIFQTU This account then used the admin functions within the Orbital markets to set the contracts into migration mode and pull the funds out of those contracts - subsequently selling them on the market via this address: GLVIXLGCDDDFHS57A6NLVICI3QJVWRAI6GO3KVF74YDOWSMY3O6KCBAIWU We are deeply sorry to users affected by this, and are working to look to how we can remedy the situation. We are currently looking into how this happened and will update you all as soon as we know more.