It was 22 May 2010, when Laszlo Hanyecz, a programmer, made history by buying two pizzas for cryptocurrency. Happy Day-It-All-Started!

P.S: our sticker pack in telegram https://t.me/addstickers/Cellmunk2

For those who missed our AMA session on 18/05/23, or want to review, here's a full transcript including mainnet roadmap news, plans, and answers to all your questions.

You can also go back and watch the recording at any time on our YouTube.

#AMA_cellframe

🏅PancakeSwap V3 staking is available for CELL/BNB, CELL/BUSD, CELL/DAI, CELL/USDT pairs on https://stake.cellframe.net

The rewards will be 0.5M for the CELL/BNB pair pool and 0.2M for the CELL/BUSD, CELL/DAI and CELL/USDT pools for the first year of staking.

#stake_cellframe #cellframe_news #staking

During the AMA session we showed an updated roadmap to keep you informed about the mainnet development process. If you missed this information, here it is again 👉

#cellframe_news

🧩Cellframe SDK and Cellframe Node Changelog

Fixed/Removed:

✅ Resolved an issue with long Proof-of-Authority (PoA) rounds.
✅ Eliminated the memory leak that occurred when using the cellframe-node-cli command 'tx_history -net Backbone -w '.
✅ Addressed a bug that caused the limit of allowed groups in GDB to be exceeded.
✅ Fixed a bug where the commission was incorrectly deducted from delegated mCELL tokens instead of CELL in transactions.
✅ Resolved a crash that occurred when encountering emission files with damaged tsd sections.

Improved/Reworked:

✅ Updated the table naming logic in GDB to overwrite the table name when new signers appear.
✅ Integrated all changes from the master branch into the release candidate, ensuring the utilization of valuable developments from the master branch in the future mainnet.

#cellframe_news

👆Cellframe Mainnet Release Candidate test results

1️⃣ 10 community validators are currently participating in the tests

2️⃣ 49 bugs fixed

🔧 All identified damage to the integrity of the memory has been eliminated, the operation of the node has become more stable.
🔧 Fixed key re-delegation bug, due to which, when re-delegating a key, the masternode disappeared from the nodelist and could not receive packets from other masternodes.
🔧 Eliminated node freezes while waiting for the completion of the operation in the blockchain database. Now transactions in the Raiden and Riemann networks have accelerated.
🔧 Fixed a bug when loading keys from the database, due to which the node was in the auto-restart state and could not start due to a segfault. The crash has been fixed and loading from GDB now works correctly.
🔧 Fixed work of commands: ledger tx -all -net , mempool_list -addr.
🔧 Fixed non-working transmission of large stream packets. Now the voting for blocks of large sizes passes successfully, and they get onto the chains.
🔧 Fixed a bug that caused the node to freeze when trying to install a stream with root nodes. Now the node does not freeze even if it fails to successfully accept incoming connections.
🔧 Now the token ticker for transactions in the mempool is indicated in all transactions.
🔧 Fixed a bug in the ledger with determining the ticker of the delegated token.
🔧Fixed master node crashes in the Raiden network
🔧 Balances are no longer lost when switching to a new staking mechanism.
🔧 Fixed a problem with the command to check the ability of a node to become a validator: now the AUTO_PROC parameter is processed correctly.

3️⃣ New features and improvements:

✅ The speed of transaction processing in RC networks has increased.
✅ The network fee has been tested and works: now network taxes are deducted from each transaction in the network to the network administrator's wallet.
✅ Added version control of the consensus protocol. Thus, when an important update appears on the network, only masternodes that have updated to the required version will participate in the consensus.
✅ A new staking mechanism has been implemented and the staking functionality has been refactored.
✅ Enhanced database protection.
✅ Implemented auto-deployment of RC nodes in Raiden and Riemann networks.
✅ A script was written for auto-updating RC nodes of beta testers.

#cellframe_news

❓If I want to run a master node, do I need a static or dynamic IP address? What happens if there’s a network outage or a change of IP address?

Dmitriy Gerasimov, CEO and CTO of Cellframe Network: ‌"You can update your IP address in the node list, but it’s better to have a static address. A change in the node address shouldn’t affect the functioning of the node; your identity is based on your key. But it should be predictable.

If you get disconnected from the internet, then that’s a problem, but it’s OK within limits. We’re now trying to improve the fault tolerance of our consensus algorithm. We don’t want to go the route of slashes for those who do not participate in consensus sometimes. We want people to be able to run a node using a basic home internet connection".

#cellframe_technology

The mainnet development process is going strong 🧑‍💻👩‍💻 To show off our development progress visually, we can show you this table with data on commits in the gitlab 18/05/23-25/05/23

#cellframe_news

❓Can Cellframe technology provide quantum resistance protection for other L1s and offer “quantum protection as a service”?

Dmitriy Gerasimov, CEO of Cellframe Network: «Yes, we can offer such service, but this service can work only if it is based on our protocols or on our signatures. So, if other L1 protocols will not use our protocol, we cannot protect it. Protection appears when the project starts to use post-quantum encryption. If it doesn't, we can't protect it. If it does, it could be provided as a service».

#cellframe_technology

❗There was a Flash Loan hack, 245 BNB was withdrawn from the Pancake v2 pool. Our team are already working on eliminating the consequences of hacking and preventing new ones.

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."