You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in the current implementation, sidechain block production uses an StfExecutor which only knows Integritee metadata. This prevents the STF from sending extrinsics (i.e.unshielding) to TargetA/B if metadata call indices are not compatible.
Two more problems are related, to keep in mind:
metadata is fundamentally mutable, so it can change over time (runtime upgrades) and we may not want to hard-cycle all service instances to update
A bridge OCW STF between TargetA and TargetB will need the indirect executor of TargetA to trigger STF functionality which sends extrinsics to TargetB and vice versa.
Complexity:
Our Architecture currently has one StfExecutor per parentchain which only knows metadata for own scope.
For SCV, the application dev has to decide on one parentchain's StfExecutor for block proposals which restricts the STF to a single parentchain as extrinsic target
Shortcut:
for Incognitee, we can just route sidechain proposer StfExecutor to TargetA in get_stf_executor_from_solo_or_parachain
better: use the parentchain specified by --shielding-target
Questions
should NodeMetadataRepo be mutable?
then we could link all 3 metadata repos after initialzation so every executor knows all metadata
The text was updated successfully, but these errors were encountered:
needed if we want to implement i.e. bridges
Problem:
in the current implementation, sidechain block production uses an StfExecutor which only knows Integritee metadata. This prevents the STF from sending extrinsics (i.e.unshielding) to TargetA/B if metadata call indices are not compatible.
Two more problems are related, to keep in mind:
Complexity:
Our Architecture currently has one StfExecutor per parentchain which only knows metadata for own scope.
For SCV, the application dev has to decide on one parentchain's StfExecutor for block proposals which restricts the STF to a single parentchain as extrinsic target
Shortcut:
for Incognitee, we can just route sidechain proposer StfExecutor to TargetA in
get_stf_executor_from_solo_or_parachain
better: use the parentchain specified by
--shielding-target
Questions
The text was updated successfully, but these errors were encountered: