> For the complete documentation index, see [llms.txt](https://docs.energyweb.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.energyweb.org/energy-solutions/green-proofs-by-energy-web/use-cases-and-reference-implementations/green-proofs-as-a-service-gpsaas.md).

# Green Proofs as a Service (GPSaaS)

The Green Proofs system ensures that energy usage is verified as green by managing and validating green certificates for various energy operations. All data sent to workers originates from the Green Proofs application, which transforms it into operations like issuing, transferring, or retiring certificates.

<figure><img src="/files/puNEXOBGFRqFxNcG7ys4" alt=""><figcaption></figcaption></figure>

When the system receives an energy usage request, Green Proofs converts it into a corresponding operation, such as retiring a specific number of green certificates (e.g., retiring 10 units to reflect renewable energy consumption). This operation is sent to a network of workers via a distribution proxy. Instead of verifying the energy usage directly, workers validate whether the certificate-related operation, like retiring green certificates, is valid based on prior information.

For instance, if a certificate with a volume of 100 units is issued, workers are informed of this through a pseudonymized ID. When an operation requires retiring 10 units, workers vote on its validity, ensuring the operation aligns with the system's current state. This decentralized approach ensures consistent and secure state verification without granting any single worker full access to the system's data, enabling efficient and trustworthy management of renewable energy certificates across any energy market.

[Learn more about GPSaaS and deploying registries with Launchpad](/launchpad-by-ew/launchpad-by-energy-web/generic-and-energy-services/green-proofs-as-a-service.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.energyweb.org/energy-solutions/green-proofs-by-energy-web/use-cases-and-reference-implementations/green-proofs-as-a-service-gpsaas.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.