Honey Labs - Building liquidity solutions for NFTs

This is a Next.JS project bootstrapped with create-react-app

General overview

Hello and welcome 👋🏼, we are happy to see that you arrived at Honey Labs - The Liquidity Solution builder for NFTs. This repo contains a Front-end interface built with NextJS and makes use of the following tools:

• Honey-SDK: for permissionless lending pools that use NFTs as collateral (🛠 WIP)

• Rainbowkit for connecting to EVM wallets

• Moralis: for fetching NFT and calling contract (read functions)

• wagmi for calling write functions on contract

• Degen-UI: for styling accompanied by Vanilla-Extract for custom CSS classes

Getting Started

The Honey Finance Ecosystem consists of several components this repo represents the Front-end.

In order to run this project you need to create a

.env #you can use the .env.example file as silver lining

You need both NEXT_PUBLIC_SERVER_URL and NEXT_PUBLIC_APP_ID to run this application. Please go to https://moralis.io/ to sign up an account. Currently contract is deployed to Polygon test net( Mumbai) only. Please set up your server in Moralis using Mumbai.

yarn install #installs all required packages
yarn dev #spins up the server at localhost:3000

In order to test the production server run:

yarn build

---

Learn more

To learn more about Honey Finance and the software it uses, take a look at the following resources:
Developer-docs - Coming soon... Your feedback and contributions are welcome! Feel free to reach out through Discord and take a look at the current Issues.

Deploy on Vercel

The easiest way to deploy your Next.JS app is by using the Vercel Platform from the creators of Next.JS. Check out the Next.JS Deployment Documentation for more details. Learn Next.JS - an interactive Next.JS tutorial.

This build is for testing purposes only...

Build Subgraph Client

These are the commands to generate the graphql client

yarn install
yarn add -D @graphprotocol/client-cli
yarn graphclient build

You need to update .graphclientrc.yaml if there are configurations changes such as new chain or new subgraph deployed. You need to update graphql under graphql folder if you are adding/modifying existed queries