5afe/safe-client-gateway v3.42.0

Version 3.42.0

on GitHub

What's Changed

Support for EIP-1271 Messages (preview)

Support for EIP-1271 Messages was added. This feature is currently in preview – in order to enable this feature you
should set the environment variable FEATURE_MESSAGES to true.

Enabling this feature, mounts the following routes:

GET /v1/chains/<chain_id>/safes/<safe_address>/messages

Returns a collection of messages that were signed by owners of the safe_adress.

{
  "next": null,
  "previous": null,
  "results": [
    {
      "type": "DATE_LABEL",
      "timestamp": <number>
    },
    {
      "type": "MESSAGE"
      // see message payload below
    }
  ]
}

GET /v1/chains/<chain_id>/messages/<message_hash>

Returns the message item that matches message_hash

{
  "messageHash": <string>,
  "status": <string>, // CONFIRMED or NEEDS_CONFIRMATION
  "logoUri": <string>, // optional
  "name": <string>, // optional
  "message": <string  or json object>,
  "creationTimestamp": <number>,
  "modifiedTimestamp": <number>,
  "confirmationsSubmitted": <number>,
  "confirmationsRequired": <number>,
  "proposedBy": {
    "value": <string>,
    "name": <string>, // optional
    "logoUri": <string> // optional
  },
  "confirmations": [
    {
      "owner": {
        "value": <string>,
        "name": <string>, // optional
        "logoUri": <string> // optional
      },
      "signature": <string>
    }
  ],
  "preparedSignature": <string> // optional
}

POST /v1/chains/<chain_id>/safes/<safe_address>/messages

Creates a message for safe_address. The payload is as follows:

{
    "message": <string>,
    "safeAppId": <number>, // optional
    signature: <string>,
}

POST /v1/chains/<chain_id>/messages/<message_hash>/signatures

Updates the message with message_hash with a signature. The signature must come from an owner of the Safe that
contains the message_hash.

The payload is as follows:

{
  "signature": "<string>"
}

See #1001, #1006, #1012, #1007, #1008, #1009, #1011, #1014, #1019, #1021, #1020

Safe Info endpoint now returns a message tag (preview)

• The Safe Info endpoint GET /v1/chains/<chain_id>/safes/<safe_address> now returns a messages_tag if FEATURE_MESSAGES is set to true #1013
• The tag is generated by retrieving the most recently modified message
• If the retrieval is successful the respective UNIX timestamp is returned, else the current UNIX timestamp is returned

MultisigExecutionDetails now has a trusted field

• The trusted parameter is already part of a MultisigTransaction transaction (in the Safe Transaction Service) #1010
• This change just forwards this parameter to the clients

Other Changes

• Bump rust from 1.63.0 to 1.65.0 in #999
• Bump serde_json from 1.0.87 to 1.0.88 in #1002
• Bump ethabi from 16.0.0 to 18.0.0 in #1003
• Bump reqwest from 0.11.12 to 0.11.13 in #1004
• Bump serde_json from 1.0.88 to 1.0.89 in #1015
• Bump serde from 1.0.147 to 1.0.148 in #1018
• Bump ethcontract-common from 0.15.4 to 0.23.0 in #1017
• Bump env_logger from 0.9.3 to 0.10.0 in #1016
• Use Ubuntu 20.04 for Github Actions in #1024

Full Changelog: v3.41.0...v3.42.0