GithubDiscordTwitterDapp
Search…
⌃K
Links
👑
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
🌀
Colonies
Colonies
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 1yr ago
Copy link