Worklog. January results

Hey everyone!

In January, we actively worked on expanding our platform’s functionality. Now, we’re excited to share updates on our websites, improvements in Cellframe Dashboard, and much more. Read on for all the details in our latest digest!

Web Development

Cellframe Explorer

We’ve added the CF-20 Token Explorer page to the Cellframe Explorer website! Now, you can quickly and conveniently get all the necessary information about CELL, KEL, QEVM, NYS, and CPUNK tokens in the native Backbone and KelVPN networks. On the new page, you’ll find data on Total Supply, Circulating Supply, the number of holders, and even see who is in the top-10 holders of each token.

Cellframe Network

Recently, the Cellframe ecosystem was expanded with a new project called QEVM, so data about it has been added to the partner page on our website. QEVM (Quantum Ethereum Virtual Machine) combines quantum-resistant blockchain technologies from Cellframe with the EVM infrastructure for deploying smart contracts. You can find more details on the project’s website.

For user convenience, we added a Shop button to the homepage and header of the website. With one click, you can visit our store to order hardware nodes and our merchandise.

Cellframe Staking

In January, we stopped accepting new LP stakes on the Cellframe staking site. This decision was made because we need to reduce the number of quantum-unsafe CELL tokens in the era of growing quantum technology development. Our team is now working on developing a quantum-resistant mechanism for creating LP tokens on the CF-20 platform.

The community vote on changing the reward distribution between stakers and validators has concluded on the Cellframe voting website. As a result, 80% of the rewards will go to validators, while 20% will be allocated to participants of the staking program. This option was supported by the majority of voters, receiving 60.70% of the total vote weight.

Cellframe Dashboard

The Remote mode will soon be available in Cellframe Dashboard, allowing users to operate the application without running a local node or downloading the full blockchain copy. To send transactions and interact with networks, the application will connect to remote public nodes. These nodes will be grouped into a special cluster, with a DNS load balancer distributing the load among them. This will reduce the technical requirements for devices and mark an important step toward developing the mobile version. If you already have both the Cellframe node and Dashboard installed, you will be able to switch between the classic and Remote modes depending on your needs. Beta testing will begin soon — stay tuned for updates.

As part of the Remote mode development, the team has implemented a set of new managers for handling wallets, networks, fees, and transactions, allowing the Dashboard’s operation mode to be changed on the fly.

Additionally, the team has added the ability to connect to any other node via the RPC protocol. This means that any masternode holder will be able to connect the Dashboard to their node. To do so, they simply need to configure the masternode to accept remote requests and enter the connection details in the corresponding field on the Settings tab in the Dashboard.

Beyond the new mode development, in January, we migrated the DEX tab to the JSON-RPC protocol, improving the application’s performance. Alongside the protocol transition, we also refactored the module responsible for all DEX operations, simplifying and optimizing its functionality.

For better usability, wallet addresses are now displayed in full.

Finally, our developers resolved a bug causing incorrect network display in the Masternode tab, where networks persisted even after node reinstallation. We also fixed an issue with infinite data loading in the DEX.

Cellframe Node

In January, we continued developing new functionality for Cellframe Node.

First, we developed a composition manager, optimizing the hardfork process. With its help, we have already adjusted the voting hardfork algorithm by introducing a new aggregation callback prototype.

As part of our work on new functionality, we implemented signature verification for the service state datum. This mechanism prevents incorrect data from entering the mempool during hardforks and eliminates the possibility of data substitution.

We also improved the tx_create_json function. It now supports passing JSON strings via RPC without escaping quotes, simplifying data processing.

In the near future, our team will begin debugging all these updates in the build.

Python Plugins

This month, we continued improving Python plugins — separate modules that extend the platform's functionality without altering the core code.

We optimized the reward calculation process for staking on a specific date, based on the reward pool.

At the same time, testing of the new staking plugin is ongoing. We are carefully comparing emission results with data from the old plugin and the planned reward accruals. This approach helps us identify potential discrepancies in the updated mechanism before it is implemented.

Finally, we developed a new data visualization module. With this tool, it will be possible to create graphs that reflect the reward accrual history for specific stakes.

Tech Writing

Our team has released a series of useful and informative materials to help developers and users better navigate our ecosystem.

In January, we prepared a brief description of fees in Cellframe Network and explained how to find their current values using the CLI command.

For your convenience, we added a description of the automatic script for setting up a masternode on Linux, as well as a comprehensive guide on all masternode setup options.

We also published a short article covering the process of creating an order for m-token delegation. On our platform, token delegation is available in different formats:

● If you don't have m-tokens but have suitable equipment to launch a masternode, you can open and fulfill an order that allows you to launch a masternode with tokens delegated from other users. In this case, you'll receive a portion of the profit from the masternode's operation.

● If you have m-tokens but don't have equipment to launch a masternode, you can create an order to delegate your m-tokens on the platform, offering other users the chance to run a masternode on their equipment. When the masternode is launched and running, the income from it will be shared between you, as the m-token owner, and the user who launched the masternode on their equipment.

JSON-RPC is a crucial tool for remote interaction with the network's nodes, and in January, we released several manuals on how to use this protocol.

The first guide provides an overview of JSON technology and explains how to access nodes remotely using JSON-RPC. The second material describes the JSON format for different types of transactions. In the third guide, we explain in detail how to sign transactions using JSON.

Our team continues working on improvements to make your experience with the platform even more comfortable. Stay tuned for updates, and you'll be the first to hear about our next achievements!