> For the complete documentation index, see [llms.txt](https://docs.startrail.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.startrail.io/ethereum-signature-validator-api/ethereum-signature-validator-api/change-logs.md).
# Change Logs
## 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.
{% hint style="info" %}
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.
{% endhint %}
### Before
```javascript
**Request Body Type**
`{message: string, signature: string, address: string }`
**Response Type**
`{ isValid: boolean, invalidReason: string | null }`
```
### After
```javascript
**Request Body Type**
`{message: string, signature: string, address: string, signMethod?: 'eth_sign' | 'personal_sign' }`
**Response Type**
`{ isValid: boolean, invalidReason: string | null, triedSignMethods?: string[] }`
```
#### Example of request
**"signMethod": "eth\_sign" / Adding "signMethod": "eth\_sign"**
```javascript
curl -X PUT -H "Content-type: application/json" --data '{"message": "test-message", "signature": "0x633bc7c201cf45fff0c1724b77c90c825a04c1b818f043915e2fedd55b4cfe681b425fe844ea3684a3860dc250527e318d3225b2d21ad0f75e419db4f0939a1b1c", "address": "0xBFC1331F8111102A51588b3b4A3E2F317B3a0363", "signMethod": "eth_sign"}' http://localhost:8080/
```
**"signMethod": "personal\_sign" / Adding "personal\_sign": "eth\_sign"**
```javascript
curl -X PUT -H "Content-type: application/json" --data '{"message": "test-message", "signature": "0x7cdf2aa9dfb2da8c6f8fe63269b4dbfb923451f0e36087479e7f2897718a6d0b6438bd44e367907e30c65a4b950c9e11f94049d38a0ca1dd4d419e107a3dade31c", "address": "0xBFC1331F8111102A51588b3b4A3E2F317B3a0363", "signMethod": "personal_sign"}' http://localhost:8080/
```
**No signMethod: Validation result is the same as before.**
```javascript
curl -X PUT -H "Content-type: application/json" --data '{"message": "test-message", "signature": "0x633bc7c201cf45fff0c1724b77c90c825a04c1b818f043915e2fedd55b4cfe681b425fe844ea3684a3860dc250527e318d3225b2d21ad0f75e419db4f0939a1b1c", "addres
s": "0xBFC1331F8111102A51588b3b4A3E2F317B3a0363"}' http://localhost:8080/
```
#### Example of response
```javascript
{ isValid: true, invalidReason: null, triedSignMethods: ['eth_sign'] }
{ isValid: true, invalidReason: null, triedSignMethods: ['personal_sign'] }
{ isValid: false, invalidReason: 'Signature is invalid', triedSignMethods: ['eth_sign', 'personal_sign'] }
{ isValid: false, invalidReason: 'Signature format is invalid' }
```
{% hint style="info" %}
triedSignMethods property is not included the response if the validation process does not reach to signature validation part such as format issue as such.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.startrail.io/ethereum-signature-validator-api/ethereum-signature-validator-api/change-logs.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.