• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

safe-global / safe-client-gateway / 8171773380 / 2
89%
main: 89%

Build:
DEFAULT BRANCH: main
Ran 06 Mar 2024 12:14PM UTC
Files 1016
Run time 19s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

06 Mar 2024 12:07PM UTC coverage: 51.55% (-0.2%) from 51.73%
8171773380.2

push

github

web-flow
Guard adding/removing recovery contracts (#1247)

This adds guards to the following routes for addding/removing recovery contracts from Tenderly:

### `POST` `/v1/chains/:chainId/safes/:safeAddress/recovery`

A signature is required in order to successfully add a recovery contract. The following message need be signed (where ${} represents placeholder values for the respective data):

`enable-recovery-alerts-${chainId}-${safeAddress}-${moduleAddress}-${signer}-${timestamp}`

 To use this guard, the route should have:

- the `chainId` as part of the path parameters
- the `safeAddress` as part of the path parameters
- the `moduleAddress` as part of the JSON body (top level - unchanged)
- the `signer` as part of the JSON body (top level - new)
- the `Safe-Wallet-Signature` header set to the signature
- the `Safe-Wallet-Signature-Timestamp` header set to the signature timestamp

On top of this, the 'Safe-Wallet-Signature-Timestamp' need be within the past 5 minutes and the 'signer' an owner of the Safe.

### `DELETE` `chains/:chainId/safes/:safeAddress/recovery/:moduleAddress`

A signature is required in order to successfully remove a recovery contract. The following message need be signed (where ${} represents placeholder values for the respective data):

`enable-recovery-alerts-${chainId}-${safeAddress}-${moduleAddress}-${signer}-${timestamp}`

 To use this guard, the route should have:

- the `chainId` as part of the path parameters
- the `safeAddress` as part of the path parameters
- the `moduleAddress` as part of the JSON body (top level - unchanged)
- the `signer` as part of the JSON body (top level - new)
- the `Safe-Wallet-Signature` header set to the signature
- the `Safe-Wallet-Signature-Timestamp` header set to the signature timestamp

On top of this, the 'Safe-Wallet-Signature-Timestamp' need be within the past 5 minutes and the 'signer' an owner of the Safe.

258 of 2082 branches covered (12.39%)

Branch coverage included in aggregate %.

7094 of 12180 relevant lines covered (58.24%)

4.41 hits per line

Source Files on job run-test:e2e:cov - 8171773380.2
  • Tree
  • List 1016
  • Changed 3
  • Source Changed 2
  • Coverage Changed 137
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 8171773380
  • 3d01fc15 on github
  • Prev Job for on main (#8171663044.1)
  • Next Job for on main (#8172013728.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc