currently all of the actions/intets are scheduled through the MagicContext account, that gets scanned periodically and drained which is suboptimal, we need to adopt an approach used by task scheduler, where the tasks are scheduled immediately through the utilization of thread local storage in the transaction executor itself.
currently all of the actions/intets are scheduled through the MagicContext account, that gets scanned periodically and drained which is suboptimal, we need to adopt an approach used by task scheduler, where the tasks are scheduled immediately through the utilization of thread local storage in the transaction executor itself.