Among the custom modules, only the archway.cwerrors.v1.Query/Errors Stargate query is enabled to be used from smart contracts. Having them available is important to allow building more sophisticated contracts.
From my experience, that issue limited the use of the callback module, since currently there's no way to query the estimated fee to be attached to the registration msg (QueryEstimateCallbackFeesRequest query). It still can be queried from outside the contract (e.g. from a frontend), but it's not the case if you have recurring automated registrations.
Exposing the Params query would be useful as well, at least to validate the automation intervals against the max_future_reservation_limit module param.
But it's not just about callback module ofc, I'm sure it will be a useful to whitelist queries for all the custom modules, if they are safe to use from cosmwasm.
Among the custom modules, only the
archway.cwerrors.v1.Query/ErrorsStargate query is enabled to be used from smart contracts. Having them available is important to allow building more sophisticated contracts.From my experience, that issue limited the use of the
callbackmodule, since currently there's no way to query the estimated fee to be attached to the registration msg (QueryEstimateCallbackFeesRequestquery). It still can be queried from outside the contract (e.g. from a frontend), but it's not the case if you have recurring automated registrations.Exposing the Params query would be useful as well, at least to validate the automation intervals against the
max_future_reservation_limitmodule param.But it's not just about
callbackmodule ofc, I'm sure it will be a useful to whitelist queries for all the custom modules, if they are safe to use from cosmwasm.