Smart Royalitics

A smart way to see insights on royalties gained and lost for your NFT collection. A user can connect their wallet and see how much they have paid in royalties. This tool can also help you keep track of the royalties earned for a sepcific collection, as well as any royalties lost due to NFTs that have been resold or otherwise transferred. The tool can also provide detailed information and analysis on the performance of your NFT collection, including data on the sales and transfers of individual NFTs, the total value of your collection, and the average royalties earned per NFT. By using a specialized tracking tool, you can gain valuable insights into the performance of your NFT collection and make informed decisions about how to manage and grow your collection.

WEBSITE

https://smart-royalitics.vercel.app/

DEMO Video:

https://www.youtube.com/watch?v=8uGNC2xg1Ww

Sample Page IMG

Installation

npm install
# or
yarn install

Build and Run

Next, run the development server:

npm run dev
# or
yarn dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying pages/index.tsx. The page auto-updates as you edit the file.

API routes can be accessed on http://localhost:3000/api/hello. This endpoint can be edited in pages/api/hello.ts.

The pages/api directory is mapped to /api/*. Files in this directory are treated as API routes instead of React pages.

Features

-Specialized tracking tool or platform -Tracks royalties paid for NFT Collection -Tracks royalties earned from NFTs -Tracks royalties lost due to NFT resales or transfers -Provides detailed information and analysis on NFT collection performance -Includes data on sales and transfers of individual NFTs -Includes total value of collection and average royalties earned per NFT -Helps user make informed decisions about managing and growing collection.

Structure

The scaffold project structure may vary based on the front end framework being utilized. The below is an example structure for the Next js Scaffold.

├── public : publically hosted files
├── src : primary code folders and files
│   ├── components : should house anything considered a resuable UI component
│   ├── contexts` : any context considered reusable and useuful to many compoennts that can be passed down through a component tree
│   ├── hooks` : any functions that let you 'hook' into react state or lifecycle features from function components
│   ├── models` : any data structure that may be reused throughout the project
│   ├── pages` : the pages that host meta data and the intended `View` for the page
│   ├── stores` : stores used in state management
│   ├── styles` : contain any global and reusable styles
│   ├── utils` : any other functionality considered reusable code that can be referenced
│   ├── views` : contains the actual views of the project that include the main content and components within
style, package, configuration, and other project files

Contributing

Anyone is welcome to create an issue to build, discuss or request a new feature or update to the existing code base. Please keep in mind the following when submitting an issue. We consider merging high value features that may be utilized by the majority of scaffold users. If this is not a common feature or fix, consider adding it to the component library or cookbook. Please refer to the project's architecture and style when contributing.

If submitting a feature, please reference the project structure shown above and try to follow the overall architecture and style presented in the existing scaffold.

Committing

To choose a task or make your own, do the following:

1. Add an issue for the task and assign it to yourself or comment on the issue
2. Make a draft PR referencing the issue.

The general flow for making a contribution:

1. Fork the repo on GitHub
2. Clone the project to your own machine
3. Commit changes to your own branch
4. Push your work back up to your fork
5. Submit a Pull request so that we can review your changes

NOTE: Be sure to merge the latest from "upstream" before making a pull request!

You can find tasks on the project board or create an issue and assign it to yourself.

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.