The Brand Protocol Litepaper
  • The Brand Protocol
  • Problem
  • Hang Corp
    • Overview
    • Relationship with the Brand Protocol
  • Hang Foundation
    • Overview
    • Bounties
  • The Protocol
    • Overview
    • Sequencer
    • Sentinel Nodes
    • Bridge
    • Brand Oracle
    • Primitives
      • Tokens
        • RWAs
        • Brand Credits
        • User Status
      • Permissioned Marketplace
      • Brand DeFi Protocol
    • Fees
  • The Portal
    • Overview
    • Functionality
    • API Usage
      • Examples
    • Pricing
Powered by GitBook
On this page
  • Overview
  • Onchain Data
  • Oracle Data
  1. The Protocol
  2. Primitives

Permissioned Marketplace

Overview

The Brand Protocol's Permissioned Marketplaces allow brands and developers to create custom marketplaces with controls over access and market dynamics. Marketplace permissions can be based on both onchain data (eg user status, balance, NFTs held) and offchain data from the Brand Oracle (eg total sales figures, AOV trends).

Onchain Data

Brands can set the dynamics of assets sales based on onchain data. For example, brands can configure whether tokenized rewards are allowed to be sold to non-loyalty members or bridged off-chain. Brands can also create custom rules that govern the sale of tokens, for example giving a value boost to tokens for tokens sold to wallets that hold a certain NFT.

Oracle Data

Brands can use the Oracle as an input for the terms of their marketplace. For example, a brand could limit the sales of founders-series tokens so that they are no longer tradable after the brand hits $100k dollars in real-world sales. Brands could also create a reward marketplace whose fees are determined as a percentage of real-world AOV.

PreviousUser StatusNextBrand DeFi Protocol

Last updated 11 months ago