vacp2p/roadmap
1
0
Fork 0
mirror of https://github.com/vacp2p/roadmap.git synced 2026-01-08 21:27:58 -05:00
Code Issues Packages Projects Releases Wiki Activity
Files
master
roadmap/content/weeklies/2025-05-12.md
fbarbu15 d5208b3c53 Chore/update namings (#332)
2025-11-10 15:25:13 +02:00

13 KiB
Raw Permalink Blame History

title, tags, date, lastmod, draft
title tags date lastmod draft
2025-05-12 Vac weekly
vac-updates
2025-05-12 2025-05-12 false

Vac 2025/05/12

vac:p2p:

  • ift:2025q1-gossipsub-perf-improvements
    • Worked on nimbus integration in Ethshadow. Modified nimbus fork here
      • Had to add a bare minimal support for umash and signalfd system calls in shadow simulator modified fork here. Nimbus BN nodes work fine now, but VC nodes exit (result defect, probably in bearssl, or signalfd)
      • Trying to run nimbus BN with lighthouse VC and Geth EL. Currently resolving inconsistent genesis state error
    • Looking into performance comparison for current gossipsub proposals
  • vac:p2p:ift:2025q2-nimlibp2p-kad-dht:routing-and-rpc
    • More progress in nim-libp2p#1324.
    • Added most of the logic for find node, and basic implementation of routing table
    • I have started to write test units for the code
  • vac:p2p:acz:2025q2-acz-consulting:libp2p-mix-consulting
    • Debug why number of streams were not decreasing after mix connections were closed
    • It was due to a difference in the signature of the functions to close a stream :(
  • vac:p2p:ift:2025q2-nimlibp2p-maintenance:maintenance
    • nim-quic#70 feat: accept and close connections gracefully
  • vac:p2p:ift:2025q2-nimlibp2p-webtransport:http3
    • continue work on http3 client nim-quic #68
    • implemeted client barebones
    • started working on event loop - transfering data from/to underlying QUIC stack and nghttp3
    • coarse tasks to be implemented after:
      • reading settings
      • sending request
      • reading response
  • vac:p2p:ift:2025q2-nimlibp2p-autotls:acme-registration
  • vac:p2p:ift:2025q2-nimlibp2p-autotls
  • misc/admin
    • 1 CC 2d off
    • 1 CC 1d off

vac:tke:

  • admin
    • 5 days off (compensating weekend in Split + public holidays)
    • review comms strategy doc and discuss with Santiago
    • review and add content to Juan's Split summary doc
    • other follow ups from Split
  • vac:tke:nomos:macroeconomy::preliminary-blockspace
    • lengthy discussions about the requirements of this study with Nomos team
  • vac:tke:nomos:macroeconomy::preliminary-block-rewards
    • Update blockspace and block rewards spec with constraints and requirements based on discussions
  • vac:tke:nomos:macroeconomy::revision-economic-model
    • reviewed the Blend Protocol v1 doc
  • vac:tke:nomos:macroeconomy:block-rewards
    • Working on actionable items from IFT all hands
    • Taking over TFM work
    • Familiarizing myself with documentation of blockspace
  • vac:tke:nomos:macroeconomy:network-state-infra
    • review the plan from Split and organize work
  • vac:tke:ift:tokenomics-research-forum::token-valuation
    • continued the analysis of the token valuation metrics using PLS Regression
  • vac:tke:status:karma-incentives:karma-params
    • review the plan from Split and organize work
    • Working on data analysis for Linea, which will in turn be used to derive the tiers for Karma

vac:qa:

  • nomos:2025q2-da-testing:data-confidentiality
  • waku:2025q2-interop-testing:maintenance
  • waku:2025q2-waku-sync-testing:unit
    • Finished state transition tests in PR 97
    • Added stress tests in same PR
    • Added edge /corner tests same PR
    • Found inaccurate results when sending message with time difference will discuss it with Simon this week
  • 2025q2-nim-libp2p-testing:gossipsub-extended
  • admin/misc
    • Parental leave 5 CC days
    • Day off 3 CC days

vac:dst:

  • admin/misc
    • ooo after offsite

vac:sc:

vac:acz:

  • ift:2025q2-zerokit:parallel-computation-study
    • Reviewd PR and try to solved nvm installed building issue in my env. Decided to merge current solution and maybe later open task for shell scripts for building zerokit
    • Resolved build issue in rln-wasm.
    • Updated README for the rln-wasm module PR.
    • PR is reviewed.
  • ift:2025q2-de-mls-tesnet:commit-and-proposal
    • Start working on splitting commit message to proposal and commit message
  • ift:2025q2-libp2p-mix-testnet:dockerize
    • Resolved LPChannel stream count issue — confirmed no spikes under yamux. Docker is in here.
  • ift:2025q2-libp2p-mix-testnet:update-rfc
    • Continued Mix RFC refactor (see mix-rev1 branch); updated sections through 5.4.
  • ift:2025q2-libp2p-mix-testnet:surb-implementation
    • Introductory discussion on SURBs and Mix protocol context.
  • ift:2025q2-de-mls-tesnet:test-deployment
  • ift:2025q2-zerokit:merkle-tree-improvement
    • Continued working on Merkle tree refactoring to improve parallelism PR:
      • Improved Merkle tree parallelism by adding support for other tree types.
      • Added more comprehensive tests and benchmarks to cover parallel execution case.
      • And finalized the benchmark report in this comment.
  • ift:2025q2-rln-status-l2:rpc-node-modification
  • ift:2025q2-zerokit:iden3-witness-review
  • ift:2025q2-rln-status-l2:prover-service
  • ift:2025q2-zerokit:semaphore-parts-bench
    • draft pr for poseidon work
    • draft pr for imt work
    • Got first benchmark comparison done between our poseidon and light-poseidon. Initial analysis: ours is about 10% faster.
    • Made my firsh chip at getting a merkle tree benchmark comparison.
  • ift:2025q2-de-mls-tesnet:consensus-rfc
    • Refine consensus RFC by adding liveness section as we discussed in offsite. Then the RFC PR is ready to review.
  • ift:2025q2-rln-status-l2:maintain
    • Discuss the prover scenario doc with Status team and clarify some points, such as denylist and prover.
  • ift:2025q2-de-mls-tesnet:multi-admin-rfc
    • Started the task with writing the de-MLS flow doc
    • Create a doc about an alternative name of "admin" in de-MLS.
  • ift:2025q2-de-mls-tesnet:blogpost-de-mls-over-waku
  • nes:2025q2-nescience-consulting:unifying-q1-docs
  • admin/misc
    • Prepared new tasks for de-mls roadmap regarding discussion on all-hands PR
    • 1 cc is ooo for two days (bank holiday)
    • 1 cc is ooo for three days (sick leave)
    • 1 cc is ooo for one day (bank holiday)
    • 1 cc is ooo for whole week

vac:nim:

vac:rfc:

vac:sec:

  • ift:2025q2-signatory-registry-implementation:signatory-inventory-revalidation
    • started populating the new defined schema
  • ift:2025q2-sec-infra-maintenance:knowbe4-renewal
    • Started the renewal process
  • ift:2025q2-awareness-program:launch-cybersecurity-training-campaign
    • Lauched the training for those who got caught during the last phishing campaign (18)

vac:nes:

  • state-separation-architecture-poc:sc-update
    • Looked into SE/DE previous works, still did not come up with a concrete way to do it. We will take the decision in the team this week.
    • Answered doubts about Q4/Q1 documentations.
    • Worked on Privacy flags and investigated whether we need True flags or not.
    • Met with engineers regarding provability issues and hybrid smart contracts.
    • Revised and investigated how other projects are using smart contracts, I think we can make a better job.
  • state-separation-architecture-poc:priv-impl
    • Private provability model.
    • Call with Moudy and Oleksandr on provability issues.
    • Private state provability proposal PR.
    • Smart contracts execution types discussion.
  • `state-separation-architecture-poc:onboarding’
    • Research wise I started to write some very high level notes on what I understand about NSSA with my own words (see here). Also I went through Moudy’s answers to my questions about Q4/Q1 docs and discussed with him about some points in UTXOs design (see here) and the need of privacy flags in the system.
    • Engineering: I made progress with the update to the utxo crate (draft PR here). While doing so I created a PR (here) and some Issues (#66, #69 #70, #71) with questions and comments about implementations that seemed to deviate from the current specifications.
Reference in New Issue View Git Blame Copy Permalink