Fluence is excited to sponsor another edition of HackFS and we are looking forward to hack with you May 15 - June 7, 2024.
Fluence, the cloudless off-chain compute protocol, enables a decentralized serverless compute and infrastructure (DePin) platform allowing developers to create compute functions and deploy them to Tier 4 data centers providing provable, decentralized CPU and RAM resources. The Fluence on-chain compute marketplace, built on IPC, facilitates the trustless matching of applications' demand for and providers' supply of capacity, respectively. The Fluence compute marketplace allows developers to deploy applications comprised of just one or many Fluence Compute Functions.
The Fluence protocol offers developers for both off- and on-chain hacks. Off-chain projects should use the Fluence cloudless compute stack to create apps or building blocks for app. On-chain projects, on the other hand, should improve the UX of the marketplace and related tooling, such as indexers and explorers, or extend the functionality of the marketplace, e.g., add a spot auction to facilitate cheaper but possibly short(er) lived deals between providers and application developers.
Create a decentralized application from Fluence cloudless functions. Your application should use at least three serverless functions (deployed to three different peers) composed and choreographed with Aqua. Alternatively, create a reusable Marine library with at least three distinct API functions and the matching (reusable) Aqua bindings. For either approach, provide ample test coverage with Aqua.
Need some ideas?
- Get your AI on with Fluence and port the openai-chagpt-api crate to Marine and implement a demo application using Aqua or
- Embrace cryptography and port a (Rust) MPC TSS library to Marine and implement a demo application covering key generation, signing and key refresh with Aqua
If your application or library requires RPC, consider using fRPC for bonus points.
Improve or expand on Fluence indexing, dashboard(s) or marketplace. For a link to the current explorers and dashboards see the dar network page.
For a little inspiration, consider:
- Improve the marketplace by extending/complementing the matcher with a spot auction or
- Implement (liquid) staking pools to delegators
- Implement a new faucet using a Web3 auth approach such as SIWE
In addition to the HackFS Rules & Regulations, teams need to fork this repo and add their submission. Keep this repo private until the end of the event.
When the number of valid, eligible and equally accomplished submissions exceeds the number of prizes, as determined by the Judge(s), the timestamp of the last change of the submitted repo will serve as the tie-breaker.
An eligible submission requires teams to
- generously document their solution with one or more readme files and, when applicable, code documentation
- commit the complete project scaffold to your forked repo including the .fluence directory
- submit a two (2) to five (5) minute (linked) video shilling your masterpiece. Youtube is penty good enough.
- submit as a Github or GitLab repo with MIT or Apache 2.0 license