> For the complete documentation index, see [llms.txt](https://docs.thesphere.as/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thesphere.as/the-sphere-ecosystem/offsetting-strategy.md).

# Offsetting Strategy

We are acutely aware of the numerous ecological concerns surrounding NFTs and blockchain technologies, in particular the Ethereum blockchain on which the Sphere Digital Soul is built. As of now, Ethereum is still using a proof-of-work consensus mechanism; we are hopeful that the transition toward proof-of-stake will happen in the near future. In the meantime, we are committed to put in place an offsetting mechanism that will rely on the amazing work done by regenerative finance initiatives like [Toucan Protocol](https://toucan.earth/) or [KlimaDAO](https://www.klimadao.finance). Through their protocols, we will buy tokenized carbon credits to cover our carbon footprint (and beyond). These tokens will be held by the Sphere Commons Pool treasury.


---

# 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.thesphere.as/the-sphere-ecosystem/offsetting-strategy.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.
