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
Currently, functions in LicenseAttachmentWorkflows require a licensing config to be included when attaching licenses. This increases gas costs for users who only want to attach a license without setting a licensing config.
To optimize, we propose separating setLicensingConfig into separate workflow functions. For example, introducing a new function like registerPILTermsAndAttachAndSetConfigs would allow users to attach a license while setting configurations only when necessary.
The text was updated successfully, but these errors were encountered:
Description and context
Currently, functions in
LicenseAttachmentWorkflows
require a licensing config to be included when attaching licenses. This increases gas costs for users who only want to attach a license without setting a licensing config.To optimize, we propose separating
setLicensingConfig
into separate workflow functions. For example, introducing a new function likeregisterPILTermsAndAttachAndSetConfigs
would allow users to attach a license while setting configurations only when necessary.The text was updated successfully, but these errors were encountered: