As the Kusama Runtime upgrade introduced new types that are not supported by pherry and pruntime in the 9866422 block, the pruntime version 0.1.1 exited abnormally. This issue has been resolved now. Please upgrade your pruntime to new version 0.1.3 ASAP!!! **
#Tracking Issue
opened 04:04PM - 29 Oct 21 UTC
relayer
P0
mining
accident
## Symptom
1. Miners and Gatekeepers relying on pherry are stuck at Kusama bl… ock 9866422 with error:
```
[2021-10-29T16:04:11Z INFO pherry] bridge() exited with error: Rpc error: Parse error: Decode error: Could not decode DigestItemType, variant doesn't exist
Caused by:
0: Parse error: Decode error: Could not decode DigestItemType, variant doesn't exist
1: Decode error: Could not decode DigestItemType, variant doesn't exist
```
2. Even on PRB where the block can be processed, pRuntime will also fail to sync block with error:
```
[2021-10-29T16:00:14Z INFO rocket::rocket] Matched: POST /bin_api/sync_combined_headers (sync_combined_headers)
[INFO phactory::bin_api_service] {"payload":"{\"message\":\"Decode input parameter
```
## Affected
- Miners cannot mine (pherry or prb)
- Gatekeepers are stuck
## Root cause
The new Kusama runtime introduces a new Digest Item, which is not decodable by the old block header definition (in both pruntime and subxt). pherry depends on subxt to decode the relay chain block header. pruntime depends on the raw block header definition to decode the inputs. Therefore when they panicked when 9866422 is reached.
## Solution
The team is working on a mitigation and a long term solution. The ETA of the mitigation is Oct 30 16:00 (UTC).
The Phala team will release a new quick fix that carry with the new Digest Item.
#Solution
sudo phala stop
sudo phala update
sudo phala start
#Note
