A platform to make Original and Cover Music Visible and Valuable
There are lots of talented artists on the Internet. They often upload their cover songs to media platforms such as Youtube, Soundcloud, StreetVoice, and so on. Nonetheless, there is no such a system that utilizes the relation between original and covers, rendering either a well-known song with many cover versions without people knowing who the original composer is, or a popular original song with people having a hard time finding other cover versions.
To this end, we create MusicChain, which employs blockchain to record the relations of original and cover songs in a graph. Furthermore, we develop a profit-sharing mechanism based on this cover song relation graph, which is quite a novel idea to our best knowledge. Specifically, both the original artists and the cover artists benefit from this system, which we believe can stir the motivation for music creation. As a result, we make original and cover music more visible and valuable.
Demo Link : Youtube (In Mandarin) Github : repo
- First make sure you start your docker and Ganache. Then execute
- After docker container starts running, execute the folling commands to alter IPFS settings. This settings is to bypass the CORS policy to let frontend can directly talk to the backend from different origins.
docker exec ipfs_host ipfs config --json API.HTTPHeaders.Access-Control-Allow-Origin '["*"]' docker exec ipfs_host ipfs config --json API.HTTPHeaders.Access-Control-Allow-Methods '["PUT", "GET", "POST", "OPTIONS"]'
- Finally restart docker container. If you start the docker-compose without datached, you may need to open another terminal and change to the project directory and then run this command.
docker-compose restart ipfs
Start MusicChain website
With Ganache and docker container running (backend & ipfs), go to
./react and execute
$ npm start
MusicChain is then running at http://localhost:3000/
Clean backend database data
Notice that you should also restart your blockchain
npm run format
- Material UI
We put our project architecture diagram in this page for clarity.
In this page, user can upload their music on the blockchain. The user is required to give name, artist, and the to upload audio file. We will do some check function before the upload is actually done.
This page shows some user information such as uploaded list and bought list. The user can also buy tokens on this page.
We offer 3 options, 100, 1000, and 10000. The exchange ratio is Ether:Token = 1:10000.
User can also sell some tokens. If the input value is greater than the balance the user has, the application will reject this transaction and show some error message, like the following shows.
At the bottom of this page, we can see all music the user had uploaded or bought. When the user click the music title, they will be redirected to the music detail page.
Music Detail Page
This page shows the information of a music. On the left side, it shows the metadata of the music.
Music Copyright Chain
On the right side, it shows the music copyright chain. Notice that user can also click music on the chain, and then they will be redirected to the that music.
If the user had not bought this music, they can click the
BUY MUSIC button to fire a transaction on the blockchain.
Then the metamask window will pop up to confirm the transaction.
However, if a user has no enough balance, we do not allow user to buy music. The page will show some error message and the button is disabled.
After the user has bought the music, the
BUT MUSIC button becomes
Then the user can click the button, the music will be added to the playlist, and the playing song changes, too.
We implement a simple search function to find relevant music based on some keywords. If the name field and the artist field are both left unfilled, it will show all musics on the blockchain.
Given the music name, the website will try to find the matched result.
The artist case is similar.
If given both keywords, the application will return the exact music if this music exists on the blockchain.
This page is only for developers. Developers can test functions on the smart contract in the easiest way.
More Than a Chain
In our current implementation, we only allow a music has only one cover from relationship. However, it is not that simple in the real world. For example, a song may be similar to 3 musics, the similarity is too close to tell which one is the right one. A even complex situation is that a song is indeed cover from 2 or more songs. In these case, some advanced implementation is needed.
As more and more music being uploaded, our smart contract becomes a database that contains data which can be used to train music generation ML models. Our smart contract has great potential, but we haven't fully realize how to put these dataset into real value.
Based on different situation, the profit sharing may not be static. In some cases, the downloaded time of a music is way more higher then the covered song. This may due to the reinterpretation of the song or some marketing efforts. No matter what, although we still have to protect the music copyright, the profit sharing ratio is reasonably to be dynamic adjusted instead of a fixed one.