AMA with Dmitry Gerasimov, May 30, 2024

AMA with Dmitry Gerasimov, May 30, 2024

Title image, read title

Hello everyone! I’m Dmitry Gerasimov, CEO of Demlabs and lead of the Cellframe project. Today I will answer questions that you sent us previously, or you can ask us right now in the youtube chat.

I still have old BSC tokens. How can I migrate them?

Just do nothing. Soon we will airdrop the new tokens to your address. We delayed it a little, but now everything is ready and we will complete the migration very soon.

The information on total supply and other metrics of the CELL token on CoinMarketCap does not match the data on the project's website. Where can I find the most up-to-date data?

Our website https://cellframe.net/ is the primary source for all the data and metrics. We have already sent all the data for CoinMarketCap and CoinGecko, but they are slow in updating the information unfortunately.

Do you plan to introduce restrictions on delegating m-tokens to masternodes by stakers? How will the percentage of rewards they receive be determined?

Yes, we are planning to restrict the maximum weight of a master node, it means that the m-token delegation will have a limit. So it will make no sense to delegate more than this limit. However delegation itself will not be restricted. Restriction of the maximum weight will create this restriction. The percentage of rewards you earn will be the same if you break your stake into many stakes, restricted by this limit. For example, if we set a limit of 50000 tokens, and you have 500000, you can just break this big stake into ten parts, and set up10 master nodes instead of just one. We are doing this just to create more decentralization in our network.

Will we be able to add user data to transactions in the native Cellframe network in the future? Such functionality could have many applications.

You can do it right now. Transactions have so-called items inside. These could be a signature, output, input, condition for conditional transaction, whatever you want. For now there is no difference between such data but in the near future this difference will be significant. So, you can get user data for transactions right now, but in the future it could cost a little more, depending on the size of your transaction.

You have previously talked about the team's plans to release a web wallet. How will it work? Will a Cellframe node be integrated into it? If not, how will it display the balance and send transactions?

It will look like Metamask or something like this. It will not have a Cellframe Node. It will communicate through JSON-RPC protocol based on HTTPS or on web sockets.

For a nested Cellframe Node please install Cellframe Wallet or Cellframe Dashboard. By the way, we are planning to merge these products. So, Cellframe Dashboard and Cellframe Wallet will be the same application, which will be called Cellframe Wallet.

When the bridge operates in two-way mode, will it be possible to transfer KEL tokens? Or will it only work with CELL tokens?

Our bridge already operates with all tokens listed on the Backbone. So yes, KEL will be possible to transfer both ways as well.

You have previously mentioned that centralized exchanges will support the CELL token in the native CF-20 protocol. Will similar support be implemented for the native KEL token?

It depends on the CEXs. When KEL goes to CEXs, it will use the same infrastructure as the native CF-20 protocol and similar support will be implemented.

By the way this is our primary goal, to go to the CF-20 protocol for all tokens of our ecosystem, because CF-20 is quantum safe. Other protocols are secondary for us, they are just helpers for liquidity aggregation. In the future, I believe, we will operate mostly on the CF-20 protocol. But as far as ERC-20 and BEP-20 protocols are concerned, we also have some plans for deeper integration. For example, one of our subprojects is to be able to work with wrapped Ethereum tokens and connect them with smart contracts inside Ethereum and BSC networks. However it’s a countdown to when the Quantum apocalypse will happen. Then we will not be able to operate in theERC-20 protocol for a long time, until it can be resurrected or relaunched with new encryption.

Please tell us about the KelVPN team's plans after the launch of the collaboration mode. Does the project have a roadmap similar to Cellframe's?

The roadmap for KelVPN is in the works right now. Next week the KelVPN lead will return from vacation and the team will complete the new roadmap and publish it. The team has a lot of plans: multihop is the most important feature, I think, related to VPN proposals. Also they are focused on reworking the market to make providers able to compete with each other and propose different variants with a single resident IP address, maybe options with smaller latencies. These options should differ in price and this price should be available on the open market.

There are two main features in my opinion: an open market for different quality of services in the KelVPN network, and the multihop feature that will allow you to connect in one country and have out of your traffic from another country.

