Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use example balance-transfer compiler occur error in location. #338

Closed
DaviRain-Su opened this issue Nov 30, 2021 · 4 comments
Closed

Use example balance-transfer compiler occur error in location. #338

DaviRain-Su opened this issue Nov 30, 2021 · 4 comments

Comments

@DaviRain-Su
Copy link

DaviRain-Su commented Nov 30, 2021

This is my test repo: https://github.com/DaviRain-Su/example-subxt.git

warning: unused import: `EventSubscription`
 --> src/main.rs:4:5
  |
4 |     EventSubscription,
  |     ^^^^^^^^^^^^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

warning: `example-subxt` (bin "example-subxt") generated 1 warning
    Finished dev [unoptimized + debuginfo] target(s) in 0.78s
     Running `target/debug/example-subxt`
Error: Rpc(Request("{\"jsonrpc\":\"2.0\",\"error\":{\"code\":1010,\"message\":\"Invalid Transaction\",\"data\":\"Transaction has a bad signature\"},\"id\":5}"))
@jsdw
Copy link
Collaborator

jsdw commented Nov 30, 2021

Offhand I'm not certain what this is about! The only thought I can offer is to make sure that the metadata you used to generate the subxt types is from exactly the Polkadot binary that you are connecting to for your test.

@ascjones may well have a much better idea than me on the matter :)

@ascjones
Copy link
Contributor

It's probably because of #330.

You can try the commit before that PR to confirm. The fix we need to have it work for different versions of signed extensions is #331

@DaviRain-Su
Copy link
Author

Offhand I'm not certain what this is about! The only thought I can offer is to make sure that the metadata you used to generate the subxt types is from exactly the Polkadot binary that you are connecting to for your test.

@ascjones may well have a much better idea than me on the matter :)

Yes, I regenerated the scale file.

@DaviRain-Su
Copy link
Author

It's probably because of #330.

You can try the commit before that PR to confirm. The fix we need to have it work for different versions of signed extensions is #331

Thx, for you help, This is the reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants