Vac 2024/06/17 §

vac:p2p: §

• nimlibp2p:vac:webrtc-transport
  • Fix nim-mbedtls MacOS installation
  • Merge small chore PR https://github.com/vacp2p/nim-webrtc/pull/13
  • DTLS ready to review https://github.com/vacp2p/nim-webrtc/pull/10
• nimlibp2p:vac:maintenance
  • https://github.com/vacp2p/nim-libp2p/pull/843
    • Older PR about races conditions; Find/implement solutions to fix it
  • fix(CI): rebuild website job https://github.com/vacp2p/nim-libp2p/pull/1125
  • fix(readme): update links https://github.com/vacp2p/nim-libp2p/pull/1126
  • fix(CI): generate website job https://github.com/vacp2p/nim-libp2p/pull/1124
  • fix(tests): testautorelay https://github.com/vacp2p/nim-libp2p/pull/1121
  • fix(tests): flaky testdaemon https://github.com/vacp2p/nim-libp2p/pull/1123
  • chore(formatting): format the whole codebase using nph 0.5.1 https://github.com/vacp2p/nim-libp2p/pull/1118
  • fix(gossipsub): pubsubpeer is created with wrong gossipsub version https://github.com/vacp2p/nim-libp2p/pull/1116

vac:tke: §

• admin
  • 2 (Frederico) + 5 (Martin) days off
  • changed the TKE milestones after getting feedback (Frederico)
  • analysis of Risk Quant Lead candidate task (Frederico)
  • Met with Martin to discuss hand-off (Juan)
• codex:cdx
  • cleaned up Litepaper (Frederico)
  • Kept working on simulations code, greatly improved efficiency (Juan)
  • Wrote piece on Filecoin government (Juan)
• codex:testnet-incentive
  • caught up the current thinking of the Codex team (Frederico)
• status:SNT-staking
  • Commented Cyp’s blogpost (Juan)
  • Discussed further directions on the swap aggregator (Juan)
• status:L2-deployment
  • Started work on catsfishing (Juan)

vac:dst: §

• vac:dst:deployment-and-analysis:codex:testnet
  • Meeting with Codex team members comparing DSNs and offering a competive analysis
• vac:dst:deployment-and-analysis:waku:10k
  • Running attempts at “10k with metrics”, new tests with noise dampening
  • Brought back missing nodes
• vac:dst:deployment-and-analysis:waku:midscale
  • Continued debugging waku regression
  • Repeated deployments with 0.28, and compared with 0.27.
  • Gave feedback to Gabriel@Waku about change in Waku logging
  • 0.28 deployment for Ivan/Hanno, plotting message time distribution to all peers.
    • Ivan specifically requested different sizes and latencies- vac:dst:deployment-and-analysis:waku:midscale
• vac:dst:tooling:vac:visualiser-tool
  • Continue work on injecting elastic information in visualiser
• vac:dst:deployment-and-analysis:vac:libp2p-version-testing
  • Tried to repeat simulations with different message size and latency witn 1.2.0 and 1.3.0
    • Couldn’t obtain data, still trying to figure out why

vac:qa: §

• waku:test-automation-status-go-cli
  • contact request tests - merged(@Florin)
  • private groups tests - in progress(@Florin)
  • reviewed Pablos’s PR where he fixed and added new functionality to status-cli(@Florin)
• waku:interop-testing-02
  • Test/peer connection management in progress(@Roman)
• nomos:test-automation-cryptarchia
  • chore: cryptarchia unit tests update on hold till 17th June(@Roman)
  • chore: cryptarchia ledger unit tests update in progress(@Roman)
• waku:test-automation-rln
  • Investigate and fix waku-simulator issues with docker/podman on windows and fedora(@Alex)
  • Began running tests(@Alex)
• waku:maintenance-nwaku
  • Answer open issues(@Alex)

vac:acz: §

• rlnp2p:waku:rlnv2-e2e
  • chore(tests): add kats test for merkle proof
  • chore: integrate uups proxy
  • chore: scaffold deployments
  • merged tests PR after addressing reviews
• stealth-address-kit:vac:maintenance
  • chore: refactor into 2 crates, example and sdk
  • chore: v0.2.0-beta release
  • chore: refactor deps, make lib lighter
• validator-privacy:nimbus:productionize-tor-push
  • reviewed codebase and paper
• secure-channels:waku:mls-design
  • Study on login and authentication options for MLS design in terms of decentralization, adding a conclusion to doc
  • Examine login mechanism of a self-hosted messaging app based on matrix named element see in github
  • Finished the (first version) of the presentation for the EthCC Brussels.
