97c653efe3
* Update rust build image version * Docker compose file for testnet * Wrap tcp into dns transport in order to resolve hostnames (#346) * Docker compose for small libp2p node network * Install etcdctl to node containers * Register libp2p nodes on etcd * Register IP address in KV store * Interconnect libp2p nodes * Use delimiter in cli and env variables * Use docker compose initial env config * Leave main Dockerfile as is, use new ones in testnet dir * Remove etcd installation script * run_mixnet.sh placeholder * Use .env file for docker compose config * Ignore local .env file * Wrap sh envvars used in strings * Remove mixnode placeholders * Use default values for envconfig * Update labels in Dockerfiles * Sanitize scripts via shellcheck * Export env for nomos node * Updated to latest libp2p config * Pass config to bootstrap node |
||
---|---|---|
.cargo | ||
.github/workflows | ||
ci | ||
consensus-engine | ||
mixnet | ||
nodes | ||
nomos-core | ||
nomos-da | ||
nomos-libp2p | ||
nomos-services | ||
simulations | ||
testnet | ||
tests | ||
.DS_Store | ||
.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