Skip to content
This repository has been archived by the owner on Aug 28, 2023. It is now read-only.

Releases: 5afe/safe-client-gateway

Version 3.43.0

12 Dec 11:14
@fmrsabino fmrsabino
v3.43.0
a53e1ed
Compare
Choose a tag to compare
Version 3.43.0

What's Changed

CreateMessage.message payload now accepts Json objects

In addition to String, CreateMessage.message now also accepts Json objects (represented as BTreeMap) safe-global/safe-client-gateway#1027

Other Changes

Full Changelog: safe-global/safe-client-gateway@v3.42.0...v3.43.0

Assets 2
Loading

Version 3.42.0

06 Dec 10:49
@fmrsabino fmrsabino
v3.42.0
5f0258d
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Version 3.42.0

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 safe-global/safe-client-gateway#1001, safe-global/safe-client-gateway#1006, safe-global/safe-client-gateway#1012, safe-global/safe-client-gateway#1007, safe-global/safe-client-gateway#1008, safe-global/safe-client-gateway#1009, safe-global/safe-client-gateway#1011, safe-global/safe-client-gateway#1014, safe-global/safe-client-gateway#1019, safe-global/safe-client-gateway#1021, safe-global/safe-client-gateway#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 safe-global/safe-client-gateway#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) safe-global/safe-client-gateway#1010
  • This change just forwards this parameter to the clients

Other Changes

Full Changelog: safe-global/safe-client-gateway@v3.41.0...v3.42.0

Assets 2
Loading

Version 3.41.0

21 Nov 10:06
@fmrsabino fmrsabino
v3.41.0
eecc620
Compare
Choose a tag to compare
Version 3.41.0

What's Changed

Full Changelog: safe-global/safe-client-gateway@v3.40.0...v3.41.0

Assets 2
Loading

Version 3.40.0

14 Nov 09:57
@fmrsabino fmrsabino
v3.40.0
7a9090f
Compare
Choose a tag to compare
Version 3.40.0

What's Changed

Full Changelog: safe-global/safe-client-gateway@v3.39.0...v3.40.0

Assets 2
Loading

Version 3.39.0

07 Nov 09:20
@fmrsabino fmrsabino
v3.39.0
0db7d32
Compare
Choose a tag to compare
Version 3.39.0

What's Changed

Full Changelog: safe-global/safe-client-gateway@v3.38.0...v3.39.0

Assets 2
Loading

Version 3.38.0

31 Oct 10:42
@fmrsabino fmrsabino
v3.38.0
95a8e29
Compare
Choose a tag to compare
Version 3.38.0

What's Changed

Full Changelog: safe-global/safe-client-gateway@v3.37.0...v3.38.0

Assets 2
Loading

Version 3.37.0

24 Oct 10:14
@fmrsabino fmrsabino
v3.37.0
528ae09
Compare
Choose a tag to compare
Version 3.37.0

What's Changed

Full Changelog: safe-global/safe-client-gateway@v3.36.0...v3.37.0

Assets 2
Loading

Version 3.36.0

17 Oct 09:34
@fmrsabino fmrsabino
v3.36.0
4e5851d
Compare
Choose a tag to compare
Version 3.36.0

What's Changed

Full Changelog: safe-global/safe-client-gateway@v3.35.1...v3.36.0

Assets 2
Loading

Version 3.35.1

28 Sep 09:50
@fmrsabino fmrsabino
v3.35.1
e1f3ecf
Compare
Choose a tag to compare
Version 3.35.1

What's Changed

Invalidate Mainnet cache in /v2/flush

  • Fixes a bug where the /v2/flush was not invalidating Mainnet related cache data in safe-global/safe-client-gateway#970
  • With the introduction of two caches (one for Mainnet and the other one for all the other networks). The /v2/flush route was executing the invalidation only for all the other chains.

Full Changelog: safe-global/safe-client-gateway@v3.35.0...v3.35.1

Assets 2
Loading

Version 3.35.0

19 Sep 09:21
@fmrsabino fmrsabino
v3.35.0
0270311
Compare
Choose a tag to compare
Version 3.35.0

What's Changed

Full Changelog: safe-global/safe-client-gateway@v3.34.1...v3.35.0

Assets 2
Loading