• secure-channels:waku:mls-poc
  • tried to implement poc using openmls and centralised DS -> not finished, found that using decentralised approach is better
  • started to investigate how to use waku as DS
• consulting:codex:proxy-re-encryption
  • attended kick-off call, meeting notes with action points for next steps
• admin/misc
  • added codex proxy re-encryption to roadmap pr and merged

vac:sc:: §

• vac:maintenance/misc
  • Setting up first certora rules in Codex repo
  • ENS usernames migrate remaining tests to forge
  • ENS usernames forge
    • https://github.com/status-im/ens-usernames/issues/129
    • https://github.com/status-im/ens-usernames/tree/foundry-template-test
  • Researched EIP4626 tokenized vaults and security vulnerabilities
  • Presented research to team
  • Meeting with Finance and Security to discuss plans with Zodiac modules
    • Finance will set up deploy script to create a SAFE with multisig and zodiac roles modifier + scope guard
      • SC team and Security team will review deploy scripts
      • SC team will deploy contracts on behalf of finance
  • Rebased Ricardos work on ENS username repo refactor
    • Branch: https://github.com/status-im/ens-usernames/commits/foundry-template/
    • Also had session with him about ironing out some processes

vac:nim: §

• tooling:vac:compiler
  • Fix an issue in nimsuggest where unknown files werent being handled: https://github.com/nim-lang/Nim/pull/23696
  • Backports: https://github.com/nim-lang/Nim/pull/23702 and https://github.com/nim-lang/Nim/pull/23701
  • Fix: “#23695: On Linux, “nimsuggest” crashes if Nim is installed in /usr/bin and the library in /usr/lib/nim” https://github.com/nim-lang/Nim/pull/23697
• tooling:vac:lsp
  • Implements the extension/status endpoint (https://github.com/nim-lang/langserver/commit/3879966eed20f04ce4254b67c5c6496c06358b79) It’s useful for asserting in tests in a reliable way as it exposes the langserver and nimsuggest instances current status (i.e. main file, known files, etc.) It can also be useful to create a specific window in extension to quickly inspect the current status for a given project
• tooling:vac:editor
  • Implements Show NimLangServer Status command. (https://github.com/nim-lang/vscode-nim/pull/67) Right now is just outputing into the output window. In the near future we are going to build a separate window to inspect it.

vac:rfc: §

• nomos:specs-init
  • Worked on data availability rfc, not ready for feedback, still in draft - https://github.com/vacp2p/rfc-index/pull/41
• admin/misc
  • Closed and moved issues from rfc old repo; archived old repo (https://github.com/vacp2p/rfc)
  • Updated readme on rfc-website - https://github.com/vacp2p/rfc.vac.dev/pull/2

vac:dr: §

• vac:admin
  • Team synced outside of standup for additional feedback.
  • (Marvin) Began investigating gossipsub lazy message issue as prep for testing.
• gsub-scaling:vac:unstructured-p2p-improvements-survey
  • Began work on research blog post for gossipsub improvements for large messages: WIP draft
• zk:codex:zk-consulting
  • Wrote notes on a binding issue in Codex proposal notes along with a solution.
  • Wrote brief notes for PolyMath.
• vac:dr:anon:vac:gossipsub-anonymity
  • Started writing Anonymized GossipSub Transport Protocol (AGTP) specification -WiP.
    • (AGTP will be renamed as the name is not fitting; just WiP atm)
    • Researched ways to prevent adversarial senders from abusing the mixnet to DoS single exit nodes; current issue: this could potentially lead to honest exit nodes being penalized and ignored.
  • Investigated mining techniques; selected proof of work for now.

vac:nes: §

• virtual-machine-creation:vac:vm-foundations
  • work on list of ZkVMs
    • Finished entering data on missing Zkvms info. [Moudy]
    • Started going through codebases ov zkVMs. [Rostyslav]
    • Updated and integrated additional information on Github and Table lists. [Moudy]
    • Started discussions about the selection of Zkvms and how to add privacy requirements.[Team]
• state-separation:vac:state-separation-architecture-01
  • Reviewed the state separation architecture prototype. [Moudy]
  • Started defining important traces and working through a first draft. [Moudy]
  • Reviewed the prototype and extracted the rest of possible topics to obtain the scope of the blogpost. [UGUR] [ACZ]
  • Work on a demo example of state separation execution for the prototype for each kind of TX. [UGUR + MOUDY] [ACZ]
  • Examine the private execution project named sarma