├── .github
├── ISSUE_TEMPLATE
│ ├── bug_report.md
│ ├── custom.md
│ └── feature_request.md
└── workflows
│ └── codeql.yml
├── .gitignore
├── .whitesource
├── CHANGELOG.md
├── CONTRIBUTING.md
├── LICENSE
├── LICENSE.md
├── README.md
├── config
├── codeql-config.yml
├── database.js
└── environment.js
├── docker
├── Dockerfile
└── docker-compose.yml
├── docs
├── PiEcosystemHub.jpeg
├── api_reference.md
├── architecture.md
├── developer_guide.md
└── user_guide.md
├── scripts
├── deploy.js
└── seedDatabase.js
├── src
├── blockchain
│ └── pi-connector.js
├── components
│ ├── Card.css
│ ├── Card.js
│ ├── Footer.css
│ ├── Footer.js
│ ├── Header.css
│ └── Header.js
├── config
│ └── constants.py
├── controllers
│ └── ProductController.js
├── dapps
│ ├── MyDapp
│ │ └── example-dapp.py
│ └── README.md
├── main
│ ├── app.js
│ ├── config.js
│ ├── controllers
│ │ ├── authController.js
│ │ └── dAppController.js
│ ├── index.js
│ ├── middleware
│ │ └── errorMiddleware.js
│ ├── models
│ │ └── User.js
│ └── routes
│ │ ├── authRoutes.js
│ │ └── dAppRoutes.js
├── middleware
│ ├── authMiddleware.js
│ └── errorMiddleware.js
├── models
│ ├── Transaction.js
│ ├── User.js
│ └── dApp.js
├── services
│ ├── apiService.js
│ ├── dAppService.js
│ ├── marketplace-service.js
│ └── userService.js
└── utils
│ ├── helpers.js
│ └── validators.js
└── tests
├── e2e
└── app.test.js
├── integration
└── api.test.js
└── unit
├── dAppService.test.js
└── userService.test.js
/.github/ISSUE_TEMPLATE/bug_report.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Bug report
3 | about: Create a report to help us improve
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | **Describe the bug**
11 | A clear and concise description of what the bug is.
12 |
13 | **To Reproduce**
14 | Steps to reproduce the behavior:
15 | 1. Go to '...'
16 | 2. Click on '....'
17 | 3. Scroll down to '....'
18 | 4. See error
19 |
20 | **Expected behavior**
21 | A clear and concise description of what you expected to happen.
22 |
23 | **Screenshots**
24 | If applicable, add screenshots to help explain your problem.
25 |
26 | **Desktop (please complete the following information):**
27 | - OS: [e.g. iOS]
28 | - Browser [e.g. chrome, safari]
29 | - Version [e.g. 22]
30 |
31 | **Smartphone (please complete the following information):**
32 | - Device: [e.g. iPhone6]
33 | - OS: [e.g. iOS8.1]
34 | - Browser [e.g. stock browser, safari]
35 | - Version [e.g. 22]
36 |
37 | **Additional context**
38 | Add any other context about the problem here.
39 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/custom.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Custom issue template
3 | about: Describe this issue template's purpose here.
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 |
11 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/feature_request.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Feature request
3 | about: Suggest an idea for this project
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | **Is your feature request related to a problem? Please describe.**
11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12 |
13 | **Describe the solution you'd like**
14 | A clear and concise description of what you want to happen.
15 |
16 | **Describe alternatives you've considered**
17 | A clear and concise description of any alternative solutions or features you've considered.
18 |
19 | **Additional context**
20 | Add any other context or screenshots about the feature request here.
21 |
--------------------------------------------------------------------------------
/.github/workflows/codeql.yml:
--------------------------------------------------------------------------------
1 | # For most projects, this workflow file will not need changing; you simply need
2 | # to commit it to your repository.
3 | #
4 | # You may wish to alter this file to override the set of languages analyzed,
5 | # or to provide custom queries or build logic.
6 | #
7 | # ******** NOTE ********
8 | # We have attempted to detect the languages in your repository. Please check
9 | # the `language` matrix defined below to confirm you have the correct set of
10 | # supported CodeQL languages.
11 | #
12 | name: "CodeQL Advanced"
13 |
14 | on:
15 | push:
16 | branches: [ "main" ]
17 | pull_request:
18 | branches: [ "main" ]
19 | schedule:
20 | - cron: '35 18 * * 2'
21 |
22 | jobs:
23 | analyze:
24 | name: Analyze (${{ matrix.language }})
25 | # Runner size impacts CodeQL analysis time. To learn more, please see:
26 | # - https://gh.io/recommended-hardware-resources-for-running-codeql
27 | # - https://gh.io/supported-runners-and-hardware-resources
28 | # - https://gh.io/using-larger-runners (GitHub.com only)
29 | # Consider using larger runners or machines with greater resources for possible analysis time improvements.
30 | runs-on: ${{ (matrix.language == 'swift' && 'macos-latest') || 'ubuntu-latest' }}
31 | permissions:
32 | # required for all workflows
33 | security-events: write
34 |
35 | # required to fetch internal or private CodeQL packs
36 | packages: read
37 |
38 | # only required for workflows in private repositories
39 | actions: read
40 | contents: read
41 |
42 | strategy:
43 | fail-fast: false
44 | matrix:
45 | include:
46 | - language: javascript-typescript
47 | build-mode: none
48 | - language: python
49 | build-mode: none
50 | # CodeQL supports the following values keywords for 'language': 'actions', 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'swift'
51 | # Use `c-cpp` to analyze code written in C, C++ or both
52 | # Use 'java-kotlin' to analyze code written in Java, Kotlin or both
53 | # Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
54 | # To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
55 | # see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
56 | # If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
57 | # your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
58 | steps:
59 | - name: Checkout repository
60 | uses: actions/checkout@v4
61 |
62 | # Add any setup steps before running the `github/codeql-action/init` action.
63 | # This includes steps like installing compilers or runtimes (`actions/setup-node`
64 | # or others). This is typically only required for manual builds.
65 | # - name: Setup runtime (example)
66 | # uses: actions/setup-example@v1
67 |
68 | # Initializes the CodeQL tools for scanning.
69 | - name: Initialize CodeQL
70 | uses: github/codeql-action/init@v3
71 | with:
72 | languages: ${{ matrix.language }}
73 | build-mode: ${{ matrix.build-mode }}
74 | # If you wish to specify custom queries, you can do so here or in a config file.
75 | # By default, queries listed here will override any specified in a config file.
76 | # Prefix the list here with "+" to use these queries and those in the config file.
77 |
78 | # For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
79 | # queries: security-extended,security-and-quality
80 |
81 | # If the analyze step fails for one of the languages you are analyzing with
82 | # "We were unable to automatically build your code", modify the matrix above
83 | # to set the build mode to "manual" for that language. Then modify this step
84 | # to build your code.
85 | # ℹ️ Command-line programs to run using the OS shell.
86 | # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
87 | - if: matrix.build-mode == 'manual'
88 | shell: bash
89 | run: |
90 | echo 'If you are using a "manual" build mode for one or more of the' \
91 | 'languages you are analyzing, replace this with the commands to build' \
92 | 'your code, for example:'
93 | echo ' make bootstrap'
94 | echo ' make release'
95 | exit 1
96 |
97 | - name: Perform CodeQL Analysis
98 | uses: github/codeql-action/analyze@v3
99 | with:
100 | category: "/language:${{matrix.language}}"
101 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # Node.js
2 | node_modules/
3 | npm-debug.log
4 | .env
5 |
6 | # Logs
7 | logs
8 | *.log
9 |
10 | # Build output
11 | dist/
12 | build/
13 |
14 | # IDEs and editors
15 | .vscode/
16 | .idea/
17 | *.swp
18 |
--------------------------------------------------------------------------------
/.whitesource:
--------------------------------------------------------------------------------
1 | {
2 | "scanSettings": {
3 | "baseBranches": []
4 | },
5 | "checkRunSettings": {
6 | "vulnerableCheckRunConclusionLevel": "failure",
7 | "displayMode": "diff",
8 | "useMendCheckNames": true
9 | },
10 | "issueSettings": {
11 | "minSeverityLevel": "LOW",
12 | "issueType": "DEPENDENCY"
13 | }
14 | }
--------------------------------------------------------------------------------
/CHANGELOG.md:
--------------------------------------------------------------------------------
1 | # Changelog
2 |
3 | All notable changes to this project will be documented in this file.
4 |
5 | ## [Unreleased]
6 | ### Added
7 | - Initial project setup
8 | - Basic application structure
9 |
10 | ## [1.0.0] - 2024-11-04
11 | ### Added
12 | - Decentralized Application Marketplace
13 | - User authentication and management
14 | - Basic API endpoints for dApps
15 |
16 | ### Changed
17 | - Updated README with installation instructions
18 |
19 | ### Fixed
20 | - Resolved issues with user registration
21 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contributing to Pi Ecosystem Integration Hub
2 |
3 | Thank you for your interest in contributing to the Pi Ecosystem Integration Hub! We appreciate your help in making this project better.
4 |
5 | ## How to Contribute
6 |
7 | 1. **Fork the repository**: Click the "Fork" button at the top right of the repository page.
8 | 2. **Clone your fork**:
9 | ```bash
10 | 1 git clone https://github.com/KOSASIH/PiEcosystemHub.git
11 | 2 cd PiEcosystemHub
12 | ```
13 |
14 | 3. **Create a new branch**:
15 | ```bash
16 | 1 git checkout -b feature/YourFeatureName
17 | ```
18 |
19 | 4. **Make your changes**: Implement your feature or fix.
20 |
21 | 5. **Commit your changes**:
22 | ```bash
23 | 1 git commit -m "Add your message here"
24 | ```
25 | 6. **Push to your fork**:
26 | ```bash
27 | 1 git push origin feature/YourFeatureName
28 | ```
29 |
30 | 7. **Create a pull request**: Go to the original repository and click on "New Pull Request".
31 |
32 | ## Code of Conduct
33 | Please adhere to our Code of Conduct in all interactions.
34 |
35 | ## Questions?
36 | If you have any questions, feel free to reach out to the maintainers.
37 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2024 KOSASIH
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 all
13 | 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 THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/LICENSE.md:
--------------------------------------------------------------------------------
1 | PiOS License
2 |
3 | Copyright (C) 2024 KOSASIH
4 |
5 | Permission is hereby granted by the application software developer (“Software Developer”), free
6 | of charge, to any person obtaining a copy of this application, software and associated
7 | documentation files (the “Software”), which was developed by the Software Developer for use on
8 | Pi Network, whereby the purpose of this license is to permit the development of derivative works
9 | based on the Software, including the right to use, copy, modify, merge, publish, distribute,
10 | sub-license, and/or sell copies of such derivative works and any Software components incorporated
11 | therein, and to permit persons to whom such derivative works are furnished to do so, in each case,
12 | solely to develop, use and market applications for the official Pi Network. For purposes of this
13 | license, Pi Network shall mean any application, software, or other present or future platform
14 | developed, owned or managed by Pi Community Company, and its parents, affiliates or subsidiaries,
15 | for which the Software was developed, or on which the Software continues to operate. However,
16 | you are prohibited from using any portion of the Software or any derivative works thereof in any
17 | manner (a) which infringes on any Pi Network intellectual property rights, (b) to hack any of Pi
18 | Network’s systems or processes or (c) to develop any product or service which is competitive with
19 | the Pi Network.
20 |
21 | The above copyright notice and this permission notice shall be included in all copies or
22 | substantial portions of the Software.
23 |
24 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
25 | INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
26 | AND NON-INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS, PUBLISHERS, OR COPYRIGHT HOLDERS OF THIS
27 | SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL
28 | DAMAGES (INCLUDING, BUT NOT LIMITED TO BUSINESS INTERRUPTION, LOSS OF USE, DATA OR PROFITS)
29 | HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
30 | TORT (INCLUDING NEGLIGENCE) ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE
31 | OR OTHER DEALINGS IN THE SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
32 |
33 | Pi, Pi Network and the Pi logo are trademarks of the Pi Community Company.
34 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | [](https://bitcoinassociation.net/)
2 | [](https://www.hyperledger.org/)
3 | [](https://www.blockchaincertification.org/)
4 | [](https://opensource.org/)
5 | [](https://www.iso.org/isoiec-27001-information-security.html)
6 | [](https://www2.deloitte.com/global/en/pages/consulting/solutions/blockchain.html)
7 | [](https://ethereum.org/en/foundation/)
8 | [](https://www.blockchainassociation.org/)
9 | [](https://www.coinbase.com/earn)
10 | [](https://github.com/sponsors)
11 | [](https://www.blockchainresearchinstitute.org/)
12 | [](https://www.hyperledger.org/)
13 | [](https://ethereum.org/en/community/)
14 | [](https://www.corda.net/)
15 | [](https://www.w3.org/community/blockchain/)
16 | [](https://daml.com/)
17 | [](https://www.bita.studio/)
18 | [](https://gbbcouncil.org/)
19 | [](https://www.blockchainassociation.org/)
20 | [](https://cryptovalley.swiss/)
21 | [](https://blockchaintechnologypartners.com/)
22 | [](https://www.ibassociation.org/)
23 | [](https://cryptoconsortium.org/)
24 | [](https://www.blockchainforsocialimpact.com/)
25 | [](https://identity.foundation/)
26 | [](https://openid.net/foundation/)
27 | [](https://entethalliance.org/)
28 | [](https://blockchainhealthcaretoday.com/)
29 | [](https://www.digitalchamber.org/)
30 | [](https://blockchainforgood.org/)
31 | [](https://www.blockchain-council.org/)
32 | [](https://www.blockchainedu.org/)
33 | [](https://cryptovalley.swiss/)
34 | [](https://www.blockchainresearchinstitute.org/)
35 | [](https://www.globalblockchainforum.com/)
36 | [](https://www.blockchainforsustainabledevelopment.org/)
37 | [](https://www.blockchaininenergy.org/)
38 | [](https://www.blockchainforsupplychain.org/)
39 | [](https://iatba.org/)
40 | [](https://www.blockchaininfinance.org/)
41 | [](https://www.blockchainforsocialimpact.com/)
42 | [](https://www.blockchainforclimate.org/)
43 |
44 | [](https://cyber.stanford.edu/blockchain)
45 | [](https://cbr.stanford.edu/)
46 | [](https://dci.mit.edu/)
47 | [](https://blockchain.harvard.edu/)
48 | [](https://blockchain.berkeley.edu/)
49 | [](https://www.oxfordblockchain.org/)
50 | [](https://www.columbiacryptography.org/)
51 | [](https://www.jbs.cam.ac.uk/faculty-research/centres/alternative-finance/)
52 | [](https://www.duke.edu/)
53 | [](https://www.stern.nyu.edu/experience-stern/centers-institutes/blockchain)
54 | [](https://michiganblockchain.org/)
55 | [](https://torontoblockchain.org/)
56 | [](https://blockchain.ucsd.edu/)
57 | [](https://www.blockchain.gatech.edu/)
58 | [](https://uwblockchain.org/)
59 | [](https://www.blockchain.usc.edu/)
60 | [](https://www.purdue.edu/blockchain/)
61 | [](https://www.northwestern.edu/)
62 | [](https://blockchain.illinois.edu/)
63 | [](https://www.ed.ac.uk/information-services/learning-technology/blockchain)
64 |
65 | [](https://online.stanford.edu/courses/sohs-ystats1-statistics-and-data-science)
66 | [](https://executive.mit.edu/course/blockchain-technologies-business-innovation-and-application/)
67 | [](https://online-learning.harvard.edu/course/blockchain-business)
68 | [](https://blockchain.berkeley.edu/certificates/)
69 | [](https://www.coursera.org/learn/blockchain)
70 | [](https://www.coursera.org/learn/toronto-blockchain)
71 | [](https://www.coursera.org/learn/duke-blockchain)
72 | [](https://www.coursera.org/learn/usc-blockchain)
73 | [](https://www.coursera.org/learn/illinois-blockchain)
74 | [](https://www.ed.ac.uk/information-services/learning-technology/blockchain)
75 | [](https://www.coursera.org/learn/columbia-blockchain)
76 | [](https://scs.georgetown.edu/programs/1001/certificate-in-blockchain-technology/)
77 | [](https://www.sps.nyu.edu/homepage/academics/graduate/degree-programs/blockchain.html)
78 | [](https://ce.uci.edu/areas/it/blockchain/)
79 | [](https://extension.ucdavis.edu/areas-study/business/blockchain)
80 | [](https://www.du.edu/learn/certificate/blockchain.html)
81 | [](https://www.umass.edu/online/certificate/blockchain/)
82 | [](https://www.miami.edu/online/certificate-in-blockchain-technology.html)
83 | [](https://professional.utexas.edu/courses/blockchain)
84 | [](https://www.pce.uw.edu/certificates/blockchain)
85 | [](https://www.coursera.org/learn/cornell-blockchain)
86 | [](https://umdearborn.edu/ce/certificate/blockchain)
87 | [](https://www.ucsf.edu/)
88 | [](https://www.marshall.usc.edu/programs/graduate-certificate/blockchain-management)
89 | [](https://www.unc.edu/)
90 | [](https://www.arizona.edu/)
91 | [](https://www.ufl.edu/)
92 | [](https://www.pitt.edu/)
93 | [](https://www.colorado.edu/)
94 | [](https://www.uconn.edu/)
95 |
96 |