`refund` action issues with deferred transaction buildup
deckb opened this issue · 0 comments
deckb commented
When massive amounts of deferred transactions are happening on a network the refund
action can fail and result in a less than ideal UX. What options are available for users and network operators to alleviate this pain point?
Small list of options:
- Force users to call
refund
manually - remove
require_auth
fromrefund
and allow anyone to batchrefund
actions