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 the currently externally-proposed majority-carries referendum to be tabled
immediately. If there is no externally-proposed referendum currently, or if there is one
but it is not a majority-carries referendum then it fails.

The dispatch of this call must be `FastTrackOrigin`.

- `proposal_hash`: The hash of the current external proposal.
- `voting_period`: The period that is allowed for voting on this proposal. Increased to
  `FastTrackVotingPeriod` if too low.
- `delay`: The number of block after voting has ended in approval and this should be
  enacted. This doesn't have a minimum amount.

Emits `Started`.

Weight: `O(1)`

- Shell successfully upgraded to Statemint but had trouble producing blocks.
- The issue was a mismatch in key types between Aura and the genesis chain spec.
- A temporary fix was created to enable ed25519 in Aura for Statemint.
- This will allow validators to validate collator signatures.
- A future upgrade will migrate Aura back to using sr25519 keys.

#30 Fix Statemint - Aura Key Scheme