-
Notifications
You must be signed in to change notification settings - Fork 4
Repositories
Link: https://github.com/DAOrecords/FonoRoot
This is the repository that we created on the MetaBUILD hackathon. We don't update it anymore.
Link: https://github.com/DAOrecords/SoundSplash
We created this repository when we did the Sound Splash event series, with 12 NFT drops. This is a fork of FonoRoot. This is currently the most central repository. The MyNFTs and StoreFront development is also happening here. The folder structure is:
-
backend- this is the backend software that is written in ExpressJS. Currently it is handling adding files to IPFS (when minting), fetching media and serving it to the front end (when image is displayed, music is played), connection to SQL database. -
contract- the FonoRoot smart contract, written in Rust. It handles NFT minting, but the artist info is not on the blockchain currently, that is handled by the backend. -
src- front end written in React, create-near-app was used for set up. SoundSplash front end still can be found here, but the DAOrecords main site is also here, as much as it exists at this point. This means the Storefront and the MyNFTs page.
TODO: This repository should be renamed or obsolated, and 2 distinct repositories should be created FonoRootMintingContract and DaoRecordsMainSite.
Link: https://github.com/DAOrecords/Troaco-template
This repository was created by forking SoundSplash. It was somewhat cleaned up, and made into a template, for album-style drops. The backend folder was removed, the src folder aims to only contain elements which are needed for this type of drop, which looks like this.
The contract folder should contain that version of the smart contract, that was used when we did the original minting. This can be important in the future, because certain drops can be incompatible with each other. Meaning, there can be an upgrade in the smart contract code that, if shipped to the old code, will break it. Because of that, that version of the smart contract should be coupled to the drop that was used when minting was done.
In this repository, there are different branches, like site-metajax, site-rarevandal. The idea is, that every time a drop is done, we are merging the branch to master, thus updating the master with recent changes/fixes. Altough the previous drops won't be effected by this, so, in case there is a serious bug, we would need to manually fix that bug in all branches.
Deployment is happening from the site- branches, not from master.
Link: https://github.com/DAOrecords/General-template
Idea is similar to Troaco. This used to be called SoundSplash-template, but it was renamed (this is why https://github.com/DAOrecords/Soundsplah-template will redirect to General-template).
This repository was also forked from SoundSplash and then cleaned. SoundSplash is now here, site-soundsplash branch was created to store the SoundSplash drop, and the SoundSplash repository is evolving into the Platform. Or Console. Probably the SoundSplash repository should be renamed, or a new repository should be created.
This is the template that we are currently using, there are 3 drop templates: Album, Mixtape, and Single. This is explained in App.js under the comment {/** NFT Landing Page Examples */}. The backend folder was removed here as well.
Link: https://github.com/DAOrecords/FonoRoot-DAO
This is a fork of Sputnik DAO, this will be the owner of the minting contracts. The revenue table, and anything about money, will be moved here, the FonoRoot contract will only contain NFT related info, management will happen through this contract.