AMA Transcript with Dmitry Gerasimov, February 26, 2026

AMA with Dmitry Gerasimov, February 26, 2026

Category: AMA

Title image, read title

Hello everyone, I’m Dmitry Gerasimov, CEO of Cellframe. Welcome to our regular AMA session! Let’s get started with the first question.

Could you please explain how Cellframe's two-level sharding will work? How much will it improve network performance compared to traditional sharding solutions?

First of all, it depends on which traditional sharding solutions you mean, as there are different approaches.

The two-level sharding in Cellframe is designed to significantly improve network performance, primarily limited only by the capabilities of the underlying hardware. One key point is that our current post-quantum signatures are much larger than traditional ones, which gives other networks an advantage today.

However, after a potential quantum attack, that advantage disappears, and our two-level sharding becomes essential. So essentially, this design is a forward-looking preparation to ensure high performance and scalability in the era of quantum computing.

What is the current status of the implementation for the second-level sharding and the hardfork mechanism?

The second-level sharding is scheduled for Cellframe Node 6.1, so it won’t be included in version 6.0.

The hardfork is almost ready: only a few minor improvements remain, mainly related to handling specific conditional transactions. For these, outputs need to be copied without changes, and some custom data needs to be translated. Everything else is already complete.

We expect the hardfork to be deployed in March. Once live, it will significantly reduce the resource requirements for masternodes, enabling faster network processing, quicker node synchronization, and a range of other performance improvements.

You previously announced the launch of native WASM smart contracts on the Cellframe mainnet. What specific tasks will they address? Why was WASM chosen for this implementation over EVM?

EVM integration is handled separately by the QEVM project.

We chose WASM because it provides key performance advantages, especially in a post-quantum environment. WASM is much faster than EVM, making it ideal for tasks that require complex, non-trivial on-chain logic, for example, liquidity provision mechanisms.

WASM smart contracts will be closely integrated with conditional transactions. This allows developers to compose complex, high-performance workflows by connecting transitional transactions together. Thanks to highly optimized C-based building blocks, these smart contracts can execute much faster than conventional approaches.

Essentially, WASM enables advanced use cases like complex trading logic while fully leveraging conditional transactions for efficiency. We plan to release this in version 6.1, either as a plugin or built-in, the exact format is still being finalized. But the focus is on having these two layers: conditional transactions and WASM, working seamlessly together.

How is the work on implementing Cellframe auctions progressing? What will be the size of the "deposit" required to rent a slot?

The full details will be announced later.

Development is in the final stages. If you follow our repository, you can already see the combined DEX + auction branch. We are currently testing how it works with the updated DEX.

Once all issues from these updates are resolved, we will release the auctions and provide full details on the slot deposit and pricing.

How is the development of the updated version of the Cellframe DEX progressing? When is the release planned?

Cellframe DEX 2.0 is already live on the backend in the Cellframe Node.

We ask all masternode holders to update their nodes to ensure smooth operation. The backend is ready, and the wallet update will follow in a few days, after which you’ll be able to use the new DEX features.

So far, over 70% of masternode holders have installed the update. Stay tuned and we’ll announce the full release soon.

What will be your solution regarding the incident with the fake m-tokens? How and when will it be implemented?

The fix is in the final stage of development.

Since we’re rolling out multiple updates: the DEX, the auction, and other features; merging everything together has introduced some new issues in different parts of the code. We’re currently polishing these final details.

We expect to have it completed soon and will provide an official update next week. Once it’s done, the issue will be fully resolved.

The Cellframe blockchain is well-prepared for quantum attacks through its use of NIST-approved PQC algorithms. But what happens if one of these algorithms is eventually broken? Do you have rapid-response mechanisms in place for such scenarios?

Yes, we have.

Our wallets support multi-algorithm signatures and multisig setups. This means if one algorithm is ever compromised, you can easily switch to another to secure your funds.

You can also use multiple algorithms at once: two, three, or more, for additional protection. All the mechanisms are already in place, giving you flexible options to safeguard your assets.

Recently, the team updated the mechanisms of the Cellframe bridge. Could you elaborate on what has changed and how cross-chain interaction between Cellframe and external networks is now structured?

The cross-chain interaction itself hasn’t fundamentally changed yet; the main updates will come in version 6.1. Native Cellframe networks will eventually operate peer-to-peer, bypassing the bridge entirely.

For the current update, we focused on security. We introduced an additional staged process for issuing cross-chain assets: when tokens are burned or frozen on an external network, the corresponding Cellframe tokens are minted or released only after passing multiple verification steps.

This multi-stage approach reduces the attack surface. While our bridge hasn’t been compromised so far, these precautions ensure that even in a worst-case scenario, hackers wouldn’t be able to access large amounts of tokens. Each step includes checks to minimize potential risks and ensure safe cross-chain transfers.

6.0 is rolling out soon, but the full peer-to-peer and updated bridge logic will be ready in 6.1 after thorough testing.

Generally speaking, how secure is communication with quantum-vulnerable networks? Could such a bridge potentially become a vector for a quantum attack?

Communication with quantum-vulnerable networks does carry some risk, which is why we take steps to minimize it. In a worst-case scenario, the bridge could be exposed for a short period, but larger networks like Bitcoin or Ethereum would likely be targeted first.

If a threat arises, we can temporarily disable the bridge to protect users. To stay safe, we strongly recommend moving your CELL tokens to the Cellframe wallet, which is fully operational across all major platforms, including iOS.

For security, make sure to transfer your tokens from ERC-20 or BEP-20 to CF-20. This ensures your assets remain protected against potential quantum attacks.

Are you planning to optimize the bridge's operation for this scenario — for example, one-click transfers for CELL holders on external networks?

Yes, this is already in progress: the optimization has begun. One-click transfers (or very few clicks) for CELL holders on external networks are possible and continuously being improved.

For now, the process works smoothly in 2–3 clicks, and we’re working to make it even more seamless. In the meantime, we encourage users to start transiting their tokens, don’t wait!

Does the team have any plans to implement native cross-chain transfers within the Cellframe Wallet?

Yes, the idea is interesting, and we’ll definitely discuss it. The functionality already exists via the bridge, but integrating it directly into the wallet, for example, as an extension, could be a valuable next step.

The CPUNK team has announced the launch of a multi-chain wallet with support for the native Cellframe protocol. But what about major projects like Metamask and TrustWallet? Are you in discussions with them regarding the integration of the CF protocol?

A big thank you to the CPUNK team, it’s a huge step for our ecosystem. With their wallet, Cellframe now has its first alternative supporting our native protocol, which is really important.

As for major projects like MetaMask and TrustWallet, we still need to grow a bit more before full integration is realistic. That said, we are actively working toward implementing CF in other wallets as well.

How is the development of the collaborative mode for KelVPN progressing? What difficulties is the team encountering during its implementation?

The development is progressing well and is in its final stages. A lot of improvements have been made, the client application was essentially rewritten from scratch.

It’s now much faster and more efficient, with numerous anti-DPI features and enhanced traffic handling. We’re confident users will really appreciate the improvements, as it should work smoothly through all DPI filters and firewalls.

Recently, the team announced the launch of a new e2e testing system. Could you tell us more about this? Why did this need arise, and how is the new system helping to optimize the development process?

Developing decentralized applications means testing in a fully decentralized environment. You need to spin up servers, root nodes, masternodes, and full nodes: essentially a full testnet. Every time you make an update or bug fix, all of these need to be updated.

Previously, teams often had to build custom Docker setups manually. Our new system automates this entirely: it spins up a Cellframe network from scratch, allowing you to test changes and check for regressions.

We also created a specialized scenario language, StageEnd, for describing complex end-to-end test cases. You don’t need to be a professional developer to use it, a QA engineer can write scenarios easily.

Running these scenarios in Docker significantly speeds up development for Cellframe, KelVPN, and other projects in the ecosystem. If you’re building on Cellframe, our team can even provide an introduction or a webinar to get you started.

Tokenization of real-world assets (RWA) is currently gaining significant popularity in the crypto industry. Is the Cellframe platform suitable for launching RWA tokens? Do you plan to develop this direction further?

Yes, the platform itself is suitable for launching RWA tokens.

As for developing this direction further, not directly from our side, mainly due to legal complexities. For example, regulatory guidance (like from the SEC) treats such tokens as real-world securities with restrictions for qualified investors. Launching them requires navigating these legal requirements, which is outside our expertise.

So, if you have the proper qualifications and regulatory approval, you’re welcome to launch on Cellframe.

That’s all the questions for today. Thank you for your support and your questions, it was very interesting. See you next time!

We are CELL! We are here!