@vedhavyas
same error. those demos exist error in gsrpc-go-dev-demo， because v13 for CreateStorageKey breaks compatibility. types.CreateStorageKey(meta, "System", "Account", account.PublicKey, nil)
error info:

Account is a map, therefore requires precisely one argument. received: 2

I'm reverting the breaking change, keeping the metadata v13 make a release in a bit. Thank you!

Sorry about this 🙏🏼

@vgeddes @vedhavyas I have fixed CreateStorageKey to be backward compatible.
And also fixed that regression as well.

PR to make it backward compatible: #166

@vgeddes @vedhavyas @ThreeAndTwo PR: #169 adds comprehensive test cases for CreateStorageKey.

@vgeddes @ThreeAndTwo can you confirm if the regression is fixed with the PR above ?

@vgeddes @ThreeAndTwo can you confirm if the regression is fixed with the PR above ?

@vedhavyas The regression was already fixed via PR: #166
But, it was not covered by tests. PR: #169 aims to cover the new changes made in CreateStorageKey with tests.

@vedhavyas @ParthDesai I tested it. CreateStorageKey is normal, but I find decimal have inaccurate for token.
current balance: 855.359271
before balance: 8.55359271
in fact balance: 8.55359271

@vedhavyas @ParthDesai I tested it. CreateStorageKey is normal, but I find decimal have inaccurate for token.
current balance: 855.359271
before balance: 8.55359271
in fact balance: 8.55359271

This may not be related to CreateStorageKey at all.

This may not be related to CreateStorageKey at all.

True.

@ThreeAndTwo double check your type please. Its usually the case

closing this since its confirmed to be fixed in latest patch.

@ThreeAndTwo please open an new issue if the above mentioned decimal issue still exists.

yeah, everything is ok, thx.