Vac 2025/06/02 §
highlights §
- Completed performance evaluations for GossipSub v1.4, v1.4+stagger, PPPt, 2.0
- Good alignment/collab with linea on bridge work
vac:p2p: §
ift:2025q1-gossipsub-perf-improvements
- Completed performance evaluations for GossipSub v1.4, v1.4+stagger, PPPt, 2.0
- Required doing some modifications in scripts/PoC implementations
- Working on a short performance comparison blogpost
- Reviewed AutoTLS specs PR
vac:p2p:ift:2025q2-nimlibp2p-autotls
vac:p2p:ift:2025q2-nimlibp2p-maintenance:maintenance
- fixing and improveing daily ci job
- ci(dependencies): fix access to tokens nim-libp2p#1421
- chore(interop): move interop code to separate folder nim-libp2p#1413
- nim-libp2p#1398 feat: withWsTransport
- nim-lang/packages#3044 Published quic in nim package repo
- nim-quic#80 refactor: make certificates part of the connection
- nim-quic#82 fix: if stream is not available in open state, raise exception
- nim-quic#81 fix: limit chronicles version to < 0.11.0
- nim-libp2p fix: limit chronicles version to < 0.11.0
- Looking into compiling BoringSSL statically part of nim-libp2p
- investigating hole punching interop
- reviewing Radek’s PRs
misc/admin
vac:tke: §
vac:qa: §
-
nomos:2025q2-da-testing:data-confidentiality
- Test/data confidentiality
PR 18 - in progress
- chore: Nomos node with mutated QUIC transport
PR 2 - paused - continue as prep. for reliability test, time box or drop ?
-
waku:2025q2-waku-sync-testing:Integration-test
- Discussions with devs resulted in found the needed flags to run the waku-sync E2E scenarios in PR 119 but task postponed till specs ready
-
waku:2025q2-interop-testing:maintenance
- After analyzing recent CI jobs found RLN tests failing due to changes in nwaku repo
- Confirmed with devs that changes are needed and not bugs so currently trying adjust the tests but still not done
- Stopped the failing topic tests modifications as Ivan confirmed they will revert the change that caused the failure
- bug: node won’t start with RLN in on-chain dynamic mode 2
Issue 3208 - re-test - failed
-
waku:2025q2-waku-go-bindings-testing:maintenance
- Merged PR with fix of errors in YML file
-
vac:2025q2-nim-libp2p-testing:gossipsub-extended-part2
-
status:2025q2-status-qa:v2-34
- Testing v2.34 on mobile, current state
- Created/investigated 3 issues
- Configured the env for tablet build bulding and built it
- Squish tests support (fixed failed tests from nightly run)
- Regression on RC 3
-
waku:2025q2-status-go-functional-testing:
- Fixed flaky test
- Reviewed existing tests in framework and prepared requirements for new tests
-
admin/misc
- Parental leave 5 CC days
- Public holiday 1 CC day
- Day off 2 CC days
vac:dst: §
vac:dst:ift:2025q2-dst-tooling:analysis-refactor
- Refactor of the analysis code
- Github: Draft PR
- Main workflow of analysis finished
- Need to adapt other cases (filter checks, store checks, plottings, documentation)
vac:dst:ift:2025q2-dst-tooling:python-deployment-scaffold
vac:sc: §
status:2025q2-sn-native-bridge-yield-bearing-module:research-design
- started simple implementation of
implementation of L1YieldETHBridge
- research on withdrawal + Yield Manager contracts
- discussions with Filip and the Linea team about the design of the L1 and L2 bridge
status:2025q2-karma-rln:implementation
status:2025q2-karma-rln:slash-karma
- Worked on certora rule fix
- This uncovered some other invariants that are necessary to proof
- Discussed the progress with the team
- We might simplify and “deactivate” reward distribuors instead
vac:acz: §
ift:2025q2-rln-status-l2:rpc-node-modification
- Implement a plugin for RPC nodes to forward transaction data directly to the Prover:
- Changed approach for implementing the RPC node using the Linea-Besu codebase instead of Besu plugin feature (PR)
- Refactored forward-transaction feature into a CLI argument by extending the BesuCommand
- Tried to set up the Besu client codebase to sync with mainnet on the test machine
ift:2025q2-zerokit:zerokit-maintaining
- Reviewed and approved merged PRs:
- Updated Rust tooling for the Nix environment (PR)
- Added build targets for different platforms (PR)
ift:2025q2-de-mls-tesnet:blogpost-de-mls-over-waku
ift:2025q2-de-mls-tesnet:commit-and-proposal
- Worked on splitting commit message to proposal and commit message branch
ift:2025q2-zerokit:error-abstraction
- Reviewed PR
- PR for better error display.
ift:2025q2-rln-status-l2:prover-service
ift:2025q2-rln-status-l2:rln-spec
ift:2025q2-de-mls-tesnet:consensus-rfc
- Applied changes ready to review RFC PR.
ift:2025q2-de-mls-tesnet:multi-admin-rfc
nes:2025q2-nescience-consulting:SE-DE-improvements
- Reviewing the older version execution types for SE/DE improvements.
- Continued work on SE/DE document.
ift:2025q2-libp2p-mix-testnet:surb-implementation
- Implementation de-prioritised in favor of establishing discrepency
- Began implementing a structured, feature-flagged logging system PR 25
ift:2025q2-zerokit:perfomance-updates-blogpost- began drafting a plan with the help of LLM: Issue 314
ift:2025q2-ift-zk-calls:ift-zk-call-3
- Selected topic and began outlining presentation on polynomial commitments for zk call.
ift:2025q2-libp2p-mix-testnet:nomos-comparison
- Started reviewing the Blend Protocol spec and output a comparison Doc
- Identified a clean separation between Blend’s application logic and its anonymous routing layer.
- Proposed a refactor to delegate message-level anonymous routing to a shared custom libp2p protocol, enabling reuse across stacks (e.g., Nomos, Waku).
- This could allow Blend and Mix to evolve as separate custom libp2p protocols, each supporting distinct anonymity models.
- Also drafted a refactored version using the Mix Protocol — mapping core flow, roles, and message lifecycle. [WiP]
ift:2025q2-zerokit:perfomance-updates-blogpost
admin/misc
- Examined the PSE RLNv3 doc
- Had detailed syncs with team to align on tasks; clarified next steps on Issue #24 and PR #20.
- Investigated branch moved, created PR #1420, GossipSub tests and CI failed. So need to reintroduce changes incrementally to isolate issues.
vac:nim: §
ift:2025q1-nimble
- [WIP] Road to nimble 1.0. New code path where parser:declarative and sat is assumed (https://github.com/nim-lang/nimble/pull/1396)
- Handles more builds cases. Including symlinks
- vnext can run the build action as well. Skips symlink for root package
- implements
setup for vnext
- implements
run cmd
- vnext is able to build
nimlangserver as dep. Improves nim set (needs a refactor). Copy nim files over the install dir, so build can happen in the install dir rather than the cache
- Fixes test
- Enabling feature works with vnext
- green: [OK] should be able to install a package using the declarative parser with a feature
- Activate transitive features
- Makes vnext the code path when declarative parser is on
- Fixes a regression
- Improves setup command with vnext. Adds support to babel packages in vnext
- Clean up
- Prevent redundant copy
- Comments a test for
vnext that relies in a lock file (deps changed)
- Merge branch ‘master’ into vnext
vac:rfc: §
vac:rfc:ift:rfc-index-maintenance:maintenance
admin/misc
vac:rfc:waku:2025q2-rfc-iteration:waku2-enr
- Started work on rfc update for WAKU2-ENR
vac:rfc:nescience:2025q2-rfc-iteration:key-protocol
vac:sec: §
ift:2025q2-signatory-registry-implementation:signatory-inventory-revalidation
- Pending to confirm EOA’s and individual accounts
ift:2025q2-custody-improvement-plan:mpc-solution-review
- Reviewed the secure usage documentation with the Inv team
ift:2025q2-signatory-registry-implementation:signatory-data-verification
- Requested for additional signer verification information
ift:2025q2-audit-plan-refinement:smart-contract-testing
- Conducted fuzz testing and invariant checks using Foundry.
ift:2025q2-cicd-security-review:gha-hardening
- Reviewed and enhanced branch protection configurations for key repositories.
- Automated the processing of secret scanning notifications and alerts.
- Coordinated with the Status team to formalize Security as designated code owners.
ift:2025q2-vulma-and-ir:remediation-tracking
- Reassessed related findings from Status-321 and Status-322 post-incident.
- Investigated reports concerning Discord AI bots and confirm bans.
ift:2025q2-iam-operations:remove-unnecessary-users
- Started investigating removal from Notion, Iplicit and Expensify
ift:2025q2-finance-automation
- Meeting with Finance to finalize approach for invoice management
- Implemented upgrades for new CC update from BBHR to Iplicit
admin\misc
- Review the Security Engineer JD to start the hiring process.
vac:nes: §