AMA with Dmitry Gerasimov, July 24, 2025
Category: AMA
Hello everyone! I’m Dmitry Gerasimov, CEO of Cellframe, and here is our regular AMA session. Let’s begin with your questions.
The team recently started shipping the first Cellframe Light hardware nodes. What other versions of these devices do you plan to release?
We have some plans to release Cellframe Medium and maybe some other versions. However, Cellframe Light will be enough for most use cases. Maybe we’ll release some more powerful devices for running more than one network with a bigger load. However, after the hard fork, we expect less load from the Backbone and KelVPN networks. So Cellframe Light will be enough. Stay tuned — maybe something will change.
Is it possible to run multiple masternodes on a single Cellframe hardware node across different CF-20 networks?
Yes, it’s possible. Just pay attention to your networks’ memory requirements. This number depends. For the current moment, it should be enough for running Cellframe Backbone and KelVPN networks. All the other networks may require more memory, and even for these two networks, it is better to have more memory than Cellframe Light has. So Cellframe Light is expected to run a masternode only in the Backbone network or maybe Cellframe VPN. Other networks cannot be checked by yourself. If you want to run too many masternodes on your single device, please prepare some hardware with at least 32 GB of memory and at least 8 CPU threads.
Recently, users have been experiencing some issues when working with Cellframe applications and services. What steps is the team taking to improve UX?
I think we are talking not about UX as user experience for the interface but about user experience in general. So the issues that were faced in the last week were more related to public RPC or public API that is now used for block retrieval, transaction uploading, and mempool operations. It’s different from the option we had before. Now we have more load and need to balance it to get some health checks from the RPC nodes. So this task is the work of the back-end team, not the UI/UX team. We are doing our best to fix it as soon as possible. Just wait a little while, and we’ll fix it.
Earlier this year, the team announced the implementation of the CF-01 standard for liquidity pool tokens on the DEX. How is the progress in this direction?
It still hasn't begun. We postponed it to August. However, it’s not too much work to implement this standard. Maybe Release 6.0 will include it as well. At least I hope so.
Regarding two-level sharding: when will the work on this functionality be completed, and what stress tests or simulations do you plan to conduct to check TPS metrics and overall network stability?
About tests and simulations, they will include every imaginable test or check and will mostly focus on performance, high load, and stability as well. About our work progress, we have mostly finished the hard fork mechanism. It will be released in the near future. After this, we’ll need to do some reflection work and update our development plans. To be more exact, for the moment, I plan to finish it in about a month or two, but the timeline can change in both directions. It could be shorter or longer.
What major development goals does the team plan to achieve by the end of 2025?
As I said before, CF-01 and also CF-02 standards, and we have the most important plans for implementation like two-level sharding and native smart contracts. And some work related to the integration of other smart contract engines like QEVM and other projects we want to help. Also, we are planning to release the new Python API and binary API as well. It’s planned not for the end of the year but for the end of summer. The new API will include not only Python. I think in September we’ll release a few more APIs for Node.js, Java, .NET, and others.
Does the team have plans for additional marketing activities for when the bull run starts?
Yes, for sure. We are preparing everything for the bull run start. When it begins, we’ll start a lot of activities.
Recently, the Cellframe ecosystem has grown significantly. Projects are actively developing and showing good results. How does the Cellframe team support them? How does your collaboration work?
We help them like our colleagues. We stay in close contact, discussing the issues, trying to move forward to meet their requirements as well as those of all projects. All significant projects that build something in our ecosystem have a common Telegram group and are connected with the Cellframe team. So this is how collaboration works.
Assuming Q-day happens tomorrow, would the Cellframe blockchain in its current stage of development withstand a quantum attack and continue functioning afterward?
Yes. We are ready. Just keep in mind, CF-20 is the only protocol ready for the quantum threat. ERC-20 and BEP-20 versions of the Cellframe tokens are not quantum-safe.
Cellframe isn’t the only blockchain project claiming quantum resistance — there are others like QANplatform, QRL, Nexus, OZONE chain, Algorand, and more. What sets Cellframe apart from them? What makes your technology unique?
I can talk a lot about the difference. By the way, some of these projects are not quantum-safe, just moving toward it. So what about us: first of all, we are really quantum-safe. On the other hand, we are ready for the high load, because the next challenge after Q-day will be to handle all the quantum-protected traffic for all transactions. We are ready for this too.
How is the development of Cellframe’s auction functionality progressing?
It’s on the final stretch now. Hold on, it should be released soon.
What are the technical and financial requirements for developer teams who want to implement their projects in the Cellframe ecosystem and participate in slot auctions?
There are no requirements except one: you should have a really good idea. You should have all the skills and a team necessary for your project. In general, you could have only a single person in your company and run the project in the Cellframe ecosystem by yourself. No problem — with AI, everything is possible.
Is the team considering launching new, more advanced DeFi services? For example, liquid staking on Cellframe DEX?
Yes, we have such plans. This functionality is related to the CF-01 standard that we are preparing to release before the end of this summer or at the beginning of autumn.
Question regarding the ultra-light mode of Cellframe Wallet: Why is the HTTP protocol used for communication with RPC nodes? Are there plans to migrate to HTTPS?
We use HTTP because we don't send any private data through the RPC nodes. It’s a public service. It returns public data; it accepts data to be publicly signed transactions. We don't receive any private key or something like this. Also, about using HTTP instead of HTTPS, right now it’s done because of load balancing between nodes. However, just to make it look better, we’ll add a TLS layer, but there is no urgent requirement to do it as soon as possible. So we postponed it for a little while.
Now we are moving to the questions from the YouTube Chat.
Are marketing plans set up for auctions to onboard as many projects as possible?
Yes, we have a lot of plans.
Since each network will need its own RPC endpoint, will we be able to add custom networks to the CFWallet with name, chainID, RPC address, etc., similar to MetaMask?
It’s already possible because, by the way, networks require just the network config. It’s just a text config file. You can already put it inside the wallet config and work. Also, you can update and change its RPC address as well. Then its name and chain download by itself.
Why does the Cellframe Java SDK start to update?
It’s updated because of requirements from CEXs. They asked to add some additional functionality. Also, by the way, I can announce something: we plan to rework it completely and release Cellframe Java SDK, also .NET SDK and JavaScript SDK as well. So a lot of things are coming.
When is the hackathon?
After the slot auction launches. We are trying to connect them with our activities in October, that’s why I think it should be in September.
Considering all the progress that has been made in terms of delivery over the past year, what in your opinion explains the lack of $CELL appreciation and valuation?
It’s a common situation for all altcoins because the previous bull run hasn’t finished with an alt season. We are in a specific phase where we are accumulating and aggregating the current development efforts. A lot of people are participating in the project development for Cellframe, not all of them are ready for release. So we need to just wait until there are a lot of deliveries. When there are a lot of deliveries from ecosystem projects, we’ll have a lot of communication between projects inside the ecosystem that will add a lot of utility for CELL, which will raise its valuation, appreciation, and adoption — many things that we are waiting for.
How is the quantum narrative going generally in the world? When you started Cellframe, what did you think the narrative would be in 2025, and how is it now?
It has become more noticeable. Just a few years ago, it was a marginal topic, but now it has become mainstream.
Is there a plan to integrate more AI-specific tooling or SDKs for devs building AI x blockchain services on Cellframe?
Indeed. That’s what I’m working on. I’m working on AI tools that will be accessible for developers and will dramatically change the situation with the development of our blockchain.
Could you clarify the new roadmap? For example, the development of "smart contracts" is removed, and "Self-Developing Blockchain" is placed in the timeline.
About smart contracts, we’ll return it back. And about Self-Developing Blockchain, I think we should prepare an article later.
Can you share a bit about how the team is working with enterprises or institutions who may need quantum-safe infrastructure?
Usually, it’s routine. Sometimes we receive requests about this, mostly from our partners, and just answer some questions, maybe consulting someone who is trying to implement our cryptography primitives.
Is Cellframe considering/having thoughts on following the path of Polkadot 2.0 and JAM? Apparently, the future model is more developer-friendly, flexible, and performant?
For this, I think we’ll launch some other project, maybe it will be the relaunch of DapCash because the current version with very soft and comfortable auction rules would be very friendly for developers. It’s not as strict as Polkadot’s auctions. So I don’t think we should change the model. I’m tracking the situation — if something changes, you’ll know it. Stay tuned.
Do you see a future where CELL becomes the default infrastructure layer for governments or defense sectors?
Yes.
What's your take on QEVM?
I'm an advisor of this project, and I propose some technologies for them. This is my personal interest in it.
Are there any investment or funding plans?
We have plans to run some side projects related to Cellframe.
What kind of developer onboarding experience does Cell provide? Any upcoming hackathons, grants, or incubators to attract talented builders to the ecosystem?
Stay tuned, it will be announced.
Okay, thank you for the huge amount of questions! Thank you for all your attention! See you next time! We are CELL! We are here!
Recent news
-
Cellframe Hardware Node User Manual
23 Jul 2025
-
Cellframe Light Hardware Nodes: Shipment Now Live!
21 Jul 2025
-
Key events and updates in the Cellframe ecosystem: June highlights
10 Jul 2025
-
Cellframe NewsBlock. Episode 19
07 Jul 2025