Send pre-construction extrinsic to parentchain after upgrading parentchain

[ziming-zung]

Context

Now, tee-worker send extrinsic to parentchain in this function:
https://github.com/litentry/litentry-parachain/blob/25bf6e0e8137209a0cc1c60cc2c89729ddc83fc6/tee-worker/enclave-runtime/src/top_pool_execution.rs#L245-L276

From the logic of the function, we know that:

• After producing block successfully, tee-worker will broadcast block to peers
• construct extrinsic from opaque calls
• send extrinsic to parentchain

The flow above has a potential bug. Let's imagine:

• If parentchain runtime version is 1 and the create_identity call type is:

pub fn create_identity(origin: OriginFor<T>, shard: ShardIdentifier, user: T::AccountId, identity: Vec<u8>)

• We use this call type to construct an extrinsic, try to send it to parentchain later.

• Before sending above extrinsic to parentchain, the parentchain upgraded. Now parentchain runtime version is 2 and the create_identity call type have changed to:

pub fn create_identity(origin: OriginFor<T>, shard: ShardIdentifier, user: T::AccountId, identity: Vec<u8>, metadata: Option<Vec<u8>>)

• At this time, tee-worker try to send above extrinsic to parentchain and it should receive an error from parentchain. Beacause the call type doesn't match

• Finally, the storage values of the sidechain and the parentchain are inconsistent. Use the example above, it means that Identity only exist on sidechain, not parentchain

I still don't have any ideas on this issue. Drop extrinsic directlly?

[github-actions]

❗ This issue is stale because it has been open for 60 days with no activity.
Remove Stale label or update it, otherwise this issue will be closed in 7 days.
@litentry/parachain