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
Entitlement migration pulls all entitlements that a migrated type needs
Disjunction access (e.g function needs access(Owner | Deposit)) is translated to conjunction authorization (auth(Owner, Deposit))
This is high priority, because we want to migrate capabilities with as few entitlements as possible, to minimize the chances of the migration causing safety issues for the migrated contracts. It is difficult to determine subset of entitlements actually needed.
Potential solutions:
Improve entitlement inference in entitlement migration in general
Don't include Owner entitlement in NFT. But other developers' contracts might have similar problem
Special case NFT in entitlements migration. But other developers' contracts might have similar problem
Impact: NFTs, majority of contracts
The text was updated successfully, but these errors were encountered:
Discord thread
context:
This is high priority, because we want to migrate capabilities with as few entitlements as possible, to minimize the chances of the migration causing safety issues for the migrated contracts. It is difficult to determine subset of entitlements actually needed.
Impact: NFTs, majority of contracts
The text was updated successfully, but these errors were encountered: