axiefy

An open-source software that aims to help primarily on NFT Game Managers of Axie Infinity in order for them to conveniently manage and track their scholars, while also being an entry to Supabase’s 2nd Hackathon “Supabase Hacktoberfest Hackathon 2021”. We are also interested in building features not only suitable for Managers, but for the player base as a whole (e.g like Breeding). Currently the App enables manager to invite their Scholars to the app (making it so that the scholars are the one inputing their ronin address) and oversee their performance like total SLP farmed and PVP Rankings

Axie Infinity

Axie Infinity is a Pokémon-inspired universe where anyone can earn tokens through skilled gameplay and contributions to the ecosystem. Players can battle, collect, raise, and build a land-based kingdom for their pets. (https://whitepaper.axieinfinity.com/)

Motivation/Ideas

On our brain storming phase, we aim to build an app that has both Web2 and Web3 element inside it. However, we couldn’t seem to think of anything at that time until we thought about building an App within Axie Infinity ecosystem, since it is one of the most popular blockchain related game in the Web3 environment. But we couldn’t find any docs regarding Ronin Wallet, which is an Ethereum side chain governing Axie Ecosystem. Thus for now, we are only creating an app focuses on giving convenience to the interactions between Managers and their Scholars.

Demo

App: https://axiefy.vercel.app/

Credentials:

email: [email protected]
password: password

Screenshots

Supabase Hacktoberfest 2021 Team Members ⚡

Captain ? Carlo Miguel Dy
Ali Asgar L. Laut

Submitted on “Made with Supabase”

Supabase Usage

Supabase Serverless Database: Used for storing data
Supabase Authentication: Used authentication, magic link, email and password, and OAuth 2.0 providers
Supabase Storage: Used storage for photo uploads
Supabase Functions & Triggers
Postgres or Supabase feature?: Used RLS to prevent unauthorized actions (Current there’s a bug we can’t figure out in the given time ?)

Setup Development Environment

Copy .env.example file

$ cp .env.example .env

Open file .env and put key and secret

SUPABASE_KEY=<SUPABASE_KEY>
SUPABASE_URL=<SUPABASE_URL>

Install dependencies

npm i

Run dev server

npm run dev

Contributing

Be in main branch

$ git checkout main

Branch out from main by the following command

$ git checkout -b <your-branch-name> # git checkout -b feature/some-cool-feature

Then push upstream the latest branch

$ git push -u origin <your-branch-name> # git push -u origin feature/some-cool-feature

You can then stage all your changes

$ git add .

And push them to the branch you created

$ git push

And finally, create a Pull Request from the repository.

Switch back to main branch or any branch you desire.

$ git checkout main # git checkout <branch-name>

Build Setup

# install dependencies
$ npm install

# serve with hot reload at localhost:3000
$ npm run dev

# build for production and launch server
$ npm run build
$ npm run start

# generate static project
$ npm run generate

For detailed explanation on how things work, check out the documentation.

Special Directories

You can create the following extra directories, some of which have special behaviors. Only pages is required; you can delete them if you don’t want to use their functionality.

`assets`

The assets directory contains your uncompiled assets such as Stylus or Sass files, images, or fonts.