Cellframe & KelVPN Technical Support Information

Cellframe & KelVPN Technical Support Information

Cellframe


If Cellframe-node doesn't connecting to the Dashboard for a long time

Example screenshot:


Usually helps simple restarting of the cellframe node and  cellframe services, but in some cases full reinstallation is reqired.

Reinstallation process:

Windows
1. Make a copy of your wallet file. 
Wallet file is located at:
C:\Users\Public\Documents\cellframe-node\var\lib\wallet
2. Uninstall both Cellframe Dashboard and cellframe-node from your PC. 
3. Check if folders "cellframe-node" and "Cellframe Dashboard" are present at "C:\Program Files\". If so, please delete them.
4. Delete the "Cellframe-Dashboard" and "cellframe-node" folders at 
C:\Users\Public\Documents\
Before deleting "cellframe-node" folder please make sure that a backup of a wallet was created or seed phrase is available.
5. Download and install the following versions of the applications:
(there should be all the latest links to updated versions of ellframe-node and cellframe-dashboard for Windows)
6. Restore your wallet by copying it back to: 
C:\Users\Public\Documents\cellframe-node\var\lib\wallet
7. Open Cellframe Dashboard.

MacOS
1. Uninstall Cellframe Dashboard and cellframe-node. 
Please use "cellframe-uninstaller" script, that is located in the "Applications" folder.
 
2. Remove old log files from you Mac.
Log files are located at:
 
Cellframe Dashboard log files:
/var/log/cellframe-dashboard
 
Cellframe Node log files: 
/Applications/CellframeNode.app/Contents/Resources/var/log

3. Open node data folder: 
/Applications/CellframeNode.app/Contents/Resources/

- Remove "etc" directory
- Open "var" directory and remove "network" and "global_db" folders
 
4. Download and install the following versions of the applications:

(there should be all the latest links to updated versions of ellframe-node and cellframe-dashboard for MacOS)

After that, please open Cellframe Dashboard and check if it is running properly.

Linux
1) $ sudo apt --purge remove cellrfame-node
2)$ sudo apt --purge remove cellframe-dashboard
folder /opt/cellframe-node contains wallet files, make sure that you've made a copy of them
3) '$ sudo rm -r /opt/cellframe-node'
4) '$ sudo rm -r /opt/cellframe-dashboard'
5) '$ sudo rm -r /var/log/cellframe-dashboard'
6)'$ sudo wget (link on latest cellframe node for linux)'
7) '$ sudo apt install ./ (name of downloaded cellframe node file)'
8) '$ sudo wget (link on the latest cellframe dashboard for linux)'
9) '$ sudo apt install ./ (name of downloaded cellframe dashboard file)'

10) then check are both Cellframe node and dashboard running properly.
'systemctl status cellframe-node' (doesn't needed for dashboard)


Cellframe wiki


Fee for the validator nodes

The recommended validator fees on the Backbone network has changed. It is now set to 0.01 CELL per transaction.
Please note that this amount is not strictly mandatory. In our network, validators can set their own preferred fee size.

Location of log, wallet and configuration files


Log files

Windows
Cellframe Dashboard:
C:\Users\Public\Documents\Cellframe-Dashboard\log

Cellframe Node:
C:\Users\Public\Documents\cellframe-node\var\log

Linux
Cellframe Dashboard:
/var/log/cellframe-dashboard

Cellframe Node:
/opt/cellframe-node/var/log

MacOS
Cellframe Dashboard:
/var/log/cellframe-dashboard

Cellframe Node:
/Users/$USER/Applications/Cellframe.app/Contents/Resources/var/log/

Wallet files

Windows
C:\Users\Public\Documents\cellframe-node\var\lib\wallet

Linux
/opt/cellframe-node/var/lib/wallet/

MacOS
/Library/Application Support/CellframeNode/

Configuration files

Windows
C:\Users\Public\Documents\cellframe-node\etc

Linux
/opt/cellframe-node/etc/

MacOS
/Library/Application Support/CellframeNode/


Harvesting issues

Didn't receive $CELL after harvesting

User pressed "Harvest" button and message "Harvest started" was received, but token still did not arrive to the wallet in Cellframe Dashboard.

1. Ask to check balance using https://explorer.cellframe.net/ 
It is possible that Dashboard is not displaying correct data. If it is a case, assist with network synchronization.

2. If tokens are not visible on explorer website - ask for a stake ID and let user know that team will investigate. 
Additionally, make sure that Backbone (or KelVPN) network is synchronized.

Stake generates low amount of rewards 

Ask for stake ID and let user know that team will investigate. 

Other errors while trying to harvest

If other errors were encountered on the staking website after clicking "Harvest" button:
- ask for the screenshot of the error
- ask for a stake ID
- let user know that team will investigate

Staking issues

YouTube guide about staking

https://www.youtube.com/watch?v=2HC_LcRnfOk

How to stake through the CLI


Command syntax:
  1. stake_lock hold 
    -net <net_name> 
    -w <wallet_name> 
    -time_staking <YYMMDD> 
    -token <ticker> 
    -value <value> 
    -fee <value>
    [-reinvest <percentage_from_1_to_100>]
    [-chain <chain_name>]
example:

  2. cellframe-node-cli stake_lock hold 
  3. -net raiden 
  4. -w mywallet 
  5. -time_staking 240705 
  6. -token tCELL 
  7. -value 1000.0e+18 
  8. -fee 0.05e+18 
  9. -reinvest 50
Don't forget to set users attention on that fact, that all the values should be represented like "'X'e+18" or a digit with 18 0's after comma. 

How to connect Dashboard to the staking website?


Preview

1) Firstly - at the top right corner of the staking website page click on the "Connect Dashboard" button.
2) Secondly - Confirm connection by starting cellframe-dashboard on your PC.
3) Last step - In your Cellframe dashboard please click "Allow" to connect your dashboard to the staking website.

If Cellframe-Dashboard doesn't connecting to the staking website

1) Ask what exact browser is used at the moment to connect Cellframe Dashboard
2)if used browser is 'Brave' :
When using Brave, Brave Shield needs to be turned off for staking website as it blocks connection from website to Dashboard application.


Didn't receive mCELL for making a stake


If new stake is displayed on the website, ask for a stake ID

If not:
- ask to check the wallet balance, if $CELL were taken
- ask for the address of the wallet that was used to make a stake.

Can't make a stake


If there is an error on the website - ask for a screenshot.


While the team is offline, ask to check if the latest version of Dashboard is used and the Backbone network is synchronized. 


A couple of things to check: 

- balance displayed in Cellframe Dashboard matches balance on https://explorer.cellframe.net/ 

- at least 0.01 CELL is left on the wallet after selecting amount of $CELL to lock to pay the network fee


Stakes are not displayed on the staking website


1. Make sure the correct network (BSC or ETH) is chosen in Metamask or Trust Wallet
2. Make sure that the correct account is selected in Metamask or Trust Wallet
3. Make sure the Dashboard is connected to the website


If still not visible - ask which positions are not displayed, ask for a screenshot and a wallet address to investigate.

About staking APY


APY is not fixed. It varies based on stake duration, reinvestment percentage. It will also change during staking period, based on the total amount of tokens in particular staking pool.
Displayed APY number is a possible value when selecting the longest lock period (2 years) and 100% reinvestment option. 

Stake details on the website


Here are a couple of examples how each stake is displayed on the website.


The following information is present:

1. Contract value
Number of $CELL or LP tokens that is staked.

2. Staked value
Contract value converted to $CELL tokens. In case of single staking, it will be the same as "Contract value".

3. Stake balance
This one represents "Staked value" + reinvested rewards at this particular moment. If lock period has not ended and reinvestment % in higher than 0, this value will increase over 

4. Your estimated reward
Estimated number of $CELL rewards for the whole staking period. This value is calculated at the time of staking and may be different at the end of lock period due to APY changes.

5. $CELL earned
Number of available $CELL for harvesting

6. mCELL
Number of mCELL received for making this particular stake. 

7. reinvestment percentage
this parameter displays what exact part of rewards earned during the staking process will be reinvested back to earn even more. 

Unstaking issues

Pressed “Unstake” but didn’t receive tokens back


1. Check balance on https://explorer.cellframe.net/ 

- Does it match balance in Cellframe Dashboard?
- Has the amount of mCELL on the wallet decreased?

2. If balance did not change on explorer website and button is greyed out.
- Ask for a stake ID.

- Assist with the synchronization of the Backbone network.


Error on the website "---> TAKE <--- ERROR! failed to add datum with take-transaction to mempool".


The most common reason for the issue is lack of $CELL in the Cellframe Dashboard wallet to pay the transaction fee in the network. At the moment, fee is 0.05 $CELL. 

However, it is possible that a rare issue have occurred. 

First, check the following:
      - Backbone network is fully synchronized
      - balance in the Cellframe Dashboard matches balance on the https://explorer.cellframe.net/
      - there is enough $CELL to pay a transaction fee.

If all of the above is correct and user is still unable to unstake, the following needs to be done.
      - open "Console" tab in "Cli" mode
      - use the following command:
            remove -gdb
            

GDB synchronizes significantly faster than network chains. After 5-10 minutes, user can try to unstake again. 

Error on the website "---> TAKE <--- ERROR! ^^^ could not find transaction"


This error means that the Backbone network is not fully synchronized. Assist with the synchronization of the network.

"Claim" button is not available after unstaking LP token


Collect the following information:
      - were mCELL taken from the wallet
      - were rewards distributed
      - ask for a stake ID for further investigation

Unstaking from the old staking website


A rare question that might appear in the group - collecting LP tokens from the old staking website. 

Ask to connect a wallet to the current staking website and to try using "Withdraw from previous staking programs" button. It is located at the bottom of the list of available staking options.



If user encounters “Cannot withdraw 0.” error, make sure the correct account is connected to the website, as well as correct network is selected.
If all of the above is true, ask for a hash of a staking transaction and let user know that team will investigate. 

Other errors on the staking  website

Collect the following information:

- What were the steps that user has taken to encounter this error?

- Ask for a screenshot.

- Ask for a stake ID if the error is related to the staking.


Migration issues


Tokens are not visible in MetaMask or Trust Wallet after the migration


Ask to add the new contract token address to the wallet. 
      New BSC contract address: 0xd98438889Ae7364c7E2A3540547Fad042FB24642

If new $CELL are still not visible, it is most likely that migration was completed partially.
In the process of migration, two transactions occur: one that migrates tokens and one that claims them. 
Here's how it looks on bscscan. 


Ask to check if both of them are present.
If "Claim Token" is missing, the same wallet needs to be connected to the migration website to collect tokens by pressing "Claim" button.

Can't connect wallet to the migration website

Migration website supports Trust Wallet and MetaMask wallets. 
If mobile device is used, it is recommended to use the browser available in these applications. 

Rare issue - token balance to migrate is 0

In very rare cases, users might experience the following issue.
When connecting Metamask or Trust Wallet to the migration website, after clicking "MAX" button, users will see that 0 appears and website does recognize the tokens in their wallets.

Before proceeding with the solution, make sure that the following information is correct:
- token are indeed on the old contract
- correct network is selected in the web3 wallet
- correct account is selected in the web3 wallet

If all of the above is true, there are two steps for the solution of the issue.

1. Clear cache and cookies for the migration website in browser
- Disconnect web3 wallet from migration website.
- Open web3 wallet, open "Connected websites" and remove migrate.cellframe.net from the list
- Clear cache and cookies for the migration website in browser
- Reload the migration page in browser
- Connect web3 wallet and click "MAX" button

If the recommendation above does not help, try the following.

2. The issue is in the wallet itself.
- Install second browser on the PC (Google Chrome or Firefox)
- Install Metamask or Trust Wallet extension
- Restore wallet in browser extension
- Connect to the migration website and try to migrate tokens

Different error on the website

Collect the following information:
      - What were the steps that user did to encounter this error?
      - Ask for a screenshot
      - Notify team in Cellframe Technical Support group in Telegram

Bridge issues

Bridge BEP-20, ERC-20  --> CF20

Tokens are not visible in Cellframe Dashboard after using the bridge

Ask to check balance using https://explorer.cellframe.net/ 

If tokens are present on explorer:
The issue is in the Backbone network synchronization. Assist with the synchronization of the network.

If tokens are not present on explorer:
When bridging, Metamask\Trust Wallet pushes 2 transactions.
Here's how the transactions look on etherscan:


Assist with checking the wallet history. If needed, ask for the hash of the transaction from BSC or ETH networks and use it to check wallet history.
If both transactions are present in the wallet history and tokens are still not displayed on the explorer website, send the transaction hash to the team for investigation.

Can't connect wallet to the bridge website

Bridge website supports Trust Wallet and MetaMask wallets. 
If mobile device is used, it is recommended to use the browser available in these applications. 

Bridge BEP-20 <-> ERC-20

General information

Cellframe Dashboard is not needed for using BEP-20 <-> ERC-20 bridge, only web3 wallet.
At the moment, Metamask and Trust Wallet are supported.

Bridge CF20 -->BEP-20, ERC-20

General information

Token withdrawals are currently available for the Backbone and KelVPN networks. 
To access the bridge functionality, make sure you're using Cellframe Dashboard version 3.0-71 or higher. 

Did not receive tokens after using bridge

First, ask if tokens were deducted from the wallet. 

Next, ask to add either BEP-20 or ERC-20 $CELL contract address to web3 wallet and check balance one more time.

If tokens are still not visible, collect the following information:
- web3 wallet address
or
- transaction hash

As usual, let user know that team will investigate.


DEX questions/issues

How DEX works?

Cellframe DEX is using conditional transactions. DEX order is a conditional transaction that is written to the blockchain. This transaction locks tokens for the exchange, meaning that after creating an order tokens will be taken from the wallet.
Tokens can be returned by cancelling an order via "DEX" tab in "My orders" section.
If order is fulfilled partially, the rest of the tokens can also be returned.

Will I receive tokens instantly after creating an order?

No. After creating an order, it will be processed as a transaction and written to the blockchain. The rest of the community will be able to see the order and if they choose to engage with it, they will have an option to fulfill it either partially of in full.

What is "Price" and how is it calculated?

"Price" field in the DEX tab is the ratio between the token in "Amount of" field to "Total" field.
Here's an example:



General steps to collect information about DEX issues


Since DEX was released recently, not a lot of questions have been asked yet.
In general, when an issue arises, collect the following information:
- detailed description of the issue
- screenshot if it is a visual bug in the "DEX" tab
- wallet address if user thinks that tokens were lost during the DEX usage

KelVPN

Server is not working


Collect the following information:

      - what server is not working

      - what version of an application is used

       - ask to use the “Send bug report” option in the application and to include a detailed description of the issue.


Refunds

We offer refunds if customers are not happy with the performance of the service and if it doesn’t work for them.

Information that should be collected:


  1. Method of payment.

    1. Credit card - date and time of payment, as well as last 4 digits of the card.

    2. Crypto - hash of the transaction.

  2. KelVPN licence key for deactivation.

  3. Purchased plan - 1, 6 or 12 months.


Information about payment should be forwarded to Mira @ascatelluma

Licence key to Andrey @cellframe_tech_support for deactivation.

Key is not found in the database

What version of the application is installed? If not the latest available from the KelVPN website, ask to reinstall the application and try using the key again.

If the latest version is installed and key is not working, ask to use "Contact us" form on the website and include the following information:
      - Version of the installed application
      - What OS is used.
      - License key that is not working
      - Purchase information (date, payment method).

In addition, ask to use "Send bug report" in the installed KelVPN application and include a detailed description of the issue.
If the application was already uninstalled, ask to install it again, try using the license key, and send a report after a failed attempt. 

Error in the GUI of the application

Collect the following information:

  1. What device is used (PC, mobile, Mac, etc.)

  2. What version of OS is used.

  3. What is the version of the application.

  4. Ask for a screenshot if possible.

  5. What were the steps that users did to encounter this error?


In addition, ask to send a bug report through the application with inclusion of the description of the error.

Collaborations, marketing offers, or White Label discussions


If any community member has an idea for the project, or a marketing offer, or would like to learn more about White Label conditions, please ask them to use "Contact form" on the website.

stereotypical text:
To find out more about White Label, please email alexey.yusupov@demlabs.net.

Kind regards,  
KelVPN Support Team.


Common procedures to resolve issues

Synchronization of the Backbone network

At first, check if the installed version of the Cellframe Dashboard is the latest available. 
Next, check the current state of the network synchronization in the Cellframe Dashboard using the "Console" tab in "Cli" mode with command:

                                    block list -net Backbone -chain main


                                    
block count -net Backbone -chain main

 When synchronization is completed, in the last line of the commands result will be a number of blocks that matches the number displayed on the https://explorer.cellframe.net/
                                    

If the number of blocks synchronized locally does not match the number on the website, one of two of the following methods can be used.
                                    - press the Backbone button at the bottom of the Cellframe Dashboard and click "Sync network". Synchronization may take a while depending on the internet connection.
                                          
                                    - open the "Console" tab in "Cli" mode and use command:
                                          net -net Backbone go sync
                                          

If synchronization does not advance after a significant period of time, it is recommended to start it from scratch using the "Clear node data" option in the "Settings" tab of the Cellframe Dashboard.
                                          


If need to remove Cellframe-node from autorunning apps list


stereotypical answer:
You could remove from autorunning apps Cellframe node, as it shown on a screenshot (located at settings tab at cellframe dashboard), so it will not start at the same moment with your PC.

After all these steps - before running Cellframe dashboard - don't forget to run your node manually!

Restarting the cellframe node


Windows


1. Close Dashboard.
2. Open "Task Manager".
3. Check if "cellframe-node" process is present.
4. If present - close it.
5. Open location where Dashboard is installed. (Default path is C:\Program Files\Cellframe-Dashboard)
6. Start "cellframe-node"
7. Open Dashboard application.

OR


1. Close Cellframe Dashboard.
2. Open Windows Task Manager
3. Find and close "Cellframe-DashboardService" process.
4. In Windows Tray, right click on the Cellframe icon, select Service -> Restart cellframe-node

On some devices, it may take a few minutes for the network panel to appear at the bottom of the Cellframe Dashboard.
To check if the node is running, open the "Settings" tab and check the status of the node.
If it is green, network panel will appear soon.
If it is red, then the node was not started. 

Linux


1. Open "Terminal".
2. Use one of the following commands:
sudo systemctl restart cellframe-node.service
sudo service cellframe-node restart

MacOS


First option. 
1. Stop the node.
      Open Terminal.
      Use the following commands:
            launchctl unload -w /Users/$USER/Library/LaunchAgents/com.demlabs.cellframe-node.plist
            launchctl stop com.demlabs.cellframe-node

2. Start the node.
      Open Terminal
      Use the following commands:
            launchctl load -w /Users/$USER/Library/LaunchAgents/com.demlabs.cellframe-node.plist
            launchctl start com.demlabs.cellframe-node

Second option.

1. Close Cellframe Dashboard.
2. Open "Activity monitor"
3. Type "cell" in search bar.
4. There should be 2 processes left after the closing the Dashboard: Cellframe-DashboardService and cellframe-node.
5. Use "Force quit" option on "Cellframe-DashboardService" first, then on "cellframe-node". PID will change for each process after its restart.
6. Open Cellframe Dashboard.

