Beats NFT Marketplace explores music collectibles through Sui objects and a web interface. Its source includes music-specific metadata and a marketplace implementation with seller payment records.
Implementation focus and source scope#
My implementation focus is the relationship between a music object and its sale. React, Next.js, TypeScript, and Sui Move support the project. This study follows the supplied beats-next repository's version-two Move modules.
The repository contains multiple contract versions. The existing public preview is retained as a product link, but this source review does not prove which module version that preview deploys.
Describe the music object#
The MusicNFT stores name, artist, genre, image and music URLs, creator address, and trait fields. Its module includes mint, burn, and metadata-update events, and a Display mapping for the music object's visible information.
These fields provide a data model for a collectible. They do not establish music licensing, ownership of external media, or royalty distribution merely by existing on the object.
Keep proceeds in the marketplace model#
The marketplace stores listed items and accumulated seller payments separately. Purchase requires the exact asking payment and records proceeds by seller address. Withdrawal uses the transaction sender to retrieve that seller's balance.
The inspected marketplace module identifies its foundation as an adapted Sui example. That attribution matters when describing the implementation rather than claiming every mechanism was designed from scratch.
Result and limits#
The source demonstrates music-object metadata and seller-proceeds mechanics. It does not establish a production royalty economy, measured artist compensation, or an independent contract audit.
The companion article explains music metadata and marketplace proceeds.