From 0dccee65a557ae3f76feec2d54e2428bac4f7716 Mon Sep 17 00:00:00 2001 From: Cofson <41572590+Cofson@users.noreply.github.com> Date: Tue, 7 Nov 2023 19:41:30 +0100 Subject: [PATCH] Create 2023-11-07.md (#11) --- content/nomos/updates/2023-11-07.md | 84 +++++++++++++++++++++++++++++ 1 file changed, 84 insertions(+) create mode 100644 content/nomos/updates/2023-11-07.md diff --git a/content/nomos/updates/2023-11-07.md b/content/nomos/updates/2023-11-07.md new file mode 100644 index 000000000..84a88a2c9 --- /dev/null +++ b/content/nomos/updates/2023-11-07.md @@ -0,0 +1,84 @@ +--- +title: 2023-10-30 Nomos weekly +tags: + - nomos-updates +date: 2023-11-07 +lastmod: 2023-11-07 +draft: false +description: Weekly update of Nomos +--- + +## `network privacy and mixnet` + +### `research` + +### `development` + +- Enriched cover traffic specs:- https://www.notion.so/Mixnet-Specification-807b624444a54a4b88afa1cc80e100c2?pvs=4#4fa4a0ba72ed44c28d5d5dd45422843c  +- Added a fallback for the case where mixnet fails: https://www.notion.so/Mixnet-Specification-807b624444a54a4b88afa1cc80e100c2?pvs=4#b9188f37004449d5b524fcd18ffceb0f  +- Nomos integration test stabilization +- Tune timeouts (by heavy debugging): https://github.com/logos-co/nomos-node/pull/492 https://github.com/logos-co/nomos-node/pull/494  +- Prevent Duplicate error from libp2p gossipsub broadcasting: https://github.com/logos-co/nomos-node/pull/498  +- Fix port conflict: https://github.com/logos-co/nomos-node/pull/504  +- Store CI artifacts: https://github.com/logos-co/nomos-node/pull/508  https://github.com/logos-co/nomos-node/pull/510  +- Mixnet implementation improvement +- Mixclient reconnect: https://github.com/logos-co/nomos-node/pull/501  + + +## `testnet` + +### `development` + +- Services APIs: https://github.com/logos-co/nomos-node/pull/476  https://github.com/logos-co/nomos-node/pull/487  https://github.com/logos-co/nomos-node/pull/488  https://github.com/logos-co/nomos-node/pull/489  +- Mempool aware of included blocks: https://github.com/logos-co/nomos-node/pull/485 +- Voter attestation: https://github.com/logos-co/nomos-node/pull/498  +- Community PRs - typos: https://github.com/logos-co/nomos-node/pull/503  https://github.com/logos-co/nomos-node/pull/481  +- Http API integration (Made the CI all green for the integrating PRs): https://github.com/logos-co/nomos-node/pull/490  +- Chat demo: https://github.com/logos-co/nomos-node/pull/495  +- Nomos node types (extract common types from nomos-node crate): https://github.com/logos-co/nomos-node/pull/496  +- Nomos update for demo call: https://www.notion.so/Nomos-update-November-2023-3b9a90935fce4e9083e6111210d0f101  +- Static testnet configuration: https://github.com/logos-co/nomos-node/pull/499  +- In order to reliably expose all services when deployed, static configuration was added. +- Public deployment of temporal nomos testnet: ⁠general⁠ +- To work out all missing pieces a temporal VPS was chosen for testnet deployment. The deployment was tested with nomos-cli app +- Preparing for testnet deployment on nomos infrastructure: https://github.com/status-im/infra-misc/issues/189  +- To have testnet properly deployed and available at nomos.tech domain, we need to deploy it on - New API: https://github.com/logos-co/nomos-node/pull/509  +- Implement a basic version concrete error for Overwatch: https://github.com/logos-co/Overwatch/pull/32  +- Remove included  blocks from mempool: https://github.com/logos-co/nomos-node/pull/485 +- DA utilities: https://github.com/logos-co/nomos-node/pull/493   +- Rework consensus API: https://github.com/logos-co/nomos-node/pull/502  +- Include block ID during serialization of carnotinfo: +- https://github.com/logos-co/nomos-node/pull/505   +- Opened a new issue: https://github.com/logos-co/nomos-node/issues/506  + +## `private PoS` + +### `research` + +- Multi-staking - prepared a discussion doc drafting a couple of ideas such as: how we can hide stake/voting power using homomorphic encryption and the consequences of that approach. The bottom line is that with Carnot and its tree structure we cannot follow the generic Proof of Stake approach and hide the voting power at the same time. We need to modify the Proof of Stake to follow the number of votes rather than the voting power during the vote aggregation phase. This modification bears consequences that need to be studied carefully, as the probability of a failure or liveness issues might be higher: https://www.notion.so/Discussing-Privacy-of-the-Multi-Staking-PoS-for-Carnot-BFT-with-homomorphisms-ab33e034c04d4a08be688cdb86eaa741  +- Rich Nodes Attack on Weighted Carnot worked out an attack that any private weighted-Carnot protocol will need to overcome: https://www.notion.so/Finding-Rich-Nodes-in-Weighted-Carnot-4a6e5964317a4765a05c46e600b69ac8  +- Private Weighted Voting w/ Ring Signatures a solution to the above attack that relies on ring signatures to break the connection between a vote and voter: https://www.notion.so/Private-Weighted-Voting-w-Linkable-Ring-Signatures-6efcf400716f401b86d42e59941d4849  +- From discussions on the above docs, started accumulating a summary of which behaviors to reward or penalize: List of Rewarded and Penalized Actions: https://www.notion.so/List-of-Rewarded-or-Penalized-Actions-3f0991ad8b4f494a9ba1d1edfb704f03  +- Derived a probability distribution for the weights of committees for a scenario  when weights of nodes, modeled as random variables, are sampled in every voting round. +- A derivation of a probability distribution for a scenario when weights of nodes are only sampled once (currently in progress). +- Wrote  a simulation code which would  allow us  to compare failure probabilities in the above  two scenarios with the (unweighted) original Carnot version. +- Details for probability distribution for the weights of committees for a scenario when weights of nodes, modeled as random variables, are sampled in every voting round, are provided in https://www.overleaf.com/read/kkmsngmcgbkj#c4de95  +- Rewards for validators/delegators: the live document https://www.notion.so/Delegation-and-Validation-Rewards-d4af3f87a0b240739ff99b15af11cb3f?pvs=4  +- Research notes on rewards for validators/delegators: https://www.notion.so/Frederico-s-Research-Notes-b426cd773e214f35a5966f18d7db7588  +- List of Rewarded or Penalized Actions: https://www.notion.so/List-of-Rewarded-or-Penalized-Actions-3f0991ad8b4f494a9ba1d1edfb704f03  + + +## `data availability` + +### `research` + +- Finished the survey on the polynomial commitment schemes: https://www.notion.so/PCS-Survey-f06926a32c2d418897ff66fef1039a6e   +- PCS related libraries were examined. The structures and benchmarks used were reviewed. Resources related to this were added to the research notes above.  +- This work in particular is a nice compilation:https://xn--2-umb.com/23/pc-bench/  +- Studied on EC+Commitment data structures. 1D or 1.5D structure may be more suitable for data availability within the scope of the Nomos project: https://www.notion.so/Erasure-Codes-Commitment-ea7c868255ad4f1a9ff9308d7f1df1c0  + +### `development` + +### `miscellaneous` + +- Nomos team will be at the offsite next week.