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

not able to send extrinsics: WASM unreachable instruction #94

Closed
brenzi opened this issue Feb 23, 2022 · 4 comments
Closed

not able to send extrinsics: WASM unreachable instruction #94

brenzi opened this issue Feb 23, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@brenzi
Copy link
Member

brenzi commented Feb 23, 2022

trying to send balances.transfer

2022-02-23 13:55:20        RPC-CORE: submitAndWatchExtrinsic(extrinsic: Extrinsic): 
ExtrinsicStatus:: 1002: Verification Error: Runtime error: Execution failed: 
Other("Wasm execution trapped: wasm trap: wasm `unreachable` instruction executed\n
wasm backtrace:\n
    0: 0x23d8 - <unknown>!rust_begin_unwind\n
    1: 0x204b - <unknown>!core::panicking::panic_fmt::h8f11323637b4db3b\n
    2: 0x1c5ae1 - <unknown>!TaggedTransactionQueue_validate_transaction\n
"): RuntimeApi, Execution failed: 
Other, \"Wasm execution trapped: wasm trap: wasm `unreachable` instruction executed\\n
wasm backtrace:\\n
    0: 0x23d8 - <unknown>!rust_begin_unwind\\n
    1: 0x204b - <unknown>!core::panicking::panic_fmt::h8f11323637b4db3b\\…
@brenzi brenzi changed the title not able to send extrinsics: WASM unreachable not able to send extrinsics: WASM unreachable instruction Feb 23, 2022
@brenzi brenzi added the bug Something isn't working label Feb 24, 2022
@brenzi
Copy link
Member Author

brenzi commented Feb 27, 2022

suspicion: the runtime wasm is too old and doesn't match the runtime_api of the current collator

compare branches

git config --global diff.tool meld
git difftool -d 7db0768a85dc36a3f2a44d042b32f3715c00a90d 4aeb95f7f38fcd519e2628f32f79044a8fef99d5 -- .

given the error message, we should look at:

changes in node-template runtime:

  • state_version: 1,
  • apart from that, nothing obviously related

The removal of default for AccountID may be an issue?

And the decl_runtime_apis has a different version primitives/api/src/lib.rs

  • #[api_version(4)] vs #[api_version(3)]

@brenzi
Copy link
Member Author

brenzi commented Feb 27, 2022

it is unlikely that the runtime is really too old, as we had trouble with integritee too - where the runtime wasm is even older - and we were able to send a force_transfer extrinsic there: integritee-network/parachain#75

@brenzi
Copy link
Member Author

brenzi commented Feb 27, 2022

@brenzi brenzi closed this as completed Mar 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant