> For the complete documentation index, see [llms.txt](https://emeth-1.gitbook.io/emeth-white-paper-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://emeth-1.gitbook.io/emeth-white-paper-en/7.-emeth-architecture/7-2.-layer-1-entire-process.md).

# 7-2. Layer 1 Entire Process

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

This page explains in detail the structure and processing flow of EMETH Layer 1, which utilizes blockchain technology, based on the functions introduced in the previous page.

1. Job registration by the Requester
   * The requester registers the parent Job information on EMETH Core on the Blockchain and pays the Fee (Fee for EMETH Node + Fee for Verifier) in EMETH tokens.
   * The dataset linked to the Job is stored in EMETH Storage.
   * Before processing begins, the requester can cancel the request by sending a Cancel declaration to EMETH Core. In this case, the paid Fee is fully refunded.
2. Constant synchronization cache by EMETH Cache server
   * The EMETH Cache server constantly synchronizes and caches Jobs on EMETH Core. Job information registered on EMETH Core is automatically linked to EMETH Cache.
3. Generation of SubJobs by L1 server
   * The L1 server monitors the information on the EMETH Cache server, and if there is a Job that can be Split and the requester has allowed Split processing, it performs the following:
     * Calls the Splitter to divide the dataset.
     * Divides the Job into multiple SubJobs and registers them with EMETH Core, linking them as parent Jobs.
4. Execution of processing by EMETH Node
   * EMETH Node monitors the information on the EMETH Cache server and performs the following:
     * Searches for attractive Jobs or SubJobs among unprocessed ones based on the Fee to EMETH Node and Deadline.
     * Sends a declaration of intent to start processing (process) to EMETH Core.
     * Downloads the dataset for the relevant Job or SubJob from EMETH Storage and starts processing.
     * Stores the processing results in EMETH Storage and sends a completion report (submit) to EMETH Core.
   * EMETH Node can also withdraw after declaring the intent to start processing. In this case, a penalty amount of EMETH tokens is confiscated and burned.
5. Processing of timed-out Jobs or SubJobs by Verifier
   * The Verifier monitors the information on the EMETH Cache server and searches for Jobs or SubJobs that have timed out.
   * Sends timeout processing to the Blockchain. At this time, the EMETH Node that was processing will have the timeout penalty amount of EMETH tokens confiscated.
6. Verification of processing results by Verifier
   * The Verifier monitors completed Jobs or SubJobs on EMETH Cache.
   * For the target Job or SubJob, it retrieves the dataset and processing results by EMETH Node from EMETH Storage.
   * Launches the Verifier program to verify, and if the verification of the processing results passes, it sends a verify command to the Blockchain; if it fails, it sends a rejectResult command. In case of SubJob failure, it re-registers the SubJob.
7. Confirmation of SubJob completion by Aggregator
   * Confirms that all SubJobs have been completed, calls the Aggregator program to integrate the processing results, and records them in EMETH Storage.
   * Simultaneously updates the Status of the parent Job on EMETH Core to Confirmed.
8. Payment of rewards based on verification results
   * The processing performance of passed Jobs or SubJobs is cumulatively counted on EMETH Core as total fuel amount.
   * For Jobs or SubJobs that fail verification, a fine is collected from EMETH Node.


---

# 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://emeth-1.gitbook.io/emeth-white-paper-en/7.-emeth-architecture/7-2.-layer-1-entire-process.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.