Lilypad Network Announcements
Open in Telegram
We're building the universal compute cloud for Al, ML & more. Making Al accessible & infrastructure open. Lilypad is Serverless Optimistic Distributed Compute.
Show moreThe country is not specifiedTechnologies & Applications24 798
2 261
Subscribers
No data24 hours
-247 days
-7130 days
Data loading in progress...
Similar Channels
Tags Cloud
No data
Any problems? Please refresh the page or contact our support manager.
Incoming and Outgoing Mentions
---
---
---
---
---
---
Attracting Subscribers
May '25
May '25
+3
in 1 channels
April '25
+8
in 0 channels
Get PRO
March '25
+25
in 0 channels
Get PRO
February '25
+24
in 0 channels
Get PRO
January '25
+13
in 0 channels
Get PRO
December '24
+12
in 0 channels
Get PRO
November '24
+1
in 0 channels
Get PRO
October '24
+9
in 0 channels
Get PRO
September '24
+2 800
in 0 channels
| Date | Subscriber Growth | Mentions | Channels | |
| 22 May | 0 | |||
| 21 May | 0 | |||
| 20 May | 0 | |||
| 19 May | 0 | |||
| 18 May | 0 | |||
| 17 May | 0 | |||
| 16 May | 0 | |||
| 15 May | 0 | |||
| 14 May | 0 | |||
| 13 May | +1 | |||
| 12 May | 0 | |||
| 11 May | 0 | |||
| 10 May | 0 | |||
| 09 May | +1 | |||
| 08 May | 0 | |||
| 07 May | 0 | |||
| 06 May | 0 | |||
| 05 May | 0 | |||
| 04 May | 0 | |||
| 03 May | +1 | |||
| 02 May | 0 | |||
| 01 May | 0 |
Channel Posts
π’ Update: Resource Provider Beta program details
π gm Resource Providers! π
Thank you for supporting the Lilypad Testnet and providing feedback while the network scales. Work to grow Testnet is yielding exciting results! Job reliability continues to increase while the community creates new modules to run on the network https://github.com/Lilypad-Tech/awesome-Lilypad.
For the next phase of Resource Provider incentives, we are launching the RP beta program! Anyone can submit a RP(s) to join the beta. Our team will be prioritizing instances with greater resources and RPs willing to actively help troubleshoot issues.
RPs selected for the beta will get a Discord role unlocking access to a channel for beta communications. Only RPs that have been accepted into the beta can post resource offers to the Lilypad solver to run jobs. Submissions are under review, weβll be reaching out to RPs next week! Apply β https://forms.gle/nS9Ksvsh2DpVSs1RA.
Resource Providers (RPs) participating in the beta will earn Lilybit reward amounts comparable to those earned on Testnet, but for running jobs and providing feedback. Bonuses will be available for running large amounts of jobs and long term uptime. The new Testnet Lilybit rewards system intends to as closely as possible replicate RP revenue on Mainnet.
RPs with greater hardware resources may earn higher rewards due to their capacity to process more resource-intensive modules. It's important to note that during the beta program RPs will not face slashing penalties, regardless of whether they are accepted into or participate in the beta. RPs in the beta program that cannot consistently run jobs will be removed. Stay tuned for more details!
RP points can be tracked here https://rp-points.lilypad.tech/. Due to many system changes, the RP leaderboard at info.lilypad.tech is still down for maintenance. Our team will be sure to provide data for RPs to know the total Lilybits that have been earned.
| 2 | Want to get more involved with Lilypad? πΈ
Weβre rolling out an Ambassador Program and looking for passionate builders, researchers, and AI enthusiasts to help shape the future of compute.
If youβre excited about AI, DeSci, open source, and the power of decentralized infrastructureβthis is for you.
Apply now π
https://docs.google.com/forms/d/e/1FAIpQLSdsJHkYlVVm9YILPodExa4AgGCfW-8bHZanf9OS57QxQee3SA/viewform | 167 |
| 3 | We are LIVE!
Watch here π
https://x.com/lilypad_tech/status/1881884659233308944?s=46 | 156 |
| 4 | π’ Update: Work in progress to launch RP Beta program
π gm Resource Providers! πΈ
Work continues to rearchitect the Testnet rewards system including planning for the Resource Provider Beta program. In order to align the rewards system closely with how RPs will operate on Mainnet, the rewards system will require RPs to run jobs in order to receive rewards. More on this soon!
Thank you to all RPs who submitted the Beta program form. We will make an announcement when the list of Beta RPs has been decided. Our team is currently implementing the new rewards system and intend on starting the Beta program as soon as the system has been setup and testing has completed.
Sign up for the Beta program with this form - https://forms.gle/sLDrgUXeV7HpCmSq8 ! | 155 |
| 5 | π’ Update: Retroactive rewards drop status
π gm Resource Providers! πΈ
A retroactive Lilybit rewards drop has been planned and is on schedule to be applied early next week. The retroactive drop will provide Lilybits to RPs that are missing rewards through no fault of their own due to IncentiveNet scaling issues.
Stay tuned for more IncentiveNet updates as we rearchitect the backend system and begin testing the next round of updates!
Our team cannot thank the community enough for the support as IncentiveNet has grown over 2024! We are energized by the growth of the network and are full steam ahead towards Mainnet launch. | 115 |
| 6 | Incentivised Testnet Update
gm gm Resource Providers
After multiple fixes for the recent issues with Resource Providers not receiving rewards on the Incentivised Testnet, weβve decided to temporarily pause the system. This pause will help address scaling challenges in the Lilybit rewards system and make necessary enhancements for Mainnet.
During the IncentiveNet pause, weβll rework the rewards system to resolve outstanding issues, with no expectation for Resource Providers to maintain uptime while points arenβt issued. Weβve started reworking the backend, and the rewards calculation will align with Mainnet goals, including a job-based mechanism to simulate the future rewards system.
- The Lilybit InventiveNet rewards will pause on Monday Dec/16/2024 and is expected to resume in mid to late January.
- A retroactive drop of Lilybits will be given to RPs missing rewards through no fault of their own up to Dec/16/2024.
- A snapshot will occur after the retro-drop to record Lilybit rewards earned by each RP. RPs will not lose Lilybits during the IncentiveNet pause.
- TestNet (IncentiveNet) will run with a small beta group of up to 20 RPs earning limited rewards during this time.
- The intention of the small beta group is to ensure TestNet can consistently run jobs. We will need RPs who are able to test and can share details about their deployment.
- When the rewards system is resumed, we will announce that Resource Providers can join the public IncentiveNet.
- RPs that do not return to running on the TestNet (IncentiveNet) when the public rewards begins will be subject to slashing.
- Lilybits earned in phases 1-6 will not be included in slashing as thanks to early network supporters.
Applications for the beta program are open now via this form https://lilypad.team/betaprog
Stay tuned for more updates as we continue to work on the re-architecture of the rewards system. Thanks for your continued support and patience as we work towards improving the system! | 127 |
| 7 | π’ Update: Rewards system investigation
π gm Resource Providers! πΈ
We are aware that nodes across the network are not receiving Lilybit rewards as expected. Our team investigated this issue and believe the root cause have been identified. The Lilybit rewards system continues to face scaling issues, so in response, our team is scaling up the system backend to handle the increased load. This work has been on-going over the last week as we carefully push updates and evaluate the results without causing additional complications.
In addition to implementing a fix, we will complete a retroactive backdrop of Lilyibt rewards for RPs missing rewards through no fault of their own. An announcement will be sent out to the community when the retro drop is completed.
Follow along in more detail at https://github.com/orgs/Lilypad-Tech/discussions/18 and https://discord.com/channels/1212897693450641498/1307591874982182982/1307591874982182982
π¨ Reminder: Lilypad v2.9.0 and older have been deprecated. RPs running v2.9.0 or older will not receive points. Running the latest version of Lilypad is critical to the ability of a RP to run jobs and earn rewards.
Check out our GitHub discussions board to see current work or report an issue: https://github.com/orgs/Lilypad-Tech/discussions/categories/rp-issue | 291 |
| 8 | π’ Update: Rewards system investigation
π gm Resource Providers! πΈ
Over the last week, our team has pushed backend updates to the Lilybit rewards system and continues to resolve points issues with some Resource Providers (RP).
An important part of the fix includes scaling up the rewards system to handle the large volume of RPs online. We will keep the community updated as this work continues. A huge thanks to the community for supporting the Testnet as it scales!
Follow along in more detail at https://github.com/orgs/Lilypad-Tech/discussions/18 and https://discord.com/channels/1212897693450641498/1307591874982182982/1307591874982182982
π¨ Reminder: Lilypad v2.9.0 and older have been deprecated. RPs running v2.9.0 or older will not receive points. Running the latest version of Lilypad is critical to the ability of a RP to run jobs and earn rewards.
Check out our GitHub discussions board to see current work or report an issue: https://github.com/orgs/Lilypad-Tech/discussions/categories/rp-issue | 95 |
| 9 | π¨ Action Required - New Release - Goethe (v2.10.0)
"As soon as you trust yourself, you will know how to live." β Johann Wolfgang von Goethe
gm Resource Providers! πΈ
Lilypad v2.10.0 - Goethe was released requiring RPs to update! https://github.com/Lilypad-Tech/lilypad/releases/tag/v2.10.0
The Docker Compose file has been updated to run Bacalhau in a separate Docker container. This change will help to ensure Bacalhau keeps running in the event that the Lilypad Resource Provider restarts or encounters an issue.
v2.10.0:
Add base services compose file
Run bacalhau in a separate container
Silence web3 event listener cancellation errors
Add solver metrics
Update Linux RP:
1οΈβ£ Stop the RP (skip if offline):
sudo systemctl stop bacalhau
sudo systemctl stop lilypad-resource-provider
Leave the local IPFS node running.
2οΈβ£ Remove the old Lilypad executable carefully:
sudo rm -rf /usr/local/bin/lilypad
3οΈβ£ Install the latest version
https://docs.lilypad.tech/lilypad/hardware-providers/run-a-node/linux#install-lilypad
4οΈβ£ Restart RP
Once configured, start the RP:
sudo systemctl start bacalhau
sudo systemctl start lilypad-resource-provider
Update Docker RP
Use the docker-compose file to effortlessly setup the RP. https://docs.lilypad.tech/lilypad/hardware-providers/run-a-node/docker#docker-compose
π¨ Reminder: Update Window
For update window with new releases, RPs will have two weeks to update before the previous version is deprecated. Failure to update in this period will prohibit a RP from remaining active on the network, having PoWs tracked or earning rewards.
Got questions? Hop into our Discord #i-need-help channel. π
GitHub | 84 |
| 10 | π’ Update: Rewards system investigation
π gm Resource Providers! πΈ
Our team greatly appreciates the patience while edge cases of some RPs not receiving rewards are investigated.
We have been running test cases to identify the root cause and believe this is related to how the rewards system backend handles recent rewards changes. Testing continues and in the meanwhile we are specing out a fix. This has taken some time as the community brought up a few different edge cases that required investigation to get the full picture.
Follow along in more detail at https://github.com/orgs/Lilypad-Tech/discussions/18 and https://discord.com/channels/1212897693450641498/1307591874982182982/1307591874982182982
Note: Our team may be slow to respond towards the end of this week as it is a holiday in some countries where we operate. That said, we are full steam ahead towards a resolution for these rewards edge cases and will further communicate next steps as soon as possible.
Check out our GitHub discussions board to see current work or report an issue: https://github.com/orgs/Lilypad-Tech/discussions/categories/rp-issue | 86 |
| 11 | π’ Update: Lilybits rewards emissions
π gm gm Resource Providers!
The 20,000 Lilybit daily limit per RP has been implemented and will take effect for Lilybit rewards moving forward. Read more about this update in this announcement. https://discord.com/channels/1212897693450641498/1256179769356189707/1308230244167192728 | 99 |
| 12 | π¨ Action Required - New Release - Fei-Fei Li (v2.9.1)
"The paradigm shift of the ImageNet thinking is that while a lot of people are paying attention to models, let's pay attention to data. Data will redefine how we think about models." - Fei-Fei Li
gm Resource Providers! πΈ
Lilypad v2.9.1 - Fei-Fei Li was released requiring RPs to update! https://github.com/Lilypad-Tech/lilypad/releases/tag/v2.9.1
π¨ Update Window
For update window with new releases, RPs will have two weeks to update before the previous version is deprecated. Failure to update in this period will prohibit a RP from remaining active on the network, having PoWs tracked or earning rewards.
v2.9.1:
* Updates have been made to the Solver to fix connection errors.
Update Linux RP:
1οΈβ£ Stop the RP (skip if offline):
sudo systemctl stop bacalhau
sudo systemctl stop lilypad-resource-provider
Leave the local IPFS node running.
2οΈβ£ Remove the old Lilypad executable carefully:
sudo rm -rf /usr/local/bin/lilypad
3οΈβ£ Install the latest version
https://docs.lilypad.tech/lilypad/hardware-providers/run-a-node/linux#install-lilypad
4οΈβ£ Restart RP
Once configured, start the RP:
sudo systemctl start bacalhau
sudo systemctl start lilypad-resource-provider
Update Docker RP
Use the docker-compose file to effortlessly setup the RP. https://docs.lilypad.tech/lilypad/hardware-providers/run-a-node/docker#docker-compose
Got questions? Hop into our Discord #i-need-help channel. π | 97 |
| 13 | π¨ Mandatory Update: Lilypad v2.9.0 Required by Tomorrow!
gm Resource Providers! πΈ
Reminder that the previous Lilypad version (2.8.0) will be deprecated tomorrow. RPs must update to v2.9.0 - Einstein to remain active in the network!
Upon every release, RPs will have 2 weeks to update to the latest Lilypad version, mentioned in the v2.9.0 release - https://discord.com/channels/1212897693450641498/1256179769356189707. Please note: The next Lilypad release will be tomorrow and RPs will have a 2 week grace period to update and then v2.9.0 will be deprecated.
Resource providers that are running older versions will no longer remain active on the network, have PoWs tracked or earn rewards. Make sure your node is updated to v2.9.0 before tomorrow to avoid interruptions!
Update Linux RP:
1οΈβ£ Stop the RP (skip if offline):
sudo systemctl stop bacalhau
sudo systemctl stop lilypad-resource-provider
Leave the local IPFS node running.
2οΈβ£ Remove the old Lilypad executable carefully:
sudo rm -rf /usr/local/bin/lilypad
3οΈβ£ Install the latest version
https://docs.lilypad.tech/lilypad/hardware-providers/run-a-node/linux#install-lilypad
4οΈβ£ Restart RP
Once configured, start the RP:
sudo systemctl start bacalhau
sudo systemctl start lilypad-resource-provider
Update Docker RP:
Use the docker-compose file to effortlessly setup the RP. https://docs.lilypad.tech/lilypad/hardware-providers/run-a-node/docker#docker-compose
Got questions? Open up a ticket in our GitHub discussions using the rp-issues category: https://github.com/orgs/Lilypad-Tech/discussions/categories/rp-issue π | 66 |
| 14 | π’ Update: Implemented initial fix for Rewards System
Our team has implemented a fix that will address the large number of daily Lilybit emissions. Changes take effect today and will reflect in the total daily Lilybits sent out going forward.
* Only one wallet (RP) will be eligible to earn rewards per GPU.
* For RPs running multiple wallets on one GPU, the wallet with the most points will be matched in our system with the GPU and will earn points. The other wallets will not earn points going forward (unless they are used on a different GPU).
* Slashing will continue to be turned off temporarily (as a grace period) until we are certain the rewards system is working as expected and to allow time for RPs to adjust. Slashing will likely be turned on mid/end of next week.
* Once turned back on, slashing will affect any address that does not have a unique GPU associated with it.
We'll communicate next steps on rewards emissions concerns once enough data has been collected on the results of this work. https://github.com/orgs/Lilypad-Tech/discussions/14#discussioncomment-11261561
To report additional RP issues, open a new github discussion by filling out this template or check out any existing discussions for your issue. https://github.com/orgs/Lilypad-Tech/discussions/new?category=rp-issue
For troubleshooting help, open a ticket in the i-need-help Lilypad Discord channel. https://discord.com/channels/1212897693450641498/1230231823674642513 | 83 |
| 15 | π’ Update: Slashing temporarily paused
π Hi Lilypad Resource Providers!
The Lilybit rewards calculation was updated and based on community feedback a bug was discovered for RPs running multiple GPUs on one server. RPs running v2.9.0 on a server with a single GPU should not be affected and are asked to continue running v2.9.0.
While our team decides the next steps to address this, slashing has been turned off temporarily. We will notifiy the community when slashing is turned back on.
IMPORTANT NOTE: With the new rewards calculation (using the daily rewards multiplier and GPU info VRAM + Tensor cores + Cuda cores), RPs should expect to receive a different number of Lilybits per day when compared to rewards earned using the previous hashrate based calculation. | 93 |
| 16 | π¨ Action Required - New Release - Einstein (v2.9.0)
"Imagination is more important than knowledge." - Albert Einstein
gm Resource Providers! πΈ
Lilypad v2.9.0 - Einstein was released requiring RPs to update! https://github.com/Lilypad-Tech/lilypad/releases/tag/v2.9.0
Changes include updates to the Lilybit Rewards calculation, an update window, & more. The Lilybit calculation will change this week to using GPU card info instead of hashrate. Slashing will be turned on this week.
π¨ Update Window
With new releases, RPs will have two weeks to update before the previous version is deprecated. Failure to update in this period will prohibit a RP from earning Lilybits.
v2.9.0:
* To fairly reward GPUs optimized for AI jobs, Lilybits will be provided based on GPU card info (VRAM, Tensor cores, Cuda cores) in addition to the PoW uptime multiplier. The calculation will no longer use hashrate, but RPs will still be required to run PoWs. https://blog.lilypadnetwork.org/update-to-the-lilybit-rewards-calculation
* RPs will report their Lilypad version to the network
* This release includes a docker-compose file for RPs to easily get setup and running! https://docs.lilypad.tech/lilypad/hardware-providers/run-a-node/docker
Update Linux RP:
1οΈβ£ Stop the RP (skip if offline):
sudo systemctl stop bacalhau
sudo systemctl stop lilypad-resource-provider
Leave the local IPFS node running.
2οΈβ£ Remove the old Lilypad executable carefully:
sudo rm -rf /usr/local/bin/lilypad
3οΈβ£ Install the latest version
https://docs.lilypad.tech/lilypad/hardware-providers/run-a-node/linux#install-lilypad
4οΈβ£ Restart RP
Once configured, start the RP:
sudo systemctl start bacalhau
sudo systemctl start lilypad-resource-provider
Update Docker RP
Use the docker-compose file to effortlessly setup the RP. https://docs.lilypad.tech/lilypad/hardware-providers/run-a-node/docker#docker-compose
Got questions? Hop into our Discord #i-need-help channel. π
https://lilypad.team/discord | 102 |
| 17 | π’ Update: Rewards yesterday
π Hi Lilypad Resource Providers!
Yesterday, the Lilybit rewards mechanism experienced a technical scaling issue resulting in all RPs not receiving points for 2024-11-05. Our team has investigated and continues to scale up the rewards infrastructure to prevent this from occurring again.
Lilybit rewards are set to go out at 00:10 UTC as usual today. RPs should also expect to receive the missing rewards for 2024-11-05 (yesterday). Regardless, this affected RPs evenly. We will be actively monitoring the system to ensure recent updates address the scaling issues.
We greatly appreciate the community's patience as IncentiveNet scales. Our team continues to balance between network scalability, cost, time, important updates, and Mainnet development. The Lilypad pond continues to grow and we cannot be more excited for the future of the network! | 84 |
| 18 | πͺ· Lilypad ambassador rewards for October πͺ·
Hi Lilypad Advocates!
The next round of monthly Lilybit Ambassador rewards were sent out today. Thank you for the hard work over the last month, your contributions are invaluable to help the network grow!
Lilybit_ rewards can be found at https://oss.lilypad.tech/.
The Lilypad Ambassador program is designed to highlight and support outgoing and passionate community members who help others, solve problems, and communicate effectively!
Learn more about becoming a Lilypad Ambassador https://lilypadnetwork.notion.site/Lilypad-Ambassadors-f11f73e91f684fa192fc2fab7985fe0d. | 104 |
| 19 | π’ Update: Rewards today
π Hi Lilypad Resource Providers!
Our team has investigated and resolved issues with an Arbitrum RPC used for the Lilypad Testnet core infrastructure (IncentiveNet). RPC errors experienced today were generally caused by problems around scaling high volumes of transactions and were mostly out of our team's control.
As a result, all RPs across the network were affected with 0 Lilybit rewards earned today (2024-10-29 in https://rp-points.lilypad.tech). With this in mind, our team has implemented a fix to the rewards system, but will not provide retoactive Lilybits. RPs were not slashed today.
We apologize for this situation and thank our community for the incredible support as Testnet grows! | 94 |
| 20 | @everyone π¨
Our APAC AMA is live NOW!
Bring your questions along and chat with Steve and Taosheng.
Come join us on X/Twitter
https://x.com/Lilypad_Tech/status/1846370890009006098
or join us on YouTube
https://www.youtube.com/live/1KCO1bMoNzA | 131 |
