Nomos blockchain node
Go to file
Giacomo Pasini 4a3d677ea9
Small fixes for libp2p network backend (#280)
* Generate network events for self messages

Waku does that and it's kind of convenient not to handle ourselves
in a different way from the rest.

* Use bigger buffer + fmt

When receiving messages coming from libp2p IWANT requests, it's
common to receive a burst of packest which can cause subscribers
to lag. To account for that, let's increase the buffer in the
broadcast channel.

* Check if topic is being subscribed before self-notification (#292)

* fmt

---------

Co-authored-by: Youngjoon Lee <taxihighway@gmail.com>
2023-08-07 06:00:41 +02:00
.cargo fix link flgs (#144) 2023-05-08 17:28:10 +02:00
.github/workflows Update and rename main.yml to master.yml (#194) 2023-06-15 12:48:36 +03:00
ci Updated integration tests cases, increased nightly iteration count (#263) 2023-07-17 21:16:05 +03:00
consensus-engine Disable tree rebuild (#293) 2023-08-04 12:17:10 +02:00
nodes/nomos-node feat: add `nomos-libp2p` crate (for nomos-network backend) (#237) 2023-07-11 10:33:57 +02:00
nomos-core fix waku feature gate (#260) 2023-07-14 15:59:16 +08:00
nomos-libp2p Small fixes for libp2p network backend (#280) 2023-08-07 06:00:41 +02:00
nomos-services Small fixes for libp2p network backend (#280) 2023-08-07 06:00:41 +02:00
simulations fix large msg sending logic (#274) 2023-08-03 20:05:43 +08:00
tests Tree settings for sim overlay (#257) 2023-07-18 14:44:23 +03:00
.DS_Store Add generic block (#93) 2023-03-14 09:55:08 -07:00
.dockerignore Docker image for nomos node (#60) 2023-02-01 10:37:15 +02:00
.gitignore Simulation initialization (#122) 2023-05-08 13:06:39 +03:00
Cargo.toml feat: add `nomos-libp2p` crate (for nomos-network backend) (#237) 2023-07-11 10:33:57 +02:00
Dockerfile Changed mockpool-node to nomos-node in Dockerfile (#212) 2023-06-21 12:02:56 +02:00
README.md Update README.md (#120) 2023-04-24 11:05:00 +02:00
rustfmt.toml add rustfmt.toml (#118) 2023-04-19 15:59:51 +08:00
shell.nix build: bump Rust to 1.70.0 to resolve clippy errors (#201) 2023-06-20 00:03:54 +09:00
sim_config.json.example Simulation initialization (#122) 2023-05-08 13:06:39 +03:00

README.md

nomos-node

Nomos blockchain node mvp

Project structure

  • nomos-core: Nomos core is the collection of essential structures for the Nomos mvp and experimental nodes.
  • nomos-services: Nomos services is the collection of components that are used as building blocks of the Nomos node prototype and the experimental nodes.
    • consensus
    • log
    • http
    • mempool
    • network
    • metrics
  • nodes: Nomos nodes is the collection of nodes that are used to run the Nomos mvp and experimental nodes.
    • nomos-node: main implementation of the Nomos mvp node.
    • mockpool-node: node with single mempool service, used to measure transaction dissemination.

Services

The Nomos node uses Overwatch as its main internal framework. This means that services request communication channels to other services to interchange information through a specified messaging API.

Service architecture

Most of the services are implemented with the same idea behind. There is a front layer responsible for handling the Overwatch service and a back layer that implement the actual service logic.

This allows us to easily replace components as needed in a type level system. In any case, a node can be setup in a declarative way composing the types. For example:

...
#[derive(Services)]
struct MockPoolNode {
    logging: ServiceHandle<Logger>,
    network: ServiceHandle<NetworkService<Waku>>,
    mockpool: ServiceHandle<MempoolService<WakuAdapter<Tx>, MockPool<TxId, Tx>>>,
    http: ServiceHandle<HttpService<AxumBackend>>,
    bridges: ServiceHandle<HttpBridgeService>,
}

Docker

To build and run a docker container with Nomos node run:

docker build -t nomos .
docker run nomos /etc/nomos/config.yml

To run a node with a different configuration run:

docker run -v /path/to/config.yml:/etc/nomos/config.yml nomos /etc/nomos/config.yml