For the complete documentation index, see llms.txt. This page is also available as Markdown.

Change Logs

@May 10, 2022

Who needs to check it?

All who uses Ethereum Signature Validator API when this update is released.

Release plan

Staging Environment: 23 of May

Production Environment: 30 of May

What is updated?

  • A new property signMethod?: 'eth_sign' | 'personal_sign' is added in request.

  • A new property triedSignMethods?: string[] is added in response.

User can now specify either eth_sign or personal_sign in request body for EOA recovery logic. If not specified, both methods are used for validation.

Before

**Request Body Type**

`{message: string, signature: string, address: string }`

**Response Type**

`{ isValid: boolean, invalidReason: string | null }`

After

Example of request

"signMethod": "eth_sign" / Adding "signMethod": "eth_sign"

"signMethod": "personal_sign" / Adding "personal_sign": "eth_sign"

No signMethod: Validation result is the same as before.

Example of response

triedSignMethods property is not included the response if the validation process does not reach to signature validation part such as format issue as such.

Last updated

Was this helpful?