Wallet is not visible in Cellframe Dashboard


Check node status in the “Settings” tab.

      - “green” but the network panel at the bottom is not displayed: leave application open until the panel appears. 

      - “red” - assist with the node restart. Process depends on the OS. 


If node status is green, network panel is displayed and Cellframe Dashboard is operating as usual, but the wallet is still not displayed - ask to check one of the following folders on the PC if the wallet file is present there. If not - wallet needs to be restored.

Wallet files are located at:
Linux:
/opt/cellframe-node/var/lib/wallet/
Windows:
C:\Users\Public\Documents\cellframe-node\var\lib\wallet
MacOS:
/Users/$USER/Applications/Cellframe.app/Contents/Resources/var/lib/wallet

Balance in Cellframe Dashboard is incorrect


  1. Ask to check if displayed balance in Cellframe Dashboard matches balance on https://explorer.cellframe.net/ 

  2. If not - ask to sync the Backbone network.

  3. If the user thinks that both Dashboard and https://explorer.cellframe.net/ show incorrect balance.

    1. find out the reason for the incorrect balance - what actions were performed by the user (new stake, harvest, etc.) that occurred that are not reflected by the current balance.

    2. ask for a Backbone wallet address or a stake ID.


Network panel is not visible


If network panel is not visible, ask to check the node status in "Settings" tab.
If the status is green: ask to leave Cellframe Dashboard open for some time. Network panel will appear soon.
If the status is red: assist with restart of the node. Steps to restart the node are available above.

Error while creating or restoring a wallet

If during the restoration process the "socket connection error" appears, this means that the node is not active. Assist user with the node restart. 



Different wallet address after restoration of the wallet


Different wallet address is a result of the mistake in the information that was used to restore the original wallet.

When restoring a wallet, information such as seed phrase, signature type, type of wallet and password must remain the same as was used in its creation. Only the name of the wallet could be changed.
Seed phrase should not contain any extra spaces before or after each keyword.

Forgot or lost seed phrase

It is not possible to restore seed phrase in Cellframe Dashboard. Seed phrases are not stored in any capacity and only accessible when creating a wallet.

The only way that is left to back up a wallet is to copy local wallet file to a safe place.
Wallet files are located at:
Linux:
/opt/cellframe-node/var/lib/wallet/
Windows:
C:\Users\Public\Documents\cellframe-node\var\lib\wallet
MacOS:
/Users/$USER/Applications/Cellframe.app/Contents/Resources/var/lib/wallet

In this folder, a file with extension .dwallet is present. This is a file that needs to be backed up.
When installing Dashboard on another PC, place this file in the exact same directory and Cellframe Dashboard will recognize it.

Website is not accessible or loading incorrectly

Website is not accessible

If error "Internal server error" is displayed in browser - the website is either being updated or down. Ask user to try to access it a little later. 

Website is not loading correctly

Ask to clear cache and cookies for it in their browser and reload the webpage.
If that doesn't help -  let user know that team will investigate.


Masternode questions


We have created thorough instructions on setting up the master node. However, some questions may still arise. If anybody needs any help, you will find all the needed information in these guides.

Link to wiki instruction: https://wiki.cellframe.net/02.+Learn/Become+a+Master+Node/Master+Node+Manual+Setup

Link to video guide: https://youtu.be/NhIdw-9FhGg


Masternode setup questions

How much $CELL for the masternode

10000 $CELL. This amount might change in the future.

Masternode approval

APPROVAL and REVIEW of Masternode Certificate

Backbone Approval


Получаем хэш транзакции от юзера (пример): 0x71C67DAA61281B45EB041A4AD517D179C4C8EA50B36B13FE20D7BF07ED29B370

Проверяем настройку конфига будущей мастерноды:
cellframe-node-cli srv_stake check -tx 0x71C67DAA61281B45EB041A4AD517D179D179C4C8EA50B36B13FE20D7BF07ED29B370 -net Backbone

cellframe-node-cli tx_history -tx 0x71C67DAA61281B45EB041A4AD517D179C4C8EA50B36B13FE20D7BF07ED29B370 -net Backbone
Должно выглядеть так: 

There are unresolved issues - не обращаем внимания, такой ответ выводится из-за того что пока нет ордера на комиссию, а он и не может появиться до того как мастернода будет одобрена

Выпускаем декрет:
cellframe-node-cli srv_stake approve -net Backbone -tx HASH -poa_cert scorpion.root.0

Проверяем, появился ли в мемпуле зерочейна:
cellframe-node-cli mempool_list -net Backbone -chain zerochain

Выпускаем второй декрет:
cellframe-node-cli decree sign -net Backbone -chain zerochain -datum HASH -certs scorpion.root.1
Ожидаемый ответ:
Datum 0xD11FF74D7469C22B02D93E7AE5C5A44428DF09C827113D0479977731966A8A59 is placed in datum pool

