OctoFi dApp

✨ OctoFi dApp is a dashboard for tracking your DeFi portfolio, finding new investment opportunities, buy / sell directly and wrap your tentacles around a sea of gains. We built this interface with our mission in mind, creating something simple to use and adding our salt & pepper to the DeFi revolution ✨

Launch OctoFi dApp

Features

• 🔩 Simple: Even a shrimp understands

• 📊 Overview: We help you to get a better, real-time overview of your investments

• 💪 Powerful: Invest in over 6300 DeFi opportunities

• 📱 Responsive: Made mobile responsive

• 🎉 Live: Deployed to Github Pages and secured with Cloudflare

Community & Feedback

OctoFi Community

Changelog

Changelog

Roadmap

Roadmap Post

Development Overview

Development Priorities

Upcoming Releases

Contributing

Please read the CONTRIBUTING.md file for details on how you can get involved in the project as well as the process for submitting bugs and pull requests.

Getting Started

These instructions will get your copy of the project up and running on your local machine for development and testing purposes.

Installing

Create a fork of this repository, clone it, and install the dependencies.

git clone https://github.com/{your-username}/octofi-app-aquafarm.git
cd octofi-app-aquafarm
yarn

yarn start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser. The page will reload if you make edits.
You will also see the lint errors in the console.

yarn test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

yarn build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance. The build is minified and the filenames include the hashes.
Your app is ready to be deployed! See the section about deployment for more information.

yarn deploy

Builds the app for production using the yarn build command.
Then it commits the output to the gh-pages branch so it can be deployed with GitHub Pages.

yarn eject

Note: this is a one-way operation. Once you eject, you can’t go back! If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project. Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own. You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Use as a template

If you'd like to use this project as a template to create your own dApp, this should give you what you need to start.

1. Open your terminal and enter below command:

 git clone -b main https://github.com/octofi/octofi-app-aquafarm.git

2. Open package.json file and change the following part:

 "homepage": "https://{Github-username}.github.io/{Github-repo-name}",

3. Open /public directory and delete CNAME.
4. Use edit.env.production as a starter file for your own environment variables to be put in a local .env.local file.
5. Then go back to your terminal and enter the following commands:
   rm -rf ./.git
   yarn cache clean --all
   yarn install --ignore-engines --ignore-scripts --network-timeout 600000
   (yarn add node-sass@4.14.0)
   (npm rebuild node-sass@4.14.0)
   npx browserslist@latest --update-db
   rm -rf ./.git
   (yarn start or build)
   git init
   git remote add origin your-github-repository-url.git
   yarn deploy
   

Built With

• Github Pages
• React

Versioning

We use Semantic Versioning for software versions of this project. For a list of all the versions available, see the tags and releases on this repository.

Authors

See the list of contributors who have participated in this project.