ee85d8737d
* Removed old kzg rs modules * Added new kzgrs core module * Implemented bytes_to_polynomial and tests * Use coefficient form * Refactor evaluations into method * Use domain elements instead of roots of unity in tests * Fix encoding and test * Clippy happy * Add comments * Implement polynomial commitment * Implement proof generation * Sketch fn signature for verification * implement proof verification * Implemented verification and tests * Return evaluations from bytes_to_polynomial as well * Use modular le bytes * Implement rs encode/decode * Implement decoding tests * Implement decode using lagrange * Cleanup imports |
||
---|---|---|
.cargo | ||
.github | ||
book | ||
ci | ||
consensus | ||
ledger/cryptarchia-ledger | ||
mixnet | ||
nodes/nomos-node | ||
nomos-cli | ||
nomos-core | ||
nomos-da | ||
nomos-libp2p | ||
nomos-services | ||
nomos-utils | ||
testnet | ||
tests | ||
.codecov.yml | ||
.dockerignore | ||
.env.example | ||
.env.testnet | ||
.gitignore | ||
Cargo.toml | ||
Dockerfile | ||
README.md | ||
compose.static.yml | ||
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 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