Выпускаем третий декрет:
cellframe-node-cli decree sign -net Backbone -chain zerochain -datum HASH -certs scorpion.root.2
Ожидаемый ответ:
Datum 0xA146DCEA5507070C3070766BA4929C49032D6B6BEF5DC79CC15E63E2CE3A87AAA87AA4F1E is placed in datum pool

Делаем proc
cellframe-node-cli mempool_proc -net Backbone -chain zerochain -datum HASH 

 Ожидаемый ответ (verify):

            isProcessed: true

            notice: Removed datum from mempool.


Удостоверяемся, появился ли ивент:

cellframe-node-cli dag event list -net Backbone -chain zerochain -offset 97705 -head 

Dump найденного ивента:

cellframe-node-cli dag event dump -net Backbone -chain zerochain -event  0xEAA9C52ADD5391B8DAEA21950B80A9E86EB229A6023973CC3A64540937AAC4D1  -from events


Выпускаем анкер:

cellframe-node-cli decree anchor -net Backbone -chain main -datum DECREE_HASH -certs scorpion.root.2

Ожидаемый ответ:

Datum 0xCCB506A77CBA51C6E8B90C612CB4FC0C5DB9E81698A830CF747B75BC03D4F76E is placed in datum pool


Удостоверяемся, появился ли в блоках:

cellframe-node-cli block list -net Backbone -chain main -offset 164275 -head

Dump блока:       

cellframe-node-cli block dump 0x611172E8A82538B3F3E86D2E646D30CA792B22CA2110F30A04EE16EC2ABAD321 -net Backbone -chain main


Invalidate Backbone

Получаем инфо из  srv_stake list keys


Pkey hash: 0xDB1364EC0EB6832D602EC4D6D50F147FF588798F8DD0D00D7F3B003A55C902AE

        Stake value: 47.0

        Related weight: 2.313371099887662699%

        Tx hash: 0xEE138408EB788F9CDF24E4045CCFBC6E9DF59DAEB8F97ECA90A3BF8C2724D124

        Node addr: BF0A::2F4F::7355::C3A5

        Sovereign addr: N/A

        Sovereign tax: 0.0%


  1. Выпускаем декрет на инвалидацию:

cellframe-node-cli srv_stake invalidate -net Backbone -signing_pkey_hash PKEY_HASH -signing_pkey_type sig_dil  -poa_cert scorpion.root.0

Ожидаемый результат:

Specified delegated key invalidated. Created key invalidation decree 0x12E63D9EE01AAC03D0458FBF3DDBD01AAE004662744E6823CBF8CEBB018C6E65.Try to execute this command with -w to return m-tokens to owner

Проверяем мемпул зерочейна:

cellframe-node-cli mempool list -net Backbone -chain zerochain


  1. Подписываем второй декрет

cellframe-node-cli decree sign -net Backbone -chain zerochain -datum HASH -certs scorpion.root.1

Ожидаемый результат:

Datum 0x44528F0F313F841E2B589BC3F5D96EB222CAF18DFB0467D98CC488A5A882730E is placed in datum pool


  1. Подписываем третий декрет:

cellframe-node-cli decree sign -net Backbone -chain zerochain -datum HASH  -certs scorpion.root.2

Ожидаемый результат:

Datum 0xA6078B034B5A83D57101E71D927E7065D85A405A90A787ECA11F9A7B8D236747 is placed in datum pool


  1. Делаем proc:

cellframe-node-cli mempool_proc -net Backbone -chain zerochain -datum HASH 


     Ожидаемый результат (verify):

            isProcessed: true

            notice: Removed datum from mempool.


  1. Удостоверяемся, появился ли ивент:

cellframe-node-cli dag event list -net Backbone -chain zerochain -head -offset 97700

Dump найденного ивента:

cellframe-node-cli dag event dump -net Backbone -chain zerochain -event  0x90081E36BE6F785BF495A81A19BB38F15F917BF416DCD61419831FC41751010A -from events


  1. Выпускаем анкер:

cellframe-node-cli decree anchor -net Backbone -chain main -datum DECREE_HASH -certs scorpion.root.2

Ожидаемый результат:

Datum 0x2B5F5DDF85E35202564F75E4D4F0C6D5891A6467F354C2748A49C5C150DF1E7B is placed in datum pool


  1. Удостоверяемся, появился ли в блоках

cellframe-node-cli block list -net Backbone -chain main -head -offset 163165 

Dump блока:       

cellframe-node-cli block dump 0x40A89D794978538ABBB550B11AEF3EF7B3668EAD5A453FAB53C9BCFEB8C1FC42 -net Backbone -chain main

Validate KelVPN

Получаем хэш транзакции от юзера (пример):

0x18A0C67FF20A6E0386C9D01FECF9E38ADD28FF67CF60BCF97CDA312A527C37CD


  1. Проверяем настройку конфига будущей мастерноды:

