> For the complete documentation index, see [llms.txt](https://docs.asphodel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.asphodel.io/whitepaper/architecture/ethereum-+-yominet.md).

# Ethereum + Yominet

We're long term crypto builders. We've seen generations of alt L1s and alt L2s come and go. We've learnt over time to be pragmatic about our chain architecture and to use blockchains as tools. In this page, we'll explain how we see each chain fitting into the Asphodel ecosystem.&#x20;

## Ethereum&#x20;

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

Ethereum is the only way for us to make our dreams of immortality concrete. It's the only programmable blockchain that's being constructed with a view to surviving for hundreds or thousands of years, and we strongly support the recent recommitment to CROPS principles. We need a blockchain we can trust to last forever - as much as that is realistically possible.&#x20;

And that blockchain is Ethereum. So $ONYX lives on Ethereum, $SOMA will live on Ethereum, and the main Asphodel world contracts will always live on Ethereum. In this way, we anchor the heart of Asphodel to the most robust and censorship resistant environment that exists.

At the same time - the Ethereum mainnet is still, despite significant upgrades, relatively expensive and slow compared to various L2 and alt-L1 options. We can't build every single part of Asphodel on Ethereum today - and we don't think the main network will be ready for us to do that for years.

That leaves us with a need for a less-secure execution environment running in parallel, at least until 2030 or so....&#x20;

## Yominet&#x20;

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

Yominet is our custom sidechain, powered by Initia. We think of it as an execution and testing environment; while it's a mainnet blockchain, it's too centralized to offer the same degree of security guarantees as on Ethereum. &#x20;

Yominet is extremely fast, cheap, and flexible. We use it to run [Kamigotchi World](https://docs.kamigotchi.io/), which does tens of thousands of transactions per day; running the same level of activity on Ethereum would cost our users far more.&#x20;

We don't know exactly what will happen to Yominet as the Ethereum roadmap and our own ecosystem both progress. It may eventually become a permanent L2 running on top of Ethereum with more serious security guarantees, or we may choose to one day deprecate it and move the contracts running on Yominet onto Ethereum. We will update more on this over the next few years. Either way, items and currencies from Kamigotchi World will be preserved over into Asphodel itself.&#x20;

## And more...?

We're open to deploying small parts of our ecosystem, or self-contained worlds, on other L2s or blockchains if we think it's appropriate. We're picky - we would only do this with very carefully chosen partners, and we would still aim to build for the long term.&#x20;


---

# 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.asphodel.io/whitepaper/architecture/ethereum-+-yominet.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.