How can KelVPN be considered a "truly decentralized VPN" if the IP addresses of all available servers currently belong to data centers?

For now we are only in the beginning stage with VPN. Most of the VPN servers don’t belong to us; people run them in the cloud. So, if servers belong to data centers, it doesn’t mean that they belong to us. However to have more residential addresses we need to run the previously mentioned feature: to run an open market with the KelVPN orders. This mostly depends on the completion of the new version of the Cellframe Node software.

Tell us more about the Dotflat flatcoin. When and how will it be integrated into CF-20 and how will it work?

Unfortunately I cannot answer this question in detail because this is a question to the DotFlat team and, I believe, they will run an AMA session soon. Actually I don't know a lot of details, we are just providing some help with integration and marketing.

When will the Cellframe hardware nodes be available for order?

Right now we are preparing the production of these nodes. Theirst of these will be a headless node, and the next one will have a display, followed by a node with a battery. So we are planning to expand production step by step, one by one. Right now we are preparing a site with a special order form. We plan to finish it next month.

The National Institute of Standards and Technology (NIST) in the USA plans to release 3-4 new post-quantum algorithms this summer. Will they be added to the Cellframe Node?

They will be added to the DAP SDK for sure. However, we need to investigate all these new algorithms because, you know, sometimes NIST loves to make weaker new algorithms, and not all of them are released in their hardened version. So, we need to investigate and look at how we can use them, then include them in the DAP SDK. Then, after some quality control, we can include them in the current branch of the software. Even if we do all this work in summer, we won’t have them in Cellframe earlier than the beginning of the next year. It’s a long process. For example, right now we are auditing a new post-quantum algorithm and it will appear in the new version of the Cellframe Node. We started to implement it about six months ago, and only in July in fact we will have it in the Cellframe Network.

When discussing the timeline for quantum computers to become fully operational and a threat to standard encryption algorithms, experts give very different estimates. What is your forecast?

My forecast is a few years. One of the forecasts is six or eight months. This is the earliest forecast that I have seen, but who knows. I think it’s a matter of years, but I could be wrong.

Will Node 5.3 help with the overall stability? As it still takes a long time to sync data into the dashboard and very often the dashboard disconnects and is not stable. Can you explain this problem and will Node 5.3 solve this problem?

The reason we are having troubles right now is that we selected not the best algorithm, and to make it synchronisable we added a lot of replies in the synchronization. So, we need to send it 10 times just to be sure that at least some part of this packet will be received by all the nodes of a shard. But in Node 5.3 this problem is eliminated, because it has a totally different sync algorithm. It is now epidemic and doesn’t require overall synchronization.

You can already try using this new 5.3 branch. We’ve already started to use it, and after we fix it, polish and pass the audit it will be really perfect software. Maybe not perfect,but in the current version it will be really nice. Most of the troubles with disconnects and synchronization will go away.

How many developers are working on the Cellframe project and how big is the Cellframe team overall? Has the team been growing in 2023 and what are your plans considering the size of the team in 2024 and 2025?

The total team has about 50 with a few new members. 30 of them are developers, and we are growing. Right now we have some new members of the marketing team. We will enlarge the team of developers after this summer, because it’s hard to hire anyone in the summer. Anyway, the people that we need to hire mostly aren't related to Node. We have a deficit in web development and UI.

By 2025, I think, we will have less need to grow the team because most of the core functionality will have already been developed. At that point we will start to pass the development to the community and most of our team will be refocused on some enterprise issues. Anyway we are looking forward to a situation that will not require a lot of new core development. It will be more about support, visionary, and new services.

Why is Dimitry Nagornykh the CEO of the Dotflat, not you?

Because this is his project, not mine. There are only 24 hours in the day and only 7 days in a week - I can’t do everything and I believe I am good only in some spheres, not in everything.

Please, send me a CELL cup!

We are preparing the Cellframe Shop with merch and hardware nodes. Stay tuned!

Okay, these were all the significant questions. Thank you for all your communications and all your time that you have spent on our cause. See you next time! We are CELL! We are here!