d67d08e81d
* Use more descriptive names for generic parameters We're starting to have tens on generic parameters, if we don't use descriptive names it'll be pretty hard to understand what they do. This commit changes the names of the mempool parameters in preparation for the insertion of the da certificates mempool to distinguish it from cl transactions. * Add mempool for da certificates * Add separate certificates mempool to binary * ignore clippy lints |
||
---|---|---|
.cargo | ||
.github | ||
ci | ||
consensus-engine | ||
mixnet | ||
nodes | ||
nomos-cli | ||
nomos-core | ||
nomos-da | ||
nomos-libp2p | ||
nomos-services | ||
simulations | ||
testnet | ||
tests | ||
.codecov.yml | ||
.dockerignore | ||
.env.example | ||
.gitignore | ||
Cargo.toml | ||
Dockerfile | ||
README.md | ||
compose.yml | ||
rustfmt.toml | ||
shell.nix | ||
sim_config.json.example |
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