Services_backend_sig (octez-evm-node-libs.Evm_node_lib_dev.Services_backend

module type S = sig ... end

module type Backend = sig ... end

module Make (Backend : Backend) (Executor : Evm_execution.S) : S

type endpoint =

| Rpc of Uri.t
| Websocket of Websocket_client.t
| Block_producer

Represents the different ways transactions can be injected into the system

type callback_status = [

| `Accepted
| `Confirmed
| `Dropped
| `Refused

]

type 'a variant_callback = 'a -> unit Lwt.t

type callback = callback_status variant_callback

A callback is called by the Tx_queue at various stages of a submitted transaction's life.

The next tick after its insertion in the queue, a transaction is submitted to the relay node within a batch of eth_sendRawTransaction requests.

Depending on the result of the RPC, its callback is called with either `Accepted or `Refused).
As soon as the transaction appears in a blueprint, its callback is called with `Confirmed. If this does not happen before 2s, the callback is called with `Dropped.

module type Tx_container = sig ... end

Tx_container is the signature of the module that deals with storing and forwarding transactions. the module type is used by Services.dispatch_request to request informations about pending transactions.

'f tx_container is a GADT parametrized by the same type argument as L2_types.chain_family. It is useful to statically guarantee that the launched tx-container uses types compatible with the chain's chain family.

type 'f tx_container =

| Evm_tx_container : (module Tx_container with type address = Evm_node_lib_dev_encoding.Ethereum_types.address and type transaction_object = Transaction_object.t) -> Evm_node_lib_dev_encoding.L2_types.evm_chain_family tx_container
| Michelson_tx_container : (module Tx_container with type transaction_object = Evm_node_lib_dev_tezlink.Tezos_types.Operation.t) -> Evm_node_lib_dev_encoding.L2_types.michelson_chain_family tx_container

val tx_container_module : 'f tx_container -> (module Tx_container)

Some functions of the Tx_container module, such as add, have interfaces which actually depend on the chain family but many others, such as clear don't.

In the former case, we usually know statically the type of the chain family and hence of the tx-container and we can for example invoke add as follows:

  let Evm_tx_container (module Tx_container) = tx_container in
  let** hash = Tx_container.add ~next_nonce ~raw_tx tx_obj in

In the latter case, statically knowing the type of the chain family is not required and the following tx_container_module function can be used to get a Tx_container module:

  let (module Tx_container) = Services_backend_sig.tx_container_module tx_container in
  let* () = Tx_container.clear () in

type ex_tx_container =

| Ex_tx_container : _ tx_container -> ex_tx_container