V2 clean code

.env.example

@@ -1,5 +1,5 @@
 # ========== DEBUG ==============
-NEXT_PUBLIC_ACTIVE_DEBUG=false
+NEXT_PUBLIC_ACTIVATE_DEBUG=false
 
 # ========== CONNECT ==============
 NEXT_PUBLIC_WALLECT_CONNECT_PROJECT_ID=xxxxx
@@ -9,10 +9,9 @@ NEXT_PUBLIC_DEFAULT_CHAIN_ID=80001
 NEXT_PUBLIC_PLATFORM_ID=4
 
 # ========== IPFS ==============
-NEXT_PUBLIC_INFURA_ID=xxxxx
-NEXT_PUBLIC_INFURA_SECRET=xxxxxx
 NEXT_PUBLIC_IPFS_BASE_URL=https://ipfs.io/ipfs/
-NEXT_PUBLIC_IPFS_WRITE_URL=https://ipfs.infura.io:5001
+NEXT_PUBLIC_IPFS_WRITE_URL=https://api.quicknode.com/ipfs/rest/v1/s3/put-object
+NEXT_PUBLIC_IPFS_SECRET=xxxxx
 
 # ========== SIGNATURE ==============
 NEXT_PUBLIC_SIGNATURE_API_URL=
@@ -23,17 +22,19 @@ NEXT_PUBLIC_BACKEND_RPC_URL=https://rpc-mumbai.maticvigil.com/v1/xxxxxxxxxxxxxxx
 NEXT_PUBLIC_MESSENGING_ENV='dev'
 
 ## ========== DATABASE ==============
-NEXT_MONGO_URI="mongodb+srv://xxxxx:yyyyy@xxx"
+DATABASE_URL="postgres://postgres:[YOUR-PASSWORD]@db.[YOUR-PROJECT-REF].supabase.co:5432/postgres"
 
 # ========== DELEGATION ==============
-## Active the delegate feature for service / proposal / release / review (the proposal validation won't be delegate)
-NEXT_PUBLIC_ACTIVE_DELEGATE=false
-## Active the delegate feature for minting ID - will call a backend api and call the smartcontract function mintForAddress
-NEXT_PUBLIC_ACTIVE_DELEGATE_MINT=false
+## Activate the delegate feature for service / proposal / release / review (the proposal validation won't be delegate)
+NEXT_PUBLIC_ACTIVATE_DELEGATE=false
+## Activate the delegate feature for minting ID - will call a backend api and call the smartcontract function mintForAddress
+NEXT_PUBLIC_ACTIVATE_DELEGATE_MINT=false
 ## This seed phrase is only used for delegate purpose
 NEXT_PRIVATE_DELEGATE_SEED_PHRASE="add you seed phrase here only for delegate purpose"
 ## Public address
 NEXT_PUBLIC_DELEGATE_ADDRESS="0xaddyouraddresshereonlyfordelegatepurpose"
+## Automatically activate delegation to BuilderPlace when minting a TLid
+NEXT_PUBLIC_ACTIVATE_DELEGATE_ON_MINT="false"
 
 # ========== OPEN DATA APIs ==============
 NEXT_PUBLIC_WORKX_API_URL=https://api.workpi.com/graphql
@@ -46,9 +47,32 @@ NEXT_PRIVATE_OPENAI_API_KEY=xxx
 NEXT_PRIVATE_LEAPAI_API_KEY=xxx
 
 # ========== WEB3MAIL ==============
-NEXT_PUBLIC_ACTIVE_WEB3MAIL=false
 NEXT_WEB3MAIL_PLATFORM_PRIVATE_KEY="xaddyouprivatekeyhere"
 NEXT_PUBLIC_WEB3MAIL_PLATFORM_PUBLIC_KEY="0x27FDabe8222d7f874406F3EaBBb9601D87EF1a82"
 NEXT_PUBLIC_WEB3MAIL_APP_ADDRESS="web3mail.apps.iexec.eth"
 CRON_SECRET="xxx"
 NEXT_WEB3MAIL_RETRY_FACTOR=5