cellframe-node-cli srv_stake check -tx 0x18A0C67FF20A6E0386C9D01FECF9E38ADD28FF67CF60BCF97CDA312A527C37CD -net KelVPN


cellframe-node-cli tx_history -tx 0x18A0C67FF20A6E0386C9D01FECF9E38ADD28FF67CF60BCF97CDA312A527C37CD -net KelVPN

Должно выглядеть так: 
There are unresolved issues - не обращаем внимания, такой ответ выводится из-за того что пока нет ордера на комиссию, а он и не может появиться до того как мастернода будет одобрена

  1. Выпускаем декрет:

cellframe-node-cli srv_stake approve -net KelVPN -tx HASH -poa_cert kelvpn.root.pvt.0

Ожидаемый результат:

Approve decree 0x374B20840E9347826A4967021356C65D9020142103FE76E3FED1D1793692DC5F successfully created

Проверяем, появился ли в мемпуле зерочейна:

cellframe-node-cli mempool_list -net KelVPN -chain zerochain


  1. Выпускаем второй декрет:

cellframe-node-cli decree sign -net KelVPN -chain zerochain -datum HASH  -certs kelvpn.root.pvt.1 

Ожидаемый результат:

Datum 0xFAF35EE1A3D44BD82BE72F3ED28141555A61CF57D222C83AAA027619220E2CCB is placed in datum pool


  1. Выпускаем третий декрет:

cellframe-node-cli decree sign -net KelVPN -chain zerochain -datum HASH   -certs kelvpn.root.pvt.2

Ожидаемый результат:

Datum 0x2FDF752B01D7A71246BA4B7648BCCA4EDCEFAF40322CE2791740946E5835AFE5 is placed in datum pool


  1. Делаем proc

cellframe-node-cli mempool_proc -net KelVPN -chain zerochain -datum HASH 



Ожидаемый ответ (verify):

         isProcessed: true

         notice: Removed datum from mempool.


  1. Удостоверяемся, появился ли ивент:

cellframe-node-cli dag event list -net KelVPN -chain zerochain -offset 1680 -head

Dump найденного ивента:

cellframe-node-cli dag event dump -net KelVPN -chain zerochain -event  0x8962F75A668A8E271BE31A35ECDE9DF94697AB2DB4555465FCE09303F3C1CF2D -from events 


  1. Выпускаем анкер:

cellframe-node-cli decree anchor -net KelVPN -chain main -datum DECREE_HASH -certs kelvpn.root.pvt.0

Ожидаемый ответ:

Datum 0xA4CF01E79E86F40A43344FFA01EC89767735819E73950D91705AF5B66A81B29D is placed in datum pool


  1. Удостоверяемся, появился ли в блоках:

cellframe-node-cli block list -net KelVPN -chain main -offset 138860 -head 

Dump блока: 

cellframe-node-cli block dump 0xA80E77EA1927B95A86FFB0FED6EBBDBDEA6F2D439C29522E8309ED8A34F3E601 -net KelVPN -chain main

Invalidate KelVPN


Получаем инфо из  srv_stake list keys


Pkey hash: 0x9A3404043A021CEDC8D6C2939548B63B8ABBA76F8867235B495CDD39BE8BB986

     Stake value: 500.0

     Related weight: 18.796992481203007518%

     Tx hash: 0x9B5F0909765B6AD529B39B22B68B5AF7845A99419A37CFD637C8263F577BEC0E

     Node addr: CCCC::0000::0001::0001

     Sovereign addr: N/A

     Sovereign tax: 0.0%


  1. Выпускаем декрет на инвалидацию:

cellframe-node-cli srv_stake invalidate -net KelVPN -signing_pkey_hash PKEY_HASH -signing_pkey_type sig_dil  -poa_cert kelvpn.root.pvt.0

Ожидаемый результат:

Specified delegated key invalidated. Created key invalidation decree 0x8C3D1A45C5FAFA74EF927BD9C8310A31C89179417FCC800EC52A5D0110766A87.Try to execute this command with -w to return m-tokens to owner

Проверяем мемпул зерочейна:

cellframe-node-cli mempool list -net KelVPN -chain zerochain


  1. Подписываем второй декрет

cellframe-node-cli decree sign -net KelVPN -chain zerochain -datum HASH -certs kelvpn.root.pvt.1

Ожидаемый результат:

Datum 0x93CF422E58AF7C5AC792EFBEFD302505CE412419740B74092A1F10F75A763170 is placed in datum pool


  1. Подписываем третий декрет:

cellframe-node-cli decree sign -net KelVPN -chain zerochain -datum HASH -certs kelvpn.root.pvt.2

Ожидаемый результат:

Datum 0x82F7F45E6E714BC4A65A38CCA4FBEADA19A3829C50C9DEC941DC925E8FCAE7A8 is placed in datum pool


  1. Делаем proc:

cellframe-node-cli mempool_proc -net KelVPN -chain zerochain -datum HASH 


Ожидаемый результат (verify):

         isProcessed: true

         notice: Removed datum from mempool.


  1. Удостоверяемся, появился ли ивент:

cellframe-node-cli dag event list -net KelVPN -chain zerochain -offset 1635  -head

Dump найденного ивента:

cellframe-node-cli dag event dump -net KelVPN -chain zerochain -event  0x0458D36D3514666D9600850132FF562C640E2D7B2C101E15415634AC7825C813 -from events 


  1. Выпускаем анкер:

cellframe-node-cli decree anchor -net KelVPN -chain main -datum DECREE_HASH  -certs kelvpn.root.pvt.0

Ожидаемый результат:

Datum 0x7D1B4D453016AC230BA40D5EA16B1572CA220214F7CD377E54900632411E3276 is placed in datum pool


  1. Удостоверяемся, появился ли в блоках

cellframe-node-cli block list -net KelVPN -chain main -offset 145515 -head

        Dump блока:   

cellframe-node-cli block dump 0x100A01199FB64039EC6E93C07665BA6CACF97E07D6A8C841BF198C24DB13080D -net KelVPN -chain main



Важная информация по подписанию декретов: В Backbone и KelVPN требуется три декрета, в то время как в raiden и riemann - всего два

Hardware requirements

Minimum requirements:
- 4 GB of RAM. This will be enough for Backbone network only. We recommend to use 8 GB.
- CPU with 2 cores 1GHz each or 1 core 2.3 GHz
- 80+ GB SSD for data storage
- stable internet connection (preferably 100 Mbps)

OS requirements

Windows:
- 10 or 11

Linux:
- Ubuntu 20.04 or above
- Debian 10 or above

MacOS:
- Bug Sur (MacOS 11.7) or above

Common questions

When will it be possible to run a masternode using Cellframe Dashboard?

It is already possible. Guide that is available on the Cellframe Wiki contains all the necessary commands for its setup. Commands should be used in "Console" tab of the Cellframe Dashboard.

Is it possible to run one node and be a validator in multiple networks?

Yes, it is possible. One node can be used to be a validator in both Backbone and KelVPN networks. 


General information


1. Look for the answer in the following groups:
Cellframe Support
Cellframe Dev EN
Cellframe Network

2. If the question was never previously answered, collect all the information that might be relevant to the issue:
- wallet address
- transaction hash
- version of the application
- screenshot of the issue

3. Let user know that team will investigate the issue. 
4. Forward the question and all the collected details to Cellframe Technical Support group in Telegram. We will update this document and keep it up to date.

Contract addresses

Cellframe

ETH contract:

0x26c8afbbfe1ebaca03c2bb082e69d0476bffe099


Old 5%-fee contract BSC:

0xf3e1449ddb6b218da2c9463d4594ceccc8934346


New 1%-fee contract BSC:

0xd98438889Ae7364c7E2A3540547Fad042FB24642


KelVPN

Old ETH contract: 

0x4abb9cc67bd3da9eb966d1159a71a0e68bd15432


Old BSC contract:

0x4e1b16ef22935a575a6811d4616f98c4077e4408


New ETH contract: 

0xDA6A3876AD460194Cd7bA28062D838C98Ee2fD1d


New BSC contract: 

0x76E8e912097F0E6b81cab73147161bb616dF1D7d




Contacting via DM

If a member of the community is reluctant to share any of their information in the Support group, please ask them to contact team using the feedback form on the website or through the e-mail. 


Cellframe:

KelVPN:

Groups to moderate and answer questions

  1. Cellframe Network

Link: https://t.me/cellframe

Main group. Here questions will be asked primarily about buying tokens, how staking/migration/bridge works. If a question is related to a technical issue, refer them to the support group for further assistance. 


  1. Cellframe Tech Support

Link: https://t.me/cellframetechsupport

A place to discuss and assist all the technical reports.


  1. Cellframe Dev EN

Link: https://t.me/cellframe_dev_en

A group for interactions with the development team. Sometimes, members may ask questions that are not related to this topic. They need to be directed to the appropriate group.


      4. Cellframe Beta Test

Link: https://t.me/cellframebetatest

Group for members of the community who participate in closed tests of early versions of applications.

      5. KelVPN Official

Link: https://t.me/kelvpnbeta

Main KelVPN group. A place to answer general questions about available functionality of the application and websites. Questions about tokens will be asked here as well.

      6. KelVPN Support

Link: https://t.me/kelvpn_tech_support

A place to assist with KelVPN technical issues.

      7. KelVPN Beta Test

Link: https://t.me/kelvpnbetatest

The same as the Cellframe Beta Test group.

  1. Cellframe Node Support.

Link: https://t.me/cellframenode

A group of community members who have set up a master node. There may be some questions about the activity of their nodes.


  1. KelVPN Node Support

Link: https://t.me/kelvpn_node_support

Group of community member who have set up a master node in KelVPN network.