is the childTrieKey property of the archive_v1_storage.storage notification redundant? #170
Description
I'm probably missing something here, but will there ever be an instance in which the value of this field (childTrieKey property on thearchive_v1_storage.storage notification) differs from the value that has been passed as a parameter of the archive_v1_storage call?
If it's always the same, then I guess that this field is redundant... Is this the case?
If it's not redundant, then I guess that we should take that into account when designing v2 of chainHead, b/c the operationStorageItems notification doesn't have this field.
If it is redundant, then we should probably consider removing it in a hypothetical v2 of storage.