Nomos blockchain node
Go to file
Youngjoon Lee e7d591b7bc
Mixnet v1 (#569)
* base

* Remove mixnet client from libp2p network backend (#572)

* Mixnet v1: Remove all mixnet legacies: mixnet crate, mixnode binary, tests, and docker (#573)

* Mixnet v1: Skeleton (#570)

* Use QUIC for libp2p (#580)

* Add Poisson interval function for Mixnet (#575)

* Mixnet network backend skeleton (#586)

* Libp2p stream read/write (#587)

* Emitting packets from mixclient using libp2p stream (#588)

* Handle outputs from mixnode using libp2p stream/gossipsub (#589)

* Refactor poisson (#590)

* Mix client Poisson emission (#591)

* Mix node packet handling (#592)

* Mix Packet / Fragment logic (#593)

* Move FisherYates to `nomos-utils` (#594)

* Mixnet topology (#595)

* Mix client/node unit tests (#596)

* change multiaddr from tcp to udp with quic-v1 (#607)

---------

Co-authored-by: Al Liu <scygliu1@gmail.com>
2024-03-12 15:47:35 +09:00
.cargo fix link flgs (#144) 2023-05-08 17:28:10 +02:00
.github Use 2x timeout for integration tests in Codecov CI (#533) 2023-11-28 09:02:24 +09:00
ci Mixnet v1 (#569) 2024-03-12 15:47:35 +09:00
consensus Mixnet v1 (#569) 2024-03-12 15:47:35 +09:00
ledger/cryptarchia-ledger move ledger into separate crate (#606) 2024-03-11 15:15:17 +01:00
mixnet Mixnet v1 (#569) 2024-03-12 15:47:35 +09:00
nodes/nomos-node Mixnet v1 (#569) 2024-03-12 15:47:35 +09:00
nomos-cli Mixnet v1 (#569) 2024-03-12 15:47:35 +09:00
nomos-core consensus-engine to carnot-engine. (#551) 2024-01-04 15:09:43 +01:00
nomos-da Update code related to rust-kzg according to its latest ver (#538) 2023-11-28 17:55:55 +09:00
nomos-libp2p Mixnet v1 (#569) 2024-03-12 15:47:35 +09:00
nomos-metrics Prometheus metrics service (#522) 2024-01-12 16:15:12 +02:00
nomos-services Mixnet v1 (#569) 2024-03-12 15:47:35 +09:00
nomos-utils Mixnet v1 (#569) 2024-03-12 15:47:35 +09:00
simulations Mixnet v1 (#569) 2024-03-12 15:47:35 +09:00
testnet Mixnet v1 (#569) 2024-03-12 15:47:35 +09:00
tests Mixnet v1 (#569) 2024-03-12 15:47:35 +09:00
.codecov.yml Disable codecov annotations (#409) 2023-09-15 15:11:50 +03:00
.dockerignore Docker image for nomos node (#60) 2023-02-01 10:37:15 +02:00
.env.example Mixnet v1 (#569) 2024-03-12 15:47:35 +09:00
.env.testnet Mixnet v1 (#569) 2024-03-12 15:47:35 +09:00
.gitignore Store logs from failed CI as artifacts (#508) 2023-11-07 09:38:10 +09:00
Cargo.toml Mixnet v1 (#569) 2024-03-12 15:47:35 +09:00
Dockerfile Bump rust (#602) 2024-03-01 13:28:05 +02:00
README.md Fix typos (#503) 2023-11-03 09:29:40 +01:00
compose.static.yml Mixnet v1 (#569) 2024-03-12 15:47:35 +09:00
compose.yml Mixnet v1 (#569) 2024-03-12 15:47:35 +09:00
rustfmt.toml add rustfmt.toml (#118) 2023-04-19 15:59:51 +08:00
shell.nix Bump rust (#602) 2024-03-01 13:28:05 +02: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 implements 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