refactor(offchain): remove claims from dispatcher

.github/.scopes.txt

@@ -1,6 +1,6 @@
 advance-runner [For every change inside the offchain/advance-runner service]
 host-runner [For every change inside the offchain/host-runner service]
-dispatcher [For every change inside the offchain/dispatcher service]
+input-reader [For every change inside the offchain/eth-input-reader service]
 graphql-server [For every change inside the offchain/graphql-server service]
 indexer [For every change inside the offchain/indexer service]
 inspect-server [For every change inside the offchain/inspect-server service]

offchain/Cargo.toml

@@ -3,7 +3,7 @@ members = [
   "advance-runner",
   "contracts",
   "data",
-  "dispatcher",
+  "eth-input-reader",
   "graphql-server",
   "grpc-interfaces",
   "host-runner",

offchain/Dockerfile

@@ -63,16 +63,16 @@ COPY --from=builder /usr/src/app/offchain/target/release/cartesi-rollups-indexer
 USER cartesi
 ENTRYPOINT ["/opt/cartesi/bin/cartesi-rollups-indexer"]
 
-FROM runtime AS dispatcher
+FROM runtime AS eth-input-reader
 RUN <<EOF
 apt-get update
 DEBIAN_FRONTEND="noninteractive" apt-get install -y --no-install-recommends ca-certificates
 rm -rf /var/lib/apt/lists/*
 EOF
-COPY --from=builder /usr/src/app/offchain/target/release/cartesi-rollups-dispatcher /opt/cartesi/bin/cartesi-rollups-dispatcher
+COPY --from=builder /usr/src/app/offchain/target/release/cartesi-rollups-eth-input-reader /opt/cartesi/bin/cartesi-rollups-eth-input-reader
 COPY onchain/rollups/export/abi /opt/cartesi/share/deployments/
 USER cartesi
-ENTRYPOINT ["/opt/cartesi/bin/cartesi-rollups-dispatcher"]
+ENTRYPOINT ["/opt/cartesi/bin/cartesi-rollups-eth-input-reader"]
 
 FROM runtime AS advance_runner
 RUN <<EOF

offchain/README.md

@@ -69,7 +69,7 @@ For details specific to the Broker and the available event streams, refer to the
 
 The [**State-fold Server**](./state-server/README.md) is the component responsible for tracking blockchain state changes and deriving *Inputs* from them to be processed.
 
-The [**Dispatcher**](./dispatcher/README.md) is the component that messages *Inputs* via the **Broker** to be processed elsewhere and submits *Claims* to the blockchain.
+The [**Ethereum Input Reader**](./eth-input-reader/README.md) is the component that messages *Inputs* via the **Broker** to be processed elsewhere.
 
 The [**Advance Runner**](./advance-runner/README.md) is the one responsible for relaying *Inputs* to the **Server Manager** to be processed by the underlying DApp running in the embedded **Cartesi Machine**.
 The **Advance Runner** obtains the resulting **Outputs** and **Claims** from the **Server Manager** and adds them to the **Broker**.
@@ -84,7 +84,7 @@ The Cartesi Node may act as a *User* (aka *Reader*) or *Validator* Node, hence p
 
 ### Reader Flow
 
-In the Reader Flow, any *Input* read from the blockchain by the **State-fold Server** is received by the **Dispatcher** and relayed to the **Broker** through an input-specific stream.
+In the Reader Flow, any *Input* read from the blockchain by the **State-fold Server** is received by the **Ethereum Input Reader** and relayed to the **Broker** through an input-specific stream.
 The *Input* is eventually consumed by the **Advance Runner** and used to advance the state of the **Server Manager**, thus generating an *Advance* request to be processed by the underlying DApp.
 
 After finishing the processing, the DApp may generate a number of *Outputs*, which are eventually retrieved by the **Advance Runner** and fed back into the **Broker** through an output-specific stream.
@@ -94,7 +94,7 @@ After finishing the processing, the DApp may generate a number of *Outputs*, whi
 ### Validator Flow
 
 The Validator Flow may only be performed by *Validator* nodes.
-It complements the Reader Flow by generating *Claims* at the end of *Epochs*, which are generated by the **Server Manager**, and sent to the **Broker** by the **Advance Runner** through a claims-specific stream to be eventually consumed by the **Dispatcher** for being submitted to the blockchain.
+It complements the Reader Flow by generating *Claims* at the end of *Epochs*, which are generated by the **Server Manager**, and sent to the **Broker** by the **Advance Runner** through a claims-specific stream to be eventually consumed by the **Authority Claimer** for being submitted to the blockchain.
 
 ### Inspect Data Flow