Investigate if a node upgrade fixes the serde decoding errors.

[gianfra-t]

Context

After the upgrade, we removed serde renaming to camelCase on some primitives from Spacewalk (see this discussion).

This was done to solve an issue in which the pendulum and spacewalk-standalone binaries were unable to start due to this re-definition, since after the upgrade, it is required to serialize the genesis config.

Although this removal did not impact anything initially, and integration tests worked correctly, the vault failed when connecting to the live nodes. Error seen from the vault's logs:

ERROR vault::system: start(): Failed to run service: Retry(RuntimeError(SubxtRuntimeError(Serialization(Error("unknown variant `xCM`, expected one of `Native`, `XCM`, `Stellar`, `ZenlinkLPToken`, `Token`", line: 1, column: 99)))))

Therefore, a rollback was implemented. This fixes the vault's connection issue, yet breaks the runtimes again (see this test, for example).

To Do's

We believe the binary of the nodes running is the issue, since they have not yet been upgraded. Only with the upgrade to 1.6.0 the renaming is removed, but the live nodes were compiled with a version of Spacewalk in which the primitive types do have the renaming macro enabled. This mismatch might be causing this issue.

In order to test (and potentially fix) this, we must:

• Upgrade one of the nodes to 1.6.0. For example, one Foucoco collator.
• Test the vault against this new updated node. The vault to test must be the one compiled at this commit hash, or any that includes the upgrade and the removal of serde renaming.

[gianfra-t]

@pendulum-chain/product this is not urgent but must be done soon, since right now the solution implemented is not permanent.