> For the complete documentation index, see [llms.txt](https://docs.lilypad.tech/lilypad/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lilypad.tech/lilypad/use-cases-agents-and-projects/project-showcase/waterlily.ai.md).

# Waterlily.ai

Waterlily.ai - An Ethical Generative AI-Art DApp

{% embed url="<https://youtu.be/oXNaCs0eyXI>" %}

[Waterlily.ai](http://waterlily.ai/) is a proof-of-concept application aiming to provide an alternative ethical solution to AI-Art generation by creating a new paradigm for AI image generation that pays royalties to the original creator and offers a new revenue stream for artists to explore.

To achieve this, Waterlily leverages the transparency & trustlessness of blockchain, with [FVM](https://fvm.dev/) smart contracts, combined with a decentralised edge compute platform in [Bacalhau](https://docs.bacalhau.org/examples/) to deliver an intuitive user experience for generative AI-Art while compensating creators for their original work with every image generation call.

Each stable diffusion model on Waterlily is trained & finetuned to a selection of artist work that has been uploaded by the artist themselves or is available in the public domain. When a user navigates to the [Waterlily.ai](http://waterlily.ai/) platform, they simply enter a text prompt for the images they want to create and choose an artist style that appeals to them.\
\
The small fee paid by the user is then distributed to the artist's wallet (except the fees required by the network to run the contract calls & return the generated images) - or to a vetted creator foundation in the case of public images.

A user can then opt to download these generated images or mint them as NFTs.

<figure><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1682476107570/3e5e30f6-f75c-4051-bae5-ee61dbb0c12b.gif?auto=format,compress&#x26;gif-q=60&#x26;format=webm" alt=""><figcaption><p>Images generated on Waterlily.ai</p></figcaption></figure>

## Video

{% embed url="<https://youtu.be/J90uzzfIrAI>" %}
Wes Floyd talks about Waterlily.ai
{% endembed %}

## Find out more about Waterlily.ai

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td></td><td><strong>Try out Waterlily.ai for yourself!</strong></td><td></td><td><a href="https://www.waterlily.ai">https://www.waterlily.ai</a></td><td><a href="https://58337262-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtadiyoOe4nTUoSulEVOV%2Fuploads%2Fgit-blob-411de7ef9022d889ce5d8eb5994e8a6408e6cdc1%2FWaterlily%20Squarish.png?alt=media">Waterlily Squarish.png</a></td></tr><tr><td></td><td><strong>Contribute to the Github or read the code</strong></td><td></td><td><a href="https://github.com/bacalhau-project/Waterlily">https://github.com/bacalhau-project/Waterlily</a></td><td><a href="https://58337262-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtadiyoOe4nTUoSulEVOV%2Fuploads%2Fgit-blob-71ef221484620ab1cfa2f95b09f2083b464b7438%2Foutercore%20waterlily.jpeg?alt=media">outercore waterlily.jpeg</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lilypad.tech/lilypad/use-cases-agents-and-projects/project-showcase/waterlily.ai.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.