From 620d60994c3bc9dc1583ebb6dc567367fcdc67f7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ux=C3=ADo?= Date: Thu, 6 Jun 2024 10:56:30 +0200 Subject: [PATCH] Update README.md - Fix `failed` type for `EXECUTED_MULTISIG_TRANSACTION` - Update default `timeout` from `5` -> `2` --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index a4b5a6f..5e3fd1e 100644 --- a/README.md +++ b/README.md @@ -32,7 +32,7 @@ If you want to integrate with the events service, you need to: - Endpoint need to answer with: - `HTTP 202` status - Nothing in the body. - - It should answer **as soon as posible**, as events service will timeout in 5 seconds, if multiple timeouts are detected **service will stop sending requests** to your endpoint. So you should receive the event, return a HTTP response and then act upon it. + - It should answer **as soon as posible**, as events service will timeout in 2 seconds, if multiple timeouts are detected **service will stop sending requests** to your endpoint. So you should receive the event, return a HTTP response and then act upon it. - Configuring HTTP Basic Auth in your endpoint is recommended so a malicious user cannot post fake events to your service. ## Events supported @@ -62,7 +62,7 @@ Some parameters are common to every event: "address": "", "type": "EXECUTED_MULTISIG_TRANSACTION", "safeTxHash": "<0x-prefixed-hex-string>", - "failed": , + "failed": "true" | "false", "txHash": "<0x-prefixed-hex-string>", "chainId": "" }