DAO Vote #6 - New Feature: Multiple Collections In Offers

Introduction

In building up Web3’s commerce layer, Boson Protocol is mindful of the importance of royalties. We aspire to support creators, artists, manufacturers, all sellers to be appropriately compensated from secondary sales.

We are now asking the community to vote on proceeding with the first step on our path to unlock the full potential of royalties in Web3: enabling multiple collections in offers, described in Boson Protocol Improvement Proposal 6.

Executive Summary

Currently, when a seller creates offers, they are all tied to a single Boson Voucher contract. While this is efficient, it offers very little in terms of flexibility when integrating with external projects like marketplaces. Implementing a new feature that would allow for multiple collections in seller’s offers will enable grouping items in corresponding collections and thus allow for royalties to be set at collection level.

Technical details and looking forward

Boson Vouchers are already compatible with ERC-721 non-fungible token standard and ERC-2981 NFT royalty standard, which provide comparatively good interoperability with the Web3 ecosystem. Hower, a comprehensive commerce infrastructure that Boson Protocol is aiming to build, requires quite a bit of flexibility that could eventually support massive, real-life scenarios. Even more so in Web3 where royalties can be built-in and thus provide unmatched reliability when comparing with legacy networks.

With that in mind, supporting multiple collections when making offers is in our view an important but only a first step on this path and you are welcome to read about what is in the works afterwards, like flexible royalties (BPIP-5) and enforcement of perpetual royalties via sequential commits (BPIP-7).

Proposal Details

Should Boson Protocol implement multiple collections in offers? Option A: Yes

Option B: No