├── .github ├── ISSUE_TEMPLATE │ ├── bug_report.yml │ ├── config.yml │ ├── documentation.yml │ ├── feature_request.md │ ├── feature_request.yml │ └── styles.yml ├── PULL_REQUEST_TEMPLATE │ └── pull_request_template.md ├── dependabot.yml └── workflows │ └── linting.yml ├── .gitignore ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── Education ├── crypto-market-basics.md ├── cryptocurrencies-introduction.md ├── fundamental-analysis.md ├── investment-strategies.md ├── resources-and-tools.md ├── risk-management-strategies.md ├── stock-market-basics.md ├── stocks-introduction.md ├── tax-implications.md ├── technical-analysis.md ├── types-of-cryptocurrencies.md └── types-of-stocks.md ├── GSSoC-CONTRIBUTORS.md ├── LICENSE ├── README.md └── app ├── .gitignore ├── index.html ├── package-lock.json ├── package.json ├── postcss.config.cjs ├── public ├── contactus.svg ├── crypto-header-image.svg ├── github.svg ├── header.svg ├── koo-icon.svg ├── login.svg ├── logo.svg ├── news-header-image.svg ├── sitemap.xml ├── stocks-header-image.svg └── trade-header-image.svg ├── src ├── App.css ├── App.jsx ├── assets │ ├── index.js │ ├── koo-icon-hover.svg │ ├── koo-icon.svg │ ├── loginIMG.svg │ ├── react.svg │ └── signupIMG.svg ├── components │ ├── Accordion.jsx │ ├── ContactForm.jsx │ ├── Features.jsx │ ├── Footer.jsx │ ├── Header.jsx │ ├── Modal.jsx │ ├── Navbar.jsx │ ├── NotFound.jsx │ ├── Pricing.jsx │ ├── Stats.jsx │ ├── Ticker.jsx │ ├── crypto │ │ ├── Header.jsx │ │ └── Widget1.jsx │ ├── news │ │ ├── CryptoWidget.jsx │ │ ├── Header.jsx │ │ └── StocksWidget.jsx │ ├── scrollButton.jsx │ ├── stocks │ │ ├── Header.jsx │ │ └── Widget1.jsx │ └── trade │ │ ├── CryptoWidget.jsx │ │ ├── Header.jsx │ │ └── StocksWidget.jsx ├── firebase │ └── auth.js ├── index.css ├── main.jsx └── pages │ ├── Cryptocurrencies.jsx │ ├── Dashboard.jsx │ ├── Derivatives.jsx │ ├── Homepage.jsx │ ├── Institutional.jsx │ ├── Login.jsx │ ├── NFT.jsx │ ├── News.jsx │ ├── SignUp.jsx │ ├── Stocks.jsx │ ├── Support.jsx │ └── Trade.jsx ├── tailwind.config.cjs ├── vercel.json └── vite.config.js /.github/ISSUE_TEMPLATE/bug_report.yml: -------------------------------------------------------------------------------- 1 | name: Bug Report 2 | description: File a bug report 3 | title: "[Bug]: " 4 | labels: ["bug"] 5 | 6 | body: 7 | - type: textarea 8 | attributes: 9 | label: Describe the bug 10 | description: A clear and concise description of what the bug is. 11 | validations: 12 | required: true 13 | - type: textarea 14 | attributes: 15 | label: To Reproduce 16 | description: Steps to reproduce the behavior 17 | value: "1. Go to '...'\n2. Click on '....'\n3. Scroll down to '....'\n4. See error\n" 18 | validations: 19 | required: true 20 | - type: textarea 21 | attributes: 22 | label: Expected behavior 23 | description: A clear and concise description of what you expected to happen. 24 | validations: 25 | required: true 26 | - type: textarea 27 | attributes: 28 | label: Screenshots/Videos 29 | description: Drag n Drop Screenshots or videos which would help us to view the bug visually 30 | validations: 31 | required: false 32 | - type: textarea 33 | attributes: 34 | label: Additional context 35 | description: Add any other context about the problem here. 36 | validations: 37 | required: false 38 | - type: checkboxes 39 | attributes: 40 | label: Please checkmark the following checklist 41 | options: 42 | - label: I make sure that similar issue is not opened 43 | required: true 44 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/config.yml: -------------------------------------------------------------------------------- 1 | blank_issues_enabled: true 2 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/documentation.yml: -------------------------------------------------------------------------------- 1 | name: 📄 Documentation issue 2 | description: Found an issue in the documentation? You can use this one! 3 | title: "[DOCS] " 4 | labels: ["documentation"] 5 | body: 6 | - type: textarea 7 | id: description 8 | attributes: 9 | label: Description 10 | description: A brief description of the question or issue, also include what you tried and what didn't work 11 | validations: 12 | required: true 13 | - type: textarea 14 | id: screenshots 15 | attributes: 16 | label: Screenshots 17 | description: Please add screenshots if applicable 18 | validations: 19 | required: false 20 | - type: textarea 21 | id: extrainfo 22 | attributes: 23 | label: Additional information 24 | description: Is there anything else we should know about this issue? 25 | validations: 26 | required: false 27 | - type: checkboxes 28 | id: terms 29 | attributes: 30 | label: Code of Conduct 31 | description: By submitting this issue, you agree to follow our Code of Conduct 32 | options: 33 | - label: I agree to follow this project's Code of Conduct 34 | required: true 35 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | title: "" 5 | labels: ["feature"] 6 | assignees: "" 7 | --- 8 | 9 | **Is your feature request related to a problem? Please describe.** 10 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] 11 | 12 | **Describe the solution you'd like** 13 | A clear and concise description of what you want to happen. 14 | 15 | **Describe alternatives you've considered** 16 | A clear and concise description of any alternative solutions or features you've considered. 17 | 18 | **Additional context** 19 | Add any other context or screenshots about the feature request here. 20 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.yml: -------------------------------------------------------------------------------- 1 | name: 💡 Feature request 2 | description: Have a new idea/feature ? Please suggest! 3 | labels: ["enhancement"] 4 | body: 5 | - type: textarea 6 | id: description 7 | attributes: 8 | label: Is your feature request related to a problem? Please describe. 9 | description: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] 10 | validations: 11 | required: true 12 | 13 | - type: textarea 14 | id: solution 15 | attributes: 16 | label: Describe the solution you'd like 17 | description: A clear and concise description of what you want to happen. 18 | validations: 19 | required: true 20 | 21 | - type: textarea 22 | id: alternatives 23 | attributes: 24 | label: Describe alternatives you've considered 25 | description: A clear and concise description of any alternative solutions or features you've considered. 26 | validations: 27 | required: false 28 | 29 | - type: textarea 30 | id: extrainfo 31 | attributes: 32 | label: Additional context 33 | description: Add any other context or screenshots about the feature request here. 34 | validations: 35 | required: false 36 | - type: checkboxes 37 | id: terms 38 | attributes: 39 | label: Code of Conduct 40 | description: By submitting this issue, you agree to follow our Code of Conduct 41 | options: 42 | - label: I agree to follow this project's Code of Conduct 43 | required: true 44 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/styles.yml: -------------------------------------------------------------------------------- 1 | name: Style Changing Request 2 | description: Suggest a style design 3 | title: "[style]: " 4 | labels: ["enhancement"] 5 | 6 | body: 7 | - type: markdown 8 | attributes: 9 | value: | 10 | Thanks for taking the time to fill out this template! 11 | - type: textarea 12 | id: style-idea 13 | attributes: 14 | label: What's the style idea? 15 | placeholder: Add descriptions 16 | value: "We need to improve" 17 | validations: 18 | required: true 19 | - type: textarea 20 | id: screenshots 21 | attributes: 22 | label: Add screenshots 23 | description: Add screenshots to show the demo 24 | placeholder: Add screenshots 25 | value: "Add screenshots" 26 | - type: checkboxes 27 | id: terms 28 | attributes: 29 | label: Code of Conduct 30 | description: By submitting this issue, you agree to follow our Code of Conduct 31 | options: 32 | - label: I agree to follow this project's Code of Conduct 33 | required: true 34 | - label: I have read the [Contributing Guidelines](https://github.com/Stoccoin-Official/Stoccoin-Website/blob/main/CONTRIBUTING.md) 35 | required: true 36 | - label: I agree to follow this project's [Code of Conduct](https://github.com/Stoccoin-Official/Stoccoin-Website/blob/main/CODE_OF_CONDUCT.md) 37 | required: true 38 | - label: I'm a GSSoC'23 contributor 39 | - label: I want to work on this issue 40 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE/pull_request_template.md: -------------------------------------------------------------------------------- 1 | ## What does this PR do? 2 | 3 | 4 | 5 | Fixes #(issue) 6 | 7 | ## Screenshots 8 | 9 | 10 | 11 | ## Type of change 12 | 13 | 14 | 15 | - Bug fix (non-breaking change which fixes an issue) 16 | - Chore (refactoring code, technical debt, workflow improvements) 17 | - New feature (non-breaking change which adds functionality) 18 | - Breaking change (fix or feature that would cause existing functionality to not work as expected) 19 | - This change requires a documentation update 20 | 21 | ## How should this be tested? 22 | 23 | 24 | 25 | - [ ] Test A 26 | - [ ] Test B 27 | 28 | ## Mandatory Tasks 29 | 30 | - [ ] Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected. 31 | 32 | ## Checklist 33 | 34 | 35 | 36 | - I haven't read the [contributing guide](https://github.com/Stoccoin-Official/Stoccoin-Website/blob/main/CONTRIBUTING.md) 37 | - My code doesn't follow the style guidelines of this project 38 | - I haven't commented my code, particularly in hard-to-understand areas 39 | - I haven't checked if my PR needs changes to the documentation 40 | - I haven't checked if my changes generate no new warnings 41 | - I haven't added tests that prove my fix is effective or that my feature works 42 | - I haven't checked if new and existing unit tests pass locally with my changes 43 | -------------------------------------------------------------------------------- /.github/dependabot.yml: -------------------------------------------------------------------------------- 1 | version: 2 2 | updates: 3 | - package-ecosystem: "npm" 4 | directory: "/" 5 | schedule: 6 | interval: "daily" 7 | -------------------------------------------------------------------------------- /.github/workflows/linting.yml: -------------------------------------------------------------------------------- 1 | name: Linting 2 | 3 | on: [push, pull_request] 4 | 5 | jobs: 6 | Linting: 7 | runs-on: ubuntu-latest 8 | 9 | steps: 10 | - name: Checkout 11 | uses: actions/checkout@v3 12 | with: 13 | ref: ${{ github.head_ref }} 14 | 15 | - name: Lint code with prettier 16 | uses: creyD/prettier_action@v4.3 17 | with: 18 | prettier_options: --write **/*.{js,md} 19 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # Logs 2 | logs 3 | *.log 4 | npm-debug.log* 5 | yarn-debug.log* 6 | yarn-error.log* 7 | lerna-debug.log* 8 | 9 | # Diagnostic reports (https://nodejs.org/api/report.html) 10 | report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json 11 | 12 | # Runtime data 13 | pids 14 | *.pid 15 | *.seed 16 | *.pid.lock 17 | 18 | # Directory for instrumented libs generated by jscoverage/JSCover 19 | lib-cov 20 | 21 | # Coverage directory used by tools like istanbul 22 | coverage 23 | *.lcov 24 | 25 | # nyc test coverage 26 | .nyc_output 27 | 28 | # Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files) 29 | .grunt 30 | 31 | # Bower dependency directory (https://bower.io/) 32 | bower_components 33 | 34 | # node-waf configuration 35 | .lock-wscript 36 | 37 | # Compiled binary addons (https://nodejs.org/api/addons.html) 38 | build/Release 39 | 40 | # Dependency directories 41 | node_modules/ 42 | jspm_packages/ 43 | 44 | # TypeScript v1 declaration files 45 | typings/ 46 | 47 | # TypeScript cache 48 | *.tsbuildinfo 49 | 50 | # Optional npm cache directory 51 | .npm 52 | 53 | # Optional eslint cache 54 | .eslintcache 55 | 56 | # Microbundle cache 57 | .rpt2_cache/ 58 | .rts2_cache_cjs/ 59 | .rts2_cache_es/ 60 | .rts2_cache_umd/ 61 | 62 | # Optional REPL history 63 | .node_repl_history 64 | 65 | # Output of 'npm pack' 66 | *.tgz 67 | 68 | # Yarn Integrity file 69 | .yarn-integrity 70 | 71 | # dotenv environment variables file 72 | .env 73 | .env.test 74 | 75 | # parcel-bundler cache (https://parceljs.org/) 76 | .cache 77 | 78 | # Next.js build output 79 | .next 80 | 81 | # Nuxt.js build / generate output 82 | .nuxt 83 | dist 84 | 85 | # Gatsby files 86 | .cache/ 87 | # Comment in the public line in if your project uses Gatsby and *not* Next.js 88 | # https://nextjs.org/blog/next-9-1#public-directory-support 89 | # public 90 | 91 | # vuepress build output 92 | .vuepress/dist 93 | 94 | # Serverless directories 95 | .serverless/ 96 | 97 | # FuseBox cache 98 | .fusebox/ 99 | 100 | # DynamoDB Local files 101 | .dynamodb/ 102 | 103 | # TernJS port file 104 | .tern-port 105 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in our 6 | community a harassment-free experience for everyone, regardless of age, body 7 | size, visible or invisible disability, ethnicity, sex characteristics, gender 8 | identity and expression, level of experience, education, socio-economic status, 9 | nationality, personal appearance, race, religion, or sexual identity 10 | and orientation. 11 | 12 | We pledge to act and interact in ways that contribute to an open, welcoming, 13 | diverse, inclusive, and healthy community. 14 | 15 | ## Our Standards 16 | 17 | Examples of behavior that contributes to a positive environment for our 18 | community include: 19 | 20 | - Demonstrating empathy and kindness toward other people 21 | - Being respectful of differing opinions, viewpoints, and experiences 22 | - Giving and gracefully accepting constructive feedback 23 | - Accepting responsibility and apologizing to those affected by our mistakes, 24 | and learning from the experience 25 | - Focusing on what is best not just for us as individuals, but for the 26 | overall community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | - The use of sexualized language or imagery, and sexual attention or 31 | advances of any kind 32 | - Trolling, insulting or derogatory comments, and personal or political attacks 33 | - Public or private harassment 34 | - Publishing others' private information, such as a physical or email 35 | address, without their explicit permission 36 | - Other conduct which could reasonably be considered inappropriate in a 37 | professional setting 38 | 39 | ## Enforcement Responsibilities 40 | 41 | Community leaders are responsible for clarifying and enforcing our standards of 42 | acceptable behavior and will take appropriate and fair corrective action in 43 | response to any behavior that they deem inappropriate, threatening, offensive, 44 | or harmful. 45 | 46 | Community leaders have the right and responsibility to remove, edit, or reject 47 | comments, commits, code, wiki edits, issues, and other contributions that are 48 | not aligned to this Code of Conduct, and will communicate reasons for moderation 49 | decisions when appropriate. 50 | 51 | ## Scope 52 | 53 | This Code of Conduct applies within all community spaces, and also applies when 54 | an individual is officially representing the community in public spaces. 55 | Examples of representing our community include using an official e-mail address, 56 | posting via an official social media account, or acting as an appointed 57 | representative at an online or offline event. 58 | 59 | ## Enforcement 60 | 61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 62 | reported to the community leaders responsible for enforcement at 63 | . 64 | All complaints will be reviewed and investigated promptly and fairly. 65 | 66 | All community leaders are obligated to respect the privacy and security of the 67 | reporter of any incident. 68 | 69 | ## Enforcement Guidelines 70 | 71 | Community leaders will follow these Community Impact Guidelines in determining 72 | the consequences for any action they deem in violation of this Code of Conduct: 73 | 74 | ### 1. Correction 75 | 76 | **Community Impact**: Use of inappropriate language or other behavior deemed 77 | unprofessional or unwelcome in the community. 78 | 79 | **Consequence**: A private, written warning from community leaders, providing 80 | clarity around the nature of the violation and an explanation of why the 81 | behavior was inappropriate. A public apology may be requested. 82 | 83 | ### 2. Warning 84 | 85 | **Community Impact**: A violation through a single incident or series 86 | of actions. 87 | 88 | **Consequence**: A warning with consequences for continued behavior. No 89 | interaction with the people involved, including unsolicited interaction with 90 | those enforcing the Code of Conduct, for a specified period of time. This 91 | includes avoiding interactions in community spaces as well as external channels 92 | like social media. Violating these terms may lead to a temporary or 93 | permanent ban. 94 | 95 | ### 3. Temporary Ban 96 | 97 | **Community Impact**: A serious violation of community standards, including 98 | sustained inappropriate behavior. 99 | 100 | **Consequence**: A temporary ban from any sort of interaction or public 101 | communication with the community for a specified period of time. No public or 102 | private interaction with the people involved, including unsolicited interaction 103 | with those enforcing the Code of Conduct, is allowed during this period. 104 | Violating these terms may lead to a permanent ban. 105 | 106 | ### 4. Permanent Ban 107 | 108 | **Community Impact**: Demonstrating a pattern of violation of community 109 | standards, including sustained inappropriate behavior, harassment of an 110 | individual, or aggression toward or disparagement of classes of individuals. 111 | 112 | **Consequence**: A permanent ban from any sort of public interaction within 113 | the community. 114 | 115 | ## Attribution 116 | 117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 118 | version 2.0, available at 119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 120 | 121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 122 | enforcement ladder](https://github.com/mozilla/diversity). 123 | 124 | [homepage]: https://www.contributor-covenant.org 125 | 126 | For answers to common questions about this code of conduct, see the FAQ at 127 | https://www.contributor-covenant.org/faq. Translations are available at 128 | https://www.contributor-covenant.org/translations. 129 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contribution Guidelines 2 | 3 | 1. Fork the repository. 4 | 2. Clone the repository.
5 | `git clone https://github.com/your-username/repository-name.git` 6 | 3. Create a new branch with a descriptive name for your feature/bug fix.
7 | `git checkout -b feature/new-feature` 8 | 4. Make changes and commits to your branch.
9 | `git add .`
10 | `git commit -m "feat: Add new feature"` 11 | 5. Push your branch to your forked repository.
12 | `git push origin feature/new-feature` 13 | 6. Submit a pull request to the original repository's master branch. 14 | 7. Wait for the maintainers to review your pull request and provide feedback. 15 | 8. Make any requested changes and push them to your forked repository. 16 | 9. Once your pull request is approved, it will be merged into the master branch. 17 | 18 | That being said, it's important to write clear and descriptive commit messages to help other contributors understand the changes you've made to the code. Here are some common commit message types and their meanings: 19 | 20 | - feat: A new feature has been added. 21 | - fix: A bug has been fixed. 22 | - docs: Changes have been made to documentation. 23 | - style: Changes have been made to the code's style or formatting. 24 | - refactor: The code has been refactored without changing its functionality. 25 | - test: Changes have been made to unit tests or test cases. 26 | - chore: Changes have been made to the build process or other non-code related tasks. 27 | 28 | For example, a commit message for adding a new feature to a project could be: 29 | 30 | `feat: Add user authentication system` 31 | 32 | And a commit message for fixing a bug could be: 33 | 34 | `fix: Fix bug in search function` 35 | 36 | Using clear and descriptive commit messages like these can help others understand your changes and make it easier to maintain the codebase. 37 | -------------------------------------------------------------------------------- /Education/crypto-market-basics.md: -------------------------------------------------------------------------------- 1 | # Table of contents 2 | 3 | - [Table of contents](#table-of-contents) 4 | - [Introduction](#introduction) 5 | - [1. Cryptocurrency?](#1-cryptocurrency) 6 | - [2. Blockchain Technology](#2-blockchain-technology) 7 | - [3. Decentralization](#3-decentralization) 8 | - [4. Cryptocurrency Exchanges](#4-cryptocurrency-exchanges) 9 | - [5. Wallets and Security](#5-wallets-and-security) 10 | - [6. Market Volatility](#6-market-volatility) 11 | - [7. Crypto Trading Strategies](#7-crypto-trading-strategies) 12 | - [8. Initial Coin Offerings (ICOs)](#8-initial-coin-offerings-icos) 13 | - [9. Regulatory Environment](#9-regulatory-environment) 14 | 15 | ## Introduction 16 | 17 | Welcome to the world of cryptocurrency! This document aims to provide you with a basic understanding of the crypto market and its key concepts. Whether you're new to the field or looking to refresh your knowledge, this guide will cover the fundamental aspects of the crypto market. 18 | 19 | ## 1. Cryptocurrency? 20 | 21 | Cryptocurrency is a digital or virtual form of currency that uses cryptography for security. 22 | Unlike traditional fiat currencies issued by central banks, cryptocurrencies operate independently of any central authority. The most well-known cryptocurrency is Bitcoin, but there are thousands of other cryptocurrencies available today, each with its own unique features and purposes. 23 | 24 | ## 2. Blockchain Technology 25 | 26 | Blockchain technology is the underlying foundation of most cryptocurrencies. 27 | It is a decentralized and distributed ledger that records transactions across multiple computers or nodes. Each transaction is grouped into a block and added to a chain of previous blocks, creating an immutable record of all transactions. This technology ensures transparency, security, and eliminates the need for intermediaries in financial transactions. 28 | 29 | ## 3. Decentralization 30 | 31 | Decentralization is a key characteristic of cryptocurrencies. 32 | Unlike traditional banking systems where a central authority controls transactions, cryptocurrencies operate on a peer-to-peer network. This means that transactions occur directly between users, without the need for intermediaries. Decentralization enhances security, privacy, and removes single points of failure. 33 | 34 | ## 4. Cryptocurrency Exchanges 35 | 36 | Cryptocurrency exchanges are platforms where users can buy, sell, and trade cryptocurrencies. 37 | These exchanges act as intermediaries, facilitating the conversion between cryptocurrencies and fiat currencies. It's important to choose a reputable and secure exchange, as the security of your funds relies on the exchange's infrastructure. 38 | 39 | ## 5. Wallets and Security 40 | 41 | Cryptocurrency wallets are digital tools used to store, send, and receive cryptocurrencies. 42 | There are two main types of wallets: hot wallets and cold wallets. Hot wallets are connected to the internet and are convenient for frequent transactions, while cold wallets are offline and offer enhanced security for long-term storage. It's crucial to keep your wallet secure by using strong passwords, enabling two-factor authentication, and regularly updating your software. 43 | 44 | ## 6. Market Volatility 45 | 46 | The crypto market is known for its high volatility, with prices experiencing significant fluctuations over short periods. 47 | Cryptocurrency prices are influenced by various factors, including market demand, regulatory developments, technological advancements, and investor sentiment. It's important to be aware of the risks associated with volatility and make informed decisions when participating in the market. 48 | 49 | ## 7. Crypto Trading Strategies 50 | 51 | Crypto trading involves buying and selling cryptocurrencies to take advantage of price movements. 52 | Various trading strategies, such as day trading, swing trading, and long-term investing, can be employed based on individual preferences and risk tolerance. It's crucial to conduct thorough research, analyze market trends, and develop a sound trading strategy to increase the chances of success. 53 | 54 | ## 8. Initial Coin Offerings (ICOs) 55 | 56 | Initial Coin Offerings (ICOs) are fundraising events in which new cryptocurrencies or tokens are sold to investors. 57 | ICOs allow project teams to raise capital for their ventures, and investors to participate in potentially lucrative opportunities. However, ICOs can be risky, as some projects may fail to deliver on their promises. Conducting due diligence and evaluating the credibility of the project is essential before investing in an ICO. 58 | 59 | ## 9. Regulatory Environment 60 | 61 | The regulatory landscape surrounding cryptocurrencies varies across different countries and jurisdictions. 62 | Governments and regulatory bodies are actively developing 63 | -------------------------------------------------------------------------------- /Education/cryptocurrencies-introduction.md: -------------------------------------------------------------------------------- 1 | 5 | 6 | # Blockchain and Cryptocurrency 7 | 8 | ## What is Blockchain? 9 | 10 | Blockchain is a technology that enables the secure sharing of information. Transactions are recorded in an account book called a ledger. A blockchain is a type of distributed database or ledger. The power to update a blockchain is distributed between the nodes, or participants, of a public or private computer network. This is known as _distributed ledger technology_, or DLT. Nodes are incentivized with digital tokens or currency to make updates to blockchains. 11 | Blockchain allows for the permanent, immutable, and transparent recording of data and transactions. This, in turn, makes it possible to exchange anything that has value, whether that is a physical item or something less tangible. 12 | 13 | A blockchain has three central attributes: 14 | 15 | 1. First, a blockchain database must be **cryptographically secure**. In order to access or add data on the database, you need two cryptographic keys: a _public key_, which is basically the address in the database, and the _private key_, which is a personal key that must be authenticated by the network. 16 | 2. Next, a blockchain is a digital log or database of transactions, meaning it happens **fully online**. 17 | 3. And finally, a blockchain is a database that is **shared across a public or private network**. 18 | > One of the most well-known public blockchain networks is the _Bitcoin blockchain_. Anyone can open a Bitcoin wallet or become a node on the network. Other blockchains may be private networks. These are more applicable to banking and fintech, where people need to know exactly who is participating, who has access to data, and who has a private key to the database. Other types of blockchains include _consortium blockchains_ and _hybrid blockchains_, both of which combine different aspects of public and private blockchains. 19 | 20 | ## How does Blockchain work? 21 | 22 | A blockchain is a distributed database that maintains a continuously growing list of ordered records, called blocks. These blocks are linked using cryptography. Each block contains a _cryptographic hash_ of the previous block, a _timestamp_, and _transaction data_. 23 | 24 | The blockchain collects transaction information and enters it into a block, like a cell in a spreadsheet. Once it is full, the information is run through an encryption algorithm, which creates a hexadecimal number called the hash. 25 | 26 | The hash is then entered into the following block header and encrypted with the other information in the block. This creates a series of blocks that are chained together. Altering any one block will cause alteration of all subsequent blocks, indicating a breach in security. A blockchain is distributed, which means multiple copies are saved on many machines, and they must all match for it to be valid. Therefore, blockchain technology is considered highly secure and protects against tampering, fraud and cybercrime. It also saves time and costs as transactions do not need to be verified or overseen by a central authority. 27 | 28 | > Blockchain technology is considered a major part of Web 3.0 development. Web3 is an idea for a new iteration of the World Wide Web which incorporates concepts such as decentralization, blockchain technologies, and token-based economics. It goes by the motto of 'Read-Write-Own'. 29 | 30 | ## Introduction to Cryptocurrencies 31 | 32 | A cryptocurrency is a digital or virtual currency secured by cryptography, which makes it nearly impossible to counterfeit or double-spend. Many cryptocurrencies are decentralized networks based on blockchain technology. 33 | A defining feature of cryptocurrencies is that they are generally not issued by any central authority, rendering them theoretically immune to government interference or manipulation. 34 | They enable secure online payments without the use of third-party intermediaries. "Crypto" refers to the various encryption algorithms and cryptographic techniques that safeguard these entries, such as elliptical curve encryption, public-private key pairs, and hashing functions. 35 | 36 | Some popular cryptocurrencies: 37 | 38 | 1. **Bitcoin (BTC):** 39 | Bitcoin was the world’s first cryptocurrency, with its origins dating back to 2008, and remains the best-known type of crypto. In January 2022, Bitcoin was the cryptocurrency with the largest market cap, at US $896 billion. 40 | 2. **Ether (ETH):** 41 | Ether is the cryptocurrency that runs on the _Ethereum_ blockchain. Unlike Bitcoin, Ether is uncapped, meaning that an infinite number of coins can theoretically be created. Ethereum also supports **smart contracts**, which are programs that run on the Ethereum blockchain and are executed automatically when certain conditions are met. 42 | 3. **Binance Coin (BNB):** 43 | Binance Coin is native to Binance, the world’s largest cryptocurrency exchange as of 2021. To ensure its value remains stable, Binance destroys or “burns” a fixed percentage of the coins in circulation. 44 | 4. **Tether (USDT):** 45 | Tether is a type of _stablecoin_, designed to have a less-volatile price by being linked to an external asset. In this case, each coin is backed by an equivalent number of US dollars, which keeps it from experiencing the same kind of pricing volatility that other cryptocurrencies face. 46 | 5. **Solana (SOL):** 47 | SOL is the native coin of the Solana platform, which functions on a blockchain system, just like Ethereum and Bitcoin. Solana’s network can perform a whopping 50,000 transactions per second, making this platform especially attractive to investors looking to trade quickly. 48 | 49 | 50 | 51 | ## Pros and Cons of Investing in Cryptocurrency 52 | 53 | Cryptocurrencies were introduced with the intent to revolutionize financial infrastructure. As with every revolution, however, there are tradeoffs involved. At the current stage of development for cryptocurrencies, there are many differences between the theoretical ideal of a decentralized system with cryptocurrencies and its practical implementation. 54 | 55 | Some advantages and disadvantages of cryptocurrencies are as follows: 56 | 57 | ### Advantages: 58 | 59 | 1. **Removes single points of failure.** In this system, centralized intermediaries, such as banks and monetary institutions, are not necessary to enforce trust and police transactions between two parties. 60 | 2. **Easier to transfer funds between parties** 61 | 3. **Removes third parties** 62 | 4. **Can be used to generate returns.** Cryptocurrency investments can generate profits. Cryptocurrency markets have skyrocketed in value over the past decade, at one point reaching almost $2 trillion. 63 | 5. **Remittances are streamlined.** Cryptocurrencies serve as intermediate currencies to streamline money transfers across borders. A fiat currency is converted to Bitcoin, transferred across borders, and subsequently converted to the destination fiat currency. This method streamlines the money transfer process and makes it cheaper. 64 | 65 | ### Disadvantages: 66 | 67 | 1. **Transactions are pseudonymous.** Though they claim to be an anonymous form of transaction, they leave a digital trail that agencies like the Federal Bureau of Investigation (FBI) can investigate. This opens up the possibility that governments and authorities (and others) can track financial transactions. 68 | 2. **Pseudonymity allows for criminal uses** 69 | 3. **Have become highly centralized.** In theory, cryptocurrencies are meant to be decentralized, their wealth distributed between many parties on a blockchain. In reality, ownership is highly concentrated. For example, just 100 addresses hold roughly 12% of circulating bitcoin and total value. 70 | 4. **Off-chain security issues.** Though cryptocurrency blockchains are highly secure, off-chain crypto-related key storage repositories, such as exchanges and wallets, can be hacked. 71 | 5. **Prices are very volatile** 72 | -------------------------------------------------------------------------------- /Education/investment-strategies.md: -------------------------------------------------------------------------------- 1 | # Investment Strategies for Stocks and Cryptocurrencies 2 | 3 | This is a introduction of different investment strategies for stocks and cryptocurrencies. It aims to assist beginners in developing their investment approach by explaining the principles and considerations behind each strategy. Please note that investment strategies should be tailored to individual goals and risk tolerance. 4 | 5 | ## 1. Value Investing 6 | 7 | Value investing involves identifying stocks or cryptocurrencies that are undervalued compared to their intrinsic worth. Key principles and considerations include: 8 | 9 | - **Fundamental Analysis**: Conduct a thorough analysis of financial statements, earnings, assets, and other indicators to assess the true value of an investment. 10 | 11 | - **Margin of Safety**: Seek investments that are priced below their intrinsic value, providing a margin of safety against potential market fluctuations. 12 | 13 | - **Long-Term Outlook**: Value investing often focuses on long-term investment horizons, allowing time for the market to recognize the underlying value. 14 | 15 | ## 2. Growth Investing 16 | 17 | Growth investing focuses on identifying stocks or cryptocurrencies with strong growth potential. Consider the following principles and considerations: 18 | 19 | - **Market Analysis**: Identify industries or sectors with promising growth prospects, such as technology, healthcare, or emerging markets. 20 | 21 | - **Company Analysis**: Assess the growth potential of individual companies, including factors like revenue growth, market share, and innovation. 22 | 23 | - **Risk Management**: Growth investing often involves higher risk due to potential market volatility. Diversification and risk management strategies are important. 24 | 25 | ## 3. Dollar-Cost Averaging 26 | 27 | Dollar-cost averaging is an investment strategy that involves regularly investing a fixed amount of money into stocks or cryptocurrencies at predetermined intervals. Key principles and considerations include: 28 | 29 | - **Consistent Investments**: Invest a fixed amount on a regular basis, regardless of market conditions. This approach helps reduce the impact of short-term market fluctuations. 30 | 31 | - **Averaging Out Volatility**: By investing at different price points over time, the strategy aims to achieve an average purchase price that smooths out market volatility. 32 | 33 | - **Discipline and Patience**: Dollar-cost averaging requires discipline and a long-term perspective, as the strategy benefits from the compounding effect over time. 34 | 35 | Remember, these are just a few investment strategies among many others. It's important to conduct thorough research, understand your risk tolerance, and align your investment strategy with your financial goals. 36 | -------------------------------------------------------------------------------- /Education/tax-implications.md: -------------------------------------------------------------------------------- 1 | # Tax Implications of Investing in Stocks and Cryptocurrencies 2 | 3 | This gives a general overview of the tax considerations associated with investing in stocks and cryptocurrencies. It is important to note that tax regulations and laws can vary by country and jurisdiction. For specific guidance, consult with a tax professional or accountant. 4 | 5 | ## Capital Gains Tax 6 | 7 | When you sell stocks or cryptocurrencies at a profit, you may be subject to capital gains tax. Capital gains are generally categorized as either short-term or long-term, based on the holding period. 8 | 9 | - Short-term Capital Gains: These are profits from assets held for one year or less and are typically taxed at the individual's ordinary income tax rate. It's important to account for these gains when filing your annual tax return. 10 | 11 | - Long-term Capital Gains: If you hold stocks or cryptocurrencies for more than one year before selling, the resulting profits may qualify for long-term capital gains tax rates. Long-term capital gains are often taxed at lower rates than ordinary income. However, specific tax rates and rules vary depending on your country and income level. 12 | 13 | ## Tax Reporting Requirements 14 | 15 | Investors in stocks and cryptocurrencies are generally required to report their investment activities for tax purposes. Here are a few key reporting considerations: 16 | 17 | - Form 1099: In some countries, such as the United States, brokers or exchanges may issue Form 1099 to report investment-related income and transactions. These forms provide important information for calculating your tax liabilities. 18 | 19 | - Cryptocurrency Reporting: Some jurisdictions require specific reporting of cryptocurrency transactions. For example, you may need to report cryptocurrency trades, exchanges, or other taxable events. Familiarize yourself with the reporting requirements in your country. 20 | 21 | - Record-Keeping: It is essential to maintain accurate records of your investment activities, including purchase dates, sale dates, and transaction details. These records will help you accurately report capital gains or losses when filing your taxes. 22 | 23 | ## Potential Deductions 24 | 25 | In certain cases, investors may be eligible for deductions related to their investment activities. Here are a few potential deductions to consider: 26 | 27 | - Investment Expenses: Expenses related to investment activities, such as brokerage fees, advisory fees, or certain research expenses, may be deductible. Consult with a tax professional to determine which expenses qualify for deductions in your jurisdiction. 28 | 29 | - Capital Losses: If you incur capital losses from selling stocks or cryptocurrencies at a loss, you may be able to offset those losses against your capital gains. This can help reduce your overall tax liability. Understand the rules and limitations surrounding capital loss deductions in your country. 30 | -------------------------------------------------------------------------------- /Education/types-of-cryptocurrencies.md: -------------------------------------------------------------------------------- 1 | # Cryptocurrency Types Overview 2 | 3 | Cryptocurrencies have revolutionized the digital financial landscape, offering unique purposes, functionalities, and use cases. This document provides an overview of various types of cryptocurrencies to help beginner investors understand the crypto landscape. 4 | 5 | ## Bitcoin (BTC) 6 | 7 | Bitcoin is the pioneering cryptocurrency that serves as a decentralized digital currency. Its primary purposes include being a store of value and a medium of exchange. Bitcoin has gained recognition as "digital gold" due to its limited supply and potential as a hedge against inflation. It is also used for remittances and as a speculative investment. 8 | 9 | ## Altcoins 10 | 11 | Altcoins refer to all cryptocurrencies other than Bitcoin. They offer different features and use cases. Some prominent altcoins include Ethereum (ETH), Ripple (XRP), Litecoin (LTC), and Cardano (ADA). Altcoins aim to provide additional functionalities beyond being a digital currency. For example, Ethereum introduced smart contracts, enabling developers to build decentralized applications (DApps) and create their own tokens. 12 | 13 | ## Stablecoins 14 | 15 | Stablecoins are cryptocurrencies designed to minimize price volatility by pegging their value to an external asset, usually a fiat currency like the US dollar. They offer stability and are often used as a medium of exchange and a store of value within the crypto ecosystem. Stablecoins allow users to mitigate exposure to the volatility of other cryptocurrencies while leveraging the benefits of blockchain technology. Examples include Tether (USDT), USD Coin (USDC), and Dai (DAI). 16 | 17 | ## Utility Tokens 18 | 19 | Utility tokens are cryptocurrencies that provide access to specific products, services, or platforms. They are typically distributed during an Initial Coin Offering (ICO) or a Token Generation Event (TGE) to raise funds for a project. Utility tokens grant holders certain privileges or rights within the associated ecosystem. These tokens can be used for voting, obtaining discounted services, or accessing exclusive features within a decentralized application or platform. 20 | 21 | ## Security Tokens 22 | 23 | Security tokens represent ownership in an underlying asset, such as equity in a company, real estate, or commodities. They are subject to securities regulations and offer investors legal rights similar to traditional securities. Security tokens leverage blockchain technology to provide benefits such as fractional ownership, increased liquidity, and faster settlement times. Compliance with regulatory requirements is crucial for security token offerings (STOs). 24 | 25 | ## Privacy Coins 26 | 27 | Privacy coins focus on enhancing transaction privacy and anonymity. They utilize cryptographic techniques to obfuscate transaction details, making it challenging to trace or link transactions to specific individuals. Examples include Monero (XMR), Zcash (ZEC), and Dash (DASH). Privacy coins cater to users who prioritize confidentiality and fungibility in their transactions, although their increased privacy features have raised concerns about potential misuse. 28 | 29 | It's essential for beginner investors to conduct thorough research and due diligence before investing in cryptocurrencies. Understanding the different types of cryptocurrencies and their respective purposes, functionalities, and use cases can help investors make informed decisions based on their investment goals and risk appetite. Stay updated with the latest news and developments in the cryptocurrency market to navigate this rapidly evolving landscape effectively. 30 | 31 | **Note:** This document provides a general overview and should not be considered financial or investment advice. Always consult with a qualified professional before making investment decisions. 32 | -------------------------------------------------------------------------------- /GSSoC-CONTRIBUTORS.md: -------------------------------------------------------------------------------- 1 | # Contributors and Colleges 2 | 3 | ## Introduction 4 | 5 | This file has been created for the contributors of GSSoC 2023 to begin their journey with open source. It lists the contributors and their respective colleges. 6 | 7 | ## Instructions 8 | 9 | If you are participating in GSSoC 2023 and would like to contribute to this project, please follow the steps mentioned in the [CONTRIBUTING.md](CONTRIBUTING.md) file. 10 | 11 | Please add your name and college above if you are a contributor: 12 | 13 | ## Contributors 14 | 15 | | Sr. No. | Contibutor's Name | Contributor's College | 16 | | :------ | :----------------------- | :-------------------------------------------------------------------------- | 17 | | 1. | Kapil | Amity University, Noida | 18 | | 2. | Ridhiman Kaur Dhindsa | IIT Guwahati | 19 | | 3. | Tushar Banik | IIT Guwahati | 20 | | 4. | Shivani | JSS Science and Technology University, Mysore | 21 | | 5. | Manash | Nitte Meenakshi Institute of Technology, Bangalore | 22 | | 6. | Mahendra Dani | VIT Bhopal University | 23 | | 7. | Kartikay Asija | GL Bajaj, Noida | 24 | | 8. | Mukul Ojha | MBM university, Jodhpur | 25 | | 9. | Pavithra P | National Institute of Technology Surathkal, Karnataka | 26 | | 10. | Tushar Verma | National Institute of Technology, Srinagar | 27 | | 11. | Amita Singh | Sharda University, Greater Noida | 28 | | 12. | Surav Krishna Shrestha | IOE, Pulchowk Campus, Tribhuvan University, Nepal | 29 | | 13. | Krishna Kalani | Sarvajanik College of Engineering and Technology , Surat | 30 | | 14. | Raghav Kumar Jha | Maharaja Agrasen Institute of Technology, New Delhi | 31 | | 15. | Shreya Bhardwaj | I.T.S Engineering College, Greater Noida | 32 | | 16. | Ganeshprasad Revadi | R V College of Engineering | 33 | | 17. | Sambhav kaushik | Banaras Hindu University, Varanasi | 34 | | 18. | Bharatiya Ayush | RNGPIT, Bardoli | 35 | | 19. | Atharvashirsh Tiwary | I2IT, Pune | 36 | | 20. | Manan Sharma | Thapar Institute of Engineering & Technology, Patiala | 37 | | 21. | Prakhar Kumar Srivastava | NIT Agartala | 38 | | 22. | Ankit Anand | Kalinga Institute Of Industrial Technology, Bhubaneswar | 39 | | 23. | Sagnik Das | ABV-IIITM Gwalior | 40 | | 24. | Sneha Kumari | Galgotias University , Greater Noida | 41 | | 25. | Vedant Bande | IIIT Jabalpur | 42 | | 26. | Saloni Singh | Galgotias University , Greater Noida | 43 | | 27. | Laxmi | Sharda University, Greater Noida | 44 | | 28. | Akshaya | Andhra University, Visakhapatnam | 45 | | 29. | Abhishek Kumar Verma | Haldia Institute Of Technology, West Bengal | 46 | | 30. | Angel Mba | University of Nigeria, Nsukka | 47 | | 31. | Saloni Lathwariya | Maa Shakumbhari University, Saharanpur | 48 | | 32. | Aryan Rana | Vellore Institute of Technology (VIT) | 49 | | 33. | Tanbir Ali | Aliah University, Kolkata | 50 | | 34. | Rakhi M. Bhagwat | K.K.Wagh Institute of Engineering Education & Research, Nashik, Maharashtra | 51 | | 35. | Vaibhav Maurya | IMRT Business School, Lucknow, Uttar Pradesh | 52 | | 36. | Atharva Raut | NBN Sinhgad Institute of Technical Campus, Pune | 53 | | 37. | Shreya Gupta | Pranveer Singh Institute of Technology, Kanpur | 54 | | 38. | Ayush Rathore | Dr.B.R. Ambedkar NIT Jalandhar | 55 | | 39. | Md Shadab Alam | National Institute of Technology Karnataka | 56 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Stoccoin-Website 2 | 3 | [Under Development]
4 | 5 |
6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 |
16 | This is a web application for trading stocks and crypto, as well as displaying news feeds and real-time data processing for stock and crypto prices. 17 | 18 | ## Tech Stack 19 | 20 | The technology stack used for this project is: 21 | 22 | - Frontend: React.js, Tailwind CSS 23 | - Backend: Node.js, Express.js, MongoDB, Firebase 24 | 25 | ## Getting started 26 | 27 | To get started with this project, you'll need to follow these steps: 28 | 29 | 1. Install Node.js and MongoDB on your local machine. 30 | 2. Clone this repository to your local machine. 31 | 3. Retrieve the API key from the official [Firebase website](https://firebase.google.com/) and use it in [auth.js](https://github.com/Stoccoin-Official/Stoccoin-Website/blob/main/app/src/firebase/auth.js). 32 | 4. Install the project dependencies by running `npm install` in the app directory. 33 | 5. Start the app by running `npm run dev` in the directory (`cd app`). 34 | 6. Open your web browser and navigate to `http://localhost:5173`. 35 | 36 | ## Contributing 37 | 38 | We welcome contributions from anyone who is interested in improving this project. If you'd like to contribute, here are some ways you can get started: 39 | 40 | [Click here for the steps to Contribute](./CONTRIBUTING.md) 41 | 42 | ## Issues 43 | 44 | Here are some issues that need to be addressed in this project: 45 | 46 | - Improve the UI design for better user experience. 47 | - Add support for more cryptocurrencies and stock exchanges. 48 | - Implement user authentication and authorization for secure trading. 49 | - Optimize the application for performance and scalability. 50 | - Improve error handling and logging for better debugging. 51 | 52 | If you're interested in working on any of these issues, please let us know by submitting a pull request or reaching out to us. 53 | 54 | > Contributors must finish their work for an issue within 4-5 days if they are either assigned or have shown interest in solving the issue to avoid conflicts. 55 | 56 | ## Connect With Us 57 | 58 |

59 | 60 | [![Twitter](https://img.shields.io/badge/Twitter-%231DA1F2.svg?style=for-the-badge&logo=Twitter&logoColor=white)](https://twitter.com/stoccoinco) 61 | [![LinkedIn](https://img.shields.io/badge/linkedin-%230077B5.svg?style=for-the-badge&logo=linkedin&logoColor=white)](https://www.linkedin.com/company/stoccoin/) 62 | [![Instagram](https://img.shields.io/badge/Instagram-%23E4405F.svg?style=for-the-badge&logo=Instagram&logoColor=white)](https://www.instagram.com/stoccoin/) 63 | 64 |

65 | 66 | ### Join our Discord Server: 67 | 68 |

69 | 70 | We have a Discord server for contributors to the Stoccoin's website on GitHub. Join our community of developers, designers, marketers, and other contributors to share your skills, collaborate on code, provide feedback, and contribute to the Stoccoin's project in meaningful ways. 71 | 72 | [Click here to join our Discord server](https://discord.gg/XVE7eaS9AA) 73 | 74 |

75 | 76 | ## License 77 | 78 | This project is licensed under the Affero General Public License v3.0. See the [LICENSE](LICENSE) file for details. 79 | -------------------------------------------------------------------------------- /app/.gitignore: -------------------------------------------------------------------------------- 1 | # Logs 2 | logs 3 | *.log 4 | npm-debug.log* 5 | yarn-debug.log* 6 | yarn-error.log* 7 | pnpm-debug.log* 8 | lerna-debug.log* 9 | 10 | node_modules 11 | dist 12 | dist-ssr 13 | *.local 14 | 15 | # Editor directories and files 16 | .vscode/* 17 | !.vscode/extensions.json 18 | .idea 19 | .DS_Store 20 | *.suo 21 | *.ntvs* 22 | *.njsproj 23 | *.sln 24 | *.sw? 25 | 26 | # Environment directories 27 | .env 28 | .env.local 29 | .env.development.local 30 | .env.test.local 31 | .env.production.local 32 | -------------------------------------------------------------------------------- /app/index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | Stoccoin 8 | 9 | 10 |
11 | 12 | 13 | 14 | -------------------------------------------------------------------------------- /app/package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "app", 3 | "private": true, 4 | "version": "0.0.0", 5 | "type": "module", 6 | "scripts": { 7 | "dev": "vite", 8 | "build": "vite build", 9 | "preview": "vite preview" 10 | }, 11 | "dependencies": { 12 | "@fortawesome/fontawesome-svg-core": "^6.4.0", 13 | "@fortawesome/free-brands-svg-icons": "^6.4.0", 14 | "@fortawesome/react-fontawesome": "^0.2.0", 15 | "@headlessui/react": "^1.7.13", 16 | "@heroicons/react": "^2.0.16", 17 | "alpinejs": "^3.12.0", 18 | "axios": "^1.4.0", 19 | "firebase": "^10.0.0", 20 | "nodemailer": "^6.9.2", 21 | "react": "^18.2.0", 22 | "react-chartjs-2": "^5.2.0", 23 | "react-countup": "^6.4.2", 24 | "react-dom": "^18.2.0", 25 | "react-icons": "^4.10.1", 26 | "react-refresh": "^0.14.0", 27 | "react-router-dom": "^6.11.2", 28 | "react-scroll-trigger": "^0.6.14", 29 | "react-toastify": "^9.1.3" 30 | }, 31 | "devDependencies": { 32 | "@types/react": "^18.0.28", 33 | "@types/react-dom": "^18.0.11", 34 | "@vitejs/plugin-react": "^3.1.0", 35 | "autoprefixer": "^10.4.14", 36 | "postcss": "^8.4.21", 37 | "tailwindcss": "^3.2.7", 38 | "vite": "^4.2.0" 39 | } 40 | } 41 | -------------------------------------------------------------------------------- /app/postcss.config.cjs: -------------------------------------------------------------------------------- 1 | module.exports = { 2 | plugins: { 3 | tailwindcss: {}, 4 | autoprefixer: {}, 5 | }, 6 | }; 7 | -------------------------------------------------------------------------------- /app/public/crypto-header-image.svg: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /app/public/github.svg: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /app/public/header.svg: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /app/public/koo-icon.svg: -------------------------------------------------------------------------------- 1 | koo 2 | -------------------------------------------------------------------------------- /app/public/login.svg: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /app/public/logo.svg: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /app/public/sitemap.xml: -------------------------------------------------------------------------------- 1 | 2 | 6 | 7 | http://localhost:5173/Login 8 | 2023-07-19T11:30:26+01:00 9 | 1.0 10 | 11 | 12 | http://localhost:5173/Login# 13 | 2023-07-19T11:30:26+01:00 14 | 0.8 15 | 16 | 17 | http://localhost:5173/SignUp 18 | 2023-07-19T11:30:26+01:00 19 | 1.0 20 | 21 | 22 | http://localhost:5173/Dashboard 23 | 2023-07-19T11:30:26+01:00 24 | 0.8 25 | 26 | 27 | http://localhost:5173/Stocks 28 | 2023-07-19T11:30:26+01:00 29 | 1.0 30 | 31 | 32 | http://localhost:5173/Cryptocurrencies 33 | 2023-07-19T11:30:26+01:00 34 | 1.0 35 | 36 | 37 | http://localhost:5173/News 38 | 2023-07-19T11:30:26+01:00 39 | 1.0 40 | 41 | 42 | http://localhost:5173/NFT 43 | 2023-07-19T11:30:26+01:00 44 | 1.0 45 | 46 | 47 | http://localhost:5173/Trade 48 | 2023-07-19T11:30:26+01:00 49 | 1.0 50 | 51 | 52 | http://localhost:5173/Institutional 53 | 2023-07-19T11:30:26+01:00 54 | 1.0 55 | 56 | 57 | http://localhost:5173/Derivatives 58 | 2023-07-19T11:30:26+01:00 59 | 1.0 60 | 61 | 62 | http://localhost:5173/Support 63 | 2023-07-19T11:30:26+01:00 64 | 1.0 65 | 66 | 67 | -------------------------------------------------------------------------------- /app/public/stocks-header-image.svg: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /app/public/trade-header-image.svg: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /app/src/App.css: -------------------------------------------------------------------------------- 1 | * { 2 | box-sizing: border-box; 3 | padding: 0%; 4 | margin: 0%; 5 | } 6 | 7 | .logo { 8 | height: 6em; 9 | padding: 1.5em; 10 | will-change: filter; 11 | transition: filter 300ms; 12 | } 13 | .logo:hover { 14 | filter: drop-shadow(0 0 2em #646cffaa); 15 | } 16 | .logo.react:hover { 17 | filter: drop-shadow(0 0 2em #61dafbaa); 18 | } 19 | 20 | @keyframes logo-spin { 21 | from { 22 | transform: rotate(0deg); 23 | } 24 | to { 25 | transform: rotate(360deg); 26 | } 27 | } 28 | 29 | @media (prefers-reduced-motion: no-preference) { 30 | a:nth-of-type(2) .logo { 31 | animation: logo-spin infinite 20s linear; 32 | } 33 | } 34 | 35 | .card { 36 | padding: 2em; 37 | } 38 | 39 | .read-the-docs { 40 | color: #888; 41 | } 42 | 43 | .active { 44 | width: fit-content; 45 | position: relative; 46 | } 47 | .active::after { 48 | display: block; 49 | content: ""; 50 | position: absolute; 51 | height: 3px; 52 | background-color: #4f46e5; 53 | border-radius: 9999px; 54 | width: 100%; 55 | transform: scaleX(1); 56 | transition: transform 0.5s; 57 | transform-origin: center; 58 | } 59 | 60 | .spinner { 61 | position: absolute; 62 | top: 50%; 63 | left: 50%; 64 | animation: spin infinite 1s linear; 65 | } 66 | 67 | @keyframes spin { 68 | from { 69 | transform: rotate(0deg); 70 | } 71 | to { 72 | transform: rotate(360deg); 73 | } 74 | } 75 | -------------------------------------------------------------------------------- /app/src/App.jsx: -------------------------------------------------------------------------------- 1 | import { lazy, Suspense, useEffect, useState } from "react"; 2 | import { BrowserRouter, Routes, Route } from "react-router-dom"; 3 | import "./App.css"; 4 | import NotFound from "./components/NotFound"; 5 | import { FaCircleNotch } from "react-icons/fa"; 6 | import Navbar from "./components/Navbar"; 7 | import Footer from "./components/Footer"; 8 | const Homepage = lazy(() => import("./pages/Homepage")); 9 | const Dashboard = lazy(() => import("./pages/Dashboard")); 10 | const Stocks = lazy(() => import("./pages/Stocks")); 11 | const Cryptocurrencies = lazy(() => import("./pages/Cryptocurrencies")); 12 | const News = lazy(() => import("./pages/News")); 13 | const Trade = lazy(() => import("./pages/Trade")); 14 | const Institutional = lazy(() => import("./pages/Institutional")); 15 | const Derivatives = lazy(() => import("./pages/Derivatives")); 16 | const NFT = lazy(() => import("./pages/NFT")); 17 | const Support = lazy(() => import("./pages/Support")); 18 | const SignUp = lazy(() => import("./pages/SignUp")); 19 | const Login = lazy(() => import("./pages/Login")); 20 | import { auth } from "./firebase/auth"; 21 | 22 | const App = () => { 23 | const [user, setUser] = useState(null); 24 | const [darkMode, setDarkMode] = useState(false); 25 | 26 | useEffect(() => { 27 | const authorizeUser = auth.onAuthStateChanged((authUser) => { 28 | if (authUser) { 29 | setUser(authUser); 30 | } else { 31 | setUser(null); 32 | } 33 | }); 34 | 35 | return () => { 36 | authorizeUser(); 37 | }; 38 | }, [user]); 39 | 40 | // Always show the homepage regardless of user login status 41 | return ( 42 |
43 | 44 |
45 |
46 | 47 | } 49 | > 50 | 51 | } /> 52 | } /> 53 | } 56 | /> 57 | } 60 | /> 61 | } /> 62 | } /> 63 | } /> 64 | } /> 65 | } /> 66 | } /> 67 | } /> 68 | } /> 69 | } /> 70 | 71 | 72 |
73 |
74 |
75 | 76 |
77 | ); 78 | }; 79 | 80 | export default App; 81 | -------------------------------------------------------------------------------- /app/src/assets/index.js: -------------------------------------------------------------------------------- 1 | export { default as loginIMG } from "./loginIMG.svg"; 2 | export { default as signupIMG } from "./signupIMG.svg"; 3 | export { default as koo } from "./koo-icon.svg"; 4 | export { default as koo2 } from "./koo-icon-hover.svg"; 5 | -------------------------------------------------------------------------------- /app/src/assets/koo-icon-hover.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 12 | 13 | koo 14 | 16 | 18 | 20 | 22 | 23 | 24 | 26 | -------------------------------------------------------------------------------- /app/src/assets/koo-icon.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 12 | 13 | koo 14 | 16 | 18 | 20 | 22 | 23 | 24 | 26 | -------------------------------------------------------------------------------- /app/src/assets/loginIMG.svg: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /app/src/assets/react.svg: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /app/src/components/Accordion.jsx: -------------------------------------------------------------------------------- 1 | import React, { useState } from "react"; 2 | 3 | function Accordion() { 4 | const faq = [ 5 | { 6 | que: "Do you have free plans?", 7 | ans: "Yea we have free plans", 8 | }, 9 | { 10 | que: "Do you have free plans?", 11 | ans: "Yea we have free plans", 12 | }, 13 | { 14 | que: "Do you have free plans?", 15 | ans: "Yea we have free plans", 16 | }, 17 | { 18 | que: "Do you have free plans?", 19 | ans: "Yea we have free plans", 20 | }, 21 | ]; 22 | 23 | return ( 24 |
25 | 30 |
31 |
32 |

33 | Have any questions? 34 |

35 |

36 | Frequently Asked Questions 37 |

38 |
39 | {faq.map((member, index) => ( 40 | 41 | ))} 42 |
43 |

44 | Still have any questions? 45 | 49 | Contact us 50 | 51 |

52 |
53 |
54 |
55 | ); 56 | } 57 | function QnA({ faq }) { 58 | const [show, setshow] = useState(false); 59 | return ( 60 |
61 |
setshow(!show)}> 62 |
65 |
66 |
67 |

68 | {faq.que} 69 |

70 |

73 | {faq.ans} 74 |

75 |
76 |
77 | 85 | 92 | 93 | 101 | 108 | 109 |
110 |
111 |
112 |
113 |
114 | ); 115 | } 116 | 117 | export default Accordion; 118 | -------------------------------------------------------------------------------- /app/src/components/ContactForm.jsx: -------------------------------------------------------------------------------- 1 | import { React, useState } from "react"; 2 | 3 | export default function App() { 4 | const [name, setName] = useState(""); 5 | const [email, setEmail] = useState(""); 6 | const [message, setMessage] = useState(""); 7 | 8 | const handleSubmit = async (e) => { 9 | e.preventDefault(); 10 | 11 | const data = { 12 | name, 13 | email, 14 | message, 15 | }; 16 | 17 | const res = await fetch("http://localhost:3000/mail", { 18 | method: "POST", 19 | headers: { 20 | "Content-Type": "application/json", 21 | }, 22 | body: JSON.stringify(data), 23 | }); 24 | }; 25 | 26 | return ( 27 |
31 |
32 |
33 |

34 | Get in Touch 35 |

36 |
37 | Reach out to us with any questions or feedback 38 |
39 |
40 |
41 | 42 |
43 |
44 |
45 |
46 |
47 | 48 | Full Name 49 | 50 | setName(e.target.value)} 55 | /> 56 |
57 |
58 | 59 | Email 60 | 61 | setEmail(e.target.value)} 65 | /> 66 |
67 |
68 | 69 | Message 70 | 71 |