search

sunshine-protocol / sunshine

Governance + Bounty Platform
Other
43 stars 16 forks source link

new structure && more #100

Closed 4meta5 closed 4 years ago

4meta5 commented 4 years ago
4meta5 commented 4 years ago

Current error from the bin/cli client

➜  sunshine-node git:(new-structure-to-match-convention) ✗ ./target/release/sunshine-cli wallet lock-shares 1 5Hb3LRTWW3QA8QEHUestBeTp8yos3dUa8iciQEsKRWEvm1FM   
Error: Rpc error: Server responded to our request with an error: Error { code: ServerError(1002), message: "Verification Error: Execution(ApiError(\"Could not convert parameter `tx` between node and runtime: No such variant in enum MultiSignature\"))", data: Some(String("RuntimeApi(\"Execution(ApiError(\\\"Could not convert parameter `tx` between node and runtime: No such variant in enum MultiSignature\\\"))\")")) }

and the node is run on -lruntime=debug so it's CLI shows

2020-06-18 19:22:32.955 tokio-runtime-worker WARN sc_rpc::author  Failed to submit extrinsic: Extrinsic verification error: Execution(ApiError("Could not convert parameter `tx` between node and runtime: No such variant in enum MultiSignature"))
Encountered an error: connection reset
Enable a logger to see more information.

I'm pretty sure it's happening because of some discrepancy between the runtime for the CLI and the node's runtime...

The same error is emitted when I try to submit the call from the client

For both the client and the CLI, I'm hard-coding it to be initialized with Alice's keys => I'm assuming this key is the sudo on the dev-chain. This needs to be verified.

4meta5 commented 4 years ago

Cool, thanks for the help @dvc94ch things are looking up :)