After Shell successfully processed the runtime upgrade to Statemint and handed over block production to the Statemint collators, they were not able to produce blocks due to a mismatch in key types. Specifically, Aura uses sr25519 keys to sign blocks, but the keys in the genesis chain spec were generated using ed25519.

A new runtime was created as a temporary fix. This runtime enables ed25519 in Aura for Statemint. This will be enacted on the Relay Chain so that validators will be able to validate the collator signatures. After the chain is producing blocks again, a follow up runtime upgrade will migrate Aura back to using sr25519 keys.

Call hash: `0x0e21b5233c7591ee89eca0cae71cf9a9a4c45fe2393075ab33361a673f5d322d`

Preimage:
![](https://i.imgur.com/pUVsJGR.png)

 Schedule a majority-carries referendum to be tabled next once it is legal to schedule
 an external referendum.

 The dispatch of this call must be `ExternalMajorityOrigin`.

 - `proposal_hash`: The preimage hash of the proposal.

 Unlike `external_propose`, blacklisting has no effect on this and it may replace a
 pre-scheduled `external_propose` call.

 # <weight>
 - `O(1)`.
 - One DB change.
 # </weight>

 Kill all storage items with a key that starts with the given prefix.

- Problem Statement: The intended audience is the Polkassembly community. The problem is that after a runtime upgrade to Statemint, Shell was unable to produce blocks due to a mismatch in key types. 
- Significance: This issue prevents block production, disrupting the operation of the Statemint chain.
- Proposed Solution: A temporary runtime that enables ed25519 in Aura for Statemint will be enacted on the Relay Chain. This will allow validators to validate the collator signatures. A subsequent runtime upgrade will revert Aura back to using sr25519 keys.
- Expected Outcomes: The solution will restore block production on the Statemint chain, ensuring its smooth operation.

#135 Fix Statemint - Aura Key Scheme