3 Frequently Asked Questions

To be updated.

I. Increase Confidence Level

Currently, Tier 1, 2, 3 are treated in the same way. No operation is needed if you are at these tiers. However, if you are at Tier 4 or 5, you can try the following tips. You can also join the Discord or Telegram miner group to discuss.

Got CONFIGURATION_NEEDED and CONFIGURATION_AND_SW_HARDENING_NEEDED

The EPID signature of the ISV enclave QUOTE has been verified correctly, but the additional configuration of the SGX platform may be needed (for further details see Advisory IDs). The platform has not been identified as compromised and thus it is not revoked. It is up to the Service Provider to decide whether or not to trust the content of the QUOTE, and whether or not to trust the platform performing the attestation to protect specific sensitive information.

– from Intel IAS API Spec

It means either the BIOS is misconfigured or the BIOS firmware is misbuilt. You can try:

  • Upgrade to the latest BIOS firmware (you may want to write to the motherboard manufacturers asking for a fix, too)
  • Disable Hyper Threading in the BIOS
  • Disable the integrated graphics in the BIOS
  • Disable advanced power management (disable the power-saving mode)
  • Check the exact adversoryIds and their description pages for the detailed fixes
Linux provides the option to override the microcode. However, it doesn’t help the SGX setup, because SGX measures the microcode carried by the BIOS only.

Got GROUP_OUT_OF_DATE

The EPID signature of the ISV enclave QUOTE has been verified correctly, but the TCB level of the SGX platform is outdated (for further details see Advisory IDs). The platform has not been identified as compromised and thus it is not revoked. It is up to the Service Provider to decide whether or not to trust the content of the QUOTE, and whether or not to trust the platform performing the attestation to protect specific sensitive information.

It means the BIOS firmware (specifically, the CPU microcode it carries) is out-of-date and must be upgraded. You can try:

  • Upgrade to the latest BIOS firmware (you may want to write to the motherboard manufacturers asking for a fix, too)
Linux provides the option to override the microcode. However, it doesn’t help the SGX setup, because SGX measures the microcode carried by the BIOS only.

How to update workers from Para2 to Khala

You need to clean all node & pruntime data , follow this command:

1sudo phala update clean

Follow this command to uninstall your phala mining scripts:

1sudo phala uninstall
2sudo rm -R ~/solo-mining-scripts-para1
3sudo rm -R ~/solo-mining-scripts-main
4sudo rm ~/main.zip
5sudo rm ~/para1.zip

You can follow this page to redownload and reinstall new phala mining scripts: https://wiki.phala.network/zh-cn/docs/khala-mining/

Got “Unable to retrieve header and parent from supplied hash” during node syncing

It you were using the our snapshot in 9/15/2021, check the updated section about the solution.

How to check the version of the running node

Assuming the node is running with the 9933 HTTP rpc port open. You can run the CURL command as below:

1curl -d '{"jsonrpc": "2.0", "method": "system_version", "params": [], "id": 83}' -H "Content-Type: application/json" -X POST http://localhost:9933

Sample result:

1{"jsonrpc":"2.0","result":"0.1.5-250ab0b-x86_64-linux-gnu","id":83}