feat: on-chain permissioned launchpad

[hthieu1110]

1. Contract

2. Service

2.a. Collections/Projects Status

2.a.1. INCOMPLETE

(DB) The collection_data from launchpad_project doesn't have a metadatas_merkle_root.
The user has to Complete the collection (See UploadMetadatas endpoint) that he can found on my-collections page (See CollectionsByCreator endpoint)

2.a.2. COMPLETE

(DB) The collection_data from launchpad_project has a metadatas_merkle_root and doesn't have a deployed_address.
The admin has to review and approve/confirm the collection (See ???)

2.a.3. CONFIRMED

(DB) ???
The admin has to deploy the collection (See deploy_collection from the contract)

2.a.4. DEPLOYED

(DB) The collection_data from launchpad_project has a deployed_address
Listed on the Marketplace

2.b. Endpoints

2.b.1. UploadMetadatas

2.b.2. CalculateCollectionMerkleRoot

2.b.3. TokenMetadata

2.b.4. CollectionsByCreator

Control the user's ownership with creatorId, returns a list of collectionData, can filter by status, can sort

2.b.5. LaunchpadProjects

2.b.6. LaunchpadProjectById

2.b.7. LaunchpadProjectsCount

3. Front-end

Access from here :

3.a. Collection creation form

I tried a way to make good forms : https://hackmd.io/TXt0Gz5_Q-OJIo6-OH674w?both

3.a.1. Datetime inputs

I made this :

The user has to type a valid datetime

The hours/minutes/seconds can be empty

3.a.2. Fields control at form submission

The button is at the step 6

If fields are invalid or required fields are not filled, an error is shown, and all the invalid/required fields are highlighted. The user has to navigate in the form to find the highlighted fields.
We could show a red pill or something near the steps to tell the user which step is concerned.

3.a.3. Collection minting periods

The user can add a whitelist (list of wallet addresses) that will be concerned by the period parameters. If there is no whitelist provided, the parameters will be effective for all users.
The CSV must be something like this :

3.a.4. Collection assets

3.a.4.1. The user must add a CSV file before images

==> If he add a new CSV file, all the images are removed (It was easier to implement)

The CSV must be something like this :

TODO: Handle attributes

3.a.4.2. The user can see the valid assets

==> He can see manually all assets metadata

3.a.4.3. Error if the added CSV has not the right headings

==> The first row must contains the columns names :
fileName, name, description, externalURL, youtubeURL, attributes

3.a.4.4. Warning if the user miss adding images that are expected in the CSV

Not blocking, the expected assets are added, the wrongs are ignored

3.a.4.5. Warning if the user adds images that are not expected in the CSV

Not blocking, the unepected assets are not added

3.a.4.6. Warning if the user adds images that are missing "name" or "attributes" values in the CSV

Not blocking, the incomplete assets are not added

3.b. User's My Collections

3.c. Admin

[netlify]

✅ Deploy Preview for testitori ready!

Name	Link
🔨 Latest commit	180e2de
🔍 Latest deploy log	https://app.netlify.com/sites/testitori/deploys/672e72240a0a7e0007fd9af1
😎 Deploy Preview	https://deploy-preview-1024--testitori.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for teritori-dapp ready!

Name	Link
🔨 Latest commit	8e85f3c
🔍 Latest deploy log	https://app.netlify.com/sites/teritori-dapp/deploys/67b6581f183ff4000838572a
😎 Deploy Preview	https://deploy-preview-1024--teritori-dapp.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.