How to structure data for contract.signed_call

Question

How to structure data for contract.signed_call

romanzac opened this issue 2 years ago · comments

Hi there,

May I get some help with data structure ? I am getting rejected by blockchain API on invalid data.

My ABI is:

{"constant":false,"inputs":[{"name":"index","type":"uint256"}],"name":"forceWithdraw","outputs":[],"payable":false,"stateMutability":"nonpayable","type":"function"}

My call is:

let withdraw_res = sc.signed_call(
"forceWithdraw",
Tokenize::into_tokens("100000000".to_string()),
Options::default(),
SecretKeyRef::new(&prvk))
.await
.unwrap();

Rees LaBree · Answer 1 · Fri Apr 15 2022 00:54:33 GMT+0800 (China Standard Time)

Were you ever able to figure this out? Would appreciate some guidance since the documentation is pretty sparse.

Roman Zajic · Answer 2 · Fri Apr 15 2022 07:26:31 GMT+0800 (China Standard Time)

Yes, I moved over to another library: https://crates.io/crates/ethers
Supportive community. I am happy using it.

Rees LaBree · Answer 3 · Fri Apr 15 2022 10:50:38 GMT+0800 (China Standard Time)

Lol. If anyone should happen to stumble across this in the future, there's something up with the versioning on secp256k1.

To get this to work, you must use secp256k1 = "0.21.1" in your toml, and the key must be typed as let prvk: secp256k1::SecretKey = .... The key parameter in signed_call is then SecretKeyRef::new(&prvk)).