logos-co/roadmap
1
0
Fork 0
mirror of https://github.com/logos-co/roadmap.git synced 2025-01-12 17:34:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

vac standup format update

Browse Source 
Signed-off-by: ksr <kaiserd@users.noreply.github.com>
This commit is contained in:
ksr 2023-09-04 12:57:42 +02:00
parent dfb356fb25
commit 778ccbce21
1 changed files with 106 additions and 90 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

196
content/roadmap/vac/updates/2023-08-28.md
View File

@ -7,26 +7,32 @@ lastmod: 2023-08-28
draft: false draft: false
--- ---
## Vac week 35
* Vac Milestones: https://www.notion.so/Vac-Roadmap-907df7eeac464143b00c6f49a20bb632 * Vac Milestones: https://www.notion.so/Vac-Roadmap-907df7eeac464143b00c6f49a20bb632
* Vac Github Repos: https://www.notion.so/Vac-Repositories-75f7feb3861048f897f0fe95ead08b06 * Vac Github Repos: https://www.notion.so/Vac-Repositories-75f7feb3861048f897f0fe95ead08b06
**Vac week 35** ### vsu::P2P
- *vsu::P2P*
- `vac:p2p:nim-libp2p:vac:maintenance` - `vac:p2p:nim-libp2p:vac:maintenance`
- Becaming a Validator in the Nimbus Consensus client (95%) - Becaming a Validator in the Nimbus Consensus client (95%)
- IWANT replies can be bigger than the pubsub message limit (100%, on review) https://github.com/status-im/nim-libp2p/issues/887 - IWANT replies can be bigger than the pubsub message limit (100%, on review) https://github.com/status-im/nim-libp2p/issues/887
- Improve gossipsub DDoS resistance (98%) https://github.com/status-im/nim-libp2p/pull/920 - Improve gossipsub DDoS resistance (98%) https://github.com/status-im/nim-libp2p/pull/920
- *vsu::Tokenomics*
- admin/misc: ### vsu::Tokenomics
- `vac:tke::codex:economic-analysis`
- Timeline of Filecoin vs competitors, IPFS vs Filecoin usage, Filip: miners perspective - admin/misc:
- `vac:tke::status:SNT-staking` - `vac:tke::codex:economic-analysis`
- Further debugging, verify Multiplier Points calculation (especially gas fee optimization, how GMX implements) - Timeline of Filecoin vs competitors, IPFS vs Filecoin usage, Filip: miners perspective
- `vac:tke::nomos:economic-analysis` - `vac:tke::status:SNT-staking`
- Book seperate calls w/ Moh and Marcin to discuss helping them w/ their relative points of focus - Further debugging, verify Multiplier Points calculation (especially gas fee optimization, how GMX implements)
- `vac:tke::waku:economic-analysis` - `vac:tke::nomos:economic-analysis`
- Call w/ Aaryamann on RLN, condense our thoughts to a "proposal" for Waku - Book seperate calls w/ Moh and Marcin to discuss helping them w/ their relative points of focus
- *vsu::Distributed Systems Testing (DST)* - `vac:tke::waku:economic-analysis`
- Call w/ Aaryamann on RLN, condense our thoughts to a "proposal" for Waku
### vsu::Distributed Systems Testing (DST)
- `vac:dst:analysis:nomos:nomos-simulation-analysis` - `vac:dst:analysis:nomos:nomos-simulation-analysis`
- Analysis done, scales to million nodes - Analysis done, scales to million nodes
- Exploratory sets of runs done - Exploratory sets of runs done
@ -38,78 +44,88 @@ draft: false
- Investigated how the existing tests are running and how the code is structured - Investigated how the existing tests are running and how the code is structured
- `admin/misc`: - `admin/misc`:
- 2 CCs ooo - 2 CCs ooo
- *vsu:Smart Contracts (SC)*
- `vac:sc::vac:secureum-upskilling` ### vsu:Smart Contracts (SC)
- Finished Secureum Slot 6
- Read a bit into Upgradable contract patterns - `vac:sc::vac:secureum-upskilling`
- `vac:sc::status:community-contracts-maintenance` - Finished Secureum Slot 6
- Moved `communities-contracts` repo to our Foundry template https://github.com/status-im/communities-contracts/pull/1 - Read a bit into Upgradable contract patterns
- Also implemented additional tests - `vac:sc::status:community-contracts-maintenance`
- `vac:sc::vac:maintainance/misc` - Moved `communities-contracts` repo to our Foundry template https://github.com/status-im/communities-contracts/pull/1
- Finished up moving `community-dapp/contracts` to foundry template - Also implemented additional tests
- `vac:sc::status:community-contracts-deployer` - `vac:sc::vac:maintainance/misc`
- Brainstormed and discussed desired deployer contract with desktop team; Discussion: https://github.com/status-im/status-desktop/issues/11954#issuecomment-1694591812 - Finished up moving `community-dapp/contracts` to foundry template
- updating ERC2470 https://eips.ethereum.org/EIPS/eip-2470 - `vac:sc::status:community-contracts-deployer`
- `vac:sc::status:snt-staking-contract-maintenance` - Brainstormed and discussed desired deployer contract with desktop team; Discussion: https://github.com/status-im/status-desktop/issues/11954#issuecomment-1694591812
- discussing issue with order of processAccount giving advantages on first callers - updating ERC2470 https://eips.ethereum.org/EIPS/eip-2470
- *vsu:Applied Cryptogarphy & ZK (ACZ)* - `vac:sc::status:snt-staking-contract-maintenance`
- `vac:acz:rlnp2p:waku:membership-management` - discussing issue with order of processAccount giving advantages on first callers
- Wrote a tool `rln_keystore_generator` : https://github.com/waku-org/nwaku/pull/1925, https://github.com/waku-org/nwaku/pull/1928, https://github.com/waku-org/nwaku/pull/1931
- `vac:acz:rlnp2p:waku:rln-relay-enhancments` ### vsu:Applied Cryptogarphy & ZK (ACZ)
- tree metadata should include chainId and contractAddress - https://github.com/waku-org/nwaku/pull/1932
- set flush_interval appropriately -https://github.com/waku-org/nwaku/pull/1933 - `vac:acz:rlnp2p:waku:membership-management`
- integrate new WakuRlnRegistry contract - https://github.com/waku-org/nwaku/pull/1943 - Wrote a tool `rln_keystore_generator` : https://github.com/waku-org/nwaku/pull/1925, https://github.com/waku-org/nwaku/pull/1928, https://github.com/waku-org/nwaku/pull/1931
- bump zerokit to v0.3.2 https://github.com/waku-org/nwaku/pull/1951 - `vac:acz:rlnp2p:waku:rln-relay-enhancments`
- tree metadata should include window of roots - https://github.com/waku-org/nwaku/pull/1953 - tree metadata should include chainId and contractAddress - https://github.com/waku-org/nwaku/pull/1932
- sync tree state from contract deployed block number - https://github.com/waku-org/nwaku/pull/1955 - set flush_interval appropriately -https://github.com/waku-org/nwaku/pull/1933
- optimization to waku_keystore - https://github.com/waku-org/nwaku/pull/1956 - integrate new WakuRlnRegistry contract - https://github.com/waku-org/nwaku/pull/1943
- fixed a `forceProgression` bug in the WakuRlnRegistry contract - https://github.com/waku-org/waku-rln-contract/pull/6 - bump zerokit to v0.3.2 https://github.com/waku-org/nwaku/pull/1951
- `vac:acz:zerokit:vac:maintenance` - tree metadata should include window of roots - https://github.com/waku-org/nwaku/pull/1953
- prevent tree db from being recreated if it exists - https://github.com/vacp2p/zerokit/pull/209 - sync tree state from contract deployed block number - https://github.com/waku-org/nwaku/pull/1955
- released zerokit v0.3.2 - https://github.com/vacp2p/zerokit/releases/tag/v0.3.2 - optimization to waku_keystore - https://github.com/waku-org/nwaku/pull/1956
- merged PR to fix a stopgap introduced by PR 201 https://github.com/vacp2p/zerokit/pull/207 - fixed a `forceProgression` bug in the WakuRlnRegistry contract - https://github.com/waku-org/waku-rln-contract/pull/6
- `vac:acz:zerokit:vac:zerokit-v0.4` - `vac:acz:zerokit:vac:maintenance`
- Prepared a PR to deal with `message_id` range check https://github.com/vacp2p/zerokit/pull/210 - prevent tree db from being recreated if it exists - https://github.com/vacp2p/zerokit/pull/209
- Researched needed changes to `rln-cli` - released zerokit v0.3.2 - https://github.com/vacp2p/zerokit/releases/tag/v0.3.2
- *vip::zkVM* - merged PR to fix a stopgap introduced by PR 201 https://github.com/vacp2p/zerokit/pull/207
- `vac:zkvm::vac:research-existing-proof-systems` - `vac:acz:zerokit:vac:zerokit-v0.4`
- 40% update of the blog is done, working on finding smoother ways to explain findings and alternatives (focusing on a blog structure rather than a document) - Prepared a PR to deal with `message_id` range check https://github.com/vacp2p/zerokit/pull/210
- `vac:zkvm::vac:proof-system-benchmarks` - Researched needed changes to `rln-cli`
- Added a summary table for different performances
- `vac:zkvm::vac:research-existing-proof-systems` ### vip::zkVM
- Finished Plonky2 research document https://www.notion.so/zkVM-cd358fe429b14fa2ab38ca42835a8451?pvs=4#01301b98f3af4157b932112ed998cff2
- Write notes on Protostar - `vac:zkvm::vac:research-existing-proof-systems`
- `vac:zkvm::vac:proof-system-benchmarks` - 40% update of the blog is done, working on finding smoother ways to explain findings and alternatives (focusing on a blog structure rather than a document)
- minor fixes plonky2 PR https://github.com/vacp2p/zk-explorations/pull/5 - `vac:zkvm::vac:proof-system-benchmarks`
- README's to make zk-explorations repo public https://github.com/vacp2p/zk-explorations/pull/4 - Added a summary table for different performances
- merged and closed needed PRs for zk-explorations repo - `vac:zkvm::vac:research-existing-proof-systems`
- work on Halo2 benchmark - Finished Plonky2 research document https://www.notion.so/zkVM-cd358fe429b14fa2ab38ca42835a8451?pvs=4#01301b98f3af4157b932112ed998cff2
- *vc::Deep Research* - Write notes on Protostar
- `vac:dr:valpriv:vac:tor-push-poc` - `vac:zkvm::vac:proof-system-benchmarks`
- dev: fixed bugs related to initialization, changed to building async tor connections, adding direct peers, triaging/debugging issues https://github.com/vacp2p/nimbus-eth2-experimental/pull/2/commits/431a76014b3f584573329993b167fe1118eca6b3 - minor fixes plonky2 PR https://github.com/vacp2p/zk-explorations/pull/5
- test: readied setup o beacon node(s) with validator keys, test attestation transmission over tor. Planning for measuring delays - README's to make zk-explorations repo public https://github.com/vacp2p/zk-explorations/pull/4
- `vac:dr:valpriv:vac:tor-push-relwork` - merged and closed needed PRs for zk-explorations repo
- solution section refined with several updates including adding a figure for the Tor-push method. - work on Halo2 benchmark
- dedicated section on "Theoretical Analysis"
- four different possible scenarios for the attacker to break the anonymity of the Tor network ### vc::Deep Research
- `vac:dr:gsub-scaling:vac:gossipsub-improvements-tech-report`
- Literature study related to scalability, overlay design, efficient message propagation in unstructured p2p networks - `vac:dr:valpriv:vac:tor-push-poc`
- Started writing a survey report on efficient broadcast in large scale p2p networks. - dev: fixed bugs related to initialization, changed to building async tor connections, adding direct peers, triaging/debugging issues https://github.com/vacp2p/nimbus-eth2-experimental/pull/2/commits/431a76014b3f584573329993b167fe1118eca6b3
- `vac:dr:gsub-scaling:vac:gossipsub-simulation` - test: readied setup o beacon node(s) with validator keys, test attestation transmission over tor. Planning for measuring delays
- Executed different gossipsub simulations in shadow simulator - `vac:dr:valpriv:vac:tor-push-relwork`
- can now collect different metrics like packet delivery ratio, data overhead, control overhead, network bandwidth utilization, average latency & standard deviations - solution section refined with several updates including adding a figure for the Tor-push method.
- `vac:dr:consensus:nomos:carnot-bribery-article` - dedicated section on "Theoretical Analysis"
- Continue work on the article on bribery attacks, PoS and Carnot. Different examples including one based on game theory were presented to show that bribery attacks are economic attacks and cannot be addressed alone in the consensus layer. Economy based solutions have to be considered at the PoS layer. - four different possible scenarios for the attacker to break the anonymity of the Tor network
- `vac:dr:consensus:nomos:carnot-vote-2-3rds-vote-aggregation` - `vac:dr:gsub-scaling:vac:gossipsub-improvements-tech-report`
- Begin work on Carnot variant that aggregates the majority of votes. - Literature study related to scalability, overlay design, efficient message propagation in unstructured p2p networks
- Designing the algorithm. - Started writing a survey report on efficient broadcast in large scale p2p networks.
- `vac:dr:consensus:nomos:carnot-paper` - `vac:dr:gsub-scaling:vac:gossipsub-simulation`
- Analyzing and discussing Carnot tests. There were variance in the latency results. We think it is due to the geographical distribution of nodes. Hence, Gusto was asked to use a single geographic zone to acheive a smooth curve while verifying that the variance is due to the latency cause by geographical distribution of nodes. - Executed different gossipsub simulations in shadow simulator
- *vc::RFC* - can now collect different metrics like packet delivery ratio, data overhead, control overhead, network bandwidth utilization, average latency & standard deviations
- `vac:rfc:rfc:status:port-status-specs` - `vac:dr:consensus:nomos:carnot-bribery-article`
- Updated RFC spec for Community History Archive protocol according to PR feedback - Continue work on the article on bribery attacks, PoS and Carnot. Different examples including one based on game theory were presented to show that bribery attacks are economic attacks and cannot be addressed alone in the consensus layer. Economy based solutions have to be considered at the PoS layer.
- https://github.com/vacp2p/rfc/pull/610 - `vac:dr:consensus:nomos:carnot-vote-2-3rds-vote-aggregation`
- This has been reviewed more and those additional comments need to be addressed as well - Begin work on Carnot variant that aggregates the majority of votes.
- Started porting `/spec/6/PAYLOADS` to Vac - Designing the algorithm.
- `vac:dr:consensus:nomos:carnot-paper`
- Analyzing and discussing Carnot tests. There were variance in the latency results. We think it is due to the geographical distribution of nodes. Hence, Gusto was asked to use a single geographic zone to acheive a smooth curve while verifying that the variance is due to the latency cause by geographical distribution of nodes.
### vc::RFC
- `vac:rfc:rfc:status:port-status-specs`
- Updated RFC spec for Community History Archive protocol according to PR feedback
- https://github.com/vacp2p/rfc/pull/610
- This has been reviewed more and those additional comments need to be addressed as well
- Started porting `/spec/6/PAYLOADS` to Vac