If event heap accounts length is > 20 there could be some user feedback or we could set an indicator (or flag) in the UI informing people a crank should be performed.
Basically this would resolve into a UI component notifying users (as an indicator) that there IS something that needs to be cranked.
Currently the only way to know is if you crank and then look at the TX logs that there was nothing done.
When we build the transaction we actually should know how many events need to be cranked, so in theory we could fetch this periodically (or on load) so a user would know the crank would be worth doing.
If event heap accounts length is > 20 there could be some user feedback or we could set an indicator (or flag) in the UI informing people a crank should be performed.
Basically this would resolve into a UI component notifying users (as an indicator) that there IS something that needs to be cranked.
Currently the only way to know is if you crank and then look at the TX logs that there was nothing done.
When we build the transaction we actually should know how many events need to be cranked, so in theory we could fetch this periodically (or on load) so a user would know the crank would be worth doing.
https://github.com/metaDAOproject/meta-dao-frontend/blob/a8c7f14a371fbc16a8cc399366d61ff3978d7361/hooks/useOpenbookTwap.ts#L182
https://the-meta-dao.canny.io/admin/board/ui-ux/p/add-detail-to-ui-element-informing-user-of-crank