* move overlay to consensus engine * Integrate random beacon in overlay This commit integrates the random beacon as specified in the nomos spec into the consensus engine library as part of the overlay. In addition, it separates the overlay part responsible for leader selection as an independent trait LeaderSelection, so as to share the overall overlay structure among most constructions. Furthermore, a leader proof has been added to a block to verify that the proposer had valid rights to do so. The current implementation hardcodes the leader selection update in the consensus service, but we probably want to abstract it away through something like the adapter pattern we use of other services in the node. * Move leader selection update to separate function * Add generic support for leader selection in consensus service (#170) * Add generic support for leader selection in consensus service * fix * use settings struct instead of tuple * fix tests
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
Description
Languages
Rust
99.4%
Groovy
0.3%
Dockerfile
0.2%