Overview
Last updated
Last updated
BUK Protocol
BUK Protocol is a solution stack of modular components which can be used to mint, trade and perform DeFi transactions for all assets that expire aka dynamic assets. The protocol consists of multiple layers:
Smart contracts - Dynamic assets require unique provisions such as validity, burn / discount rate etc. in them across the lifecycle of tokenization, transfers, trading and monetization. These functionalities are not a part of standard ERC721 or ERC1155 contracts. BUK Protocol provides template contracts for various classes of dynamic assets.
Oracles - dynamic assets change their value not just based on market events (price volatility) but also inherently due to the nature of perishability. Hence price feed Oracles are key to operating an ecosystem for dynamic assets. BUK protocol provides Oracles with inbuilt capability to establish provenance, provide price-feeds, and control burn down and backhaul to web2 systems.
Marketplace features - BUK smart contracts include ability for producers to create new closed-loop marketplaces, as well as an aggregated marketplace with cross-marketplace liquidity. Thus asset creators can operate closed loop marketplaces or allow their dynamic assets to be traded on aggregated marketplaces directly. They can also choose a combination of having their closed marketplaces, but allow their assets to be listed on aggregated marketplace.
Connectors - BUK Protocol’s smart contracts have pre-built connectors with other web3 services such as DeFi staking protocols or game development protocols which developers to leverage to extend functionalities and utility of dynamic NFTs.
Assets which expire - event tickets, hotel bookings, airline tickets, memberships and subscriptions, air-miles or card points, time-share memberships, advertisement slots etc. - differ fundamentally from perpetual assets such as tokens, PFP NFTs, vehicle or land asset NFTs etc. Some of the differences are:
Perpetual assets hold value for the owner for unlimited time. Their value can be retained or escalate / fall persistently but never completely erode. Perishable assets however, have limited purpose - their value erodes over time, or based on usage. Think of:
Event tickets are valid only for a few hours of the event
Hotel or airline tickets which have value only until the travel date.
Subscriptions which erode every month in value whether you use it or not.
Trading in perpetual assets can continue for unlimited periods, but perishable assets must be traded within their lifespan.
Perpetual assets can be staked or collateralized without consideration of expiry. Perishable assets on the other hand have expiry and hence additional rules and operations will be necessary to ensure that action is taken on the asset before its value expires.
Given their ephemeral nature, perishable assets present unique opportunities. Perishable assets can have dynamic market values influenced by factors such as demand, in-game events, or real-world economic conditions.
Proof of ownership - even though the asset itself expires, the proof of (past) ownership is valuable and can open newer applications. For example - loyalty programs for travelers who have stayed in a hotel or discount on merch for fans who attended the event of an artist or band.
Cross-chain / Cross-game applicability - Perishable RWAs shall require cross-chain movement for better liquidity and utility. For example, if someone books an event ticket using a dApp on Polygon wants to resell their ticket, they must be able to list and sell it to users on Avalanche, Base or Arbitrum chains. Similarly, users who have funds on Etherium should be able to move these funds seamlessly to buy tickets from an L2 like Polygon, and receive their tickets on their own host chain.
