The reason for the hack has been found!

Cellframe CEO Dmitry Gerasimov: "The source of the problem is a smart contract that migrated the old liquidity to the new one without taking into account the changing spread between them during the migration. The scope of the attack was limited by the amount of funds in the old pool, as well as the amount of funds on the migration smart contract.

At the moment, the migration of LP pairs is stopped. New liquidity migration rules will be published soon, stay tuned."

We became co-organizers of the Non-Stop University CRYPTO.

https://nsucrypto.nsu.ru/

This is an international cryptography competition in which participants solve not only educational problems, but also work on actual problems in the realm of cryptography. A collection of scientific articles is traditionally published based on the results of the tournament. The 2023 Cryptography Competition will be the tenth in a row. It will be held online from the 15th to the 23rd of October. We will prepare several cryptographic tasks that are relevant for both Cellframe and the development of blockchain technologies in general.

Changes in the rules for migration of CELL BSC tokens:

Single migration from the old smart contract continues to work as usual. You can migrate the CELL BSC tokens here: https://migrate.cellframe.net/

LP migration will no longer be available. If you want to migrate an LP pair to a new token, you need to do it manually:

- unpair with the old token
- migrate single token
- create a new LP token

Staking in the BSC network works as usual. You can stake v2 and v3 LP tokens here: https://stake.cellframe.net/
The team recommends using the v3 protocol.

#how_to_cellframe

What is the best choice for running a masternode: Raspberry PI or VPS?

If you are only planning to use the node for transaction validation, either of these options are a safe bet. The main thing is adherence to the minimum technical requirements. Cellframe uses Proof-of-Stake consensus, meaning that the priority of the rights to confirm transactions and form blocks depends only on the size of your stake, and not on the technical characteristics of your equipment.

If you want to use the node for generating income by providing Cellframe services, various options are open to you. For example, for the ConfCall video conferencing service, network bandwidth is more important than node characteristics. Conversely, an AI platform that is intended specifically for solving training problems and running machine learning models requires substantial computing power. In this case, Raspberry PI, in which 70-80% of the chip is occupied by video cores, will be preferable to VPS.

#cellframe_technology

We continue to develop the Cellframe mainnet. To show the progress visually, we demonstrate data on commits in gitlab, which shows the number of changes in the code for the period from May 26 to June 5 for all our projects.

#stake_cellframe #cellframe_news #staking

At the request of the community, here is more information concerning the transaction we recorded on June 1st, as a result of which 245 BNB was withdrawn using a flash loan.

Generally speaking, nothing is withheld, since all information pertaining to transactions is open and accessible, but we always err on the side of security and aim for full transparency, thus we decided not to brush this under the carpet, and want to explain what exactly happened.

Flash loans are an option provided by popular DeFi protocols. It allows you to borrow cryptocurrency without collateral, but with the condition that the debt will be returned in the same transaction block. There are many cases in which funds have been withdrawn from exchanges using the Flash loan mechanism, which was designed to operate for benign purposes.

Our two tokens - the old V2 and the new V3 - were linked by one migration contract. At the same time, there was very little liquidity in the old token - this made it possible to manipulate using the flash loan function. And if it's possible to manipulate something, then for some people it would be rude not to take advantage of the situation, right?

The modus operandi is quite well-known - the smart contract did not take into account the spread between liquidities during the migration. The amount of funds in the old pool was limited, since you are actively migrating your tokens (special thanks to you for that), so the withdrawal amount was not critical for us. Although we'd be lying if we told you it was a pleasant situation...

This is the price we paid to gain valuable experience: once bitten, twice shy.

The team is still as positive as ever, and is preparing the mainnet with even more determination.

In the following posts, we will answer your most frequently asked questions, tell you about the next steps we took, reveal our roadmap to making further progress.

And next week will be our scheduled AMA session, where we usually talk about our news and progress on the way to the mainnet.

Let's stick together. Onwards and upwards!

#staking #cellframe_news

❓We continue to answer your questions. One of the most popular is about the emission of tokens, which coincided with the exploit on June 1st.

It was part of the planned emission for the team, which we spend on the development and support of the project.

❗Our tokenomics has not changed. You can find detailed information about the emission of tokens in the article https://cellframe.net/blog/Cellframe-Tokenomics/

#staking #stake_cellframe #cellframe_news

We've updated our roadmap to keep you informed about the mainnet development process 👉

#cellframe_news

Join Cellframe, as usial, on Thursday, for our AMA!

June 15, 12:30 UTC
We go live on our YouTube channel.

CEO Cellframe Dmitriy Gerasimov will talk about:

- exploit June 1
- mainnet roadmap update
- news of all our projects

Drop questions in the form or in the comments here!

#AMA_cellframe

What did the team do in the aftermath of the situation on June 1st?

Scheduled monitoring of the infofield revealed a situation labeled by the community as a "hack".

A smart contract specialist began to investigate what had happened.

We blocked migration on all sites until the details were clarified.

We removed liquidity from the LP pairs migration contract with the old token.

We put a ban on the staking of pairs with the old token.

Single migration was enabled.

With the help of QA we checked how the commission for conducting transactions is removed, and how its size is affected by the weight of the stake.

At the same time, we monitored the ongoing discussions and kept abreast of the situation in the communities.

At the same time, we got to the bottom of and laid out the scenario of user actions

Outcome:

The attack occurred due to a vulnerability in the migration of LP pairs. We subsequently disabled all features of this migration, rendering any new attack as an impossibility.

We are now finalizing the script for parsing affected wallets and preparing airdrops.

#bugs

We continue to answer questions from the community. Today we're going to focus on the marketing wallet.

The marketing wallet contained 2,000 BNB of funds that belonged to our former partners. We agreed to give them these funds in exchange for them returning all the keys to us.

Now they have the funds and we have the keys: this gives us the freedom to concentrate on the further development of the platform, which we are actively doing. If you follow our news, you will see this.

Our marketing is financed by funds raised from the additional issuing of tokens.

In addition, a 1% tax on the new token collected for the needs of the project after the completion of the active development phase, will also go towards our marketing budget.

Plus, we have a bridge fee and a tax on trading inside the Cellframe DEX.

Participate in community events, spread the word about our projects to your friends, and get ready for the launch of our mainnet!

#stake_cellframe #cellframe_bridge