nomos:
network privacy and mixnet:
research:
- Review of the “Untraceable electronic mail, return addresses, and digital pseudonyms” paper. Review of the “The Loopix anonymity system” paper.
- Notes provided in the overleaf document https://www.overleaf.com/read/rybwvjftfrrg
development:
- Polishing mixnet to make it ready for the testnet:
- Helping preparing mixnet deployments: https://github.com/logos-co/nomos-node/pull/408
- Reviewed mixnet connection management
- Refactor the libp2p network backend: https://github.com/logos-co/nomos-node/tree/libp2p-refactor-yjlee and based on that prepare to measure the quality of unobservability - https://github.com/logos-co/nomos-node/issues/391
- Block building: https://github.com/logos-co/nomos-node/pull/401
- Fountain codes: https://github.com/logos-co/nomos-node/pull/407
- Got the mixnet retry PR merged: https://github.com/logos-co/nomos-node/pull/386
- Finish the concrete error implementation for mixnet and ready for merge: https://github.com/logos-co/nomos-node/pull/405
- WIP: fan-in message passing model for mixnode: https://github.com/logos-co/nomos-node/tree/mixnet-fan-in
testnet:
development:
- Testnet preparation: https://github.com/logos-co/nomos-node/pull/410
- Testnet POC with libp2p merged: https://github.com/logos-co/nomos-node/pull/364
- The POC for testnet using etcd and docker compose was reviewed and merged. The mixnet functionality will be added on top of this.
- Simulation branch overlay with 1 committee fix: https://github.com/logos-co/nomos-node/pull/402
- A bug where branch overlay results different from tree overlay with one committee blocked research team to use simulations results. Fixed it.
- Improvements in CI:
- Minor improvements to remove annoying red x’s from our CI
private PoS:
research:
- Shadows logic: Looking at how to describe the logic of the shadow in the most clear way: It will be divided into a set of modules, each module taking care of processing a separate communication channel.
- All channels have their logic described in adequate modules and with references to self-descripting functions. However, some of them (like how exactly to aggregate votes) must yet to be defined.
- Hastiness issues: In short, the leader, in order to limit the cost of vote aggregation can decide to not to include votes from top committees (and root in particular). This is an acceptable strategy and will lead to a correctly formed aggregation proof. The proof will include a global threshold of votes from lower committees but not from the top committees (and root committee in particular). The impact of this leader’s hastiness does not break the security of the protocol as a threshold of votes is correctly gathered. However, it may limit rewards from the top committees (and root in particular), as the votes from those committees may not be needed to reach the threshold. More on that under the issues section of the PPoS doc.
data availability:
research:
- First stab at privacy solution for the network layer for consensus and DA: https://www.notion.so/Practical-Private-Addressing-Network-Privacy-Component-2-2b9b4923124a4fdb81dba5d2bba1d289?d=99166164267a46589c5715175e1b3657#5e27d2010d30468f9d8f0d0928b9c639
- Init survey of SoA in network privacy alternative solutions
development:
- DA nomos core kickstart, added different pieces that were missing for abstractions: https://github.com/logos-co/nomos-node/pull/390
- Added attestation trait
- Added certificate trait
- Added DaProtocol trait that abstracts encoding/decoding, and put the pieces together for blob+attestation+certificate handling.
- Refactored (moved and restructured) da modules
- Refactor and improve common traits - https://github.com/logos-co/nomos-node/pull/395
- Implement a simple da protocol with full replication - https://github.com/logos-co/nomos-node/pull/400
- Implement a command to disseminate blobs through the network - https://github.com/logos-co/nomos-node/pull/396
- Added da-service to nomos node - https://github.com/logos-co/nomos-node/pull/404
- Housekeeping: