GithubDiscordTwitterDapp
Searchโ€ฆ
๐Ÿ‘‘
Index
๐Ÿช™
Protocol Info
๐Ÿ“ˆ
OS Economics
๐Ÿ”ฎ
EthereansOS Governance
๐Ÿ”ข
EthereansOS Addresses
๐Ÿค–
Factories
Factories Learn
Factories Documentation
Addresses
๐Ÿ‘พ
Items
Items Learn
Items Documentation
Understanding Items
Overview
Why Is the Item Standard Needed?
The Main Interface and Item Collections
The Main Interface and the Interoperable Interfaces
Hosting
Why Have the Extension?
Extend the Extension's Permissions
Native Items vs Wrapped vs Decks
v2 Items vs v1 Items
Item V2 Smart Contracts Protocol
Dynamic On-chain Metadata
Frontend Integration
Addresses
๐Ÿ‘ป
Guilds
Guilds Learn
Guilds Documentation
Addresses
โœจ
Covenants
Covenants Learn
Covenants Documentation
Addresses
๐Ÿ‡จ๐Ÿ‡ณ
Chinese Version
็ดขๅผ•
ๅ่ฎฎไฟกๆฏ
ๅทฅๅŽ‚ๅญฆไน 
Itemๅญฆไน 
ๅฅ‘็บฆๅญฆไน 
Guildsๅญฆไน 
Powered By GitBook
Extend the Extension's Permissions
The operator address of a Collection Extensionโ€™s permission can be a smart contract. In this case, the smart contract's logic determines the permission operation and how the permission is managed.
An example of this would be an Organizationโ€™s subDAO managing the minting permissions for a Collection using a MultiOperatorHost Extension.
Previous
Why Have the Extension?
Next
Native Items vs Wrapped vs Decks
Last modified 6mo ago
Copy link