You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it's possible to register a trigger that fires so often that it jams the network. This should be guarded against. When registering such triggers they should get rejected
The text was updated successfully, but these errors were encountered:
Does a data trigger reacts to every data event in the event pool at the round? -- inspect
Related to Trigger execution model #4937 and Record trigger execution as a transaction #4968:
One of the concepts of pooling events was preventing loop of trigger executions. If we want an event to be converted to an intrinsic transaction and inserted to the other ordered transactions without being pooled, it might come down to this issue
it's possible to register a trigger that fires so often that it jams the network. This should be guarded against. When registering such triggers they should get rejected
The text was updated successfully, but these errors were encountered: