From 2b5e6d3259d590d98e3702f3a879c7b28372ec6a Mon Sep 17 00:00:00 2001 From: productshiv Date: Wed, 22 May 2024 00:16:19 +0530 Subject: [PATCH] Updated format on notifications --- categories/notifications/paths/v3_subscription_post.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/categories/notifications/paths/v3_subscription_post.yml b/categories/notifications/paths/v3_subscription_post.yml index 276f74e..b3a5850 100644 --- a/categories/notifications/paths/v3_subscription_post.yml +++ b/categories/notifications/paths/v3_subscription_post.yml @@ -82,7 +82,7 @@ description: \ and set to \"true\", the transaction is in the mempool; if set to \"false\" or\ \ does not appear at all, the transaction has been added to a block\n \"counterAddress\"\ : undefined // an optional counter party address \n // of the transaction; for EVM-based\ - \ blockchains, this is the recipient's address\n //UTXO based chains return without this parameter, since UTXO is \n //many-to-many by design. \"addressesRiskRatio\": [ // (optional,\ + \ blockchains, this is the recipient's address\n //UTXO based chains return without this parameter, since UTXO is \n //many-to-many by design. \n \"addressesRiskRatio\": [ // (optional,\ \ subject to change; for Solana mainnet only) risk levels assigned to the addresses\ \ with which the address communicated within the transaction; the addresses are\ \ assessed using the AML/CFT solution by blockmate.io, see https://docs.blockmate.io/docs/risk-API/sources\n\