The Lilypad Network makes it easy to deploy LLMs and other programs across a global network of GPUs using a job-based (serverless) service model. The core of the job based system is a Lilypad Module spec that provides a standard Docker image format for running jobs on the network. Once a popular LLM is built into a Lilypad Module, the developer community can run the task via our dev tools, building AI powered systems with ease!

Our team is excited to announce the launch of Module Creator rewards! Community contributors can now earn Lilybit rewards for creating Lilypad Modules. The more popular a Module (popular LLMs, etc.) the more rewards a creator could earn! Rewards will also be considered for awesome implementation/apps built on top of current or new Lilypad Modules. From AI Agents to BioML workflows, we can’t wait to see what the community builds!

This announcement is part of the Community Rewards Program and is a beta test intended to create a process for building and testing Modules on Lilypad.

This rewards initiative is included in Phase 2 of the Lilypad IncentiveNet focusing on rewarding members of the community for contributing to the growth of the Network! The Community Rewards Program includes Lilypad Resource Providers in addition to the Open Source initiative and the Lilypad Ambassador program.

What’s a Lilypad Module?

A Module is a Git repository that allows you to perform various tasks using predefined templates and inputs. Using Docker for containerization, these modules can be run on the network with the Lilypad CLI and other dev tooling. Each time a job is called, a GPU on the Lilypad network is matched with the job offer and the task result is returned to the client. Current Modules include SDXL Turbo Pipeline and Llama 2.

Once a module can run on the network, check out the Lilypad docs for developer tooling to build applications using your job. Our team can’t wait to see what you build!

Submitting a Module

Once the image is built, follow the steps below to submit the module and earn Lilybits! 🎉

1. Open a pull request (PR) adding your module to the modules/ directory in our awesome-lilypad repository

   • Make sure to follow the PR template here and add any important information to get the Module running

   • Submissions not following the code of conduct will not be eligible for rewards

2. Respond to any comments from the Lilypad team on your PR

   • Our team will review PRs as often as possible

   • Rewards will be provided at the end of each month

3. Once the PR has been merged, the Module creator will earn Lilybit rewards 🎉

   • Rewards will only be considered for the first merged Module per team every 30 days (for exceptions to this please contact our team on Discord)

     • A team can be a single individual or a group of multiple individuals

   • The amount of rewards will depend on a few factors, but our team will always look at what a GPU earns in Lilybits per day (usually a RTX 4090) as a baseline to provide a fair amount of Lilybits for the work put into a Module

   • An additional page will be added to the Community Rewards dashboard to display the amount of Lilybits earned by each creator

Build an application using a Module

Bonus Lilybits may be rewarded depending on Module usage and impact across the community

• Build a service such as a text to image generator or an AI agent Researcher using a Module

• Lilypad compute is currently free to use on Testnet (IncentiveNet)

• An application built on a Lilypad Module will use a separate repo but can still be added to the awesome-Lilypad repo

• Lilypad continues to improve our developer tooling providing a CLI and JS CLI wrapper (local) for developers, more to come soon

• For inspiration, check out examples such as the JS CLI wrapper + Gradio as well as products built on the network such as the ML Workbench and Waterlily.ai

We will be sharing more details and new ways of building on Lilypad soon — stay tuned! 📬

Criteria for rewards

Testing

• Modules must pass our internal tests and be merged into the awesome-lilypad repository to be eligible for rewards

• Reach out to our team to get more info on testing the module before submission

Expected impact

• Popularity of given job = expected impact

• Potential opportunity for bonus Lilybit rewards to creators whose Modules see a lot of demand

Process for receiving Lilybits for a Module/other dev work

• At the end of each month, our team will go through new PRs to evaluate rewards earned

• Modules/products that have been built in the past will be reviewed to evaluate impact, complexity, and scope for bonus rewards

• Lilybits will be provided by GitHub username in the Community Rewards dashboard

Disclaimer

• The Module Rewards program is in beta and is subject to change by the Lilypad team

• Submissions must adhere to the Lilypad code of conduct

• Modules that harm or attempt to harm the network in any way won’t be eligible to earn Lilybits