From 62e3ffb714dc91c405983adf9b248bcf6132b20f Mon Sep 17 00:00:00 2001 From: Dzeka <132560112+dzekicb@users.noreply.github.com> Date: Tue, 10 Sep 2024 10:09:11 +0200 Subject: [PATCH] Update README.md --- uniswap-factory-pool-monitoring/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/uniswap-factory-pool-monitoring/README.md b/uniswap-factory-pool-monitoring/README.md index fd6d78a..5b3763f 100644 --- a/uniswap-factory-pool-monitoring/README.md +++ b/uniswap-factory-pool-monitoring/README.md @@ -37,7 +37,7 @@ actions: function: example:actionFn trigger: type: alert - alert: + alert: { } execution_type: parallel project_slug: "" ``` @@ -77,4 +77,4 @@ You can monitor the execution of your Web3 Action in the Tenderly dashboard unde ## Note on Alert as Trigger The alert you created in Step 1 serves as the trigger for your Web3 Action. Whenever the specified event (PoolCreated) is emitted by the UniswapV3Factory contract, Tenderly will detect it through the alert system. This alert then automatically triggers the execution of your Web3 Action, allowing you to respond to new pool creations in real-time without manual intervention. -This setup provides a powerful way to automate interactions with the Uniswap V3 ecosystem, enabling you to stay updated on new pool creations and perform custom actions as needed. \ No newline at end of file +This setup provides a powerful way to automate interactions with the Uniswap V3 ecosystem, enabling you to stay updated on new pool creations and perform custom actions as needed.