From 713ae49d3b9861fffebaf841a1a2e083686daf9e Mon Sep 17 00:00:00 2001 From: Ekaterina Mekhnetsova Date: Wed, 10 Aug 2022 11:32:54 +0300 Subject: [PATCH] [docs] #59: Update statements about triggers Signed-off-by: Ekaterina Mekhnetsova --- src/guide/advanced/triggers.md | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/src/guide/advanced/triggers.md b/src/guide/advanced/triggers.md index cc740c7f6..433341024 100644 --- a/src/guide/advanced/triggers.md +++ b/src/guide/advanced/triggers.md @@ -144,19 +144,15 @@ got registered, an asset got transferred, the Queen of Hearts decided to burn all of her assets. These types of events account for the vast majority of triggers in -Ethereum, and were the first to be implemented. As of today, we only -support un-scoped system-wide triggers with no permission validation. Work -is ongoing to make the triggers safer and more reliable, but the process is -time-consuming and work-intensive. - - +Ethereum, and were the first to be implemented. The LTS version of Iroha +only supports un-scoped system-wide triggers with no permission validation. ::: info Be mindful of the limitations. Currently triggers don't check for permissions , so they can do things your account -wouldn't be allowed to. Since the triggers are not scoped, every trigger -processes _every_ event, and the amount of work grows quadratically. +wouldn't be allowed to. Un-scoped triggers process _every_ event, and the +amount of work grows quadratically.