Substrate `storage.<pallet>.<item>.<version>.is(block)` false positive

[khssnv]

Describe the bug

The call storage.mypallet.myitem.v1.is(blockHeader) (where storage is imported from types generated by squid-substrate-typegen) returns true at block at height where it expected to return true for v2 (which added new fields to myitem type) only.

To Reproduce

1. Setup the project.

   git clone --branch debug/khssnv-squid-sdk-bug-report https://github.com/Cerebellum-Network/cere-squid-indexer.git
   cd cere-squid-indexer
   npm i

2. Launch processor.

   docker compose up -d db
   sqd process

3. See error message.

   ...
   Unexpected storage layout version selection. Selected v48013 for spec version 54116 which is higher than the next v48017.
   ...

Please tell if this one is too large and I'll prepare a minimal reproducible example.

Expected behavior

In my specific case with the project set up above, the storage.ddcCustomers.buckets.v48013.is(block) call is expected to return false instead of true at height 5,238,731 and return true at storage.ddcCustomers.buckets.v54100.is(block).

Environment (please complete the following information):

• specify the version of the core packages: "@subsquid/substrate-processor": "8.3.0", "@subsquid/substrate-typegen": "8.1.0", "@subsquid/substrate-metadata-explorer": "3.2.0"
• node.js version 16
• npm version 10.8
• OS version Linux x1 6.5.0-1027-oem #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 25 13:32:46 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
• Reproducible example or a repo link https://github.com/Cerebellum-Network/cere-squid-indexer

Applicable to decoding issues:

• chain name cere-dev
• typesBundle (if it's not built-in) https://github.com/Cerebellum-Network/cere-squid-indexer/blob/dev/specs/cere-types-bundle.json
  optional:
• block 5,238,731
• event ddcCustomers.BucketCreated
• spec version 54116
• endpoint wss://archive.devnet.cere.network/ws

[belopash]

As a workaround you can check v2 before v1, This is happening because v1 type implements v2

[khssnv]

Thanks! Looks like it is vice versa,v2 implements v1 since v2 has all the fields of v1 plus some extra.

In my specific case a lower version omits some fields of the upper version: v48013.Bucket, v54100.Bucket.