-
Notifications
You must be signed in to change notification settings - Fork 0
I use contract verify signature, but the address is not correct? #63
Comments
I’ve pushed a test into “developer” branch, it gives an idea of how to get a signature, get V, R, S from it and test it locally. I’ve also separately tested it with ethereumjs-util and got the same result |
I expect to also deploy a contract on Rinkeby to cross-verify it |
Hello @wufeiafei I've tested everything, it worked as expected. Here is a solidity contract for ECRecover
In test you can also find an example of how to properly parse a signature and pass it to the contract in the
Merged in #66 Sincerely, Alex |
I test your exapmle, the result is ok。 this is logs: |
Hello @wufeiafei I've exposed function unmarshalSignature and marshalSignature as a part of Web3.Utils. |
I test your exapmle, the result is ok。 |
Thank you very much. |
hi,
I use web3swift method "Web3Signer.signPersonalMessage" make a signature, then I use the contract method "validate", but the result is not correct, the address is different with the signature address.
this is my contract:
pragma solidity ^0.4.17;
contract BBQ {
//验签数据入口函数
function validate(uint8 v,bytes32 r,bytes32 s,uint number) view returns (address,bool){
}
and this is my swift code:
======
pls, help me check it?
The text was updated successfully, but these errors were encountered: