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
Today I've fetched Acala metadata through rpc call from public node and received different response then last Thursday. Apparently, some pallets changed. Yet, spec_version is still the same as before. This breaks Signer functionality and is unsafe.
Expected Behavior
Metadata should always be uniquely identified by spec_name and spec_version, any changes in metadata should be reflected with version bump.
There should be some mechanism to prevent this in future. I've reported similar bug in Polkadot and Kusama previously and those were fixed and covered with tests somehow, I do not know the details.
Current Behavior
CollateralCurrencyIds value is different in 2 places
Steps to Reproduce
Fetch metadata from current block
Fetch metadata from previous blocks
Compare
I used to keep a log of metadata, but only for 3 networks and I do not do it anymore.
Additional context
Node version: 2064
Code to check metadata diff:
let acala_meta_old = RuntimeMetadataV14::decode(&mut &acala_old[5..]).unwrap();
let acala_meta_new = RuntimeMetadataV14::decode(&mut &acala_new[5..]).unwrap();
for pallet_old in acala_meta_old.pallets.iter() {
let index = pallet_old.index;
for pallet_new in acala_meta_new.pallets.iter() {
if pallet_new.index == pallet_old.index {
if pallet_new != pallet_old {
println!("pallet name new: {}", pallet_new.name);
println!("in new:\n{:?}", pallet_new);
println!("in old:\n{:?}", pallet_old);
}
}
}
}
Describe the bug
Today I've fetched Acala metadata through rpc call from public node and received different response then last Thursday. Apparently, some pallets changed. Yet,
spec_version
is still the same as before. This breaks Signer functionality and is unsafe.Expected Behavior
Metadata should always be uniquely identified by
spec_name
andspec_version
, any changes in metadata should be reflected with version bump.There should be some mechanism to prevent this in future. I've reported similar bug in Polkadot and Kusama previously and those were fixed and covered with tests somehow, I do not know the details.
Current Behavior
CollateralCurrencyIds
value is different in 2 placesSteps to Reproduce
I used to keep a log of metadata, but only for 3 networks and I do not do it anymore.
Additional context
Code to check metadata diff:
Observed diff:
The text was updated successfully, but these errors were encountered: