## Inspiration

After looking at the Hack the 6ix prizes, we were all drawn to the BLAHAJ. On a more serious note, we realized that one thing we all have in common is accidentally killing our house plants. This inspired a sense of environmental awareness and we wanted to create a project that would encourage others to take better care of their plants.

## What it does

Poképlants employs a combination of cameras, moisture sensors, and a photoresistor to provide real-time insight into the health of our household plants. Using this information, the web app creates an interactive gaming experience where users can gain insight into their plants while levelling up and battling other players’ plants. Stronger plants have stronger abilities, so our game is meant to encourage environmental awareness while creating an incentive for players to take better care of their plants.

## How we built it + Back-end:

The back end was a LOT of python, we took a new challenge on us and decided to try out using socketIO, for a websocket so that we can have multiplayers, this messed us up for hours and hours, until we finally got it working. Aside from this, we have an arduino to read for the moistness of the soil, the brightness of the surroundings, as well as the picture of it, where we leveraged computer vision to realize what the plant is. Finally, using langchain, we developed an agent to handle all of the arduino info to the front end and managing the states, and for storage, we used mongodb to hold all of the data needed.
[backend explanation here]

### Front-end:

The front-end was developed with **React.js**, which we used to create a web-based game. We were inspired by the design of old pokémon games, which we thought might evoke nostalgia for many players.

## Challenges we ran into

We had a lot of difficulty setting up socketio and connecting the api with it to the front end or the database

## Accomplishments that we're proud of

We are incredibly proud of integrating our web sockets between frontend and backend and using arduino data from the sensors.

## What's next for Poképlants

* Since the game was designed with a multiplayer experience in mind, we want to have more social capabilities by creating a friends list and leaderboard
* Another area to explore would be a connection to the community; for plants that are seriously injured, we could suggest and contact local botanists for help
* Some users might prefer the feeling of a mobile app, so one next step would be to create a mobile solution for our project
## Inspiration

Uniswap creator, Hayden, mentioned during the CalHacks 8.0 kickoff that he felt some of the best features in Uniswap v3 were being under-utilized. We wanted to find out if there was something in this space we could work on.

While reading up about v3 and the v3 Oracle in particular, we experimented with the Uniswap interface for pooling. The advanced options for concentrated liquidity pooling are pretty impressive - but we felt there was more to be done to take advantage of the opportunities created by this difference between v2 and v3.

[This paper](https://arxiv.org/pdf/2106.12033.pdf) by Neuder et al. gave us some implementation-specific inspiration.

## What it does (and will do)

RainbowPool builds upon the existing Uniswap router to give LPs access to safe and cost-efficient implementations of strategic liquidity provision - like splitting liquidity provision over bins with different ranges and executing smart re-balancing.

The decentralized app we implemented this weekend allows liquidity providers to interface with our liquidity optimization smart contract. It is a web3.0 application that acts as a proof of concept for our product.

We plan on integrating Uniswap v3 Router to facilitate transactions across liquidity pools on the mainnet. Uniswap v3 Oracle will provide data for our optimization algorithms so that we can do things like automatically re-provision liquidity.

## How we built it

We used the existing [scaffold-eth](https://github.com/scaffold-eth/scaffold-eth) framework to facilitate rapid-prototyping and iteration of a user interface linked to a smart contract.

We deployed contracts on a local chain created using Hardhat.

## Challenges we ran into

When trying to integrate Uniswap v3 into our environment we ran into problems related to Solidity complier versioning. This (disappointingly) stopped us from interacting with the Uniswap Router and Liquidity Management functionality directly.

## What we learned

This hackathon was - for our team - an introduction to the dapp developement space. None of us had deployed chains locally or programmed in Solidity before this event.

## What's next for RainbowPool

Full integration with Uniswap v3 Router.

Leveraging Oracle v3 for data.

Implementation of liquidity provisioning algorithms in Solidity.
## Inspiration

We had a wine and cheese last week.

## Challenges I ran into

A W S + python 3 connecting to domain

## What's next for Whine and Cheese

A team wine and cheese