+
+# ========== MAIL NOTIFICATIONS ==============
+# "web2" or "web3"
+NEXT_PUBLIC_EMAIL_MODE=web2
+
+# ========== Multidomain ==============
+NEXT_PUBLIC_ROOT_DOMAIN=localhost:3000
+NEXT_CLOUDFLARE_TOKEN=xxx
+
+# ========== Vercel ==============
+# Vercel authentication token that can be found here: https://vercel.com/account/tokens
+NEXT_PRIVATE_AUTH_BEARER_TOKEN=
+# Vercel Project ID that can be found here: https://vercel.com/<org>/<project>/settings
+NEXT_PRIVATE_PROJECT_ID_VERCEL=
+# Vercel Team ID that can be found here: https://vercel.com/teams/<org>/settings
+NEXT_PRIVATE_TEAM_ID_VERCEL=
+
+# ========== Sendgrid ==============
+NEXT_PRIVATE_SENDGRID_VERIFIED_SENDER=
+NEXT_PRIVATE_SENDGRID_API_KEY=
+
+# ========== Posthog ==============
+NEXT_PUBLIC_POSTHOG_KEY=
+NEXT_PUBLIC_POSTHOG_HOST=

.gitignore

@@ -28,4 +28,5 @@ dist-ssr
 
 # typescript
 *.tsbuildinfo
-next-env.d.ts
+next-env.d.ts
+.vercel

README.md

@@ -1,22 +1,43 @@
-# StarterKit
+# BuilderPlace
 
 A Ready to Use NextJS dapp using [TalentLayer](https://docs.talentlayer.org/).
 
 ## Start building in few seconds
 
+### Basic configuration
 - Fork the code
 - Clone your new repository
 - Copy .env.example file into a new .env file: `cp .env.example .env`
-    - Minimum required configuration: 
-        - NEXT_PUBLIC_PLATFORM_ID: use 4, the default value, or [create your own platform](https://docs.talentlayer.org/get-a-platform-id) to setup your custom fees and more: 
+    - Minimum required configuration:
+        - NEXT_PUBLIC_PLATFORM_ID: use 4, the default value, or [create your own platform](https://docs.talentlayer.org/get-a-platform-id) to setup your custom fees and more:
         - NEXT_PUBLIC_WALLECT_CONNECT_PROJECT_ID: Create a free account on [wallet connect and get your project ID](https://cloud.walletconnect.com/)
-        - NEXT_PUBLIC_INFURA_ID & NEXT_PUBLIC_INFURA_SECRET: used to post on IPFS, create a free account on [Infura here](https://www.infura.io/product/ipfs)  
-    - For more advanced configuration [check the official doc](https://docs.talentlayer.org/technical-guides/starterkit-setup)
+        - NEXT_PUBLIC_INFURA_ID & NEXT_PUBLIC_INFURA_SECRET: used to post on IPFS, create a free account on [Infura here](https://www.infura.io/product/ipfs)
+        - DATABASE_URL: create a postgres in two clicks here [with supabase](https://supabase.com)
+    - For more advanced configuration [check the official doc](https://docs.talentlayer.org/technical-guides/builderplace-setup)
 - Use the recommended node version: `18^`, if you are using nvm just run: `nvm use`
 - Install the dependencies: `npm install`
 - Run local server for development `npm run dev`
 - That's it!
 
+### GasLess Transactions / Delegation (optional)
+To activate gasless transactions and delegation you will need a dedicated Seed & Address which will be used to execute transactions on behalf of your users, and set the following environment variables:
+
+- Set NEXT_PRIVATE_DELEGATE_SEED_PHRASE: Dedicated Seed phrase for your delegate
+- Set NEXT_PUBLIC_DELEGATE_ADDRESS: Address of your delegate
+- Add matic to NEXT_PUBLIC_DELEGATE_ADDRESS: To pay for transactions on behalf of your users
+- Set NEXT_PUBLIC_ACTIVATE_DELEGATE_MINT to true
+- If you wish to give the user the option to directly add your backend delegator to new users during onboarding set NEXT_PUBLIC_ADD_DELEGATE_MINT_ADDRESS to "true"
+
+To use this feature your Users will need to activate delegation by calling the following function on the TalentLayerId smart contract:
+```solidity
+/**
+ * @notice Allows to give rights to a delegate to perform actions for a user's profile
+ * @param _profileId The TalentLayer ID of the user
+ * @param _delegate Address of the delegate to add
+ */
+function addDelegate(uint256 _profileId, address _delegate);
+``` 
+
 ## 🛠️ TalentLayer
 
 TalentLayer is an open protocol and dev toolkit for hiring applications. You can use it to build platforms that leverage a unified decentralized backend for job posts, escrow, user profiles, and reputations.
@@ -31,7 +52,7 @@ TalentLayer is an open protocol and dev toolkit for hiring applications. You can
 
 ## 🗨 XMTP
 
-XMTP is an open protocol and dev toolkit for messaging applications. You can use it to build peer-to-peer messaging 
+XMTP is an open protocol and dev toolkit for messaging applications. You can use it to build peer-to-peer messaging
 
 ### Developer Resources
 
@@ -43,10 +64,10 @@ XMTP is an open protocol and dev toolkit for messaging applications. You can use
 
 ## ✉️ IExec - Web3mail
 
-Web3mail is a decentralized email service built by IExec which allows a platform to send emails to a user without knowing the email address of the user. 
+Web3mail is a decentralized email service built by IExec which allows a platform to send emails to a user without knowing the email address of the user.
 
 ### Developer Resources
 
 **Iexec Documentation:** [Read here.](https://tools.docs.iex.ec/tools/dataprotector)
 
-**Technical TalentLayer integration documentation:** [Read here.](https://docs.talentlayer.org/third-party-modules/iexec-web3mail)
+**Technical TalentLayer integration documentation:** [Read here.](https://docs.talentlayer.org/third-party-modules/iexec-web3mail)

docs/delegate.md

@@ -0,0 +1,63 @@
+# Delegates 
+
+## Overview
+
+Delegation is an action of allowing a used to execute on-chain transactions on your behalf.
+TalentLayer implemented delegation on the TalentLayerId contract, which allows a user to add ETH addresses as delegates, which will have on-chain rights to execute certain functions on behalf of the user.
+
+
+On BuilderPlace, we use delegation for 2 different cases:
+
+ - **CollaboratorDelegate**: A platform owner can add other users as sub-admins for the platform, which are called Collaborators. When adding a collaborator, the owner will add the collaborator's address as delegate to his own TalentLayer Id, so that the collaborator can create services or reviews using the owner's Id.
+ - **BackendDelegate**: A user can add our backend as a delegate in to let it execute transactions on his behalf, and save gas fees.
+
+### Collaborator Delegate
+
+From: BuilderPlace collaborators page
+The new collaborator must have a BuilderPlace profile and TalentLayer id
+
+- The Owner inputs the address of the new collaborator
+- Its address will be added on-chain to the Platform owner's delegates
+- The Owner can then remove a collaborator, its address will be removed on-chain
+
+
+### Backend Delegate
+
+IF the user does not have a TalentLayer Id yet:
+- From: Onboarding
+    - When the user registers as a Platform User, if the NEXT_PUBLIC_ACTIVATE_DELEGATE_MINT environment variable is set to true, then if he does not have a TalentLayer Id yet, it will be minted and transferred by our backend to the user, and our backend will add its address as a delegate of the user.
+
+IF the user already has a TalentLayer Id during onboarding, it will not be activated at this step.
+- From: Dashboard
+    - He will have the possibility to add our backend as a delegate
+
+
+### Worker onboarding
+
+- From: 
+    - case 1: BuilderPlace worker page
+    - case 2: if a worker want to apply to a job
+- Step 1: Complete the "create your profile" form 
+    - It creates the user in DB
+    - And create a TLid linked to the address if the user don't have one yet
+    - Note: this step is automatically skipped if the user already have a TLid
+- On success: 
+    - Case 1: Redirect to his dashboard
+    - Case 2: Redirect to the job page
+
+
+### Hirer onboarding
+
+- From a given BuilderPlace, i the hirer want to post a job
+- Step 1: Complete the "create your profile" form 
+    - It creates the user in DB
+    - And create a TLid linked to the address if the user don't have one yet
+    - Note: this step is automatically skipped if the user already have a TLid
+- On success: Redirect to the create job page
+
+## TalentLayerId
+
+- A TalentLayerId is a unique identifier that is linked to an address
+- We will mint the TLid for the user automatically during onboarding. 
+- In case the user already have a TLid, we will link it to his profile in DB
+- Important: In case something goes wrong, the user can create a TLid manually from the dashboard or anytime he try to execute his first onchain action

docs/platforms.md

@@ -0,0 +1,69 @@
+# Platforms
+aka Builer Place (aim to rename it to Platform)
+
+## Onboarding
+
+We have 2 types of platform on Builder Place that are different due to their posting jobPostingConditions
+
+| Platform Type | allowPosts | Description | Fees |
+| --- | --- | --- | --- |
+| Market Place | TRUE | User create his own market where he can allow others to post following his conditions. He can define his own fees rules. | Custom |
+| Company Place | FALSE | User create a place only for his own posts | Default |
+
+### JobPostingConditions
+
+```javascript
+interface JobPostingConditions {
+    allowPosts: boolean;
+    conditions?: PostingCondition[];
+}
+
+type PostingCondition = NFTCondition | TokenCondition;
+
+interface NFTCondition {
+    type: 'NFT';
+    address: string; // Address of the NFT contract
+}
+
+interface TokenCondition {
+    type: 'Token';
+    address: string; // Address of the token contract
+    minimumAmount: number; // Minimum amount of tokens required
+}
+```
+
+### Market Place
+
+- TalentLayer: this one got his own TalentLayerPlatformId. It will allow to customize fees...
+- Job posting conditions: 
+    - Public: allow others
+    - Condition: allow only someone who owns an NFT or a certain amount of tokens
+
+
+### Company Place
+
+- TalentLayer: this one use the default builderPlace TalentLayerPlatformId.
+
+
+## TODO
+
+- [x] update db schema, add jobPostingConditions
+- Complete new onboarding with step 2, create platform
+    - ask for the minimum filled required:
+        - name
+        - subdomain
+        - baseline?
+        - logo
+        - jobPostingConditions
+    - everything created after one step
+    - onSubmit
+        - mint platformId 
+        - sign message 
+        - post everything to DB
+        - Redirect to new domain
+- Add Post job in the menu for everyone if jobPostingStrategy = allow others
+    - Display the conditons on the post page
+    - Display form or an access denied message depending on current wallet connected
+- Add a form to update fees (but only accessible on superadmin for now)
+- Clean old code
+- Rename to platform?

docs/users.md

@@ -0,0 +1,71 @@
+# Users 
+
+## Onboarding
+
+We have 4 types of user on Builder Place.
+
+| User Type | Description | Onboarding From |
+| --- | --- | --- |
+| Owner | A user that owned a platform | Default domain |
+| Collaborator | A user added by a platform owner to help him administrate it | The platform custom domain |
+| Worker | A user that is searching for work | Could be both |
+| Hirer | A user that is want to post on a BuilderPlace | The platform custom domain |
+
+### Owner onboarding
+
+- From: BuilderPlace homepage
+- Step 1: Complete the "create your profile" form 
+    - It creates the user in DB
+    - And create a TLid linked to the address if the user don't have one yet
+    - Note: this step is automatically skipped if the user already have a TLid
+- Step 2: Complete the "create your platform" form
+    - Create the platform in DB
+    - Create TLPlatformId owned by the address
+- On success: 
+    - Redirect to the new platform dashboard
+
+
+### Collaborator onboarding
+
+- From: BuilderPlace collaborators page
+- Step 1: The owner complete the "add a collaborator" form
+    - It creates the user in DB (status pending as we didn't confirmed the signature)
+    - Send him an email with a link to the "create your profile" form
+    - And create a TLid linked to the address if the user don't have one yet
+- Step 2: The owner delegate onchain right to the address TLID
+- Step 3: The user click on the link and complete the "create your profile" form
+    - It update the user in DB (status confirmed)
+    - And create a TLid linked to the address if the user don't have one yet
+- On success: 
+    - Redirect to the platform dashboard
+
+
+### Worker onboarding
+
+- From: 
+    - case 1: BuilderPlace worker page
+    - case 2: if a worker want to apply to a job
+- Step 1: Complete the "create your profile" form 
+    - It creates the user in DB
+    - And create a TLid linked to the address if the user don't have one yet
+    - Note: this step is automatically skipped if the user already have a TLid
+- On success: 
+    - Case 1: Redirect to his dashboard
+    - Case 2: Redirect to the job page
+
+
+### Hirer onboarding
+
+- From a given BuilderPlace, i the hirer want to post a job
+- Step 1: Complete the "create your profile" form 
+    - It creates the user in DB
+    - And create a TLid linked to the address if the user don't have one yet
+    - Note: this step is automatically skipped if the user already have a TLid
+- On success: Redirect to the create job page
+
+## TalentLayerId
+
+- A TalentLayerId is a unique identifier that is linked to an address
+- We will mint the TLid for the user automatically during onboarding. 
+- In case the user already have a TLid, we will link it to his profile in DB
+- Important: In case something goes wrong, the user can create a TLid manually from the dashboard or anytime he try to execute his first onchain action