├── .github ├── ISSUE_TEMPLATE │ ├── config.yml │ └── open_an_issue.md └── workflows │ ├── generated-pr.yml │ └── stale.yml ├── CONTRIBUTING.md ├── CONTRIBUTING_GO.md ├── CONTRIBUTING_JS.md ├── DOCS_STYLEGUIDE.md ├── ISSUE_LABELS.md ├── LICENSE ├── LICENSING_POLICY.md ├── PLAN_A_MEETUP.md ├── README.md ├── ROADMAP.md ├── SECURITY.md ├── amending-commits.md ├── articles └── endangered-data.md ├── assets ├── CodeIsMoreLikeGuidelines.jpg ├── bg-meetup-com.jpeg ├── ethipfs │ ├── eth<3ipfs.png │ ├── ipfs-eth-grey.svg │ ├── ipfs-eth-somecolor.svg │ └── srcs │ │ ├── ethereum_logo_PC.svg │ │ └── ipfs-logo-vector-ice.svg ├── header-meetup-com.jpeg └── ipfs_image.jpeg ├── code-of-conduct-for-events.md ├── code-of-conduct-procedures-for-events.md ├── code-of-conduct.md ├── decisions └── community-forum-platform.md ├── dev ├── hooks │ └── setup_commit_msg_hook.sh ├── mkmrconfig.sh ├── readme-templates │ ├── ipfs.md │ ├── ipld.md │ ├── libp2p.md │ └── multiformats.md ├── readmes │ ├── README.md │ └── example-config.js └── scripts │ ├── clone_all_repos.sh │ └── update_git_repos.sh ├── docs └── developer-certificate-of-origin ├── ecosystem-audit ├── README.md └── ipfs-ecosystem-header.png ├── meeting-notes └── 2022-10-30-community-roundtable.md ├── okrs └── 2019-q1.md ├── projects ├── 4EVERLAND.md ├── AdaptiveClaims.md ├── AletheiaData.md ├── Anonymous Hawk.md ├── AuctionHouse.md ├── BlockchainTicketing.md ├── BraineumVerse.md ├── CID-Management-Webapp.md ├── CommunityGarden.md ├── Covision.md ├── Creativerse.md ├── CryptoSouls.md ├── DAOInsure.md ├── DBS-Decentralized Broadcast & Stream.md ├── DeFiBattles.md ├── DeStore.md ├── DefiTogether.md ├── Dexplorer.md ├── DodgingTurtis.md ├── Dspyt-NFTs.md ├── DungeonCrawler.md ├── ETHmySong.md ├── Esteroids.md ├── Evido.md ├── Flutter_IPFS_Plugin.md ├── Fractio.xyz ├── Heavenly Jungle NFT ├── HouseSec.md ├── HubShare.md ├── IPFS-Drop.md ├── IPFSScan.md ├── IPFSfB.md ├── IPLDDistributedDatasets ├── IPNS-Link.md ├── IPNSGoServer.md ├── Juni::Db.md ├── LandMine.md ├── Lifefram.md ├── MashApp.md ├── Meta Manager.md ├── MetaPets.md ├── Monaliza.md ├── NFT Museum ├── NFTIZ.md ├── NetSepio.md ├── NiftySubs.md ├── Ownft.md ├── PaperHouse.md ├── PassVault.md ├── Phi.md ├── Pictic.md ├── Rhada.md ├── RunETH.md ├── SecondLanguagePlayground.md ├── Slick.md ├── Socio Dapp.md ├── Sytime.md ├── The Convo Space.md ├── TrueBlocks.md ├── TrueRaffle.md ├── VoidReplica.md ├── WeatherChainXM.md ├── a-jam.md ├── afterme.md ├── box.md ├── chanceofxyz.md ├── codeworknft.md ├── creatorr.md ├── cryptoChampz.md ├── defluencertoolkit.md ├── genft.md ├── git3.md ├── immutable.md ├── interplanetary-contact.md ├── ipfs-chat.md ├── ipfs-cidsail.md ├── luxurify.md ├── mbondX.md ├── meetwithwallet.md ├── nft-import.md ├── nftbase.md ├── nftwitch.md ├── niftyroyale.md ├── pdarm.md ├── plebbit.md ├── py-is_ipfs.MD ├── realityDapp.md ├── smartCOOP.md ├── stonent.md ├── truesight.md └── yaytso.md ├── swatches ├── 0e8a16.png ├── 1cfc60.png ├── 3f4b56.png ├── 7057ff.png ├── b52ed1.png ├── b60205.png ├── bfe5bf.png ├── c7def8.png ├── ccf0ed.png ├── d93f0b.png ├── dcc8e0.png ├── e99695.png ├── e9dfeb.png ├── ededed.png ├── f9d0c4.png ├── fc2929.png └── fef2c0.png └── templates └── project-submission-template.md /.github/ISSUE_TEMPLATE/config.yml: -------------------------------------------------------------------------------- 1 | blank_issues_enabled: false 2 | contact_links: 3 | - name: Getting Help on IPFS 4 | url: https://ipfs.io/help 5 | about: All information about how and where to get help on IPFS. 6 | - name: IPFS Official Forum 7 | url: https://discuss.ipfs.io 8 | about: Please post general questions, support requests, and discussions here. 9 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/open_an_issue.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Open an issue 3 | about: Only for actionable issues relevant to this repository. For security issue or abuse report, please see our security policy. 4 | title: '' 5 | labels: need/triage 6 | assignees: '' 7 | 8 | --- 9 | 20 | -------------------------------------------------------------------------------- /.github/workflows/generated-pr.yml: -------------------------------------------------------------------------------- 1 | name: Close Generated PRs 2 | 3 | on: 4 | schedule: 5 | - cron: '0 0 * * *' 6 | workflow_dispatch: 7 | 8 | permissions: 9 | issues: write 10 | pull-requests: write 11 | 12 | jobs: 13 | stale: 14 | uses: ipdxco/unified-github-workflows/.github/workflows/reusable-generated-pr.yml@v1 15 | -------------------------------------------------------------------------------- /.github/workflows/stale.yml: -------------------------------------------------------------------------------- 1 | name: Close Stale Issues 2 | 3 | on: 4 | schedule: 5 | - cron: '0 0 * * *' 6 | workflow_dispatch: 7 | 8 | permissions: 9 | issues: write 10 | pull-requests: write 11 | 12 | jobs: 13 | stale: 14 | uses: ipdxco/unified-github-workflows/.github/workflows/reusable-stale-issue.yml@v1 15 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | The MIT License (MIT) 2 | 3 | Copyright (c) 2019 Protocol Labs, Inc. 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in 13 | all copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN 21 | THE SOFTWARE. 22 | -------------------------------------------------------------------------------- /LICENSING_POLICY.md: -------------------------------------------------------------------------------- 1 | # IPFS Licensing Policy 2 | 3 | In order to ensure an open source project is actually open and re-usable in a legal sense, it’s critical that licensing information is clear. Repositories in the `ipfs`, `libp2p`, and `ipld` organizations should all follow this policy for licensing their contents. 4 | 5 | Unless there is a particular reason to use a different licensing structure, please use the following for new projects: 6 | 7 | 1. Copyright should always be assigned to **Protocol Labs, Inc.,** regardless of the type of license. (In an ideal future, we can assign copyright to a foundation, but Protocol Labs is the best usable legal entity we have now.) 8 | 9 | 2. All software code should be licensed under the MIT license. Canonical license text for the MIT license can be found in this repository’s [`LICENSE` file](../LICENSE) or at the [Open Source Initiative website](https://opensource.org/licenses/MIT). 10 | 11 | 2. All documentation and non-code resources (e.g. logos and imagery) should be licensed under the Creative Commons Attribution 4.0 International (CC BY 4.0) license. An [easy-to-read, linkable description](https://creativecommons.org/licenses/by-sa/4.0/) and canonical license text in [HTML](https://creativecommons.org/licenses/by/4.0/legalcode) and [plain text](https://creativecommons.org/licenses/by/4.0/legalcode.txt) can be found at the Creative Commons website. 12 | 13 | If a repository is a software project with some built-in docs or resources (e.g. `go-ipfs`), it can all be licensed under the MIT license. The CC BY license is meant for projects that are not overwhelmingly code, such as websites, guidance, discussion repos, and so on. 14 | 15 | 16 | ## Attaching a License 17 | 18 | When licensing a project, be sure to: 19 | 20 | 1. Name the license and provide a link to it from the project README under the heading “license.” Example: 21 | 22 | ```md 23 | ## License 24 | 25 | Copyright (c) Protocol Labs, Inc. under the ****. See [LICENSE file](./LICENSE) for details. 26 | ``` 27 | 28 | Or for multiple licenses: 29 | 30 | ```md 31 | ## License 32 | 33 | All software code is copyright (c) Protocol Labs, Inc. under the **MIT license**. 34 | 35 | Other written documentation and content is copyright (c) Protocol Labs, Inc. under the **Creative Commons Attribution License**. 36 | 37 | See [LICENSE file](./LICENSE) for details. 38 | ``` 39 | 40 | 2. For software that will be redistributed, the full text of the license(s) **must** be in a file named `LICENSE` in the repository root. Other projects **should** do this, too, but their readmes can alternatively link to a separate license document, like this: [Creative Commons Attribution](https://creativecommons.org/licenses/by/4.0/). 41 | 42 | 43 | ## Contributor Licensing (DCO) 44 | 45 | We manage contributor licensing via a *Developer Certificate of Origin (DCO).* All commits with new code from any contributor **must** include a DCO signoff trailer. See the [contributing guide part 2](../CONTRIBUTING-2.md#a-license-and-a-signed-off-by-trailers-are-required) for more details. Commits with extremely trivial or changes or that do not change content (e.g. merge commits) are excepted. 46 | 47 | If you’re setting up a new repository, make sure the README includes a link to our contribution guidelines so people can find information about the DCO signoff. 48 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | # Security Policy 2 | 3 | ## Reporting a Vulnerability 4 | 5 | The IPFS protocol and its implementations are in varying but active levels of development. This means that there may be problems in our protocols, or there may be mistakes in our implementations. We take security vulnerabilities very seriously. If you discover a security issue, please bring it to our attention right away! 6 | 7 | If you find a vulnerability that may affect live deployments -- for example, expose a remote execution exploit -- please send your report privately to either: 8 | 1. The implementation team if its an issue with a particular implementation OR 9 | 2. security@ipfs.io if you're not sure or if its an underlying issue with an IPFS protocol. 10 | Please DO NOT file a public issue. 11 | 12 | If the issue is a protocol weakness or something not yet deployed, just discuss it openly. 13 | 14 | ## Reporting Abuse 15 | 16 | While [IPFS is a stack of protocols and tools for moving content-addressed data](https://specs.ipfs.tech/architecture/principles/), there is often confusion about one particular manifestation of IPFS in [HTTP Gateways](https://docs.ipfs.tech/concepts/ipfs-gateway/) like https://ipfs.io/ipfs. We have seen a lot of reports about **abuse 17 | from these IPFS gateways** (e.g. using an HTTP gateway for malware hosting, distributing questionable content, phishing purposes, etc.). These should be reported directly to the HTTP gateway product that provides the data. 18 | To report abuse about the ipfs.io HTTP gateway, please send an email to [abuse@ipfs.tech](mailto:abuse@ipfs.tech). Do not open an issue here since IPFS is a community project, and is not the same as the ipfs.io HTTP gateway. 19 | -------------------------------------------------------------------------------- /assets/CodeIsMoreLikeGuidelines.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/assets/CodeIsMoreLikeGuidelines.jpg -------------------------------------------------------------------------------- /assets/bg-meetup-com.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/assets/bg-meetup-com.jpeg -------------------------------------------------------------------------------- /assets/ethipfs/eth<3ipfs.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/assets/ethipfs/eth<3ipfs.png -------------------------------------------------------------------------------- /assets/ethipfs/srcs/ethereum_logo_PC.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 17 | 20 | 23 | 26 | 29 | 33 | 36 | 41 | 42 | 43 | -------------------------------------------------------------------------------- /assets/ethipfs/srcs/ipfs-logo-vector-ice.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | -------------------------------------------------------------------------------- /assets/header-meetup-com.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/assets/header-meetup-com.jpeg -------------------------------------------------------------------------------- /assets/ipfs_image.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/assets/ipfs_image.jpeg -------------------------------------------------------------------------------- /dev/hooks/setup_commit_msg_hook.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | # 3 | # Put this script inside the root folder of your git directory before running it. 4 | 5 | cat >.git/hooks/commit-msg <<'EOF' 6 | #!/bin/sh 7 | 8 | grep "^License:" "$1" || { 9 | echo >>"$1" 10 | echo "License: MIT" >>"$1" 11 | echo "Signed-off-by: $(git config user.name) <$(git config user.email)>" >>"$1" 12 | } 13 | EOF 14 | chmod +x .git/hooks/commit-msg 15 | 16 | -------------------------------------------------------------------------------- /dev/mkmrconfig.sh: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env bash 2 | set -eo pipefail; [[ $MKMRCONFIG_TRACE ]] && set -x 3 | 4 | # Scans Github organizations and emits a config file for use with `myrepos`. 5 | # 6 | # Dependencies: 7 | # myrepos -- https://myrepos.branchable.com 8 | # e.g. apt-get install myrepos 9 | # 10 | # Usage: 11 | # > cd $GOPATH/src/github.com/ 12 | # > path/to/mkmrconfig.sh > .mrconfig 13 | # > mr --trust-all checkout 14 | # > mr -m status 15 | # 16 | # Notes: 17 | # - Repos not starting in "go-" need to be added to more_repos. 18 | # - Watch out for Github API's requests limit, set $auth if necessary. 19 | 20 | # github oauth, e.g. "-u lgierth:personalaccesstoken" 21 | auth="" 22 | 23 | orgs=(ipfs ipld libp2p multiformats ipfs-shipyard gxed) 24 | 25 | list_repos () { 26 | org="$1" 27 | per_page=100 28 | page=1 29 | [ "$2" ] && page="$2" 30 | repos=$(curl $auth "https://api.github.com/orgs/$org/repos?page=$page&per_page=$per_page" 2>/dev/null | jq -r '.[] | "\(.name),\(.ssh_url)"') 31 | i=$(printf %s\\n "$repos" | wc -l) 32 | printf %s\\n "$repos" 33 | if test "$i" -ge "$per_page"; then 34 | list_repos "$org" $(expr "$page" + 1) 35 | fi 36 | } 37 | 38 | for org in ${orgs[@]}; do 39 | >&2 echo "# scanning github.com/$org" 40 | for r in `list_repos "$org"`; do 41 | name="$(echo "$r" | cut -d, -f1)" 42 | url="$(echo "$r" | cut -d, -f2)" 43 | echo "[$org/$name]" 44 | echo "checkout = git clone $url" 45 | echo 46 | done 47 | done 48 | -------------------------------------------------------------------------------- /dev/readme-templates/ipfs.md: -------------------------------------------------------------------------------- 1 | # 2 | 3 | [![](https://img.shields.io/badge/made%20by-Protocol%20Labs-blue.svg?style=flat-square)](http://ipn.io) 4 | [![](https://img.shields.io/badge/project-IPFS-blue.svg?style=flat-square)](https://ipfs.io) 5 | [![](https://img.shields.io/badge/freenode-%23ipfs-blue.svg?style=flat-square)](https://webchat.freenode.net/?channels=%23ipfs) 6 | [![](https://img.shields.io/badge/readme%20style-standard-brightgreen.svg?style=flat-square)](https://github.com/RichardLitt/standard-readme) 7 | 8 | > 9 | 10 | 11 | 12 | ## Table of Contents 13 | 14 | 15 | 16 | ## Install 17 | 18 | 19 | 20 | ## Usage 21 | 22 | 23 | 24 | ## Maintainers 25 | 26 | Captain: [](https://github.com/). 27 | 28 | ## Contribute 29 | 30 | Please contribute! [Look at the issues](https://github.com/ipfs//issues)! 31 | 32 | Check out our [contributing document](https://github.com/ipfs/ipfs/blob/master/contribute.md) for more information on how we work, and about contributing in general. Please be aware that all interactions related to IPFS are subject to the IPFS [Code of Conduct](https://github.com/ipfs/community/blob/master/code-of-conduct.md). 33 | 34 | Small note: If editing the README, please conform to the [standard-readme](https://github.com/RichardLitt/standard-readme) specification. 35 | 36 | ## License 37 | 38 | [MIT](LICENSE) © 2016 Protocol Labs Inc. 39 | -------------------------------------------------------------------------------- /dev/readme-templates/ipld.md: -------------------------------------------------------------------------------- 1 | # 2 | 3 | [![](https://img.shields.io/badge/made%20by-Protocol%20Labs-blue.svg?style=flat-square)](http://ipn.io) 4 | [![](https://img.shields.io/badge/project-IPLD-blue.svg?style=flat-square)](http://github.com/ipld/ipld) 5 | [![](https://img.shields.io/badge/freenode-%23ipfs-blue.svg?style=flat-square)](http://webchat.freenode.net/?channels=%23ipfs) 6 | [![](https://img.shields.io/badge/readme%20style-standard-brightgreen.svg?style=flat-square)](https://github.com/RichardLitt/standard-readme) 7 | 8 | > 9 | 10 | 11 | 12 | ## Table of Contents 13 | 14 | 15 | 16 | ## Install 17 | 18 | 19 | 20 | ## Usage 21 | 22 | 23 | 24 | ## Lead 25 | 26 | - [](https://github.com/) 27 | 28 | ## Contribute 29 | 30 | Please contribute! [Look at the issues](https://github.com/ipld//issues)! 31 | 32 | Check out our [contributing document](https://github.com/ipld/ipld/blob/master/contributing.md) for more information on how we work, and about contributing in general. Please be aware that all interactions related to IPLD are subject to the IPFS [Code of Conduct](https://github.com/ipfs/community/blob/master/code-of-conduct.md). 33 | 34 | Small note: If editing the README, please conform to the [standard-readme](https://github.com/RichardLitt/standard-readme) specification. 35 | 36 | ## License 37 | 38 | [MIT](LICENSE) © 2016 Protocol Labs Inc. 39 | -------------------------------------------------------------------------------- /dev/readme-templates/libp2p.md: -------------------------------------------------------------------------------- 1 | # 2 | 3 | [![](https://img.shields.io/badge/made%20by-Protocol%20Labs-blue.svg?style=flat-square)](http://ipn.io) 4 | [![](https://img.shields.io/badge/project-libp2p-blue.svg?style=flat-square)](http://github.com/libp2p/libp2p) 5 | [![](https://img.shields.io/badge/freenode-%23ipfs-blue.svg?style=flat-square)](http://webchat.freenode.net/?channels=%23ipfs) 6 | [![](https://img.shields.io/badge/readme%20style-standard-brightgreen.svg?style=flat-square)](https://github.com/RichardLitt/standard-readme) 7 | 8 | > 9 | 10 | 11 | 12 | ## Table of Contents 13 | 14 | 15 | 16 | ## Install 17 | 18 | 19 | 20 | ## Usage 21 | 22 | 23 | 24 | ## Lead 25 | 26 | - [](https://github.com/) 27 | 28 | ## Contribute 29 | 30 | Please contribute! [Look at the issues](https://github.com/libp2p//issues)! 31 | 32 | Check out our [contributing document](https://github.com/libp2p/community/blob/master/CONTRIBUTE.md) for more information on how we work, and about contributing in general. Please be aware that all interactions related to libp2p are subject to the IPFS [Code of Conduct](https://github.com/ipfs/community/blob/master/code-of-conduct.md). 33 | 34 | Small note: If editing the README, please conform to the [standard-readme](https://github.com/RichardLitt/standard-readme) specification. 35 | 36 | ## License 37 | 38 | [MIT](LICENSE) © 2016 Protocol Labs Inc. 39 | -------------------------------------------------------------------------------- /dev/readme-templates/multiformats.md: -------------------------------------------------------------------------------- 1 | # 2 | 3 | [![](https://img.shields.io/badge/made%20by-Protocol%20Labs-blue.svg?style=flat-square)](http://ipn.io) 4 | [![](https://img.shields.io/badge/project-multiformats-blue.svg?style=flat-square)](https://github.com/multiformats/multiformats) 5 | [![](https://img.shields.io/badge/freenode-%23ipfs-blue.svg?style=flat-square)](https://webchat.freenode.net/?channels=%23ipfs) 6 | [![](https://img.shields.io/badge/readme%20style-standard-brightgreen.svg?style=flat-square)](https://github.com/RichardLitt/standard-readme) 7 | 8 | [![Circle CI](https://img.shields.io/circleci/PROJECT/github/PROJECT/REPO.svg?style=flat-square)](https://circleci.com/gh/PROJECT/REPO) 9 | 10 | [![Travis CI](https://img.shields.io/travis/PROJECT/REPO.svg?style=flat-square&branch=master)](https://travis-ci.org/PROJECT/REPO) 11 | [![codecov.io](https://img.shields.io/codecov/c/github/PROJECT/REPO.svg?style=flat-square&branch=master)](https://codecov.io/github/PROJECT/REPO?branch=master) 12 | 13 | > 14 | 15 | 16 | 17 | ## Table of Contents 18 | 19 | 20 | 21 | ## Install 22 | 23 | 24 | 25 | ## Usage 26 | 27 | 28 | 29 | ## Lead 30 | 31 | - [](https://github.com/) 32 | 33 | ## Contribute 34 | 35 | Please contribute! [Look at the issues](https://github.com/multiformats//issues)! 36 | 37 | Check out our [contributing document](https://github.com/multiformats/multiformats/blob/master/contributing.md) for more information on how we work, and about contributing in general. Please be aware that all interactions related to multiformats are subject to the IPFS [Code of Conduct](https://github.com/ipfs/community/blob/master/code-of-conduct.md). 38 | 39 | Small note: If editing the README, please conform to the [standard-readme](https://github.com/RichardLitt/standard-readme) specification. 40 | 41 | ## License 42 | 43 | [MIT](LICENSE) © 2016 Protocol Labs Inc. 44 | -------------------------------------------------------------------------------- /dev/readmes/README.md: -------------------------------------------------------------------------------- 1 | # standard readmes 2 | 3 | The `example-config.js` provided is to be used with [RichardLitt/standard-readme-linter-regex](https://github.com/RichardLitt/standard-readme-linter-regex). 4 | 5 | Use the example templates in `examples/readme-templates` to see how these should look. 6 | 7 | -------------------------------------------------------------------------------- /dev/readmes/example-config.js: -------------------------------------------------------------------------------- 1 | const escapeRegExp = require('escape-string-regexp') 2 | 3 | // Default best way is to pass in all options from main module 4 | module.exports = function plugin (opts, data) { 5 | // You could also just use the default opts object, and return that 6 | const check = {} 7 | 8 | opts.projectName = opts.projectName || opts.project 9 | opts.projectLink = opts.projectLink || `https://github.com/${opts.project}/${opts.project}` 10 | 11 | // These are example checks, used by Protocol Labs for checking the IPFS, multiformats, IPLD, and libp2p organizations 12 | check.projectBadge = ('' + data).match(escapeRegExp(`[![](https://img.shields.io/badge/project-${opts.projectName}-blue.svg?style=flat-square)](${opts.projectLink})`)) 13 | check.freenodeBadge = ('' + data).match(escapeRegExp(`[![](https://img.shields.io/badge/freenode-%23ipfs-blue.svg?style=flat-square)](https://webchat.freenode.net/?channels=%23ipfs)`)) 14 | check.labsBadge = ('' + data).match(escapeRegExp(`[![](https://img.shields.io/badge/made%20by-Protocol%20Labs-blue.svg?style=flat-square)](http://ipn.io)`)) 15 | check.travis = ('' + data).match(escapeRegExp(`[![Travis CI](https://travis-ci.org/${opts.project}/${opts.repo}.svg?branch=master)](https://travis-ci.org/${opts.project}/${opts.repo})`)) 16 | check.cicleci = ('' + data).match(escapeRegExp(`[![Circle CI](https://circleci.com/gh/${opts.project}/${opts.repo}.svg?style=svg)](https://circleci.com/gh/${opts.project}/${opts.repo})`)) 17 | check.labsLicense = ('' + data).match(`Protocol Labs Inc.`) 18 | check.coc = ('' + data).match(new RegExp(`Please be aware that all interactions related to ${opts.projectName}`, 'gi')) 19 | check.cocLink = ('' + data).match(escapeRegExp('[Code of Conduct](https://github.com/ipfs/community/blob/master/code-of-conduct.md)')) 20 | check.contributorsLink = ('' + data).match(escapeRegExp(`https://github.com/${opts.project}/${opts.project}/blob/master/contributing.md`)) 21 | check.stdreadmeNote = ('' + data).match('Small note: If editing the README') 22 | check.notodo = !('' + data).match('(TODO|TBD)', 'gi') 23 | check.hackOnIPFS = !('' + data).match('Want to hack on IPFS', 'gi') 24 | 25 | return check 26 | } 27 | -------------------------------------------------------------------------------- /dev/scripts/clone_all_repos.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # 3 | # This script clones all repositories for a given organization into the current directory 4 | # It depends on https://www.npmjs.com/package/github-repositories 5 | # To install that: npm i -g github-repositories 6 | 7 | for i in $(github-repositories $1) 8 | do 9 | if [[ $i != *"https"* ]] 10 | then 11 | git clone "https://github.com/$1/$i" 12 | fi 13 | done 14 | -------------------------------------------------------------------------------- /dev/scripts/update_git_repos.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | # store the current dir 4 | CUR_DIR=$(pwd) 5 | 6 | # Let the person running the script know what's going on. 7 | echo "\n\033[1mPulling in latest changes for all repositories...\033[0m\n" 8 | 9 | # Find all git repositories and update it to the master latest revision 10 | for i in $(find . -name ".git" | cut -c 3-); do 11 | echo ""; 12 | echo "\033[33m"+$i+"\033[0m"; 13 | 14 | # We have to go to the .git parent directory to call the pull command 15 | cd "$i"; 16 | cd ..; 17 | 18 | # finally pull 19 | git co master 20 | git pull origin master; 21 | 22 | # let's get back to the CUR_DIR 23 | cd $CUR_DIR 24 | done 25 | 26 | echo "\n\033[32mComplete!\033[0m\n" -------------------------------------------------------------------------------- /docs/developer-certificate-of-origin: -------------------------------------------------------------------------------- 1 | Developer Certificate of Origin 2 | Version 1.1 3 | 4 | Copyright (C) 2004, 2006 The Linux Foundation and its contributors. 5 | 660 York Street, Suite 102, 6 | San Francisco, CA 94110 USA 7 | 8 | Everyone is permitted to copy and distribute verbatim copies of this 9 | license document, but changing it is not allowed. 10 | 11 | Developer's Certificate of Origin 1.1 12 | 13 | By making a contribution to this project, I certify that: 14 | 15 | (a) The contribution was created in whole or in part by me and I 16 | have the right to submit it under the open source license 17 | indicated in the file; or 18 | 19 | (b) The contribution is based upon previous work that, to the best 20 | of my knowledge, is covered under an appropriate open source 21 | license and I have the right under that license to submit that 22 | work with modifications, whether created in whole or in part 23 | by me, under the same open source license (unless I am 24 | permitted to submit under a different license), as indicated 25 | in the file; or 26 | 27 | (c) The contribution was provided directly to me by some other 28 | person who certified (a), (b) or (c) and I have not modified 29 | it. 30 | 31 | (d) I understand and agree that this project and the contribution 32 | are public and that a record of the contribution (including all 33 | personal information I submit with it, including my sign-off) is 34 | maintained indefinitely and may be redistributed consistent with 35 | this project or the open source license(s) involved. 36 | -------------------------------------------------------------------------------- /ecosystem-audit/ipfs-ecosystem-header.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/ecosystem-audit/ipfs-ecosystem-header.png -------------------------------------------------------------------------------- /projects/AdaptiveClaims.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | "Responsible Minerals Claim System" 3 | 4 | ## Category 5 | Application 6 | 7 | 8 | ## Project Description 9 | Adaptive Resources (https://adaptiveresources.io) has created a NFT marketplace that provides incentives for responsible production and trade. Using the Adaptive web application, the supply chain actors who meet system onboarding requirements can create and exchange Adaptive Claims and Adaptive invoices. Supply chain actors who sell Adaptive Claims on the marketplace are rewarded with xDai upon upstream transfers of the claims they helped produce. The token can be exchanged for local currency or for due diligence services. 10 | 11 | 12 | ## Use of IPFS, Filecoin and Libp2p 13 | IPFS is used to store the claim documents, which record the commodity information, material properties, geographical location, and beneficiaries tied to a claim token. Claim tokens are NFTs stored on the xDai blockchain. The NFTs are sold to downstream actors in a supply chain to generate payouts for the beneficiaries of a claim. 14 | 15 | 16 | ## Project Status 17 | Fundraising 18 | 19 | 20 | ## Previews 21 | ![image](https://adaptiveclaim.s3.amazonaws.com/Screenshot+2021-10-05+085245.png) 22 | ![image](https://adaptiveclaim.s3.amazonaws.com/Screenshot+2021-10-05+085358.png) 23 | 24 | 25 | ## Target Audience 26 | Mining sectors located in high-risk, conflict-affected areas of globe 27 | 28 | 29 | ## Rough estimated user base (if applicable) 30 | 0 31 | 32 | 33 | ## Github repo 34 | Smart Contracts: 35 | https://github.com/PowVT/adaptive-smart-contracts 36 | 37 | ## Website 38 | https://app.adaptiveresources.io/ 39 | 40 | ## Docs 41 | White Paper: 42 | https://github.com/PowVT/adaptive-resources-white-paper 43 | 44 | ## Team Info 45 | The Adaptive team is made up of three business professionals Jonathan, Dave and Evan. Jonathan brings experience from across Africa, Europe, the Middle East, and North America. Jonathan has managed an extensive portfolio of public sector and private sector sustainability programs. Jonathan has been involved in supporting ASM sourcing guidance for the gold and 3T industry, including working as the Gold Technical Manager for a USAID-funded project. He has managed teams in Uganda and Rwanda in the responsible sourcing field. The team also includes a blockchain technology engineer, Evan (PowVT), who will support the development of the access to finance solutions used by the company and our partners. The company plans to pilot blockchain-based technology approaches that will improve access to finance for mining operators and exporters, in a manner that also benefits mine workers and local civil society actors. 46 | 47 | 48 | ### Team Size 49 | 3 team members 50 | 51 | ### Team members 52 | Jonathan 53 | Dave 54 | Evan 55 | 56 | ## How the community can engage 57 | * GitHub Discussion: https://github.com/ipfs/community/discussions/665 58 | * Email: evan@adaptiveresources.io 59 | * Slack: N/A 60 | * Twitter: N/A 61 | * Discord: N/A 62 | * Telegram: N/A 63 | * WeChat: N/A 64 | 65 | ## How to Contribute 66 | Contact Evan at the email address above. Or better submit a PR to the adaptive-smart-contracts repo. 67 | 68 | -------------------------------------------------------------------------------- /projects/AletheiaData.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Aletheia Data 3 | 4 | ## Category 5 | Application 6 | 7 | ## Project Description 8 | Aletheia is an Open Source project that seeks to encourage both public and private entities to facilitate access to public information so that it can have a more relevant social impact. 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | Yes, we use IPFS as our secure File Storage. We'd like to integrate Filecoin 12 | 13 | ## Project Status 14 | fundraising, shipped 15 | 16 | ## Previews 17 | You can see it at https://aletheiadata.org 18 | 19 | ## Target Audience 20 | Citizens, Journalists, Governments 21 | 22 | ## Github repo 23 | https://github.com/Aletheia-Data 24 | 25 | ## Website 26 | https://aletheiadata.org 27 | 28 | ## Docs 29 | https://docs.aletheiadata.org 30 | 31 | ## Team Info 32 | [Enzo Vezzaro](https://github.com/EnzoVezzaro) - Full Stack Engineer / Founder 33 | 34 | ### Team Size 35 | 1 Person 36 | 37 | ## How the community can engage 38 | * GitHub Discussion: https://github.com/ipfs/community/discussions/697 39 | * Email: aletheiadata@gmail.com 40 | * Slack: - 41 | * Twitter: https://twitter.com/DataAletheia 42 | * Discord: - 43 | * Telegram: - 44 | * WeChat: - 45 | 46 | ## How to Contribute 47 | https://docs.aletheiadata.org/general/open-source 48 | -------------------------------------------------------------------------------- /projects/AuctionHouse.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Auction House 3 | ## Category 4 | Application 5 | 6 | ## Project Description 7 | Auction House is a fully decentralized, and customized NFT Auction Marketplace. It is built using Ethereum Smart Contracts and leverages Rarible Protocol and IPFS for decentralized storage of media (images) and NFT metadata. 8 | 9 | ## Use of IPFS, Filecoin and Libp2p 10 | The application leverages IPFS technology as a decentralized storage solution for media (images) and NFT metadata. The use of IPFS as a decentralized storage solution ensures the application is censorship-resistant. 11 | 12 | ## Project Status 13 | The project is currently under development, and has participated and won a sponsor prize in the NFT Vision Hack. 14 | 15 | ## Previews 16 | ![AuctionHouse](https://drive.google.com/uc?export=view&id=1hkUd6xv2aALlbtXtd2OZjCMA-z0X9tqf) 17 | 18 | ## Target Audience 19 | NFT Owners, Auction Marketplace participants, NFT speculators 20 | 21 | ## Rough estimated user base (if applicable) 22 | No users currently, but estimated to onboard users for alpha version in early 2022. 23 | 24 | ## Github repo 25 | 26 | https://github.com/lmedury/auctionhouse 27 | 28 | ## Website 29 | 30 | 31 | Devpost submission: https://devpost.com/software/auction-house 32 | Try it out: https://lmedury.github.io/auctionhouse/ 33 | 34 | 35 | 36 | ## Team Info 37 | 38 | The team currently involves only 1 member, Lalith Medury, responsible for designing the smart contrcts, building the frontend and integrating IPFS and Rarible protocol into the application 39 | 40 | ### Team Size 41 | Currently, only 1 42 | 43 | ### Team members 44 | Lalith Medury - A senior year undergraduate, blockchain engineer and a full stack developer from India. 45 | 46 | ## How the community can engage 47 | * GitHub Discussion: https://github.com/ipfs/community/discussions/685 48 | * Email: lalith.aakash970@gmail.com 49 | * Twitter: https://twitter.com/LalithMedury 50 | * Discord: LalithM#0811 51 | * Telegram: @lmedury 52 | 53 | ## How to Contribute 54 | The project is still under early stages of development and we would like the users to try out the demo at the link mentioned above. 55 | We would also appreciate it if users/developers provide any feedback, suggestions for improvement, report bugs and/or suggest any additional features -------------------------------------------------------------------------------- /projects/BlockchainTicketing.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | 3 | Blockchain Ticketing 4 | 5 | ## Category 6 | 7 | 8 | Application 9 | 10 | ## Project Description 11 | 12 | 13 | A decentralised ticketing marketplace with three core features: 14 | 1. Use of smart contract to regulate the secondary market - currently popular events often end up with high ticket resale price 15 | 2. Each ticket is represented as an NFT - elimininate tickets fraud and ticket could become collectible at the end of event 16 | 3. Pre-event financing option - often times event organisers struggle to obtain loan from centralised institutions, our platform offer a decentralised method to raise loan from individual investors 17 | 18 | ## Use of IPFS, Filecoin and Libp2p 19 | 20 | 21 | * IPFS: ticket details are stored in IPFS to reduce on chain cost, while hash-based mechanism of IPFS also offers a tamper-proof ticket details 22 | * Filecoin: ticket is represented as an NFT and become collectible after event starts, therefore leveraging Filecoin for persistent storage 23 | 24 | ## Project Status 25 | 26 | 27 | Under development 28 | 29 | ## Previews 30 | 31 | 32 | ![image](https://i.ibb.co/1b8Gcz1/tixlab.png) 33 | 34 | ## Target Audience 35 | 36 | 37 | * Event organisers: create open and transparent events and offer a better customer experience 38 | * Ticket buyers: browse different events and purchase tickets securely 39 | 40 | ## Github repo 41 | 42 | 43 | [https://github.com/eerkaijun/tixlab](https://github.com/eerkaijun/tixlab) 44 | 45 | ## Website 46 | 47 | 48 | The website is currently under development. 49 | 50 | 51 | 52 | [NFT Hack Submission](https://www.youtube.com/watch?v=GKkhje97x68) 53 | 54 | [NFT Hack Finale Pitch](https://www.youtube.com/watch?v=b9vErLt_cyA) 55 | 56 | ## Docs 57 | 58 | 59 | More detailed documentation to follow soon! 60 | 61 | ## Team Info 62 | 63 | 64 | ### Team Size 65 | 66 | 2 67 | 68 | ### Team members 69 | 70 | * Kai Jun Eer - a blockchain research student at the University of Edinburgh 71 | * Maria Maliarets - an experienced front end developer 72 | 73 | ## How the community can engage 74 | * GitHub Discussion: [https://github.com/ipfs/community/discussions/720](https://github.com/ipfs/community/discussions/720) 75 | 76 | ## How to Contribute 77 | 78 | 79 | * Create a pull request at our Github repository! 80 | * Let us know your ideas and thoughts in the Github discussion thread! 81 | -------------------------------------------------------------------------------- /projects/BraineumVerse.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | 3 | BraineumVerse 4 | 5 | 6 | ## Category 7 | 8 | Application (Social Media) 9 | 10 | ## Project Description 11 | 12 | BraineumVerse is a mapping of the real world into the mind-space of BraineumAI, a pseudo AI, to simplify life and its interactions. Users provide the content which is mainly images at the moment. As the system develops additional social media platform group features like friends, groups, interests can be added. The creation of stores that may or may not exist in the real world is also important as that would drive ecommerce interactions which will be conducted in its own native currency. As interactions grow a pseudoAI can be developed to learn from key interactions and at some point take over and perform the mundane tasks. 13 | 14 | ## Use of IPFS, Filecoin and Libp2p 15 | 16 | The project currently uses Web3.Storage which uses both IPFS and Filecoin to store files that will be displayed to the user. A massive number of files could be saved and displayed in that manner as users will upload their images to these systems. 17 | 18 | ## Project Status 19 | 20 | Under Development 21 | 22 | ## Previews 23 | 24 | 25 | ![](https://github.com/rbensonevans/braineumVerse/blob/master/images/braineumverse_image.png) 26 | 27 | ## Target Audience 28 | 29 | The target users ideally will be a large part of the global citizenry or users interested in "living" in a "metaverse". 30 | 31 | ## Rough estimated user base (if applicable) 32 | 33 | No users at the moment. 34 | 35 | ## Github repo 36 | 37 | https://github.com/rbensonevans/braineumVerse 38 | 39 | 40 | ## Website 41 | 42 | https://braineumverse.com 43 | 44 | 45 | https://showcase.ethglobal.co/hackfs2021/braineumverse 46 | 47 | ## Docs 48 | 49 | https://showcase.ethglobal.co/hackfs2021/braineumverse 50 | https://github.com/rbensonevans/braineumVerse/blob/master/README.md 51 | 52 | 53 | ## Team Info 54 | 55 | 56 | R. Benson Evans. 57 | 58 | Software Engineer. 59 | 60 | ### Team Size 61 | 1 62 | 63 | ### Team members 64 | R. Benson Evans. 65 | 66 | ## How the community can engage 67 | * GitHub Discussion: https://github.com/ipfs/community/discussions/680 68 | * Email: rbensonevans.braineumverse@gmail.com 69 | * Slack: N/A 70 | * Twitter: https://twitter.com/braineumverse 71 | * Discord: N/A 72 | * Telegram: N/A 73 | * WeChat: N/A 74 | 75 | ## How to Contribute 76 | 77 | The community can contribute by testing the system and by suggesting new ideas or other methods to enhance the system. Additionally, I would like create a company around this project then hire, when funding is available, a team to help build this out. 78 | 79 | -------------------------------------------------------------------------------- /projects/CID-Management-Webapp.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | CID-Management-Web-App 3 | 4 | ## Category 5 | Web Application 6 | 7 | ## Project Description 8 | Art galleries need ways to certify the authenticity of physical pieces sold to customers. Using IPFS and ERC-721 tokens, GalaxyX has built a simple web-app that art collectors can use to login and view their certificates (CID's) that are issued by the gallery. We are using this simple web-app to be one of the buillding blocks for data verification tools built with IPFS and Filecoin. 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | We use IPFS on the back-end to store and serve the metadata for the ERC-721 tokens that are acting as the digital COAs. The ERC-721 metadata hosted on IPFS and Filecoin are linked within our react app for users to view themselves. We save the data on IPFS because we want our data decentralized and available. 12 | 13 | ## Project Status 14 | live build at www.galerielestudio.com and continued development 15 | 16 | ## Previews 17 | ![galerielestudio](https://user-images.githubusercontent.com/30084404/159200476-003161a1-7701-45fd-8d15-4bc9513f46d0.png) 18 | ![coa-galerielestudio](https://user-images.githubusercontent.com/30084404/159204299-ba62659c-3f69-42da-ae21-3af360837ab1.png) 19 | 20 | 21 | ## Target Audience 22 | 23 | Customers of art galleries, and sellers who want to authenticate the art they sell. This app is for art galleries & art collectors who want to ensure digital certificates of authenticity with immutable technology to fight fraud. 24 | 25 | ## Rough estimated user base (if applicable) 26 | 50 users 27 | 28 | ## Github repo 29 | - 30 | - 31 | 32 | 33 | 34 | ## Website 35 | https://www.galaxyx.io 36 | https://www.galerielestudio.com 37 | 38 | ## Docs 39 | https://github.com/galaxyxone/glsx_live2.2 40 | 41 | ## Team Info 42 | Passionate about the open internet, based in Austin TX. Logan Lentz is a full stack developer and leads our product development. Alex Mirran is a beginner front end developer with experience in business development. Giorgio Fasoli is a beginner web designer and assists with documentation. Excited about building data-privacy solutions with IPFS and its ecosystem! 43 | 44 | ### Team Size 45 | There are two of us full time, and we also have a part-time designer 46 | 47 | ### Team members 48 | - Logan Lentz - [lead developer](https://github.com/noryev) 49 | - Alex Mirran - [business development, project manager](https://github.com/galaxyxtwo) 50 | - Giorgio Fasoli - [designer](https://github.com/galaxyxthree) 51 | 52 | ## How the community can engage 53 | * GitHub Discussion: https://github.com/ipfs/community/discussions/748 54 | * Email: llentz@galaxyx.io 55 | * Twitter: ZaphodB17 56 | * Discord: noryev#0289 57 | * Telegram: @noryev 58 | 59 | ## How to Contribute 60 | Feel free to submit an issue in our repositories if you have any problems trying our apps out and of course, any bug smashing is welcomed too! 61 | -------------------------------------------------------------------------------- /projects/CommunityGarden.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | 3 | Community Garden 4 | 5 | ## Category 6 | 7 | Application, NFT 8 | 9 | ## Project Description 10 | 11 | Community Garden is a social dApp, an NFT platform, a plant exchanger, and a plant doctor app, all in one app. Where people come together and help each other to solve their plant problems. 12 | 13 | Creators and makers can sell NFTs, garden communities can set up a profile, and receive tips and donations from their community. Viewers can go to the platform to check works from the different creators and community gardens, see details from specific NFT, mint or donate NTFs, and unlock exclusive content. 14 | 15 | ## Use of IPFS, Filecoin and Libp2p 16 | 17 | At the moment we are using NFT.Storage to save NFTs and Textile/eth to store metadata for Garden communities such: names, locations, descriptions, images, wallet addresses, and more. We are also using NFTPort for minting and donating NFTs to Garden communities. This is a win-win situation for our Garden communities because they don't have to pay any transaction fees. 18 | 19 | ## Project Status 20 | 21 | In development started with Hackathon, looking for Business Relations 22 | 23 | ## Previews 24 | 25 | Live Demo: https://namer002.hns.siasky.net/ 26 | ![image](https://raw.githubusercontent.com/electrone901/plant-doctor/main/src/images/cover_.png) 27 | 28 | ## Target Audience 29 | 30 | - Nature lovers 31 | - Creator and Artist - focus group 32 | - Plant enthusiast 33 | - Garden Communities 34 | - Green activist 35 | - Broad Audience and adoption the general goal 36 | 37 | ## Rough estimated user base 38 | 39 | Very small community of local community garden in NYC, 40 | hackathon participants, friends, fam, and coworkers. 41 | 42 | ## Github repo 43 | 44 | https://github.com/electrone901/plant-doctor 45 | 46 | ## Website 47 | 48 | https://namer002.hns.siasky.net/ 49 | 50 | ## Docs 51 | 52 | N/A 53 | 54 | ## Team Info 55 | 56 | Albert Marcial - Software Engineer, Blockchain enthusiast, and nature lover. 57 | 58 | ### Team Size 59 | 60 | Currently, it's 1 team member, looking to expand. 61 | 62 | ### Team members 63 | 64 | Albert Marcial 65 | 66 | ## How the community can engage 67 | 68 | - GitHub Discussion: https://github.com/ipfs/community/discussions/670 69 | - Email: communitygardendapp@gmail.com 70 | - Twitter: https://twitter.com/garden_nfts 71 | - Github: https://github.com/electrone901/plant-doctor 72 | 73 | ## How to Contribute 74 | 75 | Contact me for any contributions, proposals, ideas, feedback, or supports on [twitter](https://twitter.com/garden_nfts). 76 | -------------------------------------------------------------------------------- /projects/Covision.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Covision 3 | 4 | ## Category 5 | Application 6 | 7 | ## Project Description 8 | Decentralised disease outbreak surveillance system using IPFS to efficiently manage disease reportings. 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | Most of the countries need to handle their own database due to lack of a decentralised platform. This leads to complications when global data is being compiled. Being a decentralised platform handled by behind the scene Smart Contracts and IPFS provides one global platform to report medical data. 12 | Authenticity and quality of medical data is another issue when we are being faced with pandemics. With the proper use of IPFS technology Covision has been made such that only verified individuals/organisations can write data. 13 | 14 | ## Project Status 15 | Under development 16 | 17 | ## Previews 18 | ![Screenshot 1](https://media.discordapp.net/attachments/873587956013752340/873588008325111868/img1.png) 19 | ![Screenshot 2](https://cdn.discordapp.com/attachments/873587956013752340/873588011340816444/img2.png) 20 | ![Screenshot 3](https://cdn.discordapp.com/attachments/873587956013752340/873588011948970044/img3.png) 21 | ![Screenshot 4](https://cdn.discordapp.com/attachments/873587956013752340/873588013463109702/img4.png) 22 | ![Screenshot 4](https://media.discordapp.net/attachments/873587956013752340/873587990205714462/img5.png) 23 | 24 | ## Target Audience 25 | Public, government . 26 | 27 | ## Github repo 28 | https://github.com/Mr-Cryptocoder/Covision 29 | 30 | ## Rough estimated user base (if applicable) 31 | 6 beta users 32 | 33 | ## Website 34 | The website is set to be hosted in the next 30 days 35 | 36 | 37 | ## Team Info 38 | ### Team Size 39 | 1 40 | 41 | ### Team members 42 | Sanil 43 | - Full stack web developer. 44 | - Proficient with JS, IPFS, libp2p, Blockchain. 45 | - https://github.com/Mr-Cryptocoder 46 | 47 | 48 | ## How the community can engage 49 | * GitHub Discussion: 50 | * Email: sanildev21@gmail.com 51 | 52 | ## How to Contribute 53 | We welcome contributors whole heartedly - reach us out at sanildev21@gmail.com. Please feel free to raise an issue in our repository if you have any difficulties. 54 | -------------------------------------------------------------------------------- /projects/Creativerse.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | The Creativerse 3 | 4 | ## Category 5 | Decentralized Minecraft Protocol 6 | 7 | ## Project Description 8 | A truly decentralized Minecraft protocol where you own plots of land as NFTs, and each NFT stores the block data of that plot. This allows anyone to run a Creativerse server, enabling it to be a truly decentralized server. 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | Stores Minecraft schematics and metadata on IPFS, and leverages NFT.Storage for persistent storage 12 | 13 | ## Project Status 14 | Launching on Feb. 18 with it's initial version 15 | 16 | ## Previews 17 | [Demo Shown at NFTHack2022](https://twitter.com/CreativerseMC/status/1482836845847199748?s=20&t=qYqyNxYqVooMYe3wiJ7nqg) 18 | 19 | ## Target Audience 20 | Web2 and NFT enthusiasts who also like playing Minecraft! 21 | 22 | ## Rough estimated user base (if applicable) 23 | 50 followers on Twitter 24 | 25 | ## Github repo 26 | https://github.com/CreativerseMC/CreativerseMC-Plugin 27 | 28 | ## Website 29 | https://CreativerseMC.com/ 30 | 31 | https://showcase.ethglobal.com/nfthack2022/creativerse-minecraft-on-ethereum 32 | 33 | ## Docs 34 | https://phazejeff-creativerse.gitbook.io/creativerse/ 35 | 36 | ## Team Info 37 | Just me right now! 38 | 39 | ### Team Size 40 | 1 41 | 42 | ### Team members 43 | Phaze Jeff 44 | 45 | ## How the community can engage 46 | * GitHub Discussion: https://github.com/ipfs/community/discussions/740 47 | * Twitter: https://twitter.com/CreativerseMC 48 | * Discord: https://discord.gg/FHAZcVfxDn 49 | 50 | ## How to Contribute 51 | Test out the project, and give some feedback! 52 | -------------------------------------------------------------------------------- /projects/CryptoSouls.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | 3 | CryptoSouls 4 | 5 | ## Category 6 | 7 | Application 8 | 9 | ## Project Description 10 | 11 | CryptoSouls is an NFT minting and battling game. In it, souls of famous warriors can be minted as NFT's, complete with a set of 5 stats: Strength, Intelligence, Endurance, Charisma, and Luck. 12 | 13 | Players can enlist their CryptoSouls in the Battle Arena, where they're matched up against other CryptoSouls. Battles consist of 3 rounds of random stat matchups, with the warrior having the higher stat the victor! 14 | 15 | ## Use of IPFS, Filecoin and Libp2p 16 | 17 | Assets and token data are uploaded to IPFS and used when minting the each CryptoSoul. It's the foundation for the NFT's used in the game and secondary economy. 18 | 19 | ## Project Status 20 | 21 | Under development 22 | 23 | ## Target Audience 24 | 25 | The target audience is gamers using Ethereum and people who get involved in crypto collectables. 26 | 27 | ## Github repo 28 | 29 | https://github.com/junoware/cryptosouls 30 | 31 | ## Website 32 | 33 | https://showcase.ethglobal.co/web3weekend/cryptosouls 34 | 35 | ## Team Info 36 | 37 | ### Team Size 38 | 39 | 1 40 | 41 | ### Team members 42 | 43 | Yambo -- Developer, Designer, Project Manager 44 | 45 | ## How the community can engage 46 | • GitHub Discussion: https://github.com/ipfs/community/discussions/621 47 | • Email: yambo.eth@gmail.com 48 | • Twitter: @yambo_eth 49 | 50 | ## How to Contribute 51 | 52 | Donations and development funds, especially in ETH and/or LINK, are happily accepted at `0xa1455E19c297B9A0A0E894208d041ad40cc5c23d` 53 | -------------------------------------------------------------------------------- /projects/DBS-Decentralized Broadcast & Stream.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | DBS-Decentralized Broadcast & Stream 3 | 4 | ## Category 5 | 6 | Infrastructure, Application 7 | 8 | ## Project Description 9 | 10 | Integrating Live Stream for Audius music Creators- Decentralized Broadcaster Streamer 11 | There are various music creators on Audius, this is a decentralized platform for audio creators. 12 | This project focuses on live streaming, concerts for those music creators. It is a platform which allows user to create his/her live stream for which people have to get a pass to watch. 13 | We have implemented Unlock protocol such that users would need to pay a certain amount to our streaming platform so that they can get access to new content or concerts hosted by their favourite independent creators. 14 | 15 | ## Use of IPFS, Filecoin and Libp2p 16 | 17 | The project uses Textile's Buckets to host the streaming site on the blockchain. We are going to implement NFT drops in the live stream where we would use IPFS to store the metadata. 18 | 19 | ## Project Status 20 | 21 | The Beta was built during the Web3Weekend hackathon from ETHGlobal and was selected as the finalist also won sponsor prize from Livepeer. 22 | 23 | ## Previews 24 | 25 | | Creator Dashboard | Viewer Dashboard | 26 | |------|-------| 27 | |[![alt text](https://raw.githubusercontent.com/Rishikeshk9/DBS-Decentralized-Broadcaster-Streamer/main/Creator%20Dashboard.png)](https://youtu.be/RGCnPxr1PNc "DBS-Decentralized Broadcast & Stream")|| 28 | 29 | ## Target Audience 30 | 31 | Content Creators, Music Creators, Live Streamers, Gamers 32 | 33 | ## Github repo 34 | 35 | https://github.com/Rishikeshk9/DBS-Decentralized-Broadcaster-Streamer 36 | 37 | ## Website 38 | 39 | https://bafzbeic2l4q6n7ecxhbqg64hqpweo7h4bhczjkqgmfyaj4zmblpnvobfqe.textile.space/ 40 | 41 | https://youtu.be/RGCnPxr1PNc 42 | 43 | 44 | https://showcase.ethglobal.co/web3weekend/dbs-decentralized-broadcast-stream 45 | 46 | ## Team Info 47 | 48 | 49 | ### Team Size 50 | 2 51 | ### Team members 52 | [Rushikesh Kardile](https://github.com/Rishikeshk9) - CEO, SuperSapiens 53 | 54 | [Vinay Sudrik](https://github.com/optimus789) - Developer 55 | ## How the community can engage 56 | * GitHub Discussion: https://github.com/ipfs/community/discussions/592 57 | * Email: hello@supersapiens.in 58 | * Twitter: https://twitter.com/RushiKardile 59 | * Discord: https://discord.gg/TtScUuZhh2 60 | * Telegram: @rishikeshk9 61 | 62 | 63 | ## How to Contribute 64 | 65 | You can directly ping us on the given links above, If you actively want to contribute -------------------------------------------------------------------------------- /projects/Dexplorer.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Dexplorer 3 | 4 | ## Category 5 | Application 6 | 7 | ## Project Description 8 | Dexplorer is a Distributed file explorer built with the power of IPFS. Quickly organize your files and store them on an immutable file system. 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | Dexplorer uses IPFS to store files. Infura is used for interacting with IPFS. Dexplorer completely depends upon IPFS. 12 | 13 | ## Project Status 14 | Under development 15 | 16 | ## Previews 17 | ![Empty Files](https://media.discordapp.net/attachments/843867515084079137/871490797198012446/DEX3.png?width=1075&height=535g) 18 | ![Uploading Files](https://media.discordapp.net/attachments/843867515084079137/871490799056080946/DEX2.png?width=1055&height=535) 19 | ![Organized Files](https://media.discordapp.net/attachments/843867515084079137/871490800905752607/DEX.png?width=1076&height=535) 20 | 21 | 22 | ## Target Audience 23 | Anyone who wishes to use a distributed file system which is immutable and censorship resistant. 24 | 25 | ## Rough estimated user base (if applicable) 26 | The project was built for the purpose of organizing and sharing files within my friends. 27 | 28 | ## Github repo 29 | https://github.com/codeyager/Dexplorer 30 | 31 | ## Website 32 | Adding in a month. 33 | 34 | ## Docs 35 | https://github.com/codeyager/Dexplorer/blob/main/README.md 36 | 37 | ## Team Info 38 | 39 | ### Team Size 40 | 2 41 | 42 | ### Team members 43 | 44 | Thambidurai K 45 | - https://github.com/codeyager 46 | 47 | Akbar Nawas 48 | - https://github.com/codeyager 49 | 50 | ## How the community can engage 51 | * GitHub Discussion: https://github.com/ipfs/community/discussions/633 52 | * Email: akbarnawas7@gmail.com 53 | * Slack: 54 | * Twitter: 55 | * Discord: 56 | * Telegram: 57 | * WeChat: 58 | 59 | ## How to Contribute 60 | Check out the instructions mentioned on our repository. Please reach out via email for clarifications. 61 | -------------------------------------------------------------------------------- /projects/Dspyt-NFTs.md: -------------------------------------------------------------------------------- 1 | # Project Name 2 | 3 | Dspyt-NFTs (ipfs-gallery) 4 | 5 | ## Category 6 | 7 | Application 8 | 9 | ## Project Description 10 | 11 | An interactive web application built with ReactJS to upload and view images. The application interacts with Filecoin and IPFS. In particular, nft.storage provides an access via api for the application to store files. 12 | 13 | Further we consider to add minting NFTs in the application and generating metadata based on Artificial Intelligence. 14 | 15 | ## Project Status 16 | 17 | Under development in [Encode Filecoin Accelerator](https://medium.com/encode-club/announcing-the-encode-filecoin-accelerator-c55f09264e8c) 18 | 19 | ### Plans 20 | 21 | * Extend IPFS storage to web3.storage 22 | * Mint uploaded images on Polygon 23 | * Add Machine Learning Algorithm that will create metadata 24 | 25 | ## Previews 26 | 27 | [NFT hack 2022 || ETHGlobal](https://showcase.ethglobal.com/nfthack2022/dspyt-nfts) 28 | 29 | [Live Demo](https://ipfs-personal-gallery.vercel.app/) 30 | 31 | ## Target Audience 32 | 33 | NFT projects, new and proficient web3 users. 34 | 35 | We want to extend the reach of the existing userbase for Filecoin and improve the experience with existing projects. 36 | 37 | ## Github repo 38 | 39 | [Dspyt-NFTs](https://github.com/dspytdao/Dspyt-NFTs) 40 | 41 | ## Website 42 | 43 | [Live Demo](https://ipfs-personal-gallery.vercel.app/) 44 | 45 | 46 | ## Docs 47 | 48 | [Docs](https://github.com/dspytdao/Dspyt-NFTs/blob/main/dspyt/README.md) 49 | 50 | ## Team Info 51 | 52 | ### Team Size 53 | 54 | 3 55 | 56 | ### Team members 57 | 58 | [DspytDAO](https://twitter.com/DspytDAO) 59 | 60 | [Pavel Fedotov](https://github.com/Pfed-prog) 61 | 62 | [Grigore Gabriel Trifan](https://github.com/TheSlayer-666) 63 | 64 | ## How the community can engage 65 | 66 | [GitHub Filecoin Discussion](https://github.com/filecoin-project/community/discussions/466) 67 | 68 | [GitHub IPFS Discussion](https://github.com/ipfs/community/discussions/738) 69 | 70 | [Twitter](https://twitter.com/DspytDAO) 71 | 72 | [Discord](https://discord.gg/peRHyNZrss) 73 | 74 | ## How to Contribute 75 | 76 | Contact us on Social Media and/or open an Issue on [Dspyt-NFTs](https://github.com/dspytdao/Dspyt-NFTs) 77 | 78 | For feedback session and enquiries we have a [calendly](https://calendly.com/pavel-fedotov) 79 | 80 | We really appreciate your feedback 81 | 82 | -------------------------------------------------------------------------------- /projects/Esteroids.md: -------------------------------------------------------------------------------- 1 | # IPFS community project 2 | 3 | ## Project Name 4 | Esteroids 5 | 6 | ## Category 7 | Decentralized websites 8 | 9 | ## Project Description 10 | [Esteroids](https://esteroids.xyz/esteroids_demo.mp4) is a tool for the Web3 community to discover ENS+IPFS. Made by the community - for the community. 11 | 12 | We want Esteroids to be a combination of an early day Yahoo directory with a search engine, made in a modern way to fit the decentralized web. 13 | 14 | Esteroids has two functionalities. One is an explorer for users to discover new and popular ENS+IPFS, while the other is an option to search in our ENS+IPFS website's database. 15 | 16 | We update esteroids.eth hourly with new ENS+IPFS websites. 17 | 18 | Besides the esteroids.eth website we also have a [Twitter account](https://twitter.com/e_steroids), announcing all new ENS+IPFS websites as people create them. 19 | 20 | ## Use of IPFS, Filecoin and Libp2p 21 | Esteroids is an IPFS+ENS websites showcasing other IPFS+ENS websites. 22 | 23 | ## Project Status 24 | Alpha, you can see our progress in [http://esteroids.eth](http://esteroids.eth) (with Brave) or [http://esteroids.eth.link](http://esteroids.eth.link) (in other browsers). 25 | 26 | ## Previews 27 | ![esteroids_demo](https://user-images.githubusercontent.com/20537195/124447188-6af6a200-dd81-11eb-9417-2e0820e6e113.gif) 28 | 29 | 30 | 31 | ## Target Audience 32 | dWeb enthusiastics, Ethereum, DeFi, NFTs and dApp users. 33 | 34 | ## Rough estimated user base (if applicable) 35 | 36 | 37 | ## Github repo 38 | We will open [http://esteroids.eth.link](http://esteroids.eth.link) React app in the next version (Beta) and add a link here. 39 | 40 | ## Website 41 | [http://esteroids.eth](http://esteroids.eth) (with Brave) or [http://esteroids.eth.link](http://esteroids.eth.link) (in other browsers). 42 | 43 | 44 | ## Docs 45 | 46 | 47 | ## Team Info 48 | 49 | ### Team Size 50 | Two people. 51 | 52 | ### Team members 53 | - Eyal Ron 54 | - eyal@esteroids.xyz 55 | - https://github.com/eyalron33/ 56 | - Algorithms, communications, business development. 57 | 58 | - Tomer Leicht 59 | - tomer@esteroids.xyz 60 | - https://github.com/tomlightning/ 61 | - Main developer, business development. 62 | 63 | ## How the community can engage 64 | * Github discussion: https://github.com/ipfs/community/discussions/607 65 | * Email: contact@esteroids.xyz 66 | * Twitter: https://twitter.com/e_steroids 67 | 68 | ## How to Contribute 69 | 70 | -------------------------------------------------------------------------------- /projects/Evido.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Evido 3 | 4 | ## Category 5 | Application 6 | 7 | ## Project Description 8 | Decentralizing journalism and evidence collection with the power of Inter Planetry File System 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | One of the biggest risks faced by journalists is that their content can be manipulated and controlled by those in high power. Even if they try to publish pieces of evidence through various centralized sources, they are tracked down and suppressed. The truth never sees the light. 12 | 13 | We provide a decentralized platform for journalism providing anonymity to journalists who wish to relinquish the true evidences and facts through our 'Evido'. 14 | 15 | ## Project Status 16 | Under development 17 | 18 | ## Previews 19 | ![Screenshot 1](https://media.discordapp.net/attachments/853989819206074382/854407595023663174/Screenshot_11.png?width=1046&height=589) 20 | ![Screenshot 2](https://media.discordapp.net/attachments/853989819206074382/854407605941960754/Screenshot_12.png?width=1046&height=589) 21 | ![Screenshot 3](https://media.discordapp.net/attachments/853989819206074382/854407607757701152/Screenshot_13.png?width=1046&height=589) 22 | ![Screenshot 4](https://media.discordapp.net/attachments/853989819206074382/854407612275884062/Screenshot_14.png?width=1046&height=589) 23 | 24 | ## Target Audience 25 | Journalists, news agencies and civil bodies. 26 | 27 | ## Github repo 28 | https://github.com/Adithya-adi-Menon/ipfs-evido 29 | 30 | ## Rough estimated user base (if applicable) 31 | 5 beta users 32 | 33 | ## Website 34 | The website is set to be hosted in the next 30 days 35 | 36 | ## Docs 37 | 38 | 39 | ## Team Info 40 | ### Team Size 41 | 5 42 | 43 | ### Team members 44 | Adithya Menon S 45 | - Full stack web developer. 46 | - Proficient with JS, PHP and Java. 47 | - https://github.com/Adithya-adi-Menon/ 48 | 49 | Vasanth T 50 | - Front end developer. 51 | - Good with problem solving and competitive programming. 52 | - https://github.com/vasanthsteve23 53 | 54 | ## How the community can engage 55 | * GitHub Discussion: https://github.com/ipfs/community/discussions/599 56 | * Email: adithyamenons17@gmail.com 57 | * Slack: 58 | * Twitter: 59 | * Discord: 60 | * Telegram: 61 | * WeChat: 62 | 63 | ## How to Contribute 64 | We welcome contributors whole heartedly - reach us out at adithyamenons17@gmail.com. Please feel free to raise an issue in our repository if you have any difficulties. 65 | -------------------------------------------------------------------------------- /projects/Flutter_IPFS_Plugin.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | IPFS Plugin for Flutter 3 | 4 | ## Category 5 | Plugin/Library 6 | 7 | ## Project Description 8 | A plugin library for the IPFS using HTTP API and Infura. The code is implemented in Dart and the plugin can be imported and used in android application projects. Support for iOS and Windows will be added soon. 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | Flutter is one of the rapidly growing cross-platform development frameworks. This plugin uses IPFS HTTP API along with Infura to easily store and retrieve strings, files and JSON objects on the IPFS. 12 | 13 | ## Project Status 14 | Under development 15 | 16 | ## Previews 17 | ![How to use](https://raw.githubusercontent.com/hackyguru/HostedImages/master/ipfs-flutter.PNG) 18 | 19 | 20 | ## Target Audience 21 | Flutter developers who wish to use IPFS in their project 22 | 23 | ## Rough estimated user base (if applicable) 24 | 3 beta testers. 25 | 26 | ## Github repo 27 | https://github.com/hackyguru/IPFS-Flutter 28 | 29 | ## Website 30 | A pub.dev package will be published soon. 31 | 32 | ## Docs 33 | https://github.com/hackyguru/IPFS-Flutter/blob/master/README.md 34 | 35 | ## Team Info 36 | 37 | ### Team Size 38 | 2 39 | 40 | ### Team members 41 | Kumaraguru T 42 | - Full stack web developer and blockchain enthusiast. 43 | - https://github.com/hackyguru/ 44 | 45 | Mridula Kalaiselvan 46 | - Front end developer 47 | - https://github.com/Mridula90/ 48 | 49 | 50 | ## How the community can engage 51 | * GitHub Discussion: https://github.com/ipfs/community/discussions/595 52 | * Email: kumaragurut7@gmail.com 53 | 54 | ## How to Contribute 55 | We welcome contributions. Please reach us out through email - kumaragurut7@gmail.com if you're interested. Feel free to open an issue at your repository in case you find any. 56 | -------------------------------------------------------------------------------- /projects/Fractio.xyz: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Fractio.xyz 3 | 4 | ## Category 5 | NFT 6 | 7 | ## Project Description 8 | Dynamic Multilayer NFT Editor and Framework 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | We are at the moment building our own IPFS Node on the AWS cloud and want to start 12 | a fractio pinning service for project related uploads. We need a special directory structure that 13 | allows each user to have his own directory and subdirectories for every PYE-NFT Token he creates. 14 | 15 | ## Project Status 16 | In development started with Hackathon, Looking for Business Relations 17 | 18 | ## Previews 19 | Youtube Live Demo :https://youtu.be/EmZr0L0uris 20 | ![image](https://user-images.githubusercontent.com/34139485/115134813-c3849180-a013-11eb-8a08-fded456576ad.png) 21 | 22 | ## Target Audience 23 | Entertainment Industry 1st focus Group 24 | Young Art, Sport, Music Fans are the 2nd. focus group 25 | Broad Audience and adoption the general goal 26 | 27 | ## Rough estimated user base 28 | very small community of hardcore developers, 29 | hackathon participants, friends, fam and 30 | 31 | ## Github repo 32 | https://github.com/FractioXYZ // organization account 33 | https://github.com/FractioXYZ/pye_editor // demo repo 34 | https://github.com/FractioXYZ/fraxio_framework // project repo 35 | 36 | ## Website 37 | https://fraxio.herokuapp.com 38 | 39 | ## Docs 40 | https://github.com/FractioXYZ/fraxio_docs 41 | 42 | ## Team Info 43 | We are a team of 5 that met at the Hackathon and came up with a very sweet idea that 44 | is going to revolutionize the entire blockchain space 45 | 46 | ### Team Size 47 | Now we have 5 team members. 48 | 49 | ### Team members 50 | Irvin C. - Business & Marketing Strategist 51 | Louell S. - Technical Community Manager 52 | Daniel P. - Social Media Engineer 53 | Nathan M. - Operational Security Manager 54 | Aron A. - Chief Digital Architect 55 | 56 | ## How the community can engage 57 | GitHub Discussion: https://github.com/ipfs/community/discussions/503 58 | Email: irvin@fractio.xyz 59 | Slack: N/A 60 | Twitter: https://twitter.com/IoFrax 61 | Discord: https://discord.gg/VrPNVmAE 62 | Telegram: N/A 63 | Medium : N/A 64 | WeChat: N/A 65 | Github : https://github.com/FractioXYZ 66 | 67 | ## How to Contribute 68 | 69 | We are looking for long Term Business Relations 70 | -------------------------------------------------------------------------------- /projects/Heavenly Jungle NFT: -------------------------------------------------------------------------------- 1 | ## Heavenly Jungle NFT 2 | 3 | ## Category 4 | Application 5 | 6 | ## Project Description 7 | DAO NFT Platform allowing fractional ownership. Includes minting, auctions, royalties, licensing and the option to rage quit. 8 | 9 | ## Use of IPFS, Filecoin and Libp2p 10 | Currently using Pinata's IPFS pinning service. Looking for guidance on this matter. 11 | 12 | ## Project Status 13 | Early Development 14 | 15 | ## Previews 16 | 17 | 18 | ## Target Audience 19 | Art Communities, Individual Artists 20 | 21 | ## Rough estimated user base (if applicable) 22 | 23 | 24 | ## Github repo 25 | 26 | https://github.com/Mol-LeArt/Heavenly-Jungle 27 | 28 | ## Website 29 | 30 | http://dannointerweb.com/heavenly-jungle/ 31 | 32 | ## Docs 33 | 34 | ![NFT View](https://ipfs.io/ipfs/QmTvZq1BDZ5MnyC9DnFPvr3uMp8cLRF7iR8gpMmgfU6kND) 35 | ![About Commons](https://ipfs.io/ipfs/QmYTHHUubnLZUuUs5NVWMbCrvQ6DN5Z5pihkXyRsJJmaKa) 36 | ![Administate the Commons](https://ipfs.io/ipfs/QmTGWaTVzzKmzxMrkp4XNt6xv8XYdaa6Engup12qprKik5) 37 | ![Commons Gallery](https://ipfs.io/ipfs/QmRHbJKQLGNtQVaW9F2uj9Dsnk2g78sEACK5BGRn5J1AyW) 38 | 39 | 40 | ## Team Info 41 | 42 | Daniel - front end dev 43 | krishna - community 44 | audsssy - smart contract 45 | ### Team Size 46 | 3 possibly growing 47 | ### Team members 48 | 49 | Daniel - https://github.com/JFF-Danno 50 | Stamford - https://github.com/audsssy 51 | 52 | ## How the community can engage 53 | * GitHub Discussion: https://github.com/ipfs/community/discussions/515 54 | * Email: 55 | * Slack: 56 | * Twitter: https://twitter.com/MolLeArt 57 | * Discord: https://discord.gg/QmSVrw6Y 58 | * Telegram: 59 | * WeChat: 60 | 61 | ## How to Contribute 62 | 63 | -------------------------------------------------------------------------------- /projects/HouseSec.md: -------------------------------------------------------------------------------- 1 | ![ alt text for screen readers](https://media.discordapp.net/attachments/873587956013752340/877065863826640906/huge.png?width=424&height=424) 2 | ## Project Name 3 | HouseSec 4 | 5 | ## Category 6 | Application 7 | 8 | ## Project Description 9 | HouseSec is more like a Smart Home where Document Validity, Bill Payments and Resources Optimization are done in one platform. 10 | 11 | ## Use of IPFS, Filecoin and Libp2p 12 | HouseSec uses IPFS to store the important House Documents and Validation of the documents. IPFS plays the major role in this area.It uses Algorithm to verify the House Documents and House Bills which makes them immutable and gives transperancy. 13 | 14 | ## Project Status 15 | Under development 16 | 17 | ## Previews 18 | ![Screenshot 1](https://media.discordapp.net/attachments/873587956013752340/873615194872479814/h2.jpeg?width=877&height=403) 19 | ![Screenshot 2](https://media.discordapp.net/attachments/873587956013752340/873615212442423316/h1.jpeg?width=892&height=403) 20 | ![Screenshot 3](https://media.discordapp.net/attachments/873587956013752340/873614427793006673/pic3.png?width=705&height=403) 21 | ![Screenshot 4](https://media.discordapp.net/attachments/873587956013752340/873614413607882803/pic0.png?width=706&height=403) 22 | ## Target Audience 23 | Anyone who wants to store House Related Documents which validates in the background 24 | 25 | ## Rough estimated user base (if applicable) 26 | Yet to be deployed. 27 | 28 | ## Github repo 29 | https://github.com/Freakytedy18/HouseSec 30 | 31 | ## Website 32 | Yet to be Deployed 33 | 34 | ## Docs 35 | https://github.com/Freakytedy18/HouseSec/tree/master#readme 36 | ## Demo 37 | 38 | ## Team Info 39 | 40 | ### Team Size 41 | 1 42 | 43 | ### Team members 44 | Keerthana K 45 | - Blockchain Enthusiast and FullStack Developer 46 | - https://github.com/Freakytedy18 47 | 48 | 49 | 50 | ## How the community can engage 51 | * GitHub Discussion: 52 | * Email: vklakshmi73@gmail.com 53 | * Slack: 54 | * Twitter: 55 | * Discord: 56 | * Telegram: 57 | * WeChat: 58 | 59 | ## How to Contribute 60 | We welcome contributions in documentation/ development of HouseSec. Please reach us out through email -vklakshmi73@gmail.com4 if you're interested. Feel free to open an issue at your repository in case you find any. 61 | -------------------------------------------------------------------------------- /projects/HubShare.md: -------------------------------------------------------------------------------- 1 | ![ alt text for screen readers](https://media.discordapp.net/attachments/853989819206074382/861668838462717952/HubShare.png?width=500&height=120) 2 | ## Project Name 3 | Hub Share 4 | 5 | ## Category 6 | Application 7 | 8 | ## Project Description 9 | Hub Share is a secure and decentralized file sharing web application built with JS-IPFS. 10 | 11 | ## Use of IPFS, Filecoin and Libp2p 12 | Hub Share stores the files in IPFS and encrypts the link to the file with an cryptographic algorithm. This makes the file storage secured, private and immutable. IPFS plays a major role here as our novelty totally relies on it. 13 | 14 | ## Project Status 15 | Under development 16 | 17 | ## Previews 18 | ![Screenshot 1](https://media.discordapp.net/attachments/853989819206074382/863102516996472872/image0.png?width=873&height=403) 19 | ![Screenshot 2](https://media.discordapp.net/attachments/853989819206074382/863102476243566642/image0.png?width=873&height=403) 20 | ![Screenshot 3](https://media.discordapp.net/attachments/853989819206074382/863102518757949470/image0.png?width=873&height=403) 21 | ![Screenshot 4](https://media.discordapp.net/attachments/853989819206074382/863102322121244682/image0.png?width=873&height=403) 22 | ## Target Audience 23 | Anyone who wants to share confidential and important files which require better privacy 24 | 25 | ## Rough estimated user base (if applicable) 26 | Yet to be deployed. 27 | 28 | ## Github repo 29 | https://github.com/bkyogesh28/HubShare 30 | 31 | ## Website 32 | Yet to be Deployed 33 | 34 | ## Docs 35 | https://github.com/bkyogesh28/HubShare#readme 36 | 37 | ## Demo 38 | https://youtu.be/XDOaD5jdPV4 39 | 40 | ## Team Info 41 | 42 | ### Team Size 43 | 2 44 | 45 | ### Team members 46 | Yogeshwar B K 47 | - Full stack web developer and CyberSecurity Enthusiast. 48 | - https://github.com/bkyogesh28/ 49 | 50 | Jawahar P M 51 | - Front end developer and BlockChain Enthusiast 52 | - https://github.com/Jawaharpmm 53 | 54 | 55 | ## How the community can engage 56 | * GitHub Discussion: https://github.com/ipfs/community/discussions/618 57 | * Email: bkyogesh28@gmail.com 58 | * Slack: 59 | * Twitter: 60 | * Discord: 61 | * Telegram: 62 | * WeChat: 63 | 64 | ## How to Contribute 65 | We welcome contributions in documentation/ development of HubShare. Please reach us out through email -bkyogesh28@gmail.com if you're interested. Feel free to open an issue at your repository in case you find any. 66 | -------------------------------------------------------------------------------- /projects/IPFS-Drop.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | IPFS-Drop 3 | 4 | ## Category 5 | Application 6 | 7 | ## Project Description 8 | Decentralizing the power of File Manager using Inter Planetry File System 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | It makes sharing files very simple as you can just share the hash and others can access the file using the hash instead of you spending your internet and Users can still access the files through the file hash or the unique link generated. 12 | 13 | We provide a decentralized platform for file storage. 14 | 15 | ## Project Status 16 | Under development 17 | 18 | ## Previews 19 | ![Screenshot 1](https://media.discordapp.net/attachments/853989819206074382/867805704692695090/Web_capture_22-7-2021_215857_localhost.jpeg?width=1285&height=663) 20 | ![Screenshot 2](https://cdn.discordapp.com/attachments/853989819206074382/867805706492968980/Web_capture_22-7-2021_215938_localhost.jpeg) 21 | 22 | 23 | ## Target Audience 24 | Public , Content Delivery . 25 | 26 | ## Github repo 27 | https://github.com/vasanthsteve23/IPFS_DROP.git 28 | 29 | ## Rough estimated user base (if applicable) 30 | 3 beta users 31 | 32 | ## Website 33 | The website is set to be hosted in the next 30 days 34 | 35 | ## Team Info 36 | ### Team Size 37 | 1 38 | 39 | ### Team members 40 | Vasanth T 41 | - Full Stack Developer. 42 | - Good with problem solving and competitive programming. 43 | - https://github.com/vasanthsteve23 44 | 45 | ## How the community can engage 46 | * GitHub Discussion: https://github.com/ipfs/community/discussions/628 47 | * Email: 18eucs125@skcet.ac.in 48 | * Slack: 49 | * Twitter: 50 | * Discord: 51 | * Telegram: 52 | * WeChat: 53 | 54 | ## How to Contribute 55 | We welcome contributors whole heartedly - reach us out at 18eucs125@skcet.ac.in. Please feel free to raise an issue in our repository if you have any difficulties. 56 | -------------------------------------------------------------------------------- /projects/IPFSScan.md: -------------------------------------------------------------------------------- 1 | ## Project Name IPFS Scan 2 | 3 | ## Category 4 | 5 | Application 6 | 7 | ## Project Description 8 | 9 | IPFS Scan shows the file's(CID) storage status on IPFS Network, including gelocation information and incentive layers'(Crust/Filecoin/Arweave) on-chain storage state. 10 | 11 | ## Use of IPFS, Filecoin and Libp2p 12 | 13 | 1. IPFS Gateway: IPFS Scan uses public web3authed gateways to query informations of IPFS DHT information 14 | 2. IPFS remote pinning service: IPFS Scan accepts IPFS remote pinning service API standards, query storage infos from pinning service-side 15 | 16 | ## Project Status 17 | 18 | Beta 19 | 20 | ## Previews 21 | 22 | 23 | ![](https://crustipfs.xyz/ipfs/QmNUbu4LhKSuYxkt7eD2ZYE6ChBgrMm6uqxPoUfxyoJhGT?filename=ipfs_scan_ss3.png) 24 | 25 | ![](https://crustipfs.xyz/ipfs/QmTwvpsj37vSYPK8Rdk9xf8YLufLZV5BtjxhtvfL677MPP?filename=IPFSSCAN.png) 26 | 27 | ![](https://crustipfs.xyz/ipfs/QmRrhcibZceLPi9DXRzrkP7Fzg6H7okq5fvFiiwt4iT4tB?filename=ipfs_scan_ss2.png) 28 | 29 | ## Target Audience 30 | 31 | All the NFT projects, especially marketplace/listing services. They can show the storage distributed information. Now it already be integrated by: 32 | 33 | 1. RMRK: https://rmrk.app 34 | 2. NFTScan: https://nftscan.com 35 | 36 | ## Rough estimated user base (if applicable) 37 | 38 | No data yet 39 | 40 | ## Github repo 41 | 42 | https://github.com/crustio/ipfsscan 43 | 44 | ## Website 45 | 46 | 47 | 48 | https://ipfsscan.crustapps.net 49 | 50 | ## Docs 51 | 52 | https://github.com/crustio/ipfsscan/tree/main/docs 53 | 54 | ## Team Info 55 | 56 | Decoo(Crust Application Team) dedicate in building Crust and IPFS-based applications, currently we build [Crust Files](https://files.crustapps.net), [Crust Pins](https://crustapps.net/#/pins) and [IPFS Scan](https://ipfsscan.crustapps.net) 57 | 58 | ### Team Size 59 | 60 | 0-10 61 | 62 | ### Team members 63 | 64 | - Luke(https://github.com/badkk) 65 | - Gavin(https://github.com/gavfu) 66 | - Eric(https://github.com/XueMoMo) 67 | 68 | ## How the community can engage 69 | * GitHub Discussion: 70 | * Email: kun@crust.network 71 | * Slack: / 72 | * Twitter: @CrustNetwork 73 | * Discord: badkk#7013 74 | * Telegram: / 75 | * WeChat: / 76 | 77 | ## How to Contribute 78 | 79 | Pull Request 80 | -------------------------------------------------------------------------------- /projects/IPFSfB.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | InterPlanetary File System for Business (IPFSfB) 3 | 4 | ## Category 5 | 6 | Developer tooling 7 | 8 | ## Project Description 9 | 10 | InterPlanetary File System for Business (IPFSfB) is an enterprise blockchain storage network based on InterPlanetary File System. IPFSfB is intended to help developers to build their private network on IPFS, leveraging the capability that enabling private storage for any blockchains. 11 | 12 | ## Use of IPFS, Filecoin and Libp2p 13 | 14 | InterPlanetary File System for Business (IPFSfB) is based on go-ipfs, which is a networking tooling and infrastructure consisted of IPFS and Libp2p. To enabling a private network on IPFS, an IPFS infrastructure and a networking-based tool like go-ipfs or js-ipfs are required. 15 | 16 | ## Project Status 17 | 18 | shipped 19 | 20 | ## Previews 21 | 22 | Contributors Flow 23 | ![Contributors Flow](https://raw.githubusercontent.com/feliciss/IPFSfB/master/docs/flow/flow-v1-contributor.png) 24 | Users Flow 25 | ![Users Flow](https://raw.githubusercontent.com/feliciss/IPFSfB/master/docs/flow/flow-v3-user.png) 26 | 27 | ## Target Audience 28 | 29 | IPFS/Libp2p developer, system developer and engineer 30 | 31 | ## Rough estimated user base (if applicable) 32 | 33 | 100+ 34 | 35 | ## Github repo 36 | 37 | 38 | 39 | ## Website 40 | 41 | 42 | 43 | 44 | 45 | 46 | ## Docs 47 | 48 | 49 | 50 | ## Team Info 51 | 52 | ### Team Size 53 | 54 | 1 55 | 56 | ### Team members 57 | 58 | Feliciss - an independent developer and full stack engineer 59 | 60 | ## How the community can engage 61 | 62 | * GitHub Discussion: 63 | * Email: fiveswind@gmail.com 64 | * Slack: N/A 65 | * Twitter: N/A 66 | * Discord: N/A 67 | * Telegram: N/A 68 | * WeChat: N/A 69 | 70 | ## How to Contribute 71 | 72 | 73 | Before contributing, read contributors guide at . 74 | Then, describe your request and make a pull request in . -------------------------------------------------------------------------------- /projects/IPLDDistributedDatasets: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | IPLD Distributed Datasets 3 | 4 | ## Category 5 | Developer Tooling 6 | 7 | ## Project Description 8 | IPLD can be used to store datasets in IPFS rather than as flat files. Additionally, IPLD's advanced data layouts can be used to do lookups by key while fetching only a small number of blocks. 9 | 10 | The goal of this project is to provide tooling and libraries to allow developers to store large datasets using IPLD and utilize them in applications. 11 | 12 | ## Use of IPFS, Filecoin and Libp2p 13 | This project uses IPFS and IPLD to store and distribute the datasets. 14 | 15 | ## Project Status 16 | The project is currently in the development phase, but has already been shown to work using a dataset with 100k entries. 17 | 18 | ## Target Audience 19 | Developers and projects wanting to store static datasets on IPFS that require decentralized, fast lookups. 20 | 21 | ## Github repo 22 | https://github.com/aditsachde/ipld-distributed-datasets 23 | 24 | ## Docs 25 | https://github.com/aditsachde/ipld-distributed-datasets/blob/master/README.md 26 | 27 | ## Team Info 28 | 29 | ### Team Size 30 | 1 31 | 32 | ### Team members 33 | Adit Sachde 34 | 35 | ## How the community can engage 36 | * GitHub Discussion: https://github.com/ipfs/community/discussions/604 37 | * Email: contact [at] aditsachde.com 38 | 39 | ## How to Contribute 40 | Help pin the datasets or contribute new datasets! 41 | -------------------------------------------------------------------------------- /projects/IPNSGoServer.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | IPNSGoServer 3 | 4 | ## Category 5 | 6 | Developer tooling, API 7 | 8 | ## Project Description 9 | 10 | Create IPNS records for users without the need to run their own IPFS node to allow them to easily update their data. The goal is to provide hundreds of users their own private public key, a key use case would be NFT buyers and giving only them the ability to update their NFTs metadata. 11 | 12 | ## Use of IPFS, Filecoin and Libp2p 13 | 14 | This project uses the IPNS library which is used in conjunction with IPFS for "updating" the decentralized data. It uses Libp2p/crypto library to generate private/public keys. 15 | 16 | ## Project Status 17 | 18 | brainstorming/under development 19 | 20 | ## Target Audience 21 | 22 | My project's users will be developers or companies that want an easy to use tool to create & update IPNS records in their dapp. 23 | 24 | ## Rough estimated user base (if applicable) 25 | 26 | I currently have no users. 27 | 28 | ## Github repo 29 | 30 | https://github.com/mrodriguez3313/IPNSGoServer 31 | 32 | 33 | https://showcase.ethglobal.com/web3jam/customizeable-nfts 34 | 35 | ## Team Info 36 | 37 | My name is Marco Rodriguez-Salinas a solo developer (for now) looking to exapand my developer skills in web3. I am passionate about the future of decentralized storage and want to create easy to use tools to onboard new developers. 38 | 39 | ### Team Size 40 | 1 person 41 | 42 | ## How the community can engage 43 | * GitHub Discussion: https://github.com/ipfs/community/discussions/701 44 | * Email: marco.rodriguez113@gmail.com 45 | * Twitter: @fancyB_nft 46 | * Discord: https://discord.gg/B8NRJhBb | legendofmar#3868 47 | 48 | ## How to Contribute 49 | 50 | You can find me in Discord often, if you would like to chat and discuss how to use this software. I to hear how you can use this tool and what features should be added to improve the API. -------------------------------------------------------------------------------- /projects/Juni::Db.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | ”Juni::Db" 3 | 4 | ## Category 5 | Database 6 | 7 | ## Project Description 8 | It's a very highload action to store large amounts of data on-chain. The most-common and useful solution for decentralised apps is to use IPFS as a data storage and store on-chain only hashes. Our team, inspired by the OrbitDB, focuses on the scalability, decentralised, easy-learning solution. We work on the development of the configurable database module that allows users to store and manipulate a big amount of data. 9 | ### Key advantages 10 | Usability - just integrate and code 11 | Security - built-in encryption 12 | Scaling - ready for changes and big data 13 | ### Available storage data types 14 | Key-value - simple key-value storage 15 | Hash - hash storage like Redis hash 16 | ## Use of IPFS, Filecoin and Libp2p 17 | IPFS - data storage and database driver 18 | 19 | ## Project Status 20 | 21 | Completed product architecture and design, fundraising 22 | 23 | ## Target Audience 24 | Target audience - Substrate and IPFS developers 25 | 26 | ## Rough estimated user base (if applicable) 27 | 28 | Early product stage: under development 29 | 30 | ## Github repo 31 | 32 | https://github.com/uddugteam/juniDB 33 | 34 | ## Website 35 | 36 | https://uddug.com 37 | 38 | 39 | 40 | ## Docs 41 | 42 | https://docs.google.com/document/d/1t0--n2MrcVwU1rj6rpRW4uBUlx_5uS_uM7_EGYid8To/edit?usp=sharing 43 | 44 | ## Team Info 45 | 46 | 47 | Core of our team is of united, like-minded professionals with solid experience. We are constantly evolving our capabilities to help software technology companies to do more with less: develop software solutions faster and ensure high quality within time constraints, with fewer resources, and lower costs. We combine proven methodologies, business domain knowledge and technology expertise of skilled software professionals to deliver highly optimized solutions and services across a wide range of industry domains. 48 | Team range of experience begins from developing small scaled websites up to complex blockchain architectures. Our projects are diverse, but all of them share the need to have a software solution for humans. 49 | ### Team Size 50 | 4 51 | 52 | ### Team members 53 | 54 | Tech lead, backend: Andrew Skurlatov 55 | 56 | https://github.com/andskur 57 | 58 | https://www.linkedin.com/in/andrew-skurlatov/ 59 | 60 | Junior back-end developer: Sergey Grachev 61 | 62 | https://github.com/Misnaged 63 | 64 | https://www.linkedin.com/in/painof-donbass-b07187206/ 65 | 66 | Head of product: Mike Manko 67 | 68 | https://github.com/MikeMS-sys 69 | 70 | https://www.linkedin.com/in/mikhail-manko-97a491a2/ 71 | 72 | DevOps: Ivan Podcebnev 73 | 74 | https://github.com/naykip 75 | 76 | https://www.linkedin.com/in/naykip/ 77 | 78 | ## How the community can engage 79 | * GitHub Discussion: https://github.com/ipfs/community/discussions/612 80 | * Email: info@uddug.com 81 | 82 | ## How to Contribute 83 | 84 | 85 | Reach-out and suggest improvements & features 86 | 87 | Report bugs 88 | 89 | Brainstorming 90 | 91 | Any ideas 92 | 93 | Promotional channels 94 | 95 | Words of encouragement 96 | 97 | Any kind of feedback 98 | 99 | -------------------------------------------------------------------------------- /projects/LandMine.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | 3 | LandMine 4 | 5 | ## Category 6 | 7 | Application 8 | 9 | ## Project Description 10 | 11 | Landmine is a platform where each property {like apartments,bunglow} is represented as an nft and then these nft are put up for sale. 12 | -Buyers can buy the properties listed on the site. 13 | -After Buyer agress to buy the property they will upload the agreement details which will be saved in the ipfs platform and seller will complete the transaction after the completion of payment. 14 | -Buyer can verify these transaction details by using their property id by entering their id and they will get the ipfs link of their agreement. 15 | 16 | ### Use of IPFS 17 | - We have used ipfs for storing the documents related to the agreement details . 18 | - here is the link 19 | for the demo agreement details made by using ipfs. 20 | 21 | 22 | ## Project Status 23 | 24 | Need to add the registration page, redesign the ui and the transaction page and little tweaks in the smart contracts regarding the revenue. 25 | 26 | ## Previews 27 | 28 | Screenshots: ![alt text](https://siasky.net/vAHX05cSzk8_3diwKLFumx4lGXFN3M0cgVAioQDQxdjrIg) 29 | 30 | 31 | ![alt text](https://siasky.net/LADILo82OTgI6clQsVhn5w58BVwqpB_QVFJ7Vg8zpEz1FQ) 32 | 33 | 34 | ![alt text](https://siasky.net/jADE_NAY6CdapliFLhKSFY6zQwAFXblvLxS3Q4WqdvIHPw) 35 | 36 | 37 | ![alt text](https://siasky.net/LAC6uvrtyQzAPYqBXMiSAiq0Fx_8kUGgg1EWZxxOsd0U3Q) 38 | 39 | 40 | ![alt text](https://siasky.net/DADm7GaFYmjPhP8eM7a2FmN61eOcFvpBY3TC_P7kLDz5ag) 41 | ![alt text](https://siasky.net/fAb9RSi49mIgDIRlLb4qy_cHAsRPub1rYY2yXeSmr07Aqw) 42 | 43 | ![alt text](https://siasky.net/fABWmFWSi_B-VcxYXNhjFQPDoJ5YPfEVm5tn3ioaAEV_Mw) 44 | ![alt text](https://siasky.net/zACIz4ziCpjSOpy4OQcHeFBL2i1DAldxB_aGqMBoGe1lnQ) 45 | 46 | ![alt text](https://siasky.net/vAOlzpNoPqCbA6QvK7MZmWBxqpe-LLA_qYjA9kUZjbXJVQ) 47 | 48 | 49 | Video: https://youtu.be/QuhAO8GlKT8 50 | 51 | ## Target Audience 52 | 53 | General public interested in buying and selling property. 54 | 55 | ## Rough estimated user base (if applicable) 56 | 57 | N/A 58 | 59 | ## Github repo 60 | 61 | https://github.com/Mr-Maximus/landmine_project 62 | 63 | ## Website 64 | 65 | TBA 66 | 67 | ## Docs 68 | 69 | In progress 70 | 71 | ## Team Info 72 | 73 | The LandMinw team was assembled as part of the Chainlink hackathon there are currently 2 members 74 | 75 | ### Team Size 76 | 2 members 77 | 78 | ### Team members 79 | [Madan Raj.S](https://github.com/Mr-Maximus) 80 | [Mukesh Jaiswal](https://github.com/MukeshJaiswal01) 81 | 82 | 83 | ## How the community can engage 84 | GitHub Discussion:https://github.com/ipfs/community/discussions/529 85 | Email: jaiswalsamar443@gmail.com 86 | Slack: N/A 87 | Twitter: @Maximus1_ @MukeshJ_eth 88 | Discord: N/A 89 | Telegram: N/A 90 | WeChat: N/A 91 | 92 | ## How to Contribute 93 | 94 | Please reachout to email jaiswalsamar443@gmail.com 95 | -------------------------------------------------------------------------------- /projects/Lifefram.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Lifefram (formerly known as Peopedia) 3 | 4 | ## Category 5 | Application 6 | 7 | ## Project Description 8 | We're building a global decentralized database to store records of the deceased for 300 years and beyond. Knowledge should last forever, including the knowledge of us. 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | We use IPFS to ensure biographies are stored in a decentralized manner across different nodes. Any IPFS nodes are free to duplicate our data on their nodes. 12 | 13 | ## Project Status 14 | Beta version is live at https://lifefram.org 15 | 16 | ## Previews 17 | * [Main page](https://github.com/lifefram/lf/blob/main/screenshot-lifefram.org-2022.02.03-11_59_33.png) 18 | * [Sample of a biography](https://github.com/lifefram/lf/blob/main/screenshot-lifefram.org-2022.02.03-12_00_22.png) 19 | * [Listing of biographies](https://github.com/lifefram/lf/blob/main/screenshot-lifefram.org-2022.02.03-12_02_39.png) 20 | 21 | ## Target Audience 22 | Global audience, especially those with loved ones who have just passed away. 23 | 24 | ## Rough estimated user base (if applicable) 25 | We project to receive over 20,000 visits per month in the coming months. 26 | 27 | ## Github repo 28 | https://github.com/lifefram/lf 29 | 30 | ## Website 31 | https://lifefram.org 32 | 33 | ## Team Info 34 | The idea of this project got started when our founder tried to write a biography of his departed aunt on Wikipedia. Sadly, the article was rejected because his aunt was not considered a notable person. Which gave him the idea to create this platform where anyone could memorialize anyone else who has passed away. 35 | 36 | Our mission is to manage a global decentralized database to document those who have passed away permanently and persistently for 300 years and beyond. 37 | 38 | To ensure every biography would last forever, we’ve set out to build a platform that is redundant and decentralized from any central authority. With this aim, we’ve built a data storage network based on decentralized storage system that is independent from operating system and geographic location with more independence foreseeable in the future, thus ensuring that even after we’re gone, the knowledge of us shall continue to persist in this world. 39 | 40 | ### Team Size 41 | Three 42 | 43 | ### Team members 44 | Melvin Wong, Not-Your-Everyday Developer 45 | Pedro Machado, Blockchain System Engineer 46 | Shin Gahee, UI/UX Designer cum Content Curator 47 | 48 | ## How the community can engage 49 | GitHub Discussion: https://github.com/ipfs/community/discussions/729 50 | Email: hello@lifefram.org 51 | Discord: https://discord.gg/HxcdrgMeYa 52 | 53 | ## How to Contribute 54 | We're looking for people to help spread the news of this project. We're non-profit and forever will be. 55 | 56 | If you wish your loved ones to be forever remembered, please log in to our site and create a biography of them. 57 | 58 | We're more than happy to return the same favor for your project. 59 | -------------------------------------------------------------------------------- /projects/Meta Manager.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | 3 | Meta Manager 4 | 5 | ## Category 6 | 7 | Application 8 | 9 | ## Project Description 10 | 11 | The Meta Manager is a fully decentralized one-stop-shop data manager for meta creators to easily manage their META and transaction data all in one place. 12 | 13 | **Highlight features:** 14 | 15 | * Decentralized Identifier (DID) based META/NFT metadata, which means it’s truly blockchain networks agnostic. 16 | * All data stores on IPFS nodes, which means everyone can access that data anywhere, anytime, and forever. 17 | * The meta creators can mint an NFT or a collection of NFTs onto any blockchain networks they would like. 18 | * The creators can use their wallet account's private/public keys to encrypt/decrypt certain sensitive data for each NFTs. 19 | 20 | ## Use of IPFS, Filecoin and Libp2p 21 | 22 | The project utilizes IPFS to store the metadatda for digital creators but would like to explore how to plug it into Filecoin. 23 | 24 | ## Project Status 25 | 26 | The MVP was done during the Scaling Ethereum Hackathon and won a prize from Protocol Labs, but it's still under development to enhance the existing features and add new features. We're keen to fundraising at the same time as well. 27 | 28 | ## Previews 29 | 30 | | Landing Page | Meta List Page | 31 | |------|-------| 32 | ||| 33 | 34 | | Create Metadata | 35 | |------| 36 | || 37 | 38 | ## Target Audience 39 | 40 | Meta Creators 41 | 42 | ## Rough estimated user base (if applicable) 43 | 44 | The product is still heavily under develoment, not online yet. 45 | 46 | ## Github repo 47 | 48 | https://github.com/nama-finance/meta-manager 49 | 50 | ## Website 51 | 52 | https://nama.finance 53 | 54 | https://showcase.ethglobal.co/scaling/nama-finance 55 | 56 | 57 | ## Docs 58 | 59 | https://github.com/nama-finance/meta-manager 60 | 61 | ## Team Info 62 | 63 | 64 | ### Team Size 65 | 66 | 1 67 | 68 | ### Team members 69 | 70 | Victor, Certified blockchain solution architect and Ethereum developer. He has around 15 years of IT project development and management experiences. Participated and led several large-scale distributed and decentralized systems design and development in banking, blockchain, telecom, and media industries etc. 71 | 72 | ## How the community can engage 73 | 74 | * GitHub Discussion: https://github.com/ipfs/community/discussions/557 75 | * Email: victor@nama.finance 76 | * Twitter: https://twitter.com/nama_finance 77 | * Telegram: https://t.me/namaprotocol 78 | 79 | ## How to Contribute 80 | 81 | -------------------------------------------------------------------------------- /projects/MetaPets.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | MetaPets 3 | 4 | ## Category 5 | NFTs browser based game 6 | 7 | ## Project Description 8 | An Artists Metaverse full of cute 3D Animals with a Paint-to-Earn system. Artists will participate in painting contests where the community will vote for their favourite. Tokens will be distributed based on ranking of the leaderboard. 9 | 10 | https://www.youtube.com/watch?v=Y0BSrEWZ8dw 11 | 12 | This project won the first place for the Mercury Hackathon in the video game category: https://angelhack.com/blog/announcing-mercury-hackathon2021-winners-%f0%9f%8e%89.html/ 13 | 14 | ## Use of IPFS, Filecoin and Libp2p 15 | Artists will paint on 3D animals models directly in the browser, the painting are actually JPG files base64 encoded that are stored in IPFS (web3.storage). 16 | 17 | ## Project Status 18 | Beta => users can already paint on the MetaPets and submit their artwork which will give them a unique link to share to the world so everyone can admire their piece of art! 19 | 20 | ## Previews 21 | ![image](https://i.ibb.co/LnJFBsV/mp.png) 22 | 23 | 24 | ## Target Audience 25 | Every NFTs games enthusiast and more generally people who love to draw! 26 | 27 | ## Rough estimated user base (if applicable) 28 | As we didn't begin advertising the project, we don't have any active user. 29 | 30 | ## Github repo 31 | https://github.com/metapets 32 | 33 | ## Website 34 | https://beta.metapets.art/ 35 | 36 | I cannot post the link to our Mercury Hackathon project submission as the link has been revoked since the submissions are closed 37 | 38 | ## Docs 39 | https://whitepaper.metapets.art/ 40 | 41 | ## Team Info 42 | 43 | ### Team Size 44 | 5 45 | 46 | ### Team members 47 | Kevin Tale - Founder of MetaPets 48 | I'm working in tech for almost 10 years now, mainly in frontend developement. I've discovered the blockchain technology in 2013 and immediately grew a passion for it. I've also always wanted to create a video game. NFTs gave me this opportunity, thus MetaPets is born! 49 | 50 | Julian Rutherford 51 | He's our blockchain expert, he mastered making decentralized application, especially with the Flow blockchain. He is now helping us creating great smart contracts to manage the MetaPets NFTs and the $NIMO currency. 52 | 53 | Lara Branco 54 | Lara is giving life to the MetaPets by modeling them in 3D. She already created a video game released on Apple and Google stores! 55 | 56 | Florian Veniat 57 | Our art director. He's been drawing since he was capable to hold a pen! He is creating the concept art of the MetaPets. 58 | 59 | Antoine Boniface Achille 60 | He is our Unity expert. He has the hard mission to create the smoother painting tool possible! It is thanks to him that you can draw on these beautiful MetaPets. 61 | 62 | 63 | ## How the community can engage 64 | * Email: contact@metapets.art 65 | * Twitter: https://twitter.com/metapetsNFT 66 | * Discord: https://discord.gg/rBPP7uxnwd 67 | 68 | ## How to Contribute 69 | https://github.com/ipfs/community/discussions/694 70 | You can help use better the painting system if you have great skill with Unity! 71 | Also, twitter follows and joining our discord server will grantly help us building a community 🙏 72 | -------------------------------------------------------------------------------- /projects/Monaliza.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | 3 | Monaliza 4 | 5 | ## Category 6 | 7 | NFT, Truffle, NodeJS, React, Python, IPFS Storage, CELO, Docker, Kubernetes, Solidity 8 | 9 | ## Project Description 10 | 11 | The project is aimed to be a connector between instagram/social media and NFTs, enabling the average instagram/social media user to be able to mint their own NFTs and submit them straight to their instagram, utilising their fanbase and followers, as well as Opensea, and persist this to IPFS as a storage point. This would hopefully get the average person to be able to adopt blockchain without having to leave the comfort of their favourite platform and make their instagram posts/pictures/videos an NFT. 12 | 13 | ## Project Status 14 | 15 | Under Development 16 | 17 | ## Previews 18 | 19 | ![Landing Page Preview](https://raw.githubusercontent.com/MrFord123/Mona/main/MonaSS.png) 20 | 21 | ## Target Audience 22 | 23 | Our target audience is those already using social media as a means of displaying their art. 24 | Artists, Animators, Illustrators, Photographers and the likes 25 | 26 | ## Rough estimated user base (if applicable) 27 | 28 | We're hoping both the users of the platform will be able to tap into their fanbase as well as users of social media platforms. 29 | 30 | ## Github repo 31 | 32 | https://github.com/monalisanft/nfthack 33 | 34 | ## Website 35 | 36 | Landing Page - https://monaliza.app/ 37 | 38 | ## Docs 39 | 40 | https://www.notion.so/monalisanft/Monaliza-a624fe444b11470db6972bdc134984f1 41 | 42 | ## Team Info 43 | 44 | Aina 45 | - Project Manager 46 | - Background In Corporate Finance 47 | - Entrepreneur in Fintech 48 | - Consultant 49 | - Blockchain Professor in a Business School 50 | 51 | Seema 52 | - Blockchain Backend Developer with a focus on Solidity, Truffle, NodeJS and Infrastructure as Code 53 | 54 | Jasmin 55 | - Marketing 56 | - Curator of all things Art 57 | - Entrepreneur 58 | 59 | George 60 | - Solutions Architect 61 | 62 | Darien 63 | - Security Engineer 64 | - Front End/DApp Developer 65 | - Crypto/Blockchain Specialist 66 | 67 | ### Team Size 68 | 69 | Currently a team of 5 70 | 71 | ### Team members 72 | 73 | Darien Ford 74 | Jasmin Fiori 75 | George Clarke 76 | Aina Raherimanantsoa 77 | Seema Sharma 78 | 79 | ## How the community can engage 80 | GitHub Discussion: https://github.com/ipfs/community/discussions/493 81 | Twitter: https://twitter.com/Monalizanft 82 | Instagram: https://instagram.com/monalizanft 83 | Discord: https://discord.gg/adezAErE 84 | LinkedIn: https://www.linkedin.com/company/monaliza 85 | TikTok: https://tiktok.com/@monalizanft 86 | 87 | ## How to Contribute 88 | 89 | We are very much open to all ideas, feedback and to build out a community. What would be great would be early users 90 | -------------------------------------------------------------------------------- /projects/NFT Museum: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | "NFT Museum" 3 | ## Category 4 | 5 | NFT, Museum, WebGL, Unity, C#, IPFS, Fleek 6 | 7 | ## Project Description 8 | 9 | Hi I’m Saru, making virtual NFT museum on IPFS by my selves from scratch includes 3D assets. 10 | 11 | I want to make the place for all NFT artists to share their arts easily for FREE, and the place for any people to explore and enjoy arts from all over the world. 12 | 13 | ## Use of IPFS, Filecoin and Libp2p 14 | 15 | Entire Museum, Assets and all files on IPFS 16 | 17 | ## Project Status 18 | 19 | open at 11pm May 14th PT 20 | https://museum.on.fleek.co/ 21 | or 22 | museum.saru.eth/ 23 | 24 | ## Previews 25 | 26 | 27 | 28 | ## Target Audience 29 | 30 | NFT Artists, Collectors as visitors, and all Art lovers 31 | 32 | ## Rough estimated user base (if applicable) 33 | 34 | In current Museum as opening, around 60 NFT Artists are featured in museum by applied. 35 | Also as Pre-Open, we have 30 - 70 new visitors coming to the museum. 36 | 37 | ## Github repo 38 | 39 | https://github.com/Sarupto/nftmuseum 40 | 41 | ## Website 42 | 43 | https://museum.on.fleek.co/ 44 | museum.saru.eth/ 45 | 46 | 47 | 48 | 49 | 50 | 51 | ## Team Info 52 | 53 | 54 | ### Team Size 55 | 1 56 | 57 | ### Team members 58 | Saru Builder, Unity Engineer, 3DCGI Artist and more 59 | 60 | ## How the community can engage 61 | * GitHub Discussion: https://github.com/ipfs/community/discussions/554 62 | * Email: sarupto.art@gmail.com 63 | * Twitter: https://twitter.com/Sarupto 64 | * Discord: https://discord.gg/5ETMk3svt7 65 | 66 | 67 | ## How to Contribute 68 | 69 | Any advices, ideas or supports are grateful 70 | -------------------------------------------------------------------------------- /projects/NFTIZ.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | NFTIZ 3 | 4 | ## Category 5 | 6 | Application 7 | 8 | ## Project Description 9 | 10 | NFTIZ is a Figma plugin that enables you to transform your design into a NFT. With NFTIZ, it's super easy to turn your Figma creations into NFT, put them on sale on OpenSea or send them as gifts to your friends. 11 | 12 | ## Use of IPFS, Filecoin and Libp2p 13 | 14 | Uploading images on IPFS with NFT.storage 15 | 16 | ## Project Status 17 | 18 | Shipped a first version that let you mint a frame as an image, and working on a second version to upload more complex files such as design systems, frameworks, etc 19 | 20 | ## Previews 21 | 22 | The first version of the plugin is available here: https://www.figma.com/community/plugin/1047579004421824566/NFTIZ 23 | ![image](https://user-images.githubusercontent.com/67648863/148956807-b8ccdea4-1b3f-48f0-88a2-2f6705395fed.png) 24 | 25 | 26 | ## Target Audience 27 | 28 | Designers and Figma users 29 | 30 | ## Rough estimated user base (if applicable) 31 | 32 | 4 millions potential users 33 | 34 | ## Github repo 35 | 36 | https://github.com/Meyanis95/NFTIZ 37 | 38 | ## Website 39 | 40 | https://nftiz-app.xyz/ 41 | 42 | https://showcase.ethglobal.com/web3jam/nftiz 43 | 44 | 45 | ## Team Info 46 | 47 | Yanis, building web3 products - @yanis_mez_ 48 | 49 | ### Team Size 50 | 1 51 | 52 | ## How the community can engage 53 | * GitHub Discussion: 54 | * Twitter: @yanis_mez_ 55 | * Discord: sinaxyz#3158 56 | * Telegram: @meyanisxyz 57 | -------------------------------------------------------------------------------- /projects/PaperHouse.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | 3 | Paper House 4 | 5 | ## Category 6 | 7 | Application 8 | 9 | ## Project Description 10 | 11 | An NFT Platform for Researchers & Scholars. One-stop solution to mint and publish a research paper on the blockchain, explore numerous research papers, and also fund research. 12 | 13 | ## Use of IPFS, Filecoin and Libp2p 14 | 15 | All the data related to Research papers are stored decentralized on IPFS and Filecoin with the help of nft.storage service created by protocol lab 16 | 17 | IPFS hash is then stored on chain for NFT tokenURI 18 | 19 | ## Project Status 20 | 21 | Beta 22 | 23 | ## Previews 24 | 25 | ![UiDesign](https://github.com/Paper-House/PaperHouse/blob/94afd19b3b1a9a2ad9469cf0de04b08d47ef8381/Images/UiDesign.jpg) 26 | 27 | ## Target Audience 28 | 29 | Researchers and scholars 30 | 31 | ## Rough estimated user base 32 | 33 | 100 34 | 35 | ## Github repo 36 | 37 | https://github.com/Paper-House/PaperHouse 38 | 39 | ## Website 40 | 41 | https://paper-house.netlify.app/ 42 | 43 | ## Submission Link 44 | 45 | https://devfolio.co/submissions/paper-house-a03b 46 | 47 | ## Docs 48 | 49 | https://github.com/Paper-House/PaperHouse/blob/main/README.md#Getting-Started 50 | 51 | ## Team Info 52 | 53 | ![Creators](https://github.com/Paper-House/PaperHouse/blob/7e7d51b9a26a55986d3932b1b40f5be1aabb6dea/Images/Creators.jpg) 54 | 55 | ### Team Size 56 | 57 | 3 58 | 59 | ### Team members 60 | 61 | - Sanket Marathe [@MSanket9](https://github.com/msanket9)
62 | - Sairaj Kapdi [@SairajK19](https://github.com/SairajK19)
63 | - Rhutik Parab [@c0deb1ind31](https://github.com/c0deb1ind31) 64 | 65 | ## How the community can engage 66 | * GitHub Discussion: https://github.com/ipfs/community/discussions/668 67 | * Email: theofficialpaperhouse@gmail.com 68 | * Twitter: https://twitter.com/Paper_HouseHQ 69 | * Discord: https://discord.gg/9xaTDxMpBy 70 | * Telegram: https://t.me/PaperHouseOfficial 71 | 72 | 73 | ## How to Contribute 74 | 75 | Our source code is open source and we are happy to receive pull requests on Github. 76 | -------------------------------------------------------------------------------- /projects/PassVault.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | PassVault 3 | 4 | ## Category 5 | Application 6 | 7 | ## Project Description 8 | PassVault is a browser extension built with Inter Planetry File System. Users can use their seed phrase to login their account and view their saved credentials. PassVault was built considering security as the #1 priority and is better than most of the traditional password managing methods. 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | The uniqueness of PassVault is that it uses IPFS for secure and immutable storage of passwords. IPFS adds more value to the password manager by making it decentralized and private. 12 | 13 | ## Project Status 14 | Under development 15 | 16 | ## Previews 17 | ![Paraphrase](https://cdn.discordapp.com/attachments/853989819206074382/858407010306359367/Screenshot_from_2021-06-26_23-29-59.png) 18 | ![GET and POST](https://media.discordapp.net/attachments/853989819206074382/858407041424162866/Screenshot_from_2021-06-26_23-29-55.png?width=1011&height=569) 19 | ![Dashboard](https://media.discordapp.net/attachments/853989819206074382/858407043983605800/Screenshot_from_2021-06-26_23-29-47.png?width=1011&height=569) 20 | 21 | ## Target Audience 22 | Anyone who wants to store and manage passwords in their browser. 23 | 24 | ## Rough estimated user base (if applicable) 25 | 7 beta testers. 26 | 27 | ## Github repo 28 | https://github.com/hackyguru/PassVault 29 | 30 | ## Website 31 | A docs site is set to be hosted soon. 32 | 33 | ## Docs 34 | https://github.com/hackyguru/PassVault/blob/master/README.md 35 | 36 | ## Team Info 37 | 38 | ### Team Size 39 | 3 40 | 41 | ### Team members 42 | Kumaraguru T 43 | - Full stack web developer and blockchain enthusiast. 44 | - https://github.com/hackyguru/ 45 | 46 | Mridula Kalaiselvan 47 | - Front end developer 48 | - https://github.com/Mridula90/ 49 | 50 | Emma Thomas 51 | - UI/UX designer 52 | - https://github.com/Emma-Thomas-jj 53 | 54 | ## How the community can engage 55 | * GitHub Discussion: https://github.com/ipfs/community/discussions/595 56 | * Email: kumaragurut7@gmail.com 57 | * Slack: 58 | * Twitter: 59 | * Discord: 60 | * Telegram: 61 | * WeChat: 62 | 63 | ## How to Contribute 64 | We welcome contributions in documentation/ development of PassVault. Please reach us out through email - kumaragurut7@gmail.com if you're interested. Feel free to open an issue at your repository in case you find any. 65 | -------------------------------------------------------------------------------- /projects/Phi.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Phi 3 | 4 | ## Category 5 | 6 | Application 7 | 8 | ## Project Description 9 | 10 | A decentralized, secure, end-to-end encrypted chat engine built on blockchain & IPFS. 11 | 12 | You can send chat requests to Ethereum addresses. Once they approve, they become your friends. You can then share text messages and image attachments securely. 13 | 14 | ## Use of IPFS, Filecoin and Libp2p 15 | 16 | Chat messages and friend requests are shared securely using Textile threads. 17 | Image attachments are shared securely using Textile buckets. 18 | Profile information is stored in Ceramic. 19 | 20 | ## Project Status 21 | 22 | Under development. 23 | 24 | ## Previews 25 | 26 | ![](https://challengepost-s3-challengepost.netdna-ssl.com/photos/production/software_photos/001/753/201/datas/gallery.jpg) 27 | ![](https://challengepost-s3-challengepost.netdna-ssl.com/photos/production/software_photos/001/753/212/datas/gallery.jpg) 28 | ![](https://challengepost-s3-challengepost.netdna-ssl.com/photos/production/software_photos/001/753/671/datas/gallery.jpg) 29 | ![](https://challengepost-s3-challengepost.netdna-ssl.com/photos/production/software_photos/001/753/284/datas/gallery.jpg) 30 | 31 | ## Target Audience 32 | 33 | Anyone looking for a web 3.0 solution for communication. 34 | 35 | ## Rough estimated user base (if applicable) 36 | 37 | As its under development, no users at the moment. 38 | 39 | ## Github repo 40 | 41 | 42 | 43 | ## Website 44 | 45 | 46 | 47 | 48 | 49 | 50 | ## Docs 51 | 52 | 53 | ## Team Info 54 | 55 | 56 | ### Team Size 57 | 1 58 | 59 | ### Team members 60 | Robin Thomas 61 | 62 | ## How the community can engage 63 | * GitHub Discussion: 64 | * Email: 65 | * Slack: 66 | * Twitter: 67 | * Discord: 68 | * Telegram: 69 | * WeChat: 70 | 71 | ## How to Contribute 72 | 73 | All ideas, feedback and supports are welcome. 74 | -------------------------------------------------------------------------------- /projects/Pictic.md: -------------------------------------------------------------------------------- 1 | 2 | ## Project Name 3 | Pictic 4 | 5 | ## Category 6 | Application 7 | 8 | ## Project Description 9 | A simple screenshot utility that has the ability to shots on IPFS using local IPFS nodes or remote ones. 10 | 11 | ## Use of IPFS, Filecoin and Libp2p 12 | * [ipfs-http-client](https://www.npmjs.com/package/ipfs-http-client) is used for adding files to IPFS using the ipfs API. 13 | * Hosted go-ipfs is used for remote storage (if user chooses) 14 | * Local go-ipfs can used for local IPFS add API calls. 15 | 16 | ## Project Status 17 | Beta 18 | 19 | ## Previews 20 | 21 | 22 | 23 | 24 | ## Target Audience 25 | Any user that needs a simple screenshot utility that is both easy to use and stable. I started the project because using the snipping tool/paint combo for me was starting to be fatiguing. 26 | 27 | ## Rough estimated user base (if applicable) 28 | No data yet 29 | 30 | ## Github repo 31 | https://github.com/hayzamjs/Pictic 32 | 33 | ## Website 34 | Not available yet. 35 | 36 | ## Docs 37 | Not available yet. 38 | 39 | ## Team Info 40 | Right now I'm the only one ([hayzamjs](https://github.com/hayzamjs)) part of this project, I've also worked on other projects like [libipfs](https://github.com/scala-network/libipfs) for the IPFS community. 41 | 42 | ### Team Size 43 | 1 44 | 45 | ### Team members 46 | [Hayzam](https://github.com/hayzamjs) - Lead Developer 47 | 48 | ## How the community can engage 49 | * Discord: https://discord.gg/ZTkkRPZnQ7 50 | 51 | ## How to Contribute 52 | They can contribute by helping me test, fix bugs or even make suggestions on what we could add in future releases (by preferably making a pull request). 53 | -------------------------------------------------------------------------------- /projects/Rhada.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | 3 | Rhada 4 | 5 | ## Category 6 | 7 | Application 8 | 9 | ## Project Description 10 | 11 | Rhada is building an application to help crypto-native organisations connect payment streams to real world events. We are initially focusing on DAOs looking to provide incentive structures for meaningful participation, by offering a way to start and stop payment streams based on whether members log meaningful activities that further the interests of the DAO. 12 | 13 | ## Use of IPFS, Filecoin and Libp2p 14 | 15 | Any and all events that are used to modify Rhada streams are publicly auditable in IPFS. We initially used Textile as a publicly accesible, distributed event log that adds full transparency to our application, and allows contributors, investors and partipants to query event logs and ensure pre-event transactions are valid - without requiring expensive on-chain storage. 16 | 17 | ## Project Status 18 | 19 | Under active development, from PoC to MVP. Currently seeking further funding. 20 | 21 | ## Previews 22 | 23 | https://www.youtube.com/watch?v=erdGiquvddc 24 | 25 | ## Target Audience 26 | 27 | We will initially targeting DAOs looking to increase meaningful participation by incentivising members of the community. 28 | 29 | ## Rough estimated user base (if applicable) 30 | 31 | 1 (Ourselves!) 32 | 33 | ## Github repo 34 | 35 | https://github.com/RhadaPay 36 | 37 | ## Website 38 | 39 | https://rhada.co (not yet launched) 40 | 41 | 42 | https://showcase.ethglobal.co/hackfs2021/rhadapay 43 | 44 | 45 | ## Docs 46 | 47 | https://github.com/RhadaPay 48 | 49 | ## Team Info 50 | 51 | We are 4 developers based in the USA, Canada, Italy and the UAE, all with previous experience on DApp and Blockchain development. 52 | 53 | * Franceso is a full stack blockchain engineer and consultant 54 | * Levi is a full stack engineer who has entered and won multiple past hackathons 55 | * Kevin is a student at Vanderbilt University who has past professional contracting work in the blockchain industry 56 | * Jordan is a full stack engineer and previous founder of a startup in the UAE. 57 | 58 | ### Team Size 59 | 4 60 | 61 | ### Team members 62 | 4 63 | 64 | ## How the community can engage 65 | * GitHub Discussion: https://github.com/ipfs/community/discussions/652 66 | 67 | Reach out to me directly, while we get our team presence established! 68 | * Email: jordan.imran@rhada.co 69 | * Discord: jordaniza#9868 70 | * Telegram: @jordaniza 71 | 72 | ## How to Contribute 73 | 74 | We're looking to canvas from the community at this stage. Contribution could be in the form of feedback on the initial project idea, and in particular we're looking to speak with anyone who has experience in DAO governance and can help guide us on some of the challenges they've been facing. 75 | -------------------------------------------------------------------------------- /projects/RunETH.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | 3 | RunETH 4 | 5 | ## Category 6 | 7 | Application 8 | 9 | ## Project Description 10 | 11 | An on-chain proof-of-workout decentralised application to help people develop good fitness habits where people stake their crypto as a proof of their commitment, 12 | and upload their proofs on IPFS for a truly open and global accountability system. 13 | 14 | ## Use of IPFS, Filecoin and Libp2p 15 | 16 | Daily workout proofs (generated using smartphones or smart-watches) are submitted onto IPFS using pinata.cloud SDK to track daily progress of all participants as well as 17 | create a system of immutable global accountability to make sure users reach their goals. 18 | 19 | ## Project Status 20 | 21 | Under active development. 22 | 23 | ## Previews 24 | 25 | https://user-images.githubusercontent.com/32522659/124522524-35999500-de11-11eb-9b1f-a092a7a9480d.mp4 26 | 27 |
28 |
29 | 30 | 31 | ![RunETH Diagram](https://github.com/saxenism/RunETH/blob/8923598f121ceb22f81d01a1b8a00cb2c7fd9603/Workflow.png) 32 | 33 |
34 |
35 | 36 | ![ss-4](https://user-images.githubusercontent.com/32522659/124523015-d63c8480-de12-11eb-868f-2cec90828a99.PNG) 37 | 38 |
39 |
40 | 41 | 42 | ![ss-3](https://user-images.githubusercontent.com/32522659/124523021-dd639280-de12-11eb-8b3c-dd03aa5db378.PNG) 43 | 44 | 45 |
46 |
47 | 48 | 49 | ![ss-2](https://user-images.githubusercontent.com/32522659/124523040-ea808180-de12-11eb-9806-c0ed29cce25b.PNG) 50 | 51 | 52 |
53 |
54 | 55 | 56 | ![ss-1](https://user-images.githubusercontent.com/32522659/124523045-ed7b7200-de12-11eb-8318-1ee282dfdb25.PNG) 57 | 58 | 59 |
60 |
61 | 62 | ## Target Audience 63 | 64 | Anyone who wants to build positive fitness habit in a decentralised, immutable, global accountability system. 65 | 66 | ## Rough estimated user base (if applicable) 67 | 68 | Friends and Family as of now (beta testers) 69 | 70 | ## Github repo 71 | 72 | https://github.com/saxenism/RunETH 73 | 74 | ## Website 75 | 76 | https://showcase.ethglobal.co/hackmoney2021/runeth 77 | 78 | ## Docs 79 | 80 | Work in progress (Under development) 81 | 82 | ## Team Info 83 | 84 | I am Rahul Saxena, building this project solo. 85 | 86 | ## How the community can engage 87 | * GitHub Discussion: https://github.com/ipfs/community/discussions/637 88 | * Email: saxenism@gmail.com 89 | * Twitter: @saxenism 90 | * Discord: Rahul Saxena#8139 91 | * Telegram: @YaamiDancho 92 | 93 | ## How to Contribute 94 | Please give out suggestions or point out issues [here](https://github.com/saxenism/RunETH/issues) or [tag me on twitter](https://twitter.com/saxenism) or become a part of [discussions](https://github.com/ipfs/community/discussions/637). 95 | If you are a developer, you are free to [open PRs](https://github.com/saxenism/RunETH/pulls). 96 | -------------------------------------------------------------------------------- /projects/SecondLanguagePlayground.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | LibP2P - Second Language Education Playground 3 | 4 | ## Category 5 | Application 6 | 7 | ## Project Description 8 | Education playground is a project developed for educators play with students different games helping to learn a second language. 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | The project is all build-up with LibP2P communications between an Educator and students. Once teacher creates a room it shares with students the link to that room. 12 | The app automatically detects that room has an owner and students can follow educator directions. 13 | 14 | ## Project Status 15 | Alpha 16 | 17 | ## Previews 18 | https://github.com/filipesoccol/libp2p-second-language-playground/blob/master/src/assets/screenshot.png 19 | 20 | 21 | 22 | ## Target Audience 23 | Educators and students 24 | 25 | ## Github repo 26 | https://github.com/filipesoccol/libp2p-second-language-playground/ 27 | 28 | ## Website 29 | https://filipesoccol.github.io/libp2p-second-language-playground/ 30 | 31 | ## Docs 32 | Docs incluede on Github Readme. 33 | 34 | ## Team Info 35 | We are a couple. When pandemic starts Marcela and other teachers struggle to teach using different technologies aroud the web, some of those tools were paid and hard for other teacher to understand and use. 36 | Our idea is to use both knowledge to create open-source playgrounds where teachers could use them to teach students a second language. 37 | 38 | ### Team Size 39 | Two of us. 40 | 41 | ### Team members 42 | Filipe Montanari Soccol - Systems Analyst 43 | Marcela Furumoto Kurozawa - English Teacher 44 | 45 | ## How the community can engage 46 | * GitHub Discussion: https://github.com/ipfs/community/discussions/650 47 | * Email: filipe.soccol@gmail.com 48 | * Twitter: https://twitter.com/filipesoccol 49 | -------------------------------------------------------------------------------- /projects/Sytime.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Sytime 3 | 4 | ## Category 5 | 6 | Application, API 7 | 8 | ## Project Description 9 | 10 | Sytime is decentralised chat application. 11 | Users can connect to our DApp with their Ethereum wallet, with an extension like Metamask. 12 | Sytime allows users to create and edit personal accounts on the Ceramic platform leveraging decentralized identity 13 | and user data sovereignty to interact with other users in a chat. 14 | Users can also chat with others in different rooms and view the history of each room as well as send pictures to chat. 15 | The list of rooms is also stored as part of the ceramic profile so users can keep their chat history handy in different browser sessions. 16 | 17 | ## Use of IPFS, Filecoin and Libp2p 18 | 19 | We use IPFS pubsub to chat and with everything connected to the chat. 20 | Also we use Web3.Storage to store the history of messages. 21 | We are deployed on Fleek! We also will use IPFS for share media like music/video and pictures. 22 | 23 | ## Project Status 24 | 25 | fundraising, under development 26 | 27 | ## Previews 28 | 29 | ![1](https://ethglobal.s3.amazonaws.com/rec3dQTX9jnVOXz6A/Screenshot_2021-11-21_at_16.45.36.png) 30 | ![2](https://ethglobal.s3.amazonaws.com/rec3dQTX9jnVOXz6A/Screenshot_2021-11-21_at_16.45.16.png) 31 | ![3](https://ethglobal.s3.amazonaws.com/rec3dQTX9jnVOXz6A/Screenshot_2021-11-21_at_16.45.26.png) 32 | 33 | We are also live [here](https://sparkling-morning-4135.on.fleek.co/) 34 | 35 | ## Target Audience 36 | 37 | We are web3 chat app, so everyone can use it! 38 | 39 | ## Rough estimated user base (if applicable) 40 | 41 | 5-10 users now :D 42 | 43 | 44 | ## Github repo 45 | 46 | https://github.com/ThirdRockEngineering/Sytime 47 | 48 | ## Website 49 | 50 | https://sparkling-morning-4135.on.fleek.co/ 51 | 52 | 53 | https://showcase.ethglobal.com/web3jam/sytime 54 | 55 | ## Docs 56 | 57 | This is what we have so far: https://utopian-zebu-9e1.notion.site/201473ba3c8c42b9b33b34f914e9372a?v=be2e9bd2134b4e20b72e2ff2829eb1d7 58 | 59 | ## Team Info 60 | 61 | We are team of 3! We recently graduate from a Fullstack Academy coding bootcamp and after that took a 1 place in best use of IPFS/Filecoin in Web3 Jam. :) 62 | 63 | ### Team Size 64 | 3 person right now, but we want to grow! 65 | 66 | ### Team members 67 | [Emil Sharafutdinov](https://www.linkedin.com/in/emilishere/) 68 | [Freddy G](https://www.linkedin.com/in/freddyjgomez/) 69 | [Nicholas Zehr](https://www.linkedin.com/in/nicholas-zehr-pmp/) 70 | 71 | ## How the community can engage 72 | * GitHub Discussion: https://github.com/ipfs/community/discussions/709 73 | * Email: emil.shrft@gmail.com 74 | * Discord: https://discord.gg/2qaCxbwk 75 | 76 | 77 | ## How to Contribute 78 | 79 | Check out our [project board](https://github.com/ThirdRockEngineering/Sytime/projects/2) for available issues :) 80 | -------------------------------------------------------------------------------- /projects/The Convo Space.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | The Convo Space 3 | 4 | ## Category 5 | Protocol, Application 6 | 7 | ## Project Description 8 | The Decentralized Conversation Layer of Internet, customizable plugins for apps connecting conversations and communities across the Internet. 9 | 10 | **Highlight features:** 11 | 12 | - Introducing an Open-Source Decentralized Conversation Layer that can be used to start instant conversations on any website/mobile-app/NFT/topic in a decentralized and unstoppable manner. 13 | - Convo is an extensible layer that anyone can utilize to build conversational apps powered by Convo's API. 14 | - With Convo users can truly own their data and shows an aggregated view of all the conversations you've had powered by Convo's API throughout the internet on the Dashboard with the ability to delete them. 15 | - With Convo you can download your all of your own data and erase all of it from every website. 16 | - With Convo you can monetize your data by creating DataTokens and exposing your Data to the world of DeFi. 17 | - With Convo you can build you own interface/apps using the API to access user data (only by authentication). 18 | - With Convo you can further build and verify your decentralized digital identity with support for ENS along with Proof of Humanity and BrightID. 19 | 20 | ## Use of IPFS, Filecoin and Libp2p 21 | The project utilizes Textile's ThreadDB and IPFS for building the Convo's API and Filecoin for data storage and backups. 22 | 23 | ## Project Status 24 | The Beta was built during the Web3Weekend hackthon from ETHGlobal and won prizes from Protocol Labs, Textile, Ocean Protcol, ENS. 25 | It's still under heavy development and would use the funds to enhance the existing features and buidling new ones. 26 | 27 | ## Previews 28 | 29 | | Project Demo | Dashboard | 30 | |------|-------| 31 | |[![alt text](https://theconvo.space/images/poster.png)](https://youtu.be/p5-jQy7vKk8 "The Convo Space")|| 32 | 33 | ## Target Audience 34 | Developers and Applications/Websites/MetaVerse 35 | 36 | ## Rough estimated user base (if applicable) 37 | Early to say but the potential userbase is in ~Millions 38 | 39 | ## Github repo 40 | https://github.com/anudit/convo 41 | https://github.com/anudit/convodocs 42 | 43 | ## Website 44 | https://theconvo.space 45 | https://showcase.ethglobal.co/web3weekend/the-convo-space 46 | 47 | ## Docs 48 | https://docs.theconvo.space 49 | 50 | ## Team Info 51 | 52 | ### Team Size 53 | 1 54 | 55 | ### Team members 56 | 57 | [Anudit Nagar](https://github.com/anudit), Full Stack Blockchain and Web Developer, and Researcher. 58 | 59 | ## How the community can engage 60 | 61 | * GitHub Discussion: https://github.com/ipfs/community/discussions/562 62 | * Email: nagaranudit@gmail.com 63 | * Twitter: https://twitter.com/anuditnagar 64 | 65 | ## How to Contribute 66 | - Try out The Convo Space 67 | - Reach-out and suggest improvements & features, report bugs. 68 | 69 | -------------------------------------------------------------------------------- /projects/TrueBlocks.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | TrueBlocks / Unchained Index 3 | 4 | ## Category 5 | Infrastructure, Public Good, Indexing Solution 6 | 7 | ## Project Description 8 | - TrueBlocks is an open-source project which includes an indexing solution for any blockchain, better explained [here](https://trueblocks.io/docs). 9 | - Unchained Index is a collection of techniques within TrueBlocks that uses IPFS and an Ethereum smart contract to produce, publish, and distribute the index in a Web 3.0 native way. 10 | - By "Web 3.0 native" we mean it is (a) reproducible, (b) uncapturable, (c) private by default, and (d) most importantly, cheap. 11 | - Using IPFS, and without the user's intervention, the index is naturally, cheaply and equitably distributed as heavy users of the chain carry a heavier burden and lighter users of the chain carry a lighter burden. 12 | - Unlike other index providers, Unchained Index seeks to treat chain data like a "public good" by limiting dependency on central gatekeepers, retaining the immutable nature of the chain data and, promoting cheap and widespread data access to the chain data. 13 | 14 | ## Use of IPFS, Filecoin and Libp2p 15 | - Unchained Index leverages IPFS to broadly distribute the index of the chain data cheaply, securely, verifiably and decentrally. 16 | - Currently, we use Pinata as a pinning services, however, we wish to explore the use of FileCoin as a pinning service. 17 | 18 | ## Project Status 19 | 20 | - Unchained Index was conceived and initially developed as part of ETHGlobal HackFS in August 2020. We received a prize for our work from Pinata. 21 | - It remains under active development and is an intergral building block of TrueBlocks, including its use in our [Account Explorer](https://github.com/TrueBlocks/trueblocks-explorer) application. 22 | 23 | ## Previews 24 | - [Video Explainer of Unchained Index](https://unchainedindex.io/) 25 | 26 | ## Target Audience 27 | 28 | - Trueblocks and the Unchained Index are broadly applicable to many users. Being an indexing solution for blockchains in general, and the Ethereum mainnet in particular, anyone can use the data we produce. 29 | - Our primary audience is ultimately 'regular users', meaning individuals looking for fully-local access to blockchain data without reliance on any third party (including ourselves). 30 | 31 | ## Rough estimated user base (if applicable) 32 | 33 | - Being alpha software, we have no users in production but many interested potential users and active conversations in our Discord. 34 | 35 | ## Github repos 36 | 37 | - 38 | - 39 | - 40 | 41 | ## Websites 42 | 43 | - 44 | - 45 | 46 | ## Docs 47 | 48 | - 49 | 50 | ### Team size 51 | 52 | - Four (two full time) 53 | 54 | ### Team members 55 | 56 | - Thomas Jay Rush - [lead developer](https://github.com/tjayrush) 57 | - Dawid Szlachta - [full stack developer](https://github.com/dszlachta) 58 | - Matt Dodson - [documentation](https://github.com/MattDodsonEnglish) 59 | - Meriam Zandi - [product manager](https://www.linkedin.com/in/meriam-zandi-6799661b1/) 60 | 61 | ## How the community can engage 62 | 63 | - GitHub Discussion: [click here](https://github.com/ipfs/community/discussions/658) 64 | - Email: jrush@trueblocks.io 65 | - Slack: N/A 66 | - Twitter: @trueblocks 67 | - Discord: [click here](https://discord.gg/kAFcZH2x7K) 68 | - Telegram: N/A 69 | - WeChat: N/A 70 | 71 | ## How to contribute 72 | 73 | - Join our [discord](https://discord.gg/rMdunZHCuu) and check out our [GitHub repo](https://github.com/TrueBlocks/trueblocks-core). We welcome all feedback and PRs. 74 | -------------------------------------------------------------------------------- /projects/TrueRaffle.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | TrueRaffle 3 | 4 | ## Category 5 | 6 | Raffle, Dapp, IPFS, Social Media 7 | 8 | ## Project Description 9 | 10 | A dapp which uses Chanlink VRF to make cryptographically secure random raffles making them trustless. 11 | The goal is to use it with comments from Social Media (e.g. Youtube, Instagram) or just participation with Metamask. 12 | The winner is saved on chain and verifiable by the Smartcontract. 13 | 14 | ## Project Status 15 | 16 | The project is currently under development. Currently brainstorming the next steps. 17 | 18 | ## Previews 19 | 20 | ![image](https://raw.githubusercontent.com/ScarFace06/TrueRaffle/main/Images/youtuberaffle.png) 21 | 22 | ## Target Audience 23 | 24 | Social Media user, everyone who wants to host a Raffle. 25 | 26 | ## Rough estimated user base (if applicable) 27 | 28 | Currently it's under development, therefore we don't have any users at the moment. 29 | 30 | ## Github repo 31 | 32 | https://github.com/ScarFace06/TrueRaffle 33 | 34 | ## Website 35 | 36 | The Project isn't hostet yet 37 | 38 | ## Docs 39 | 40 | https://github.com/ScarFace06/TrueRaffle/blob/main/README.md 41 | 42 | ## Team Info 43 | 44 | 45 | ### Team Size 46 | 3 47 | 48 | ### Team members 49 | ScarFace 50 | - Front End Developer 51 | - bussiness information systems student 52 | - https://github.com/ScarFace06 53 | 54 | Oilyshelf 55 | - Full Stack Developer 56 | - bussiness information systems student 57 | - https://github.com/oilyshelf 58 | 59 | Averycode 60 | - Front End Developer 61 | - bussiness information systems student 62 | - https://github.com/averycode 63 | 64 | ## How the community can engage 65 | GitHub Discussion: 66 | Email: dacesar06@gmail.com 67 | Slack: 68 | Twitter: 69 | Discord: 70 | Telegram: 71 | WeChat: 72 | 73 | ## How to Contribute 74 | 75 | Just reach out to us and we can develop together! Besides that we are fairly new to Blockchain development, therefore we got a lot of questions, that need to be answered :). 76 | https://github.com/ipfs/community/discussions/497 77 | -------------------------------------------------------------------------------- /projects/VoidReplica.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | VoidReplica 3 | 4 | ## Category 5 | 6 | Application 7 | 8 | ## Project Description 9 | 10 | - The students are made to upload their assignment in either of a format. 11 | - The result is a stored in a Decentralised platform. 12 | - The main Objective of VOID REPLICA is to avoid the problem of plagiarism. 13 | - The content cannot be changed or copied without attributing the creator. 14 | - By using the immutability of Block Chain every original files gets it's fingerprints stored in the form of a block chain network where it resides forever 15 | 16 | ## Use of IPFS, Filecoin and Libp2p 17 | 18 | - Solidity was used to write smart contracts. 19 | - The uploaded files are parsed through IPFS and the generated hash of the IPFS files are stored in MYSQL database. 20 | - The files are fetched and displayed using INFURA. 21 | 22 | ## Project Status 23 | 24 | Fund raising: 25 | - The project is under fund raising state,where it has been completely developed. 26 | 27 | ## Previews 28 | 29 | 30 | 31 | 32 | ## Target Audience 33 | 34 | - Students 35 | - Educational Institutions 36 | - Online Exam Portals 37 | - Online work Submission portals 38 | 39 | ## Rough estimated user base (if applicable) 40 | 41 | Approximately we have 20 users who uses to submit their online work assignments. 42 | 43 | ## Github repo 44 | 45 | - https://github.com/bkyogesh28/CivicHacks2021 46 | ## Website 47 | 48 | 49 | ## Docs 50 | 51 | - https://devpost.com/software/void-replica 52 | 53 | ## Team Info 54 | 55 | The project was developed by two members in the Civic Hacks 2021.We've won the Best Student Success hack using IPFS. 56 | - [Yogesh B K](https://github.com/bkyogesh28) -FullStack Developer,Backend Developer. 57 | - [Samuel Wycliffe](https://github.com/npc203) -Machine Learning Aspirant,Backend Developer. 58 | 59 | ### Team Size 60 | 5 members 61 | ### Team members 62 | - [Yogesh B K](https://github.com/bkyogesh28) -FullStack Developer,Backend Developer. 63 | - [Samuel Wycliffe](https://github.com/npc203) -Machine Learning Aspirant,Backend Developer. 64 | - [Saravanan M](https://github.com/Saravanan01-01) -Angular Developer,Frontend Developer. 65 | - [Keerthana K](https://github.com/Freakytedy18)- Frontend developer,Php developer. 66 | - [Jawahar P M](https://github.com/Jawaharpmm) -Blockchain Developer,Machine Learning Aspirant. 67 | 68 | ## How the community can engage 69 | * GitHub Discussion: https://github.com/ipfs/community/discussions/533 70 | * Email: 18eucs131@skcet.ac.in 71 | * Slack: 72 | * Twitter: 73 | * Discord: https://discord.gg/qb49MB2g 74 | * Telegram: 75 | * WeChat: 76 | 77 | ## How to Contribute 78 | 79 | - As it is a open Source any one can contribute to https://github.com/bkyogesh28/CivicHacks2021 80 | 81 | -------------------------------------------------------------------------------- /projects/WeatherChainXM.md: -------------------------------------------------------------------------------- 1 | ## WeatherChainXM 2 | 3 | ## Category 4 | IoT, Open Data, Smart Contracts, Smart Agriculture 5 | 6 | ## Project Description 7 | CHAINLINK + IPFS open hardware weather station. Energy and communication autonomous IoT sensor node, with weather sensors, that stores sensor data directly to IPFS and automates execution of parametric weather insurance contracts on-chain via the distributed CHAINLINK oracle system. 8 | 9 | ## Use of IPFS 10 | IPFS is used as storage for weather data recorded by the weather station, via a custom developed library that runs directly on the weather station's microcontroller. 11 | 12 | ## Project Status 13 | Weather station is already deployed on numerous sites, with the latest version including IPFS support. 14 | 15 | ## Previews 16 | ![Hardware](https://raw.githubusercontent.com/exmgr/WeatherChainXM/main/atmos41+exm-IoT-node.jpg) 17 | 18 | ## Target Audience 19 | Farms, Parametric Insurance providers 20 | 21 | ## Github repo 22 | https://github.com/exmgr/WeatherChainXM 23 | 24 | ## Website 25 | https://devpost.com/software/weatherchainxm 26 | 27 | ## Docs 28 | https://github.com/exmgr/WeatherChainXM/blob/main/README.md 29 | 30 | ## Team Info 31 | 32 | 33 | ### Team Size 34 | 3 35 | 36 | ### Team members 37 | Manolis Nikiforakis 38 | - Full stack developer 39 | 40 | Stratos Theodorou 41 | - Full stack developer 42 | - UI/UX 43 | 44 | Nikos Tsiligaridis 45 | - Hardware Developer 46 | 47 | ## How the community can engage 48 | * GitHub Discussion: https://github.com/ipfs/community/discussions/521 49 | * Email: connect@exm.gr 50 | * Slack: 51 | * Twitter: 52 | * Discord: 53 | * Telegram: 54 | * WeChat: 55 | 56 | ## How to Contribute 57 | Build and deploy :) Smart-contract side of the project is still in early/proof-of-concept stage. All feedback is welcome. -------------------------------------------------------------------------------- /projects/afterme.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | After Me 3 | ## Category 4 | 5 | Application 6 | ## Project Description 7 | 8 | Trustless estate planning solution that allows users to manage their digital assets in life and beyond. 9 | ## Project Status 10 | 11 | MVP operational 12 | ## Previews 13 | 14 | https://i.ibb.co/BzM0kTZ/1-set-up-contract.jpg 15 | https://i.ibb.co/V3mCY6K/manage-contract.jpg 16 | https://i.ibb.co/097dmHw/my-content.jpg 17 | https://i.ibb.co/T8MS1wG/archives.jpg 18 | 19 | ## Target Audience 20 | 21 | Customer segments:
    22 |
  1. Users of traditional centralized estate planning solutions that are motivated by After Me’s lower price point
    2. 23 | 24 |
  2. Post-mortem vloggers that wish to leave behind a record of their personality without being exposed to public scrutiny
    3. 25 | 26 |
  3. Public persons interested in retaining ownership of their natural identity through a claiming service (value prop. on the product roadmap)
    4. 27 | 28 | 29 | ## Github repo 30 | 31 | https://github.com/EightRice/afterme 32 | 33 | ## Website 34 | 35 | https://www.deathisreal.com Password: cl_hack **ONLY ON KOVAN TESTNET** 36 | 37 | ## Docs 38 | 39 | https://drive.google.com/file/d/1-fTdNrganmovKyCGh5x71nsg9SiDe2Ir/view?usp=sharing 40 | 41 | ## Team Info 42 | 43 | After Me is currently a one-man-show. Andrei Taranu - product manager www.andreitaranu.ml 44 | 45 | ## How the community can engage 46 | GitHub Discussion: 47 | Email: astmobronsita@gmail.com 48 | Twitter: @andreitaranu 49 | Discord: https://discord.gg/RKTHJZF 50 | https://github.com/ipfs/community/discussions/485 51 | 52 | ## How to Contribute 53 | 54 | Flutter and Solidity code,
    Promotional campaign management (Google Tag Manager, Funnel Analysis, Social Media Marketing, etc)
    Business development (attracting attention from potential investors)
    Words of encouragement
    **Any kind of feedback** 55 | -------------------------------------------------------------------------------- /projects/chanceofxyz.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | ChanceOf.xyz 3 | 4 | ## Category 5 | 6 | DApp,IPFS 7 | ## Project Description 8 | 9 | ChanceOf.xyz creates Data 'Legos' that help people know the chances of something happening before they transact. Based on the pioneering work of Dr. Sam Savage, ChanceOf.xyz uses the SIPmath specificaion for communicating uncertainties as actionable data. Chance-data is shared via IPFS as a public untilty. 10 | ## Use of IPFS, Filecoin and Libp2p 11 | 12 | IPFS plays important role in ChanceOf.xyz as the proabilty libraries are loaded and fetched from IPFS. 13 | 14 | ## Project Status 15 | 16 | The project was created by a team of strangers in four weeks. We came together somewhat randomly during team formation at ETH Global hackathon and created a chance of DeFi loan liquidating dApp (prototype). The probability data is stored and retrieved from IPFS. We would like to continue to project and make chance-data a public utility. 17 | 18 | ## Previews 19 | 20 | https://strangers-united.kitlung.com/#/ 21 | You will need to connect a crytpo wallet to see the demo. We do not retrieve any information from your wallet as this is just a demo. 22 | 23 | ## Target Audience 24 | 25 | We started off with DeFi data but have plans to put covid-19 transmision probabilies, sport/gaming, rare event data and more. 26 | 27 | ## Rough estimated user base (if applicable) 28 | Currently it's under development 29 | 30 | ## Github repo 31 | 32 | https://github.com/Strangers-United/Strangers-United 33 | 34 | ## Website 35 | 36 | https://chanceof.xyz/ 37 | 38 | ## Docs 39 | 40 | No time due to the short hackathon schedule. 41 | 42 | ## Team Info 43 | 44 | Currently we are team of 5 people. All of us were strangers to each other when we started. The youngest of us is 15. We are based in 4 different countries and 5 different timezones. 45 | 46 | ### Team Size 47 | :five: 48 | ### Team members 49 | You may find the team as contributors on this repo 50 | https://github.com/Strangers-United/Strangers-United 51 | 52 | ## How the community can engage 53 | * GitHub Discussion: https://github.com/ipfs/community/discussions/526 54 | * :e-mail: Email: i001962@gmail.com 55 | * Our Discord server: https://discord.gg/FRG7HChvCG 56 | 57 | ## How to Contribute 58 | 59 | We are looking for contributors that have historical data sets or predictive models to 'bottle' their outputs in SIPMath format. As well app developers that specialize in data viz. Our plan is to create a searchable index of IPFS based chance-data. We believe measuring uncertinty and sharing it in an auditable and additive way will be more important for permissionless networks. 60 | -------------------------------------------------------------------------------- /projects/codeworknft.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Codework NFT 3 | 4 | ## Category 5 | 6 | Application, NFT 7 | 8 | ## Project Description 9 | 10 | A dapp where users can make a post on what they need for their website and developers to find work. Developers can upload their codes which is stored on IPFS. Users can see a preview of the developers's codes on a web page. They can pay to see the code. 11 | 12 | ## Use of IPFS, Filecoin and Libp2p 13 | 14 | Codes and off-chain data are stored on IPFS 15 | 16 | ## Project Status 17 | 18 | Under Development 19 | 20 | ## Previews 21 | 22 | ![image](https://ethglobal.s3.amazonaws.com/recw2NNpXwkKGYxTK/cover.png) 23 | 24 | ## Target Audience 25 | 26 | - Anyone that need a website to be build 27 | - Developers looking for freelance 28 | 29 | ## Rough estimated user base (if applicable) 30 | 31 | None 32 | 33 | ## Github repo 34 | 35 | https://github.com/ysongh/Codework-NFT 36 | 37 | ## Website 38 | 39 | https://codeworknft.netlify.app/ 40 | 41 | 42 | https://showcase.ethglobal.co/web3weekend/codeworknft 43 | 44 | ## Docs 45 | 46 | 47 | ## Team Info 48 | 49 | You Song Hou - Full Stack Developer 50 | 51 | ### Team Size 52 | 1 53 | 54 | ### Team members 55 | You Song Hou 56 | 57 | ## How the community can engage 58 | * GitHub Discussion: https://github.com/ipfs/community/discussions/577 59 | * Email: yousonghou@gmail.com 60 | * Twitter: @ysongit 61 | 62 | ## How to Contribute 63 | 64 | Any advices, ideas, feedback, or supports -------------------------------------------------------------------------------- /projects/creatorr.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Creatorr 3 | 4 | ## Category 5 | NFT, Dapp, IPFS hosting, Social Media, Streaming 6 | 7 | ## Project Description 8 | The goal is for Creatorr to be a platform which helps create an incentivized content creation support system. Creatorr fans earn unique dynamic NFT tokens from their content creator in exchange for donations and support. The tokens are collectible, tradeable and/or sellable. 9 | 10 | ## Project Status 11 | MVP functionality being developed. Next Milestone is private alpha testing. 12 | 13 | ## Previews 14 | https://nameless-wave-72583.herokuapp.com/index.html 15 | 16 | ![homepage](https://i.ibb.co/GphMP9R/Capture.png) 17 | 18 | ![streamer](https://i.ibb.co/LSG51Jj/Capture2.png) 19 | 20 | ## Target Audience 21 | Content creators, NFT collectors and anyone that wants to support content creators. 22 | 23 | ## Rough estimated user base (if applicable) 24 | New to the space but Web2 analogies would be 25 | Patreon: 6 Million Patrons 2021 26 | Twitch : Peaks pre-covid 800k a day 27 | 28 | ## Github repo 29 | https://github.com/demo-hub/creatorr 30 | 31 | ## Website 32 | https://nameless-wave-72583.herokuapp.com/index.html 33 | 34 | ## Docs 35 | https://www.youtube.com/watch?v=6JNUpGN_XpM 36 | 37 | ## Team Info 38 | Introduce your amazing team - how many team members are working on this project and who are they? 39 | 40 | ### Team Size 41 | Now we have 6 team members.  42 | 43 | ### Team members 44 | 45 | João Rodrigues, Technical Leader 46 | - 3 years of web development experience 47 | 48 | Rosalie Avalon van Beek, Marketing manager 49 | - Content creator 50 | - Community manager 51 | - Dog lover 52 | 53 | Andrew Rangel, Full-stack dev 54 | - 9+ years native mobile development experience 55 | - 5 years of full stack web development experience 56 | - Product management and social media 57 | 58 | Thomas Ford, Back-end dev/Systems 59 | - Python, Solidity/Blockchain Dev 60 | - Systems Management 61 | - NFT maniac,Roboticist,Dog Lover, Degen 62 | 63 | Jurjen Folkertsma, Designer/Front-end dev 64 | - Passion for design 65 | - User experience is key 66 | - Front end dev 67 | 68 | Nuno Monteiro, Front-end dev 69 | - Ability to quickly change gears and adapt to changes 70 | - Creative thinking 71 | - Out of the box ideas 72 | 73 | ## How the community can engage 74 | Discussion: - https://github.com/ipfs/community/discussions/501 75 | Email: - info@creatorr.fan 76 | Twitter: - https://twitter.com/Creatorrfan 77 | Discord: https://discord.gg/NVv5kK6j2k 78 | Telegram: - https://t.me/creatorrfans 79 | Github : https://github.com/demo-hub/creatorr 80 | 81 | ## How to Contribute 82 | We are very early in the development phase yet so all feedback is appreciated. You can engage with us using the platforms mentioned above. We are prepping a private test phase sometime in the near future, so if you want to take part, join our discord or telegram group. 83 | -------------------------------------------------------------------------------- /projects/cryptoChampz.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | 3 | "Crypto Champz" 4 | 5 | ## Category 6 | 7 | NFT Gaming 8 | 9 | ## Project Description 10 | 11 | Crypto Champz is a Universal Character Generator that takes advantage of NFT composability to create robust characters that are playable in an endless variety of games. We use Chainlink VRF to randomly generate Champion characteristics such as Hometown, Background, Skills, Traits, Stats (Strength, Charisma, etc.) and more! Each Champion also has artwork that was custom designed for our project, and there are multiple variations of artwork available. Putting it all together, there are over 100 trillion different combinations, ensuring each Champion is special. 12 | 13 | Crypto Champz serve as NFT primitives that can be used to traverse the Metaverse of blockchain games. For example, your Champion might be used in a card game, a virtual board game, a farming simulator, or even your next D&D campaign! Of course, it can also be traded as a collectible. To jump start the ecosystem, we have created two mini games. One game lets you battle your Champz with other players. Chainlink oracles are used to retrieve weather conditions which can affect the outcome of the duel. Another game has a DeFi twist with Chainlink Price Feeds - players get rewarded for loyalty to high performing assets. 14 | 15 | ## Use of IPFS, Filecoin and Libp2p 16 | 17 | We use IPFS to store the images for our NFTs. 18 | 19 | ## Project Status 20 | 21 | Under development 22 | 23 | ## Previews 24 | 25 | ![Human A](https://i.imgur.com/vwOKoIg.png) 26 | 27 | ![Demon B](https://imgur.com/tAfgK5s.png) 28 | 29 | ## Target Audience 30 | 31 | NFT collectors and Blockchain game developers 32 | 33 | ## Rough estimated user base (if applicable) 34 | 35 | Not yet launched. 36 | 37 | ## Github repo 38 | 39 | https://github.com/cds95/crypto-champions 40 | 41 | ## Website 42 | 43 | https://cryptochampz.com 44 | 45 | ## Docs 46 | 47 | Coming soon 48 | 49 | ## Team Info 50 | 51 | ### Team Size 52 | 53 | 5 54 | 55 | ### Team members 56 | 57 | CultureVictory - Product Mgmt - https://github.com/rohhan 58 | CDS95 - Full stack Web3 dev - https://github.com/cds95 59 | Oozyx - Blockchain dev - https://github.com/Oozyx 60 | C4RE B34R - Art - No GitHub Account 61 | Architect - Art - No GitHub Account 62 | 63 | ## How the community can engage 64 | 65 | - GitHub Discussion: https://github.com/ipfs/community/discussions/512 66 | - Email: Coming soon 67 | - Slack: N/A 68 | - Twitter: twitter.com/cryptochampz 69 | - Discord: Coming soon 70 | - Telegram: Coming soon 71 | - WeChat: N/A 72 | 73 | ## How to Contribute 74 | 75 | Please feel free to reach out on Twitter to start a discussion about contributing :) 76 | -------------------------------------------------------------------------------- /projects/defluencertoolkit.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Decentralized Influencer Toolkit 3 | 4 | ## Category 5 | 6 | Toolling, Social Media 7 | 8 | ## Project Description 9 | 10 | Tools for online communities to communicate in a decentralized way. 11 | 12 | ## Use of IPFS, Filecoin and Libp2p 13 | 14 | IPFS is used for content hosting and sharing, IPLD to link it all up and GossipSub to broadcast. 15 | 16 | ## Project Status 17 | 18 | Protocols and Prototypes have been built for; 19 | 20 | - Adaptative-bitrate live streaming. 21 | - Live chat. 22 | - Chat moderation tools. 23 | - Video hosting. 24 | 25 | I am currently designing a forum/twitter thingy. 26 | 27 | ## Github repo 28 | 29 | github.com/sionois/dit 30 | 31 | ## Team Info 32 | 33 | Just me Simon, hello! 👋 34 | 35 | ## How the community can engage 36 | * Discussion: https://github.com/ipfs/community/discussions/580 37 | * Discord: SionoiS#5373 38 | * Project Github: https://github.com/SionoiS/dit/discussions 39 | 40 | ## How to Contribute 41 | 42 | There's many way to help for one you can find bugs but also help creating libraries in many language or refine the protocols. 43 | 44 | I also wish to create a website for the project using the tech. 45 | -------------------------------------------------------------------------------- /projects/git3.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Git3 3 | 4 | ## Category 5 | Application 6 | 7 | ## Project Description 8 | The idea is to create a decentralized GitHub on Blockchain and IPFS/Filecoin. A Smart Contract represents the git 9 | repository and stores all important information. The files of the repository on the other hand are currently pushed 10 | to IPFS. 11 | You might ask yourself: Why Github on Blockchain? 12 | Here are a few arguments why I believe that having such a system on Blockchain makes sense: 13 | - Many open sources developers have a donate button. You are able to send a donation through a third party app to them. 14 | I would like to eliminate the need for a third party app. Every repository has a donation button integrated - from the beginning 15 | - Open issues and attach a bounty. Are you using an open source package and have a bug/idea/issue with it? Open an issue 16 | and leave a bounty for a developer. This incentives developers to resolve issues faster and earn some money, maybe allowing 17 | them to spend more time to develop their code. Another example is given here: [IPFS Devgrants](https://github.com/ipfs/devgrants/blob/master/README.md) 18 | Read the Bounty section ;) 19 | 20 | ## Use of IPFS, Filecoin and Libp2p 21 | Git3 uses currently IPFS to store the files of a repository. The future idea is to use CID for all internals of git, 22 | making use of IPFS's benefits, like deduplication. 23 | 24 | ## Project Status 25 | I started with it during an EthGlobal hackathon. Since then I rewrote most parts of the code, published a git3 Python client, 26 | and deployed the Smart Contracts to a testnet (Polygon Mumbai). The idea is to get it into a MVP stage within the next 3 months, 27 | so users can start to use it. 28 | 29 | ## Previews 30 | [![Screenshot-from-2021-10-20-13-51-12.png](https://i.postimg.cc/tT4BbsmW/Screenshot-from-2021-10-20-13-51-12.png)](https://postimg.cc/Z9X8F5m5) 31 | 32 | ## Target Audience 33 | In the beginning, I would like to get some projects from web3 into Git3 so that there is a way to support those guys 34 | work easily. But we are open to have everyone who wants to use the platform to use it. 35 | 36 | ## Rough estimated user base (if applicable) 37 | None, since it is not up and running. 38 | 39 | ## Github repo 40 | 1. https://github.com/varkiwi/git3-frontend 41 | 2. https://github.com/varkiwi/git3-client 42 | 3. https://github.com/varkiwi/git3-contracts 43 | 44 | 45 | ## Website 46 | Currently no website up and running. 47 | 48 | 49 | ## Docs 50 | Currently no dedicated docs site. The README's contain all the information. 51 | 52 | ## Team Info 53 | Currently there is only one team member: Jacek Varky 54 | 55 | ### Team Size 56 | Team size is currently: 1 57 | 58 | ### Team members 59 | Jacek Varky 60 | 61 | ## How the community can engage 62 | * GitHub Discussion: https://github.com/ipfs/community/discussions/676 63 | * Email: jaca347@gmail.com 64 | * Twitter: @Git314 65 | 66 | 67 | ## How to Contribute 68 | Check out the repository page and the issues. There is a lot to do. Feel free to test and report bugs or even contribute. 69 | -------------------------------------------------------------------------------- /projects/immutable.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Immutable 3 | 4 | ## Category 5 | Application 6 | 7 | ## Project Description 8 | Immutable is a web and desktop application that leverages the immutablity of blockchain and Inter Planetry File System to store critical evidences and documents pertaining to a lawsuit. 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | We have used IPFS along with JavaScript in building the application. The evidences and documents uploaded by the lawyers are saved in the IPFS storage and the private keys are used to fetch the authenticity of the documents. We will also be using both FileCoin and Libp2p in some parts of our project during the Next Step Grant programme. 12 | 13 | ## Project Status 14 | Under development 15 | 16 | ## Previews 17 | ![Logging In](https://cdn.discordapp.com/attachments/814552534416621591/837603512292605972/pic75ekhiq9v.png) 18 | ![Adding a case](https://cdn.discordapp.com/attachments/814552534416621591/837603517123264512/pic1ygfbgogo.png) 19 | ![Uploading evidences](https://media.discordapp.net/attachments/814552534416621591/837604525601980436/Screenshot_236.png) 20 | ![File uploaded in IPFS](https://cdn.discordapp.com/attachments/814552534416621591/837603602532139029/Screenshot_231.png) 21 | 22 | ## Target Audience 23 | Lawyers, police officials, government officials and judges. 24 | 25 | ## Rough estimated user base (if applicable) 26 | 5 (since we have a very focussed user base, we tried to beta test with a minimum number of users). 27 | 28 | ## Github repo 29 | https://github.com/Adithya-adi-Menon/immutable 30 | 31 | ## Website 32 | The website is set to be hosted in the next 30 days 33 | 34 | ## Docs 35 | https://devpost.com/software/immutable-ipfs-for-storing-authentic-evidences 36 | 37 | ## Team Info 38 | 39 | ### Team Size 40 | 5 41 | 42 | ### Team members 43 | Adithya Menon S 44 | - Full stack web developer. 45 | - Proficient with JS, PHP and Java. 46 | - https://github.com/Adithya-adi-Menon/ 47 | 48 | Kumaraguru T 49 | - Web and Flutter developer. 50 | - Proficient with Python, Dart and thrust areas. 51 | - https://github.com/hackyguru 52 | 53 | Vasanth T 54 | - Front end developer. 55 | - Good with problem solving and competitive programming. 56 | - https://github.com/vasanthsteve23 57 | 58 | Mridula 59 | - Front end developer 60 | - Proficient with web technologies and Dart. 61 | - https://github.com/Mridula90 62 | 63 | Emma Thomas 64 | - UI/UX designer 65 | - Proficient with Figma, Material design and Creative suite. 66 | - https://github.com/Emma-Thomas-jj 67 | 68 | ## How the community can engage 69 | * GitHub Discussion: https://github.com/ipfs/community/discussions/535 70 | * Email: 18eucs002@skcet.ac.in 71 | * Slack: 72 | * Twitter: 73 | * Discord: 74 | * Telegram: 75 | * WeChat: 76 | 77 | ## How to Contribute 78 | All of us at Immutable are beginners with blockchain. But, we have prior experience with developing amazing full stack applications. We welcome contributions to our project on our GitHub repo. Please feel free to send a message on our discussion thread if you wish to contribute. Steps to contribute to our project can be found in the README in our project repository. 79 | -------------------------------------------------------------------------------- /projects/ipfs-chat.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | 3 | ipfs-chat 4 | 5 | ## Category 6 | 7 | 8 | 9 | Application 10 | 11 | ## Project Description 12 | 13 | 14 | Real time, end-to-end encrypted, p2p messenger using go-IPFS-Pubsub. Allows private messaging & secure in-chat file/directory sharing. Server/broker-less (viz. no signaling/rendezvous server needed). Works over both LAN and internet (uses built-in NAT-traversal, if needed). 15 | 16 | ## Use of IPFS, Filecoin and Libp2p 17 | 18 | 19 | Nodes discover peers primarily by querying the DHT for providers of a time-based rendezvous file. Every node also resolves the same libp2p-keys over IPNS-Pubsub to prime the swarm. Uses IPFS-Pubsub both for the chatroom and further peer discovery. Uses IPNS over Pubsub for peer authentication. 20 | 21 | ## Project Status 22 | 23 | 24 | Beta. 25 | 26 | ## Previews 27 | 28 | 29 | ![ipfs-chat-screen](https://github.com/SomajitDey/ipfs-chat/raw/main/screenshot.png) 30 | 31 | ## Target Audience 32 | 33 | 34 | Anyone who needs a demonstrably secure and anonymous p2p-chat and file-sharing app. IRC lovers might find this highly relatable. It's also easy to install for those who care about it. 35 | 36 | ## Rough estimated user base (if applicable) 37 | 38 | 39 | There's no way to track the total number of current users. All that we know are the following stats. 40 | 41 | As of Thu Nov 11 07:55:30 UTC 2021: 42 | 43 | - [GitHub stars](https://github.com/SomajitDey/ipfs-chat/stargazers): 35 44 | - [GitHub forks](https://github.com/SomajitDey/ipfs-chat/network/members): 3 45 | - Github clones (as obtained from GitHub Insights > Traffic) : 1197 46 | - Upvotes received in [reddit](https://www.reddit.com/r/ipfs/comments/p6u8u1/terminalbased_secure_chatrooms_using_goipfs_cli/?utm_source=share&utm_medium=web2x&context=3): 43 47 | - Views in [discuss.ipfs.io](https://discuss.ipfs.io/t/terminal-based-chat-app-using-go-ipfs-pubsub-no-rendezvous-server-needed/11888): 161 (and a ❤) 48 | 49 | ## Github repo 50 | 51 | 52 | https://github.com/SomajitDey/ipfs-chat 53 | 54 | ## Website 55 | 56 | 57 | 58 | 59 | ## Docs 60 | 61 | 62 | https://github.com/SomajitDey/ipfs-chat/blob/main/README.md 63 | 64 | ## Team Info 65 | 66 | 67 | ### Team Size 68 | 69 | 1 70 | 71 | ### Team members 72 | 73 | [Somajit Dey](https://github.com/SomajitDey) 74 | 75 | ## How the community can engage 76 | * GitHub Discussion: 77 | 1. https://github.com/ipfs/community/discussions/687 78 | 2. https://github.com/SomajitDey/ipfs-chat/discussions 79 | * Email: 80 | * Slack: 81 | * Twitter: 82 | * Discord: 83 | * Telegram: 84 | * WeChat: 85 | 86 | ## How to Contribute 87 | 88 | 89 | https://github.com/SomajitDey/ipfs-chat#contribute 90 | -------------------------------------------------------------------------------- /projects/ipfs-cidsail.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | ipfs-cidsail 3 | 4 | ## Category 5 | 6 | Application 7 | 8 | ## Project Description 9 | 10 | This project is about a tool that helps you find/check/keep track of files published on IPFS. Something that compares filesystems to either local IPFS datastore and/or network availability. If you got a file and want to see if is has been published on IPFS 11 | 12 | ## Use of IPFS, Filecoin and Libp2p 13 | 14 | This project uses the IPFS javascript libraries. This are the libraries used: { "dependencies": { "file-type": "^16.4.0", "ipfs-http-client": "^49.0.4", "ipfs-only-hash": "^4.0.0", "meow": "^9.0.0" } } - file-type: Detect the file type 15 | 16 | ipfs-http-client : An interface (client) to ipfs daemon 17 | ipfs-only-hash: A small utility to get a hash of a file without add it to IPFS 18 | meow: cli utility 19 | It is written in javascript (nodejs). It's a command line utility. 20 | 21 | ## Project Status 22 | 23 | under development 24 | 25 | ## Previews 26 | 27 | ![cidcli help](https://github.com/acul71/ipfs-cidsail/blob/master/img/cidcli_01_help.png) 28 | ![cidcli tmp files tree](https://github.com/acul71/ipfs-cidsail/blob/master/img/cidcli_02_tree.png) 29 | ![cidcli run on tmp 1/2](https://github.com/acul71/ipfs-cidsail/blob/master/img/cidcli_03_tmp.png) 30 | ![cidcli run on tmp 2/2](https://github.com/acul71/ipfs-cidsail/blob/master/img/cidcli_04_tmp.png) 31 | ![cidcli run on aardvark.png file](https://github.com/acul71/ipfs-cidsail/blob/master/img/cidcli_05_aardvark.png) 32 | 33 | ## Target Audience 34 | 35 | ipfs developers, ipfs users 36 | 37 | ## Rough estimated user base (if applicable) 38 | 39 | 40 | ## Github repo 41 | 42 | https://github.com/acul71/ipfs-cidsail 43 | 44 | ## Website 45 | 46 | 47 | 48 | https://showcase.ethglobal.co/scaling/ipfs-cidsail 49 | 50 | ## Docs 51 | 52 | https://github.com/acul71/ipfs-cidsail 53 | 54 | ## Team Info 55 | 56 | Luca Pisani https://www.birdo.net/lucapisanicv/cv.html 57 | 58 | ### Team Size 59 | 1 60 | ### Team members 61 | 1 62 | 63 | ## How the community can engage 64 | * GitHub Discussion: https://github.com/ipfs/community/discussions/601 65 | * Email: luca.pisani@birdo.net 66 | * Slack: 67 | * Twitter: 68 | * Discord: lucap#5517 69 | * Telegram: 70 | * WeChat: 71 | 72 | ## How to Contribute 73 | 74 | Go to https://github.com/acul71/ipfs-cidsail and follow instruction to install. Check the app and report any bugs/anomalies opening an issue 75 | -------------------------------------------------------------------------------- /projects/luxurify.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | 3 | Luxurify 4 | 5 | ## Category 6 | 7 | Application 8 | 9 | ## Project Description 10 | 11 | The Luxurify ecosystem is a platform featuring luxury watch registration, verification, marketplace and an escrow service. The provenance of your watch is inscribed in blockchain. 12 | 13 | ### Build for Brand 14 | - Register your brand with certificates 15 | - Claim watches and start selling. 16 | - Protection against fakes. 17 | - Promotion of the official service network. 18 | - Transparent ownership transfers. 19 | - Dynamic pricing via WatchSignals. 20 | 21 | ### Build for Owner 22 | - Protection against fakes and stolen property. 23 | - Transparent ownership transfers. 24 | - Growth in resale value. 25 | - Ethernal provenance record. 26 | - Dynamic pricing via WatchSignals. 27 | - Convenient marketplace. 28 | 29 | ### Build for Collector 30 | - Convenient marketplace. 31 | - Fast, Secure, Trusted place to buy Authentic Luxury Watches. 32 | 33 | 34 | ## Project Status 35 | 36 | Under Development 37 | 38 | ## Previews 39 | 40 | Screenshots: https://drive.google.com/drive/folders/1BPX_MQOQQNyKONO0fTu6w8Y44Uw3nFeB?usp=sharing 41 | Video: https://youtu.be/SMfm2SZ-3rY 42 | 43 | ## Target Audience 44 | 45 | Watch's brands, owners and collectors 46 | 47 | ## Rough estimated user base (if applicable) 48 | 49 | N/A 50 | 51 | ## Github repo 52 | 53 | https://github.com/nnluukhtn/luxurify 54 | 55 | ## Website 56 | 57 | https://luxurify.netlify.app/ 58 | 59 | ## Docs 60 | 61 | TBA 62 | 63 | ## Team Info 64 | 65 | The Luxurify team was assembled as part of the Chainlink hackathon there are currently 3 memebers 66 | 67 | ### Team Size 68 | 3 members 69 | 70 | ### Team members 71 | [Luu Nguyen](https://github.com/nnluukhtn) 72 | [Hai Chung](https://github.com/haichungcn) 73 | [Tuan Nguyen](https://github.com/garfdev) 74 | 75 | ## How the community can engage 76 | GitHub Discussion: https://github.com/ipfs/community/discussions/491 77 | Email: luxurifyhq@gmail.com 78 | Slack: N/A 79 | Twitter: N/A 80 | Discord: N/A 81 | Telegram: N/A 82 | WeChat: N/A 83 | 84 | ## How to Contribute 85 | 86 | Please reachout to email luxurifyhq@gmail.com 87 | -------------------------------------------------------------------------------- /projects/mbondX.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 |
    3 | mbondX 4 | 5 | ## Category 6 | Application 7 | 8 | ## Project Description 9 | This project provide the platform where user can buy and sell bonds. we use onchain orderbook to execute the trade like OasisDex . it implements a sorted order book by providing additional sorting structure. 10 | price of particular offer is stored in the list, these prices are ranked according to price offered. 11 | when buyer buy the bond at certain price, if this price is matched with list then trade get executed . 12 | 13 | After buying of bond user is directed toward indenture page, here user is required to submit their signature to download indenture document which provide the details like coupon rate, principal amount , maturity etc. 14 | 15 | 16 | 17 | ## Use of IPFS, Filecoin and Libp2p 18 | we used ipfs-htttp-client packag to store the indenture document which provide the details like coupon rate, principal amount , maturity etc. 19 | 20 | ## Project Status 21 | Its at development stage, i have to integrate superfliud technology to distribute interest rate . I have to improve Ux of whole project 22 | 23 | ## Previews 24 | 25 |
    26 | 27 |
    28 | 29 | 30 | 31 | 32 | ## Target Audience 33 | Anyone who wanted to buy and sell bonds 34 | 35 | ## Rough estimated user base (if applicable) 36 | N/A 37 | 38 | ## Github repo 39 | https://github.com/MukeshJaiswal01/mBondX 40 | 41 | ## Website 42 | 43 | 44 | video : https://youtu.be/Bb5RcJGGl4o 45 | submission: https://showcase.ethglobal.co/scaling/mbondx 46 | 47 | ## Docs 48 | https://github.com/MukeshJaiswal01/mBondX#readme 49 | 50 | ## Team Info 51 | Currently i am hacking solo 52 | 53 | ### Team Size 54 | 1 55 | 56 | ### Team members 57 | Mukesh Jaiswal 58 | 59 | ## How the community can engage 60 | * GitHub Discussion: https://github.com/ipfs/community/discussions/552 61 | * Email: jaiswalsamar443@gmail.com 62 | 63 | * Twitter: @MukeshJ_eth 64 | 65 | 66 | ## How to Contribute 67 | we love to get feedback from protocol team. for any query reach to : jaiswalsamar443@gmail.com 68 | -------------------------------------------------------------------------------- /projects/meetwithwallet.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Meet with Wallet 3 | 4 | ## Category 5 | Application 6 | 7 | ## Project Description 8 | Meet with Wallet provides an easy way to share your (or your DAO's) calendar and schedule meetings without any hassle or back-and-forth communication. All possible by simply connecting your crypto wallet. No registration needed, no more emails (only if you want to) - Information about your meetings is encrypted and kept private (only you have access), and only meeting time slots are public for an improved user experience. You know Calendly right? Same thing here, but for #web3! 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | We use IPFS to store not only public information about wallet's calendars, but as well as private information about each meeting. The information is first encrpted with the user's wallet, and then upload to IPFS. Of course, it can only be decrypted by the same user (wallet). 12 | 13 | ## Project Status 14 | MVP shipped, improving with new features and subscription plans for individuals, and strating the structure for DAOs/Communities. 15 | 16 | ## Previews 17 | ![image](https://ipfs.io/ipfs/QmdtzGM6xBf6EyQvNDbtZ3YhLLFk3TjZLr4QRxkY1SoqHa) 18 | ![image](https://ipfs.io/ipfs/QmYMsU7yMBAqLEpt33ksauDstUE2y7U8oz3yowviYaDugK) 19 | 20 | 21 | ## Target Audience 22 | Individuals that needs to. organize their day to day meetings, especially in a remote world, as well as communities that wants to provide easy to schedule solutions for their members. 23 | 24 | ## Rough estimated user base (if applicable) 25 | We just started a month ago and have around 300 users. 26 | 27 | ## Github repo 28 | https://github.com/appcalipse/meet-with-wallet-contracts 29 | 30 | ## Website 31 | https://meetwithwallet.xyz 32 | 33 | ## Docs 34 | Not applicable 35 | 36 | ## Team Info 37 | A full hand of individuals trying to bring incredible UX to web3 38 | 39 | ### Team Size 40 | 5 41 | 42 | ### Team members 43 | 9Tails.eth - Creator / Product 44 | 15+ years of product management and tech development. Created 3 startups and worked in several industries, delivering digital products to millions of active users. 45 | 46 | Israel "Falleco" Crisanto - Head of Technology 47 | 13+ years of full stack experience, being responsible for large crictical corporate systems, including payment processing for the Brazilian financial system. In the last 3 years has been focusing in generating value by building high performance teams that can work side by side with product and business. 48 | 49 | EricP3reira - Senior Frontend Developer 50 | 5+ years of software development, focusing on providing incredible user experience for clients. Got into tech by developing a full management system for a business he used to work as a stock manager. Started playing around with web3 5 months ago. 51 | 52 | Sávio Azambuja - Frontend developer 53 | 3 years of software development focusing in frontend applications for multiple segments. Jumped into web3 because of the the metaverso and have been lurking the space for 6 months. 54 | 55 | Antariksh Verma - Solidity Developer 56 | High school student going deeper and deeper into tech development. Recently won 5 hackathons and recently got drained down the we've rabbit hole. 57 | 58 | ## How the community can engage 59 | * Email: it_people@meetwithwallet.xyz 60 | * Twitter: https://twitter.com/meetwithwallet 61 | * Discord: https://discord.gg/an2q4xUkcR 62 | 63 | ## How to Contribute 64 | Come to our Discord and lets talk 65 | -------------------------------------------------------------------------------- /projects/nftbase.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | NFTBase 3 | 4 | ## Category 5 | NFT, Dapp, marketplace, IPFS application, metadata, ENS domain, IPFS hosting 6 | 7 | ## Project Description 8 | NFTbase is the DAO based the metaverse marketplace and community for NFTs. We will make the world where human creativity is fully respected. 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | 1) Wer are going to host our website on IPFS with ENS domain. It means that if you search "www.nftbase.eth" or "www.nftbase.eth.link" on your web browser, you can access to NFTBase which is uploaded on IPFS. We wanna be the first generation Dapp live on IPFS.  12 | 13 | 2) As we are a marketplace for NFT, it's required for us to enable users to create new NFT items. NFT contains digital artworks - JPG,PNG,MP4 etc,. As we believe decentralization without thrid party service is important, we will upload the metadata of NFT on IPFS. It means we have to use IPFS for storage of data. 14 | 15 | ## Project Status 16 | Under development (80%) 17 | 18 | ## Previews 19 | https://nftbase.ai  20 | 21 | ## Target Audience 22 | NFT artists, NFT collectors, NFT investors, Governance token investors, NFT curators etc 23 | 24 | ## Rough estimated user base (if applicable) 25 | It's not launched yet, but hope that user pool will grow up fastly 26 | 27 | ## Github repo 28 | https://github.com/team-nftbase 29 | 30 | ## Website 31 | https://nftbase.ai 32 | 33 | ## Docs 34 | https://drive.google.com/file/d/1misyizpRhYQfeMkxXdWK0WUwwH6Mw5xW/view, http://techtree.kr:8090/download/attachments/31916391/NFTbase%20Business%20Introduction.pdf?version=1&modificationDate=1617047806720&api=v2 35 | 36 | ## Team Info 37 | Introduce your amazing team - how many team members are working on this project and who are they? 38 | 39 | ### Team Size 40 | Now we have 5 team members.  41 | 42 | ### Team members 43 | John wick, Business developer 44 | - Blockchain entrepreneur / Project manager / Strategies 45 | - Worked in the global crypto-exchange ('18~'20) 46 | - Blockchain Project ('20~'21)  47 | - Its coin is listed up on several exchanges 48 | - It's ranked in 500th cryptocurrency 49 | - Pre-MBA 50 | 51 | KUK, Full stack developer 52 | - Current CEO of a development company 53 | - 15 years of development career 54 | - Won a blockchain hackthon and run a pool for a mainnet blockchain 55 | - Have worked with SAMSUNG / LG / KOREA ARMY / SEOUL GOVERMENT 56 | - C, C#, C++, JAVA, Python, Lua, Ruby, Solidity 57 | - KAIST graduate software course 58 | 59 | DONGIN 60 | - Full-stack developer 61 | 62 | JAEJIN 63 | - Full-stack developer 64 | 65 | JUWON 66 | - blockchain developer. 4 years of development career. 67 | 68 | 69 | ## How the community can engage 70 | GitHub Discussion: N/A 71 | Email: admin@nftbase.ai 72 | Slack: N/A 73 | Twitter: https://twitter.com/BaseNft 74 | Discord: https://discord.gg/DujYFjJXXP 75 | Telegram: https://t.me/nftbase 76 | Medium : https://nftbase.medium.com/  77 | WeChat: N/A 78 | Github : https://github.com/team-nftbase 79 | 80 | ## How to Contribute 81 | 82 | Through this grant and our effort for this grant, we'd like to contribute for IPFS by 83 | 84 | 1) Making active real use cases of Dapp service on IPFS  85 | 2) Contributing IPFS by improving some detailed obstacles that developers face 86 |    (For example, we need to re-assign a new path for uploaded website resources when we try to upload a website on IPFS. We will resolve this problem by developing tools) 87 | 3) Using IPFS to upload metadata of NFT items. → 88 | 89 | If you have any ideas or suggestions, please check this and comment  90 | 91 | https://github.com/ipfs/community/discussions/506 -------------------------------------------------------------------------------- /projects/nftwitch.md: -------------------------------------------------------------------------------- 1 | ## NFTwitch 2 | 3 | ## Category 4 | Application 5 | 6 | ## Project Description 7 | NFTwitch allows Twitch streamers to mint NFTs as they grow their follower count, verified via Chainlink calls to the Twitch API. These exclusive collectibles can be given away or sold to fans. The streamer benefits from the immediate source of income, and the fan benefits from exclusive perks to NFTwitch holders. Upon transfer of the NFTwitch, the perks are also transferred to the new owner. This creates an ecosystem that helps low-income streamers stay afloat, and rewards fans both immediately and in the long-term as the streamer grows in popularity. 8 | 9 | ## Project Status 10 | Beta is live on Rinkeby testnet 11 | 12 | ## Previews 13 | ![Screenshot](https://raw.githubusercontent.com/AntonStrickland/AntonStrickland/master/static/images/projects/nftwitch.jpg) 14 | 15 | ## Target Audience 16 | Twitch Streamers and their fans. Streamers will use the dapp to generate NFTs to be given away or sold to fans. 17 | 18 | ## Rough estimated user base (if applicable) 19 | Potentially as large as Twitch's user base, but right now it's just me. 20 | 21 | ## Github repo 22 | https://github.com/AntonStrickland/nftwitch 23 | 24 | ## Website 25 | https://nftwitch.link 26 | 27 | ## Docs 28 | https://github.com/AntonStrickland/nftwitch#readme 29 | 30 | ## Team Info 31 | 32 | ### Team Size 33 | 1 34 | 35 | ### Team members 36 | Anton Strickland (Kinjo) - Game developer with an interest in blockchain. Streams programming and game development on Twitch. 37 | 38 | ## How the community can engage 39 | GitHub Discussion: https://github.com/ipfs/community/discussions/480 40 | Email: admin@nftwitch.link 41 | Slack: N/A 42 | Twitter: N/A 43 | Discord: https://discord.gg/Zx9gpyhMMr 44 | Telegram: N/A 45 | WeChat: N/A 46 | 47 | ## How to Contribute 48 | Reach out to your favorite Twitch streamer and let them know about this dapp! We also need more Chainlink nodes using the Twitch external adapter to help decentralize the network. On the programming side, we need to check the smart contracts for any issues, improve the UI and UX on the front-end, and integrate Layer 2 solutions to reduce gas fees. And suggestions for new features, especially involving IPFS, are always welcome! 49 | -------------------------------------------------------------------------------- /projects/niftyroyale.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Nifty Royale 3 | 4 | ## Category 5 | NFT 6 | 7 | ## Project Description 8 | Nifty Royale is a platform that aims to be a NFT marketplace with a gamification element. A battle royale game is executed on-chain to determine a winner who will receive a one-of-a-kind NFT as the prize. 9 | 10 | 11 | 12 | ## Project Status 13 | Under Development 14 | 15 | ## Previews 16 | https://www.youtube.com/watch?v=9AdxVI3Q4CI 17 | ![Nifty Royale Status Page](https://imgur.com/a/snEEH76) 18 | 19 | ## Target Audience 20 | NFT artists, NFT collectors, NFT investors, NFT curators 21 | 22 | 23 | ## Rough estimated user base (if applicable) 24 | N/A 25 | 26 | ## Github repo 27 | https://github.com/aa-wong/nifty-royale 28 | 29 | ## Website 30 | niftyroyale.com 31 | 32 | ## Docs 33 | TBD 34 | 35 | ## Team Info 36 | The Nifty Royale team was assembled as part of the Chainlink hackathon there are currently 4 memebers residing in 3 different countries. 37 | 38 | ### Team Size 39 | 4 Members 40 | ### Team members 41 | Tim Nan 42 | Karen Sheng 43 | Aaron Wong-Ellis 44 | Sam Teboul 45 | ## How the community can engage 46 | GitHub Discussion: https://github.com/ipfs/community/discussions/488 47 | Email: info@niftyroyale.com 48 | Slack: N/A 49 | Twitter: @niftyroyale 50 | Discord: https://discord.gg/GFRjkxevGp 51 | Telegram: N/A 52 | WeChat: N/A 53 | 54 | ## How to Contribute 55 | Reach out to our email or join or discord. We will be launching the beta soon on our website! -------------------------------------------------------------------------------- /projects/pdarm.md: -------------------------------------------------------------------------------- 1 | 2 | ## Project Name 3 | 4 | Parametric Digital Asset Risk Management 5 | 6 | ## Category 7 | 8 | DeFi risk management, dApp, IPFS 9 | 10 | ## Project Description 11 | 12 | A dApp which provides parametric stablecoin lending protection on Aave (other DeFi platforms TBD), using IPFS+Chainlink+TUSD+Aave. 13 | 14 | For additional information about our project please see our [Devpost project page](https://devpost.com/software/parametric-digital-asset-risk-management) where we discuss the following: 15 | 16 | - About the project 17 | - Inspiration 18 | - The Problem 19 | - What it does 20 | - How we built it 21 | - Challenges we ran into 22 | - Accomplishments that we're proud of 23 | - What we learned 24 | - What's next for Parametric Digital Asset Risk Management 25 | - How we integrated with sponsors 26 | 27 | ## Use of IPFS, Filecoin and Libp2p 28 | 29 | We used IPFS to deploy and host our project’s application, website, store and display images on the website, and to display smart contract analytical data on user dashboards. 30 | 31 | ## Project Status 32 | 33 | Under development 34 | 35 | ## Previews 36 | 37 | - [5 Minute Pitch and Demo video](https://www.youtube.com/watch?v=nHXhbZFmX6M) 38 | - [Please check out our 7 minute slowed down and extended demo video!](https://youtu.be/tqz92QOn9kw) 39 | - [IPFS Live Demo](https://ipfs.io/ipfs/QmdY4Fq33R4tnnMDR4spSPeT7ony4ZSd7Gs7Rp9rAEwDQ5/) 40 | 41 | Screen Shot 2021-04-23 at 9 38 28 PM 42 | 2021-04-16_00-26-54 43 | Screen Shot 2021-04-23 at 9 38 18 PM 44 | 45 | 46 | 47 | ## Target Audience 48 | 49 | The current audience is Non-DeFi users who seek to interact with DeFi lending protocols in a manner that has circuit breakers and guard rails, and DeFi natives who seek risk-adjusted yields. 50 | 51 | ## Rough estimated user base (if applicable) 52 | 53 | [1, inf) users 54 | 55 | ## Github repo 56 | 57 | https://github.com/chainlink-hackathon2021-insurance/DeFi-Lending-Insurance 58 | 59 | ## Website 60 | 61 | IPFS 62 | https://ipfs.io/ipfs/QmdY4Fq33R4tnnMDR4spSPeT7ony4ZSd7Gs7Rp9rAEwDQ5/ 63 | 64 | 65 | ## Docs 66 | 67 | Devpost Submission: https://devpost.com/software/parametric-digital-asset-risk-management 68 | 69 | ## Team Info 70 | 71 | We are a team of four blockchain enthusiasts and builders seeking to expand on an ambitious concept using IPFS as one of our core pillars. 72 | 73 | ### Team Size 74 | 75 | 4 76 | 77 | ### Team members 78 | 79 | - Seth Andrus: System Architecture 80 | - Luis Ramírez: Smart Contract & Frontend Development 81 | - Mike Robinson: Product Manager & Market Researcher 82 | - Lukas Sexton: UI/UX design and research 83 | 84 | ## How the community can engage 85 | * GitHub discussion: https://github.com/ipfs/community/discussions/513 86 | * Email: Parametric.Link@protonmail.com 87 | 88 | ## How to Contribute 89 | 90 | We welcome any new ideas from you in the form of pull requests to our repo. You can also reach out to any of us through our Devpost submission or on our GitHub discussion board. 91 | -------------------------------------------------------------------------------- /projects/plebbit.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | plebbit 3 | 4 | ## Category 5 | Social media 6 | 7 | ## Project Description 8 | Serverless, adminless, decentralized reddit alternative with no transaction fees and captchas over peer-to-peer pubsub to prevent spam. 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | - IPFS for immutable data, like a published comment or a recent subplebbit page. 12 | - IPNS for mutable data, like replies to a comment, upvote counts, new posts/comments published on a subplebbit, etc. 13 | - Pubsub for authors publishing comments/votes to a subplebbit and for the captcha challenge exchange between authors and subplebbits. 14 | 15 | ## Project Status 16 | Under development 17 | 18 | ## Previews 19 | 20 | 21 | ## Target Audience 22 | The world 23 | 24 | ## Rough estimated user base (if applicable) 25 | 0 26 | 27 | ## Github repo 28 | - https://github.com/plebbit/whitepaper/discussions/2 29 | - https://github.com/plebbit/plebbit-js 30 | 31 | ## Website 32 | 33 | ## Docs 34 | - https://github.com/plebbit/whitepaper/discussions/2 35 | - https://github.com/plebbit/plebbit-js/blob/master/README.md 36 | 37 | ## Team Info 38 | - Esteban Abaroa https://twitter.com/estebanabaroa estebanabaroa@protonmail.com 39 | - Rinse https://twitter.com/Rinse_12 40 | - Abideen Sadiq Ayinde https://twitter.com/Abideen_AS 41 | 42 | ### Team Size 43 | 3 44 | 45 | ### Team members 46 | 47 | ## How the community can engage 48 | * GitHub Discussion: https://github.com/ipfs/community/discussions/746 49 | * Email: estebanabaroa@protonmail.com 50 | * Slack: 51 | * Twitter: https://twitter.com/getplebbit 52 | * Discord: https://discord.gg/E7ejphwzGW 53 | * Telegram: https://t.me/plebbit 54 | * WeChat: 55 | 56 | ## How to Contribute 57 | We are hiring JS devs, contact Esteban Abaroa on Telegram @estebanabaroa or Discord estebanabaroa#2853 58 | -------------------------------------------------------------------------------- /projects/py-is_ipfs.MD: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | py-is_ipfs 3 | 4 | ## Category 5 | 6 | developer tooling, IPFS, Python library 7 | 8 | ## Project Description 9 | 10 | My first encounter with IPFS was through NFT's and looking into how projects host (im)mutable metadata and images. I soon realised a lot of projects used centralised methods instead of decentralised alternatives like IPFS. While contributing to [HonestNFT Shenanigan Scanning Tools](https://github.com/Convex-Labs/honestnft-shenanigans) I needed a way to label NFT's as centralised or not. What started out with a simple heuristic as `link contains ipfs` turned into `link includes a valid CID`. 11 | 12 | But I now realise we need better heuristics that can detect all possible IPFS links, hashes, domains, ... Ideally a "one way" method to say, *"Yes, this link is valid and points to a decentralised storage method"*. 13 | 14 | I researched existing libraries and scripts, but found no comprehensive method in Python. There are some (limited) alternatives in other languages, but a Python implementation would be a good addition to the community tools. 15 | 16 | ## Use of IPFS, Filecoin and Libp2p 17 | 18 | I envision leveraging existing related projects and published specs to build upon in this new Python library. 19 | 20 | ## Project Status 21 | 22 | Brainstorming/ideation phase and some rough unpublished scripts for testing methods. 23 | ## Previews 24 | 25 | ```python 26 | import is_ipfs 27 | 28 | is_ipfs.is_CID("QmY7Yh4UquoXHLPFo2XbhXkhBvFoPwmQUSa92pxnxjQuPU") # True 29 | is_ipfs.is_CID("bafybeierhgbz4zp2x2u67urqrgfnrnlukciupzenpqpipiz5nwtq7uxpx4") # True 30 | is_ipfs.is_IPFS_URL("https://ipfs.io/ipfs/QmY7Yh4UquoXHLPFo2XbhXkhBvFoPwmQUSa92pxnxjQuPU") # True 31 | ``` 32 | ## Target Audience 33 | 34 | Ranging from users with limited coding experience up to professional developers. 35 | 36 | 38 | 39 | ## Github repo 40 | 41 | https://github.com/Barabazs/py-is_ipfs 42 | 43 | 45 | 46 | 47 | 48 | 50 | 51 | ## Team Info 52 | 53 | I'm a (FL)OSS enthusiast working as a solo developer. I'm currently focusing on empowering end-users in the NFT space to prevent and detect unfair projects or blatant scams. 54 | ### Team Size 55 | 1 56 | ### Team members 57 | [Barabazs](https://github.com/Barabazs) 58 | 59 | ## How the community can engage 60 | * Project Repo Discussion: https://github.com/Barabazs/py-is_ipfs/discussions/1 61 | * IPFS Community Discussion: https://github.com/ipfs/community/discussions/745 62 | * Twitter: twitter.com/barabazs_ 63 | 64 | ## How to Contribute 65 | 66 | In the first stage of the project I want to release a beta version. 67 | The community can then test it however they want and contribute with issues, code reviews, pull requests or discussing ideas. 68 | -------------------------------------------------------------------------------- /projects/realityDapp.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Reality dApp 3 | 4 | ## Category 5 | application 6 | 7 | ## Project Description 8 | Decentralized real estate using daps as NFTs 9 | 10 | ## Use of IPFS, Filecoin and Libp2p 11 | I used IPFS for uploading supporting documents for the loan on a seller dashboard so that they can verify 12 | that users can make payments for the loan they take out. 13 | 14 | ## Project status 15 | Project started during ETHGlobal NFTHack. I got it out in the public and people have been receptive. 16 | 17 | 18 | ## Previews 19 | 20 | 21 | [Screenshot 1](https://ethglobal.s3.amazonaws.com/recR9ZsvqlBHqQWdT/Screen_Shot_2022-01-16_at_12.17.46_AM.png) 22 | [Screenshot 2](https://ethglobal.s3.amazonaws.com/recR9ZsvqlBHqQWdT/Screen_Shot_2022-01-16_at_12.17.46_AM.png) 23 | 24 | ## Target Audience 25 | Real estate, home buyers, sellers, buikders 26 | 27 | ## Rough estimated user base (if applicable) 28 | This would be a great tool to give people with bad credit a decentralized means to buy a home without going through banks 29 | 30 | ## Github repo 31 | https://github.com/Josiassejod1/realityDapp 32 | 33 | MIT licence 34 | 35 | ## Website 36 | https://www.dalvin.net 37 | 38 | 39 | https://showcase.ethglobal.com/nfthack2022/reality-dapp 40 | 41 | 42 | ## Docs 43 | Haven't got any 44 | 45 | 46 | ## Team Info 47 | I worked on this solo 48 | 49 | ### Team Size 50 | 1 51 | 52 | ### Team members 53 | Dalvin Josias Sejour 54 | 55 | ## How the community can engage 56 | * GitHub Discussion: https://github.com/ipfs/community/discussions/723 57 | * Email: dalvin.josias@gmail.com 58 | * Twitter: https://twitter.com/officialdalvinj 59 | * Discord: Officialdalvinj#9144 60 | 61 | ## How to Contribute 62 | 63 | Show support and if there are any builders 64 | -------------------------------------------------------------------------------- /projects/smartCOOP.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | 3 | SmartCOOP 4 | 5 | ## Category 6 | 7 | Application 8 | 9 | ## Project Description 10 | 11 | SmartCOOP tries to offer implementation of basic agricultural cooperative logic in the form of smart contracts. In this way we try to propose some possible solutions for problems individual agricultural producers confront while working inside of the traditional frame of cooperatives and big corporate buyers. 12 | 13 | ## Use of IPFS, Filecoin and Libp2p 14 | 15 | Beside attempting to implement basic business logic of agricultural cooperative through smart contract we would like to use IPFS for our dapp back end. 16 | 17 | ## Project Status 18 | 19 | Under development 20 | 21 | ## Previews 22 | 23 | 24 | 25 | 28 | 29 | 30 | 31 | ## Target Audience 32 | 33 | Main target group will be agricultural cooperatives, cooperative associations, federations and other relevant stakeholders like agricultural universities and institutes. 34 | 35 | ## Rough estimated user base (if applicable) 36 | 37 | N.A. 38 | 39 | ## Github repo 40 | 41 | https://github.com/ilijapet/smartCOOP2.0_react_version 42 | 43 | ## Website 44 | 45 | https://muddy-art-3856.on.fleek.co/ 46 | 47 | ## Docs 48 | 49 | https://github.com/ilijapet/blockchain-developer-bootcamp-final-project/blob/main/smartCOOP/README.md 50 | 51 | ## Team Info 52 | 53 | Hello my name is Ilija and this initiative is for now one man show. I'm a ConsenSys certified Ethereum blockchain developer with 4 years of programming experience in Python, Javascript and Solidity. I have formal education in Philosophy with a main focus on technology and science. Beside DApp development I'm interested in real world implicaiton of blockchain technology. 54 | 55 | ### Team Size 56 | 57 | One person 58 | 59 | ### Team members 60 | 61 | ## How the community can engage 62 | 63 | - GitHub Discussion: 64 | 65 | https://github.com/ipfs/community/discussions/735 66 | 67 | - Email: ilijapet@gmail.com 68 | - Slack: 69 | - Twitter: @iliandili 70 | - Discord: ilija#9502 71 | - Telegram:ilija p 72 | - WeChat: 73 | 74 | ## How to Contribute 75 | 76 | By proposing new ideas on how blockchain technology can be used in the field of agricultural cooperatives or contributing to SmartCOOP DApp code. 77 | -------------------------------------------------------------------------------- /projects/stonent.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | Stonent 3 | ## Category 4 | Application 5 | 6 | ## Project Description 7 | Stonent helps NFT-artists fight with intellectual property theft. We use neural network to detect plagiarism of NFT ERC1155 tokens directly in blockchain using Chainlink oracles. 8 | 9 | ## Use of IPFS, Filecoin and Libp2p 10 | We download NFTs from IPFS and indexed it via neural network placed on chainlink external adapter. 11 | 12 | ## Project Status 13 | under development 14 | 15 | ## Previews 16 | DAPP with originality score ![image](https://user-images.githubusercontent.com/31879791/117173733-bdddc880-add5-11eb-9eb3-b74e9ba6db98.png) 17 | 18 | 19 | ## Target Audience 20 | NFT artist and NFT buyers 21 | 22 | ## Rough estimated user base (if applicable) 23 | 0-10 24 | 25 | ## Github repo 26 | https://github.com/vladimir3322/stonent_project 27 | 28 | ## Website 29 | http://stonent.us-east-2.elasticbeanstalk.com/ 30 | 31 | ## Docs 32 | https://github.com/vladimir3322/stonent_project/blob/main/Readme.md 33 | 34 | ### Team Size 35 | 2-3 36 | 37 | ### Team members 38 | https://github.com/StepanSamsonov 39 | https://github.com/vladimir3322 40 | 41 | ## How the community can engage 42 | * https://github.com/ipfs/community/discussions/546 43 | * Discord: arch1362 44 | ## How to Contribute 45 | We are very early in the development phase yet so all feedback is appreciated. 46 | 47 | -------------------------------------------------------------------------------- /projects/yaytso.md: -------------------------------------------------------------------------------- 1 | ## Yaytso 2 | 3 | ## Category 4 | NFT creation tool 5 | 6 | ## Project Description 7 | A silly platform for creating your own uniquely patterned egg. The user, or rather egg-mage, uploads an image file that then textures a 3D egg. If they would like to conjure their egg onto the Ethereum blockchain and world, they are guided to do so. 8 | 9 | ## Project Status 10 | Hacked together for the hackathon, and now looking beyond into the eggverse. 11 | 12 | ## Previews 13 | ![image](https://user-images.githubusercontent.com/38079642/114130295-18f2cd00-98b5-11eb-9c2e-fccfcf5d3a84.png) 14 | 15 | ## Target Audience 16 | Anyone with some knowledge of Ethereum and NFTs. Ideally if the project can garner some funding it could be partially driven by giveaways or egg drop/hunts to allow for the general public to engage with the creation process. Most people are aware/interested in NFTs and everyone loves eggs, so it is pretty well suited for wide adoption. Part of the general goal of the project is to abstract enough of the nitty gritty to make blockchain more approachable and fun. 17 | 18 | ## Rough estimated user base (if applicable) 19 | I think a few people looked at it during the hackathon, but I haven't really marketed it since. 20 | 21 | ## Github repo 22 | https://github.com/aklevecz/yaytso 23 | 24 | ## Website 25 | https://yaytso.art 26 | 27 | ## Docs 28 | https://github.com/aklevecz/yaytso#readme 29 | 30 | ## Team Info 31 | Ariel Klevecz - CEO (Chief Egg Officer) 32 | The mind behind the project and eggthusiast 33 | Frontendy fullstacky dev who is continuing to enjoy exploring IPFS 34 | 35 | ### Team Size 36 | 1 37 | 38 | ### Team members 39 | Ariel Klevecz 40 | 41 | ## How the community can engage 42 | GitHub Discussion: 43 | Email: teh@raptor.pizza 44 | Slack: 45 | Twitter: 46 | Discord: 47 | Telegram: 48 | WeChat: 49 | 50 | ## How to Contribute 51 | Make some eggs! 52 | -------------------------------------------------------------------------------- /swatches/0e8a16.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/0e8a16.png -------------------------------------------------------------------------------- /swatches/1cfc60.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/1cfc60.png -------------------------------------------------------------------------------- /swatches/3f4b56.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/3f4b56.png -------------------------------------------------------------------------------- /swatches/7057ff.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/7057ff.png -------------------------------------------------------------------------------- /swatches/b52ed1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/b52ed1.png -------------------------------------------------------------------------------- /swatches/b60205.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/b60205.png -------------------------------------------------------------------------------- /swatches/bfe5bf.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/bfe5bf.png -------------------------------------------------------------------------------- /swatches/c7def8.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/c7def8.png -------------------------------------------------------------------------------- /swatches/ccf0ed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/ccf0ed.png -------------------------------------------------------------------------------- /swatches/d93f0b.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/d93f0b.png -------------------------------------------------------------------------------- /swatches/dcc8e0.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/dcc8e0.png -------------------------------------------------------------------------------- /swatches/e99695.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/e99695.png -------------------------------------------------------------------------------- /swatches/e9dfeb.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/e9dfeb.png -------------------------------------------------------------------------------- /swatches/ededed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/ededed.png -------------------------------------------------------------------------------- /swatches/f9d0c4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/f9d0c4.png -------------------------------------------------------------------------------- /swatches/fc2929.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/fc2929.png -------------------------------------------------------------------------------- /swatches/fef2c0.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ipfs/community/b99ec428b2c95cfb586cbe3d90ad2c6317e9b6c0/swatches/fef2c0.png -------------------------------------------------------------------------------- /templates/project-submission-template.md: -------------------------------------------------------------------------------- 1 | ## Project Name 2 | 3 | ## Category 4 | 5 | 6 | ## Project Description 7 | 8 | 9 | ## Use of IPFS, Filecoin and Libp2p 10 | 11 | 12 | ## Project Status 13 | 14 | 15 | ## Previews 16 | 17 | 18 | ## Target Audience 19 | 20 | 21 | ## Rough estimated user base (if applicable) 22 | 23 | 24 | ## Github repo 25 | 26 | 27 | ## Website 28 | 29 | 30 | 31 | 32 | ## Docs 33 | 34 | 35 | ## Team Info 36 | 37 | 38 | ### Team Size 39 | 40 | ### Team members 41 | 42 | ## How the community can engage 43 | * GitHub Discussion: 44 | * Email: 45 | * Slack: 46 | * Twitter: 47 | * Discord: 48 | * Telegram: 49 | * WeChat: 50 | 51 | ## How to Contribute 52 | 53 | --------------------------------------------------------------------------------