diff --git a/Vechain-EasyA-Hackathon-Boston-Oct-2023/applications/API Documentation.md b/Vechain-EasyA-Hackathon-Boston-Oct-2023/applications/API Documentation.md deleted file mode 100644 index 54234937..00000000 --- a/Vechain-EasyA-Hackathon-Boston-Oct-2023/applications/API Documentation.md +++ /dev/null @@ -1,523 +0,0 @@ -# Sozo inFashion API Reference - -## Description -Sozo's REST API is structured in a way that allows developers to easily fetch data, make user-specific updates, and understand the information being provided. All responses are in JSON format and use standard HTTP response codes. - -| Base URL | -| ----------- | -| `https://sozo.api.com` | - -## Endpoints -```http -GET /users -GET /users/{user_id} -POST /users/create -PATCH /users/{user_id} -DELETE /users/{user_id} - -GET /jobs/{job_id} -POST /jobs/create -POST /jobs/{job_id}/cancel - -GET /pieces -GET /pieces/{piece_id} -POST /pieces/create -PATCH /pieces/{piece_id} -``` -*** -## Users - -**GET** _/users_ - -Returns a list of all users. -| Parameter | Type | Description -| ----------- | :-----------: | ----------- | -| limit | `integer` | `optional` Maximum number of designer users to return; Default is 20. | -| role | `string` | `optional` Type of users to return ('designer' or 'client') | - -**Response** - -Returns an array of objects containing the following data. -| Key | Type | Description -| ----------- | :-----------: | ----------- | -| user_id | `string` | Unique value assigned when user is created in the database. | -| username | `string` | A user's display name; Also used for login. | -| email | `string` | A user's email address. | -| role | `string` | A user's role ('designer' or 'client'). | -| first_name | `string` | A user's first name. | -| last_name | `string` | A user's last name. | -| bio | `string` | A description of the user. | -| active_status | `number` | 1 indicates **active** **OR** 0 indicates **not active** | - -**Example** - -Request: -```http -GET /users?limit=2 -``` -Response: -```json -[ - { - "user_id": "hTwR4QEXHYPf7Ua6tjjM", - "username": "DrewDream", - "email": "dreamlife@yahoo.com", - "role": "designer", - "first_name": "Drew", - "last_name": "Thompson" - "bio": "Bold stitches, fierce fabrics. Transforming threads into masterpieces. 🧵✨ #FashionAlchemy #StyleVisionary", - "active_status": 1 - }, - { - "user_id": "Hfkq7urNonHMonGREKU3", - "username": "TaylorJ", - "email": "taylor.joslin@gmail.com", - "role": "client", - "first_name": "Taylor", - "last_name": "Joslin", - "bio": "Dedicated to refining elegance through precision. Crafting timeless designs with meticulous attention to detail. Fashion designer focused on timeless style.", - "active_status": 1 - } -] -``` -*** - -**GET** _/users/{user_id}_ - -Retrieve a single user account. -| Parameter | -| ----------- | -| No parameters | - -**Reponse** - -Returns a single user object containing the following data. -| Key | Type | Description -| ----------- | :-----------: | ----------- | -| user_id | `string` | Unique value assigned when user is created in the database. | -| username | `string` | A user's display name. | -| email | `string` | A user's email address. | -| role | `string` | A user's role ('designer' or 'client'). | -| first_name | `string` | A user's first name. | -| last_name | `string` | A user's last name. | -| bio | `string` | A description of the user (max length: 200 characters). | -| active_status | `number` | 1 indicates **active** **OR** 0 indicates **not active** | - -**Example** - -Request: -```http -GET /users/hTwR4QEXHYPf7Ua6tjjM -``` -Response: -```json -{ - "user_id": "hTwR4QEXHYPf7Ua6tjjM", - "username": "DrewDream", - "role": "designer", - "first_name": "Drew", - "last_name": "Thompson", - "bio": "Bold stitches, fierce fabrics. Transforming threads into masterpieces. 🧵✨ #FashionAlchemy #StyleVisionary", - "active_status": 1 -} -``` -*** - -**POST** _/users/create_ - -Creates a new user account. -| Parameter | Type | Description -| ----------- | :-----------: | ----------- | -| username | `string` | `required` User's display name. Does not allow special chatacters; Can be used for login. | -| email | `string` | `required` User's email address; Can be used for login. | -| role | `string` | `required` User's role ('designer' or 'client'). | -| first_name | `string` | `required` User's first name. | -| last_name | `string` | `required` User's last name. | -| bio | `string` | `optional` Description of the user (max length: 200 characters). | - -**Response** - -Returns a single user object containing the following data. - -| Key | Type | Description -| ----------- | ----------- | ----------- | -| user_id | `string` | Unique value assigned when user is created in the database. | -| username | `string` | User's display name. | -| email | `string` | User's email address. | -| role | `string` | User's role ('designer' or 'client'). | -| first_name | `string` | User's first name. | -| last_name | `string` | User's last name. | -| bio | `string` | Description of the user. | -| active_status | `number` | 1 indicates **active** **OR** 0 indicates **not active** | - -**Example** - -Request: -```http -POST /users/create -``` -Request Body: -```json -{ - "username": "RachelY", - "email": "rachel.yearny@gmail.com", - "role": "client", - "first_name": "Rachel", - "last_name": "Yearney" -} -``` -Response: -```json -{ - "user_id": "H094iAjZyPWr4rm0y9WL", - "username": "RachelY", - "email": "rachel.yearny@gmail.com", - "role": "client", - "first_name": "Rachel", - "last_name": "Yearny", - "bio": "", - "active_status": 1 -} -``` -*** - -**PATCH** _/users/{user_id}_ HTTP/1.1 - -Update parts of a user's profile information. -| Parameter | Type | Description -| ----------- | :-----------: | ----------- | -| username | `string` | `optional` A user's display name. Does not allow special chatacters; Can be used for login. | -| email | `string` | `optional` A user's email address. | -| first_name | `string` | `optional` A user's first name. | -| last_name | `string` | `optional` A user's last name. | -| bio | `string` | `optional` A description of the user. | - -**Response** - -Returns a single user object containing the following data. - -| Key | Type | Description -| ----------- | ----------- | ----------- | -| user_id | `string` | Unique value assigned when user is created in the database. | -| username | `string` | A user's display name. | -| email | `string` | A user's email address. | -| role | `string` | A user's role ('designer' or 'client'). | -| first_name | `string` | A user's first name. | -| last_name | `string` | A user's last name. | -| bio | `string` | A description of the user. | -| active_status | `number` | 1 indicates **active** **OR** 0 indicates **not active** | - -**Example** - -Request: -```http -PATCH /users/H094iAjZyPWr4rm0y9WL HTTP/1.1 -``` -Request Body: -```json -{ - "username": "YearOfRachel", - "bio": "Sculpting sophistication in every stitch. Empowering women through distinctive designs. Committed to redefining style with grace and purpose." -} -``` -Response: -```json -{ - "user_id": "H094iAjZyPWr4rm0y9WL", - "username": "YearOfRachel", - "email": "rachel.yearny@gmail.com", - "role": "client", - "first_name": "Rachel", - "last_name": "Yearny", - "bio": "Sculpting sophistication in every stitch. Empowering women through distinctive designs. Committed to redefining style with grace and purpose.", - "active_status": 1 -} -``` -*** - -**DELETE** _/users/{user_id}_ - -Deletes a single user from the database. -| Parameter | -| ----------- | -| No parameters | - -**Reponse** - -Returns an object containing the following data: -| Key | Type | Description -| ----------- | ----------- | ----------- | -| user_id | `string` | Unique value assigned when user is created in the database. | -| username | `string` | A user's display name. | -| deleted | `boolean` | `true` to indicate account was successfully deleted **OR** `false` to indicate the account was not deleted. | - -**Example** - -Request: -```http -DELETE /users/hTwR4QEXHYPf7Ua6tjjM -``` -Response: -```json -{ - "designer_id": "hTwR4QEXHYPf7Ua6tjjM", - "username": "DrewDream", - "deleted": true -} -``` -*** - -## Jobs -**GET** _/jobs/{job_id}_ - -Retrieve details of a single job, established between a client and designer user. -| Parameter | -| ----------- | -| No parameters | - -**Reponse** - -Returns a single job object containing the following data. -| Key | Type | Description -| ----------- | :-----------: | ----------- | -| job_id | `string` | Unique value assigned when a job is created. | -| client_id | `string` | Client user's unique id. | -| designer_id | `string` | Designer user's unique id. | -| payment_status | `string` | Status of payment for job. Possible values are `not paid` `pending` or `paid`. | -| active_status | `number` | 1 indicates **active** **OR** 0 indicates **not active** | - -**Example** - -Request: -```http -GET /jobs/uD7uQ4xjuCT9spwhyNVRxiYk9 -``` -Response: -```json -{ - "job_id": "uD7uQ4xjuCT9spwhyNVRxiYk9", - "client_id": "Hfkq7urNonHMonGREKU3", - "designer_id": "hTwR4QEXHYPf7Ua6tjjM", - "payment_status": "not paid", - "active_status": 1 -} -``` -*** - -**POST** _/jobs/create_ - -Creates a new job. -| Parameter | Type | Description -| ----------- | :-----------: | ----------- | -| client_id | `string` | `required` Client user's unique id. | -| designer_id | `string` | `required` Designer user's unique id. | - -**Response** - -Returns a single job object containing the following data. - -| Key | Type | Description -| ----------- | ----------- | ----------- | -| job_id | `string` | Unique value assigned when a job is created. | -| client_id | `string` | A client user's unique id. | -| designer_id | `string` | A designer user's unique id. | -| payment_status | `string` | Status of payment for job. Possible values are `not paid` `pending` or `paid`. | -| active_status | `number` | Indicates whether a job is active; 1 is **active** **OR** 0 is **not active** | - -**Example** - -Request: -```http -POST /jobs/create -``` -Request Body: -```json -{ - "client_id": "Hfkq7urNonHMonGREKU3", - "designer_id": "hTwR4QEXHYPf7Ua6tjjM" -} -``` -Response: -```json -{ - "job_id": "uD7uQ4xjuCT9spwhyNVRxiYk9", - "client_id": "Hfkq7urNonHMonGREKU3", - "designer_id": "hTwR4QEXHYPf7Ua6tjjM", - "payment_status": "not paid", - "active_status": 1 -} -``` -*** - -**POST** _/jobs/{job_id}/cancel_ - -Cancels an active job; The job must be in a cancelabe state (active_status == 1 && payment_status == "not paid"). -| Parameter | -| ----------- | -| No parameters | - -**Reponse** - -Returns a single job object if the request was successful. Returns an error if the job is not in a cancelable state. -| Key | Type | Description -| ----------- | :-----------: | ----------- | -| job_id | `string` | Unique value assigned when a job is created. | -| client_id | `string` | A client user's unique id. | -| designer_id | `string` | A designer user's unique id. | -| payment_status | `string` | Status of payment for job. Possible values are `not paid` `pending` or `paid`. | -| active_status | `number` | 1 indicates **active** **OR** 0 indicates **not active** | - -**Example** - -Request: -```http -POST /jobs/{job_id}/cancel -``` -Response: -```json -{ - "job_id": "uD7uQ4xjuCT9spwhyNVRxiYk9", - "client_id": "Hfkq7urNonHMonGREKU3", - "designer_id": "hTwR4QEXHYPf7Ua6tjjM", - "payment_status": "not paid", - "active_status": 0 -} -``` -*** - -## Pieces - -**GET** _/pieces_ - -Returns a list of all designer users. -| Parameter | Type | Description -| ----------- | :-----------: | ----------- | -| limit | `integer` | `optional` Maximum number of designer users to return; Default is 20. | - -**Response** - -Returns an array of objects representing pieces created by designers. Each object contains the following data. -| Key | Type | Description -| ----------- | :-----------: | ----------- | -| piece_id | `string` | Unique value assigned when a piece in the database. | -| designer_id | `string` | A designer user's unique id. | -| piece_name | `string` | A piece's name. Determined by the designer. | -| image_name | `string` | Name of the image uploaded for the piece. | -| description | `string` | A description of the piece. | - -**Example** - -Request: -```http -GET /pieces?limit=2 -``` -Response: -```json -[ - { - "piece_id": "hgmjw3vx4bfnQs9", - "designer_id": "hTwR4QEXHYPf7Ua6tjjM", - "piece_name": "Stars & Spangles", - "image_name": "hgmjw3vx4bfnQs9.jpg", - "description": "Unveiling the \"Stars & Spangles\" hoodie: a premium cotton masterpiece embodying the spirit of the United States. Vibrant stars and stripes meticulously dance across this garment, a dynamic celebration of American pride. Perfect for Independence Day or any occasion, this hoodie seamlessly merges style with patriotism. Wear the colors that echo the nation's heartbeat, making the Stars & Spangles a timeless symbol of your love for the land of the free." - }, - { - "piece_id": "AgiUjJGhhKtX3oY", - "designer_id": "NRDF8FB61BuYThN2scFA", - "piece_name": "Stars & Spangles", - "image_name": "AgiUjJGhhKtX3oY.jpg", - "description": "\"The Raven's Veil\" is a bewitching cloak that cascades in mysterious ebony folds. Embroidered ravens soar across the midnight fabric, their feathers intricately detailed in silver thread. The garment whispers tales of ancient lore, weaving elegance with an enigmatic edge. Embrace the mystique, as the Raven's Veil envelops you in a silhouette of shadowed allure." - } -] -``` -*** - -**POST** _/pieces/create_ - -Creates a piece. -| Parameter | Type | Description -| ----------- | :-----------: | ----------- | -| piece_name | `string` | `required` A piece's name. | -| image_name | `string` | `required` Name of the image uploaded for the piece. | -| description | `string` | `optional` A description of the piece (max length: 400 characters). | - -**Response** - -Returns a single piece object containing the following data. -| Key | Type | Description -| ----------- | ----------- | ----------- | -| piece_id | `string` | Unique value assigned when a piece in the database. | -| designer_id | `string` | A designer user's unique id. | -| piece_name | `string` | A piece's name. Determined by the designer. | -| image_name | `string` | Name of the image uploaded for the piece. | -| description | `string` | A description of the piece. | - -**Example** - -Request: -```http -POST /users/create -``` -Request Body: -```json -{ - "piece_name": "Red Monty", - "image_name": "IMG_46.jpg", - "description": "" -} -``` -Response: -```json -{ - "piece_id": "1rjJDBYmLo5pgT7", - "designer_id": "YRmNWCQuQdAWbR8u7eP4", - "piece_name": "Red Monty", - "image_name": "1rjJDBYmLo5pgT7.jpg", - "description": "" - } -``` -*** - -**PATCH** _/pieces/{piece_id}_ HTTP/1.1 - -Updates information for a specific piece. -| Parameter | Type | Description -| ----------- | :-----------: | ----------- | -| piece_name | `string` | `optional` A piece's name. | -| image_name | `string` | `optional` Name of the image uploaded for the piece. | -| description | `string` | `optional` A description of the piece (max length: 400 characters). | - -**Response** - -Returns a single piece object containing the following data. -| Key | Type | Description -| ----------- | ----------- | ----------- | -| piece_id | `string` | Unique value assigned when a piece in the database. | -| designer_id | `string` | A designer user's unique id. | -| piece_name | `string` | A piece's name. Determined by the designer. | -| image_name | `string` | Name of the image uploaded for the piece. | -| description | `string` | A description of the piece. | - -**Example** - -Request: -```http -PATCH /users/H094iAjZyPWr4rm0y9WL -``` -Request Body: -```json -{ - "piece_name": "Red Python", - "description": "This sizzling masterpiece entwines the fierce allure of red with a sleek python pattern. The sultry silhouette, adorned with glistening serpent scales, invites you to embrace the wild side. A bold statement, embodying passion and power in every slither." -} -``` -Response: -```json -{ - "piece_id": "1rjJDBYmLo5pgT7", - "designer_id": "YRmNWCQuQdAWbR8u7eP4", - "piece_name": "Red Python", - "image_name": "1rjJDBYmLo5pgT7.jpg", - "description": "This sizzling masterpiece entwines the fierce allure of red with a sleek python pattern. The sultry silhouette, adorned with glistening serpent scales, invites you to embrace the wild side. A bold statement, embodying passion and power in every slither." -} -``` diff --git a/Vechain-EasyA-Hackathon-Boston-Oct-2023/applications/artika_refashion (new).md b/Vechain-EasyA-Hackathon-Boston-Oct-2023/applications/artika_refashion (new).md deleted file mode 100644 index 68cc1d31..00000000 --- a/Vechain-EasyA-Hackathon-Boston-Oct-2023/applications/artika_refashion (new).md +++ /dev/null @@ -1,139 +0,0 @@ -# Vechain -Easy A Startup Grant Application Template -Hackathon Date: 7-8th Oct 2023 - -## Project Overview -- Problem statement: BCG track -- Are you applying for the grant with the same project you submitted at the vechain Hackathon: Yes -- Project name: Artika Refashion -- Team name: Artika Refashion -- GitHub handle: Zibilicious -- College / Employer: Boston University -- Payment Address: 0x50545abB29D7e1724d04958eB2c31aBEF4227559 - -### Overview - -We are Artika Refashion, a marketplace that connects independent fashion designers to users for fixing, upstyling, and innovating fashion. It all starts with a user's piece - a vintage jacket handed down from father to father, for example. This jacket has sentimental and monetary value but now needs upstyling or repair. That's where we come in: users can connect with fashion designers to customize or upgrade existing pieces, and the change is recorded on-chain, via NFTs representative of the clothing. Over time this will tell a story, which further adds value and expression to the piece. -With Artika 2.0, we directly partner with brands to create clothing tagged with NFTs. With this approach, we can include even more information about a piece, like verifying that its production is environmentally friendly or the materials used. At this stage, we can tie in loyalty tokens for exclusive content from brands, which further establishes them as environmentally friendly and rewards users for being a part of our platform. Vechain is a sustainable blockchain with EVM compatibility, low gas fees, and a focus on sustainability. With a rich ecosystem of libraries, would provide the best development and user experience. - -### Project Details - -- [BCG One-pager](https://docs.google.com/presentation/d/1Luw6KogeUF-JXmZVR5bVUMikw8UoAuFe/edit#slide=id.p1) -- [Pitch Deck](https://www.canva.com/design/DAFwn8CgBDg/FY_CvfOqyIX_y02IhlxmWg/edit?utm_content=DAFwn8CgBDg&utm_campaign=designshare&utm_medium=link2&utm_source=sharebutton) -- [UI Mockups/designs](https://www.figma.com/file/c6xrEmp5I8KnHepTvaHxwK/artika-refashion?type=design&node-id=0-1&mode=design&t=uaGC8cLWyiq9SIkn-0) -- [API specifications](https://github.com/IainWinter/Artika/blob/main/docs/api.md) - -### Tech stack - -- Smart contracts, written in Solidity, on VeChainThor. -- React Native frontend to create single codebase for all platforms (iOS, Android, Web). -- back4app BaaS to efficiently create, manage and scale backend resources. -- RESTful API backend made with back4app. -- Real-time database, provided by back4app, to store user data and link related objects. - -### PoC -Our PoC was submitted to the VeChain/EasyA hackathon and can be found [here](https://github.com/IainWinter/ArtikaRefashion) - -### Ecosystem Fit -We differ as the only fashion SaaS company in Web3, with a digital platform that connects independent fashion designers to users, promoting circular fashion by means of fixing, upstyling, and innovating fashion. Moreover, while sustainable supply chain tracking has been applied to many industries, no venture allows the consumer to view the product’s sustainable production and renovation history, to which they can contribute (sustainable supply chain tracking is introduced in Artika 2.0). - -* Web2 Competitors: - * Depop - * Poshmark - * Thredup - * Stitch Fix - * Fiverr - * Upwork - * Etsy - -## Team - -### Team members - -- Zi Zheng (Team Lead) -- Alika Grigorova (Project manager) -- Anna Sokolova (Project manager) - -### Team Website - -- [artikarefashion.com](https://www.artikarefashion.com/) - -### Team's experience - -* Zi - * Zi has 4+ years of experience working cross-functionally developing and managing mobile apps and websites from marketing agencies and startups to global corporations like Goodyear and Bank of America. - * https://www.zizheng.io/ -* Anna - * Anna has started multiple initiatives and held club leadership positions , as well as gained professional experience managing operations as an intern at Berkshire Hathaway HomeServices. -* Alika - * Alika has worked as a project manager for non-profit initiatives, and gained professional experience as a financial analyst in a private business company. - -### Team Code Repos - -- https://github.com/IainWinter/ArtikaRefashion -- https://github.com/IainWinter/Artika - -### Team LinkedIn Profiles - -- https://www.linkedin.com/in/zi-zheng/ -- https://www.linkedin.com/in/anna-sokolova-419a41273/ -- https://www.linkedin.com/in/alika-grigorova-61159b281/ - -## Development Roadmap - -#### Overview - -| | Milestone 1 | Milestone 2 | Milestone 3 | Milestone 4 | Total | -| -------------------------- | ----------- | ----------- | ----------- | ----------- | -------- | -| Estimated Duration | 30 d | 60 d | 30 d | 20 d | 140 d | -| Full-time equivalent (FTE) | 2 | 2 | 1 | 1 | 5 | -| Cost (up to $ 30,000) | $ 5,000 | $ 5,000 | $ 10,000 | $ 10,000 | $ 30,000 | - -#### Milestone 1 — Backend & Smart Contracts -| Number | Deliverable | Specification | -| ------ | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------- | -| 1. | Documentation | Create the full specification of our API and data requirements for the storage of text and images. | -| 2. | Smart Contracts | Create smart contracts for adding tracking data points to an NFT. Provide an API for users to mint their own NFTs for their clothes | -| 3. | Backend | Create the backend API and a simple test suit. | -| 4. | Simplest Frontend | Create a simple HTML frontend without any styling to gain an idea of our app's requirements for state management. | - -#### Milestone 2 — Backend -| Number | Deliverable | Specification | -| ------ | ---------------- | ------------------------------------------------------------------------------------------- | -| 1. | Documentation | Create in-depth documentation outlining API functionality (smart contract triggers, user authentication, data management). | -| 2. | back4app | Create resources (API, databases, test data, etc.) on the back4app platform, as outlined in the documentation. | -| 3. | Smart Contracts | Create smart contracts for tracking user history stored on VeChain Thor (conducted on the VeChain testnet by interacting with a public node via the Thorest API). | -| 4. | UI | Create barebones UI in in react native to ensure basic frontend-backend communication. | -| 5. | Unit Testing | Conduct unit testing of all major functions and smart contracts to ensure business logic robustness. | - -### Milestone 3 - Frontend -| Number | Deliverable | Specification | -| ------ | ------------ | --------------------------------------------------------------------------------------------------------- | -| 1. | Build UI | Iteratively build frontend according to design mockups; Done on a per screen basis where functionality is consistent across all platforms. | -| 2. | Connect Backend | Install the ```Parse SDK``` via respective node module and initialize it using App Keys provided on the back4app website. | -| 3. | Functional Testing | Ensure UI interactions propagate through API to trigger smart contracts and testnet updates. Similar testing for traditional database querying and updates. | - -### Milestone 4 - Deployment & Marketing -| Number | Deliverable | Specification | -| ------ | --------------- | -------------------------------------------------------------------------------- | -| 1. | Deployment | Deplay app on the App and Google Play Store. Store compliance would have been verified in previous milestone while creating beta builds of the app. | -| 2. | Write tutorials | Create blog posts on the website to teach new users how to best use our product. | -| 3. | Marketing | Create a marketing campaign to attract new users. | - -## Future Plans - -### Artika 1.0: -Build a decentralized platform to connect designers and users to facilitate sustainable fashion. Each piece of clothing will be represented as an NFT, each with a unique story, encouraging users to repair and upstyle their clothes instead of throwing them away. - -### Artika 2.0: -Introduce a "sustainably produced" line of clothing, tracked through NFTs and historical records in the supply chain. Our tokenized loyalty system will include Early Access Tokens and VIP Event Access Tokens, which enhance demand and create unique opportunities for users. This collaboration is mutually beneficial, allowing luxury brands to build a "green" reputation without sacrificing profits while gaining new customers. ARTIKA 2.0 also enables users to trade redesigned clothing, boosting engagement and demand. Our long-term vision is to become the go-to social media app in the Web3 fashion industry for entertainment, inspiration, and services. - -## Additional Information - -We have already created UI mockups and a pitch deck which was presented at the Vechain/EasyA hackathon at Harvard. We won 2nd place on the BCG track with these assets, and have edited them since then to reflect the budget and time available provided by this grant. We have not applied for any other grants. - -## Points of contact: -- Peter Zhou (Chief scientist at Vechain) -- Marina Fortunato (Project manager at Vechain) -- Bernhard Kronfellner (Boston Consulting Group) - - diff --git a/Vechain-EasyA-Hackathon-Boston-Oct-2023/applications/sozo_infashion.md b/Vechain-EasyA-Hackathon-Boston-Oct-2023/applications/sozo_infashion.md index 66e38ad7..59d570b2 100644 --- a/Vechain-EasyA-Hackathon-Boston-Oct-2023/applications/sozo_infashion.md +++ b/Vechain-EasyA-Hackathon-Boston-Oct-2023/applications/sozo_infashion.md @@ -31,7 +31,7 @@ As different philosophies and Vechain implementation ideas emerged while working - [BCG One-pager](https://docs.google.com/presentation/d/1Luw6KogeUF-JXmZVR5bVUMikw8UoAuFe/edit#slide=id.p1) - [Pitch Deck](https://www.canva.com/design/DAFwn8CgBDg/FY_CvfOqyIX_y02IhlxmWg/edit?utm_content=DAFwn8CgBDg&utm_campaign=designshare&utm_medium=link2&utm_source=sharebutton) - [UI Mockups/designs](https://www.figma.com/file/c6xrEmp5I8KnHepTvaHxwK/artika-refashion?type=design&node-id=0-1&mode=design&t=uaGC8cLWyiq9SIkn-0) -- [API specifications](https://github.com/KShervington/sozo-infashion-api/blob/5374a16ffee270c1c615674251f3ab389a76f678/API%20Reference.md) +- [API specifications](https://github.com/KShervington/sozo-infashion-api/blob/main/API%20Reference.md) ### Tech stack