Skip to content

Signing Message Error Under SafePal Environment #103

@zhangyouxin

Description

@zhangyouxin

Signing Message Error Under SafePal Environment

The method to call ethereum to sign a message is different in safepal:

// signing message in browser:
let signedMessage = await this.provider!.send('personal_sign', [address /* from */, messageForSigning /* message */]);
// signing message in safepal:
let signedMessage = await this.provider!.send('personal_sign', [messageForSigning /* message */]);

I used an Android device, open force-bridge dapp in SafePal APP, and when I tried to transfer my assets from nervos -> bsc, the message to be signed is as below:

actual

Thus causing the transaction to fail:

result

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions