mirror of
https://github.com/vacp2p/roadmap.git
synced 2026-01-08 21:27:58 -05:00
19 KiB
19 KiB
title, tags, date, lastmod, draft
| title | tags | date | lastmod | draft | |
|---|---|---|---|---|---|
| 2025-07-14 Vac weekly |
|
2025-07-14 | 2025-07-14 | false |
Vac 2025/07/14
highlights
- QA: Keycard first tests executed
- QA: Progress on status mobile app testing using appium
- QA: Waku sync testing almost done
- QA: Improvements in execution and speed for status desktop automated tests
- DST: Analyzing potential reproducible issue with waku Store protocol
vac:p2p:
ift:2025q1-gossipsub-perf-improvements- Looked into Ethereum consensus, and P2P interface specs
- Looked in detail into DAS (and possible approaches and discussions on dissemination and sampling)
- catching up different discussions and proposals on dissemination and sampling
vac:p2p:ift:2025q2-nimlibp2p-maintenance:maintenance- Started to modify nim-quic to use BoringSSL/AWS-LC (they're the same API wise, still not sure which one to use)
- Currently it uses cmake and this is a big problem as it still introduces an additional dependency and nimbus is actively trying to avoid to use cmake
- I'm trying to get it to compile without cmake, just with {.compile.} pragmas
vac:p2p:ift:2025q2-nimlibp2p-maintenance:maintenance- continued working on performance improvements issue: nim-libp2p#1484
- current performance improvement is approximately 55.5%
- chore: utilizing newSeqUninitialized nim-libp2p#1510
- chore: add template newSeqUninit nim-libp2p#1518
- perf(noise): encryptWithAd improvement nim-libp2p#1520
- refactor(yamux): memory usage improvements nim-libp2p#1504
- one test fails
- chore: removing unused type StreamSeq nim-libp2p#1507
- continued working on performance improvements issue: nim-libp2p#1484
vac:p2p:ift:2025q2-nimlibp2p-autotls:cert-installation- Wrapping up cert installation
- Dealing with async issues on switch
- `vac:p2p:ift:2025q2-nimlibp2p-kad-dht
- Primed my brain reading the original research paper
- perused the spec
- Documented initial code perusal with a PR
misc/admin- 1 CC 2d OoO (sick leave)
vac:tke:
admin- 6 CC days off
vac:tke:ift:logos-token:redemption-window- finalized modeling and simulating the LOGOS/BU arbitrage problem
- simulating certain scenarios to answer core questions
vac:tke:nomos:stress-test::review-block-rewards- addressed questions from Nomos team about spec
vac:tke:nomos:stress-test::blend-validator-split- couldn't find a rationale to split the rewards to validators and blend
vac:tke:status:karma-incentives- looking in to uUSD, Steakhouse vaults and Morpho
- reviewing Cyp's docs and progressing with Karma modeling
vac:qa:
waku:2025q3-interop-testing:jswaku-filter-hardening- Added 3 more reliability tests for network conditions
- Got some feedback on the 1st PR
waku:2025q3-interop-testing:maintenance- Adjusted Waku interop tests to latest nwaku changes and fixes
status:2025q3-status-go-functional-testing:reliability-communities- Tried to create tests for this task but it's not ready yet
- Switched to group chat actions functional tests
status:2025q3-status-go-functional-testing:framework-improvements- Fixed the reliability failures
keycard:2025q3-keycard-testing:shell-tests- Wrote test plan for integration tests
- Updated Shell's firmware to v0.9.20
- Logged test results; shared updates here
waku:2025q3-interop-testing:wakucannary- Attempted communication using the tool (on hold due to focus on store sync)
waku:2025q2-waku-sync-testing:Integration-testvac:2025q3-nim-libp2p-testing:gossipsub-completion- test(gossipsub): behavior unit tests 1 – merged
- test(gossipsub): behavior unit tests 2 – merged
- test(gossipsub): gossipsub unit tests 1 – merged
- test(gossipsub): gossipsub unit tests 2 – merged
vac:2025q3-nim-libp2p-testing:gossipsub-performance- Started investigation
status:2025q3-status-qa-desktop:maintenancestatus:2025q3-status-qa-mobile:framework-adjustments- Investigated iOS automation via Squish and Appium
- Squish failed to hook; Appium failed due to simulator crashes
- Manual test on LambdaTest worked
- Switched to Appium and started a new Android-only framework
- Investigated iOS automation via Squish and Appium
admin/misc- OOO: 5 CC days
vac:dst:
admin/misc- 1 CC OOO from Wednesday 9th to Friday 11th
vac:dst:ift:2025q2-dst-research-destination:forum-post- Add reports to forum and summarize DST activity, closing the task
vac:dst:ift:2025q2-dst-research-destination:public-reports- Group public reports and closing the task
vac:dst:status:2025q3-status-go-evaluation:*- Create main document with some results
- Call with some questions with Status
vac:dst:waku:2025q3-waku-evaluation:regression-testing- Added Memory Usage charts (nim GC and container metrics)
- Ran longer running tests to check discv5 over time (still need to analyze)
- Handling lightpush request that was pushing to many nodes
- Unable to reproduce this. Assume max-connections was higher in previous experiments.
vac:dst:waku:2025q3-waku-evaluation:store-dial-failurevac:dst:waku:2025q3-dst-tooling:general-tooling- Minor fix to plotting code
vac:sc:
admin/misc- CC's were out
vac:acz:
ift:2025q3-de-mls-tesnet:consensus-layer- Continue working on consensus layer implementation on the branch
ift:2025q2-zerokit:perfomance-updates-blogpost- Reviewed blogpost in PR
ift:2025q3-libp2p-mix-testnet:update-rfc- Finalized Sections 8.3 to 8.5 (mix-rev1-continue).
ift:2025q3-zerokit:rln-wasm-maintaining- Continued work on the remaining tasks related to the Node.js test case.
ift:2025q3-zerokit:ci-revisingift:2025q3-de-mls-tesnet:de-mls-maintainingift:2025q3-rln-status-l2:e2e-prover-testing- End to end unit test - merged
- End to end benchmark - merged
- Epoch service unit test - merged
- Prover memory allocation profiling such as Memory tracking allocator and LeakTracer allocator
- Explore / Read about Rust + Metrics: source 1 Not generic (Prometheus only), source 2, source 3 (too Actix centrix), source 4 (Not maintained) and source 5 -> Use metrics crate
- Prover + Metrics - WIP
ift:2025q3-zerokit:zerokit-maintaining- Zeroize 2nd attempt - merged
- Doc PR - merged
ift:2025q3-zerokit:big-endian-support- Waku + BE endian format - updated based on the discussions.
- Discussed the issue of generating commitmentId out of field, now there is a version that waku side is somewhere wrongly converted BE to LE PR
ift:2025q3-de-mls-tesnet:multi-steward-rfc- Addressed feedbacks on PR
- Had discussion about who can create votin proposal in poc and RFC.
ift:2025q2-de-mls-tesnet:blogpost-de-mls-over-waku- Finalized blogpost, only wait for the de-MLS RFC is merged.
ift:2025q3-rln-status-l2:rln-spec-maintain- Added storage section to the Status RLN Deployment spec
acz:t1- Review Draft of zkVM selection doc
- Having discussion about q3 tasks basically clarify the commits.
- Review alternative of pedersen commitment doc
- Ran nexus and risc0 tests for Pedersen commitments on a more powerful computer, and concluded that EC operations are infeasible in zkVMs (even with precompile).
- Drafted a mitigation recommendation to replace Pedersen commitments for UTXOs with Merkle tree.
- Wrote a simple test with precompiling for UTXO-type Merkle tree generation in Risc0.
- Began review of Zisk and Ziren (rebrand of zkmips).
admin/misc- Provided context and feedback regarding Mix project state and task alignment.
- Synced briefly with P2P team on branch unification – clarified key differences and proposed isolating protocol logic into Mix Entry/Exit layers.
- Assist in planning Acz <-> Nescience tasks for Q3.
vac:rfc:
vac:rfc:nomos:2025q3-rfc-iteration- Completed open pr reviews - https://github.com/vacp2p/rfc-index/pull/156 , https://github.com/vacp2p/rfc-index/pull/164
vac:rfc:nomos:2025q3-rfc-iteration:mantle-digital-signature- Continued work on Mantle Digital Signature RFC, should have first draft next week
vac:rfc:waku:2025q3-rfc-iteration:qaku- Started reviewed the qaku codebase
vac:rfc:codex:2025q3-rfc-iteration:block-exchange- First draft of Codex Block Exchange: https://github.com/vacp2p/rfc-index/tree/codex/raw/codex-block-exchange-raw
vac:sec:
ift:2025q3-multisig-secondary-interface-deployment:initial-evaluation- Reviewed Safe CLI
ift:2025q3-wallet-management-policy-revalidation:review-current-documentation- Reviewed Signatory Add runbook
- Reviewed Master Wallet Index documentation
ift:2025q2-signatory-registry-implementation:signatory-vault-deployment- Added verified signatory data into the secure vault
- Updated the master wallet index
ift:2025q3-cicd-security-review:status-design-reviews- Worked on open items in Status security design review (issue#692)
- Continue defining scope, requirements, and pre-audit readiness for Status and Codex external audits
ift:2025q3-vulma-and-ir:incidents- Begin investigation into the recent SNT phishing attempt; coordinate with stakeholders for evidence gathering and response
ift:2025q3-vulma-and-ir:remediation-tracking- Continue work on unresolved Dependabot and CodeQL findings; focus on critical repositories and high/medium issues
ift:2025q3-vulma-and-ir:incidents- Follow up recent SNT phishing attempt; coordinate with stakeholders for evidence gathering and response
- Finalize and finish pending work circulate Keycard incident post-mortem documentation
- Complete updates to IR process documentation and share with relevant teams
ift:2025q3-vulma-and-ir:remediation-tracking- Continue work on unresolved Dependabot and CodeQL findings; focus on critical repositories and high/medium issues
admin/misc- Reviewed the secure treasury Q3 commitments
- 1 CC on vacation
vac:nes:
-
vac:nes:2025q3:state-separation-architecture-poc:zkvm- Continued research on zkVMs. Some of the already analyzed projects in the past did not change.
- Worked on zkvm criteria, alternatives, and deep analysis on each of them.
- Draw conclusions about R0 zkVM and which one is the best fit for NSSA.
- Finished the instruction metering analysis for Risc0 task.
- Started working on the selective privacy proof of concept using risc0 subtask. See draft here and an explanation of the work in progress here.
-
vac:nes:2025q3:state-separation-architecture-poc:seq-check
vac:nim:
-
ift:2025q3-nimble- Fixes an issue where sometimes, when using special versions a duplicated entry appears in
nimble.pathshttps://github.com/nim-lang/nimble/pull/1420- Fixes an issue where sometimes, when using special versions a duplicated entry appears in
nimble.paths - fix issue
- Progress
- fix test (misses
setup)
- Fixes an issue where sometimes, when using special versions a duplicated entry appears in
- Fixes an issue where
processRequirementswas overriding special versions https://github.com/nim-lang/nimble/pull/1417- Fixes an issue where
processRequirementswas overriding special versions - removes unused
- Fix test
- Fixes an issue where
- Improves package collection for SAT
https://github.com/nim-lang/nimble/pull/1416
- Improves the special version tests so it includes run and custom actions.
- disables all suites except requires to iterate quicker
- removes fake tesst
- remove test
- reenables suites. Changes the way special versions are collected
- Include special versions in list action
https://github.com/nim-lang/nimble/pull/1415
- Include special versions in list action
- Adds paths to the list action. When in
--debugshow the build cmd
- Improves release action to generate release notes. Updates changelog (latest commit: 2025-07-07 10:08:09)
https://github.com/nim-lang/nimble/pull/1414
- Improves release action to generate release notes. Updates changelog
- Adds "should be able to install a special version"
https://github.com/nim-lang/nimble/pull/1413
- Adds "should be able to install a special version"
- Removes unused import
- Release version
0.20.0
- Fixes an issue where sometimes, when using special versions a duplicated entry appears in
-
ift:2025q3-nim-ide-tooling- Updates
nimblecommit https://github.com/nim-lang/Nim/pull/25036
- Updates