roadmap/2024-01-08.md at 16e6cb3b7eff4af56cddae704dfbdbbfdbb21f5b

title

Vac 2024/01/08

nimlibp2p:vac:maintenance:
- flaky tests: trying out a hypothesis about runners specs

vac:tke::codex:economic-analysis
- Update Notion and Tokenomics Design Canvas (TDC) for Codex (@Matty)
- Add new Collateral Insurer role to litepaper
- Follow up with Codex on litepaper feedback and next steps for testnet incentive design and token allocation
vac:tke::status:SNT-staking
- Update Notion and TDC for SNT (@Matty)
- Follow up with John on Wednesday call for 2024 Status plan
vac:tke::nomos:economic-analysis
- Clean up Nomos Notion and update TDC (@Frederico)
- Finish agent based simulations on wealth concentration impacted by leader selection
- Read darkpaper when Nomos team has finished incorporating team comments and can share (expect it this week)
vac:tke::waku:economic-analysis
- Clean up Waku Notion, and create a best thinking draft of TDC (@Martin)
- Finalize and share L2 overview with Waku business model meeting Tue

eng-10ktool:vac:bandwidth-test:
- Gather all data from Kubernetes and create document with plots (https://www.notion.so/Nim-Rust-comparison-9dc4e4c3c0914773971608e8af911943)
- Compare nim, rust and waku bandwidth, packet and times.
- End of the week got stucked because some Kubernetes issues. They are fixed now
- Ran some gowaku simulations. Results differ a lot from nwaku (half bandwidth, no packet loss).
vac:dst:software-testing:waku:test-automation-interop-testing
- Retested some fixes
- Fixed tests related to 1MB message
- Removed deprecated RPC protocol and cleaned up the code
- Investigated with Prem some node connection issues/regression
software-testing:waku:test-automation-nwaku
- clarified testing priorities with Waku:
  1. RLN
  2. Peer Exchange
  3. Discv5
  4. Peer Connection Management
- Open Issue [bug: SqliteDriver WakuMessage attribute saving]
  - After further investigation with Ivan we decided it behaves as expected
  - Issue
- Lightpush
  - Updated PR with comments PR
    - Blocked until SEGFAULT solved
- Autosharding
  - Implemented and merged tests PR
  - Requested help for overloaded function mock test case PR; Nim Forum
- Peer Connection Management
  - Implemented and merged tests PR
  - Thorough investigation on module types and base58
software-testing:waku:test-automation-go-waku
- Wrote 10 test to improve store tests coverage https://github.com/waku-org/go-waku/pull/993
- Go-Waku node operations on Pi 4 (hobby activity)

rlnp2p:waku:rln-relay-enhancments
- continue work on proof of concept for state transition proof for onchain roots in rln: https://github.com/vacp2p/rln-contract/issues/32
secure-channels:waku:ethereum-chat
- Created a 4-step approach for Ethereum as Authentication Service article

codex:codex-airdrop-contract-exploration
- add possible token airdrop solutions https://docs.google.com/document/d/1lH6dPSuSzGIFmbJeaXNmx8cIU7dveI9KxE1rxdoKagQ/edit#heading=h.f8xnzmojer6t
status:community-contracts-maintenance
- start implementing the first new specs based on https://notes.status.im/JsEoWi8rSaqa-s3b2LCF5A?view
- review deployer contract properties doc https://notes.status.im/s/291mb-8nA

proofsystems:vac:research-existing-proof-systems
- Finished researching Arecibo (https://blog.lurk-lang.org/posts/arecibo-supernova/)
- Started writing CycleFold writeup (https://eprint.iacr.org/2023/1192.pdf)
proofsystems:vac:benchmarks
- Continued working on a refactoring for halo2 PRs https://github.com/vacp2p/zk-explorations/pull/22 https://github.com/vacp2p/zk-explorations/pull/21
- Reviewed halo2-common PR
state-separation:vac:state-separation-doc
- Discuss UTXO/Merkle on discord
- Reviewd literature concerning pruning Merkle trees in Bitcoin and other UTXO systems; mentioned in the original white paper but never implemented due to issues with history.
- Discuss recursiveness of Nova
- Work on notes for mimblewimble (pending upload)
- Finish the first version of the report about how we can update public state with a private execution, here is the report.

gsub-scaling:vac:gossipsub-simulation
- Investigated the latency spikes issue with floodpublish for large messages. The problem was small TCP cwnd at start of connection, same is the case with floodpublish peers, and latencies accumulate for multi-hop paths
  - Sending dummy data immidiately after connection setup resolves the problem.
  - However, this can make peers vulnerable to buffer overflow attacks