Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/dst/logos/2026q4-anoncomms-evaluation.md
Original file line number Diff line number Diff line change
Expand Up @@ -95,8 +95,8 @@ TBD
> *Note*: This needs more input from project

* fully qualified name: `ift-ts:dst:logos:2026q4-anoncomms-evaluation:discovery-vs-discv5`
* owner: TBD
* status: not started
* owner: Alberto
* status: in progress (5%)
* start-date: 2026/10/01
* end-date: 2026/12/31

Expand Down
3 changes: 3 additions & 0 deletions content/dst/logos/2026q4-messaging-evaluation.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,9 @@ and ensure they don't happen again.
- Repeated the PR 4347 full delivery test three times at the configured publish rate to validate the [full delivery report](https://app.notion.com/p/3ea8f96fb65c812a9ae2dc71ef28860e).
- Completed the [Logos Delivery v0.40.0-rc.1 Store and Edge regression report](https://app.notion.com/p/40e8f96fb65c819aa6ddd04a3a8c106a)
- Confirmed in two follow-up runs that Store backfill exhausts node connections and causes send-confirmation timeouts.
- Updated the [Logos Delivery v0.40.0-rc.1 regression report](https://app.notion.com/p/40e8f96fb65c819aa6ddd04a3a8c106a) with rc.2 and rc.3 results from 1,000-node runs.
- Confirmed the Store connection fix in v0.40.0-rc.2 and the Edge-to-Core lightpush delivery fix in rc.3 at 1,000 nodes.
- Ran v0.40.0-rc.2 with 60 minutes of message sending to examine where relay connection counts level off.


### Messaging API — General Availability
Expand Down
2 changes: 1 addition & 1 deletion content/dst/logos/2026q4-storage-evaluation.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ filesharing client implementation under heavy/big workloads.
> *Note*: This needs more input from project
* fully qualified name: `ift-ts:dst:logos:2026q4-storage-evaluation:filesharing-client-mix`
* owner: Alberto
* status: in progress (50%)
* status: in progress (60%)
* start-date: 2026/10/01
* end-date: 2026/12/31

Expand Down
6 changes: 4 additions & 2 deletions content/dst/status/2026q4-status-evaluation.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,9 +25,9 @@ TBD

* fully qualified name: `ift-ts:dst:status:2026q4-status-evaluation:reliability`
* owner: Alberto
* status: in progress (99%)
* status: done
* start-date: 2026/10/01
* end-date: 2026/12/31
* end-date: 2026/11/17

#### Description

Expand All @@ -42,6 +42,7 @@ Compare results with old status-go.
- [Status analysis branch](https://github.com/status-im/status-go/tree/dst-analysis).
- [status-im/status-go#8036](https://github.com/status-im/status-go/issues/8036) [Epic] Optimizing messaging pipeline
- Replaced the receiver’s sliding debounce with a fixed batch window; the first fix reduced median delivery from about 120 seconds to 17 seconds.
- Improved the benchmark codebase and added delivery-latency-over-time plots and latency buckets.
- Documents:
- Identified a light-node rate-limiter timing mismatch causing valid messages to remain pending in MVDS and arrive minutes late.
- Identified a feedback loop in which delayed processing delays acknowledgements, triggers MVDS retransmissions, and increases the processing backlog.
Expand All @@ -51,6 +52,7 @@ Compare results with old status-go.
- Reduced median delivery from 130 seconds to 1.4 seconds, p95 from 197 seconds to 2.11 seconds, and maximum from 226 seconds to 3.45 seconds in the latest experiment.
- Recorded no deliveries over 10 seconds in 38,000 messages, compared with 7,556 of 7,600 previously, and reduced MVDS retransmissions from thousands to zero.
- [Status delivery latency investigation](https://discord.com/channels/1210237582470807632/1555207381355597915/1567195622635733054)
- Ran 8-hour and 24-hour reliability experiments, analysed the results, and updated the [Status-go benchmark report](https://app.notion.com/p/Status-go-benchmarks-2026q4-4168f96fb65c808fb58df4ae5acf4273).

### Logos delivery integration

Expand Down
12 changes: 12 additions & 0 deletions content/nim/ift/2026q4-nim-core-libs.md
Original file line number Diff line number Diff line change
Expand Up @@ -143,6 +143,15 @@ Use the nim-web3 approach as the model for the LSP implementation:
- [nim-lang/langserver#515](https://github.com/nim-lang/langserver/pull/515) Support multi-root workspaces
- [nim-lang/langserver#516](https://github.com/nim-lang/langserver/pull/516) Resolve package by nimble file + `nimble.paths`
- [nim-lang/langserver#523](https://github.com/nim-lang/langserver/pull/523) Restart nimsuggest on `nimble.paths` changes
- [nim-lang/langserver#526](https://github.com/nim-lang/langserver/pull/526) Fix `cancelTest` race crash
- [nim-lang/langserver#530](https://github.com/nim-lang/langserver/pull/530) Run `nim --version` and `nimsuggest --info` async
- [nim-lang/langserver#528](https://github.com/nim-lang/langserver/pull/528) Stop capped nimsuggests on workspace folder change
- [nim-lang/langserver#529](https://github.com/nim-lang/langserver/pull/529) Do not return a stopping instance in getNimsuggest
- [nim-lang/langserver#527](https://github.com/nim-lang/langserver/pull/527) Avoid notifications in MCP mode
- [nim-lang/langserver#500](https://github.com/nim-lang/langserver/pull/500) Fix MCP `nimFindSymbols` and `nimCheckProject` take a file uri
- [nim-lang/nimony#2955](https://github.com/nim-lang/nimony/pull/2955) nifmake: add `--keepgoing` option
- [nim-lang/Nim#26685](https://github.com/nim-lang/Nim/pull/26685) IC: reuse module symbols of re-exported modules
- [nim-lang/Nim#26686](https://github.com/nim-lang/Nim/pull/26686) IC: don't rerun the config producer after a no-op nim.cfg save

### Nimlangserver and nimsuggest support for IFT projects

Expand Down Expand Up @@ -209,3 +218,6 @@ Provide initial rules for IFT projects, such as flagging `asyncSpawn`, with seve
- Added local linters to the cache-invalidation key.
- Added exit-code tests.
- Released [Nim Lint 1.0.0](https://forum.nim-lang.org/t/14279)
- [iftech/nim-lint#4](https://github.com/iftech/nim-lint/issues/4) lint ideas
- [iftech/nim-libp2p#3369](https://github.com/iftech/nim-libp2p/issues/3369) feat: Linters: Enforce implicit `result` is not used.
- Designed semantic and raw-source checks for nim-lint.
9 changes: 9 additions & 0 deletions content/nim/ift/2026q4-nimble.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,6 +64,15 @@ Add regression coverage for fixes and update usage documentation when behavior c
- [nim-lang/nimble#1923](https://github.com/nim-lang/nimble/pull/1923) Make nimble dump use the installed locked Nim and write nothing (fixes #1919, fixes #1920)
- [nim-lang/nimble#1922](https://github.com/nim-lang/nimble/pull/1922) CI: move the latest tag to each nightly build's commit
- [nim-lang/nimble#1921](https://github.com/nim-lang/nimble/pull/1921) Canary: run nimble setup before the tests
- [nim-lang/nimble#1936](https://github.com/nim-lang/nimble/pull/1936) Canary: check out repos with plain git so a broken submodule can't fail it
- [nim-lang/nimble#1935](https://github.com/nim-lang/nimble/pull/1935) Fix nimble dump printing nothing for an unbuilt develop Nim
- [nim-lang/nimble#1934](https://github.com/nim-lang/nimble/pull/1934) Fix SAT taking 25 minutes to fail on a large graph with no solution
- [nim-lang/nimble#1933](https://github.com/nim-lang/nimble/pull/1933) Fix invalid package name errors printing "$1" or the name twice
- [nim-lang/nimble#1931](https://github.com/nim-lang/nimble/pull/1931) Fix "No Nim found" for packages that require nothing
- [nim-lang/nimble#1930](https://github.com/nim-lang/nimble/pull/1930) Fix git:// requirements hanging until the connection times out
- [nim-lang/nimble#1929](https://github.com/nim-lang/nimble/pull/1929) Fix SAT failing when a missing package can be avoided
- [nim-lang/setup-nimble-action#20](https://github.com/nim-lang/setup-nimble-action/pull/20) Add nimble-sha256 to pin the release archive's hash (fixes #18)
- [nim-lang/setup-nimble-action#19](https://github.com/nim-lang/setup-nimble-action/pull/19) Retry nimble downloads and resolve only published releases

### CI integration review

Expand Down
7 changes: 5 additions & 2 deletions content/p2p/ift/2026q4-nimlibp2p-gossipsub-topic-streams.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,13 +46,15 @@ including subscription changes and peer disconnects.
- [iftech/nim-libp2p#3271](https://github.com/iftech/nim-libp2p/pull/3271) feat(gossipsub): add topic stream transport
- [iftech/nim-libp2p#3272](https://github.com/iftech/nim-libp2p/pull/3272) feat(gossipsub): integrate topic streams
- [iftech/nim-libp2p#3327](https://github.com/iftech/nim-libp2p/pull/3327) test(gossipsub): add topic streams interoperability
- [iftech/nim-libp2p#3409](https://github.com/iftech/nim-libp2p/pull/3409) fix(gossipsub): drop topic frames after protocol violations
- [iftech/nim-libp2p#3400](https://github.com/iftech/nim-libp2p/pull/3400) fix(gossipsub): preserve negotiation for graylisted peers


### Delivery And Resource Budgets

* fully qualified name: `ift-ts:p2p:ift:2026q4-nimlibp2p-gossipsub-topic-streams:delivery-budgets`
* owner: not assigned yet
* status: not started
* owner: Richard
* status: in progress (25%)
* start-date: 2026/10/01
* end-date: 2026/12/31

Expand All @@ -68,3 +70,4 @@ control messages continue to use the ordinary GossipSub stream.
- Per-peer stream and byte limits
- Tests for delivery, resource exhaustion, and control-stream behavior
- Ensure no regressions are introduced in a real life network deployment
- [iftech/nim-libp2p#3410](https://github.com/iftech/nim-libp2p/pull/3410) fix(gossipsub): separate incoming and outgoing topic stream limits
12 changes: 11 additions & 1 deletion content/p2p/ift/2026q4-nimlibp2p-maintenance.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ ensuring that nim-libp2p remains functional and usable for its primary users —

* fully qualified name: `ift-ts:p2p:ift:2026q4-nimlibp2p-maintenance:maintenance`
* owner: Richard/Vlado/Gabe
* status: in progress (42%)
* status: in progress (50%)
* start-date: 2026/10/01
* end-date: 2026/12/31

Expand Down Expand Up @@ -192,3 +192,13 @@ as issues arise during the quarter.
- [iftech/nim-libp2p#3358](https://github.com/iftech/nim-libp2p/pull/3358) fix(relay): reject reservations that expire more than 24 h ahead
- Fixed duplicate messages in the automated workflow.
- Extended the review tool to test files and added Radek to its allowed list.
- [iftech/nim-libp2p#3422](https://github.com/iftech/nim-libp2p/pull/3422) fix(pubsub): back off budget-rejected and short-lived streams
- [iftech/nim-libp2p#3421](https://github.com/iftech/nim-libp2p/pull/3421) fix(gossipsub): validate topic stream byte budgets
- [iftech/nim-libp2p#3412](https://github.com/iftech/nim-libp2p/pull/3412) chore(build): require Nim 2.2.6 and default to 2.2.14
- [iftech/nim-libp2p#3420](https://github.com/iftech/nim-libp2p/pull/3420) fix(kademlia): count valid records toward get-value quorum
- [iftech/nim-lsquic#187](https://github.com/iftech/nim-lsquic/pull/187) chore(build): require Nim 2.2.6 and test 2.2.14
- [iftech/nim-libp2p#3408](https://github.com/iftech/nim-libp2p/pull/3408) fix(peerid): align parsing with key-derived size limits
- [libp2p/test-plans#871](https://github.com/libp2p/test-plans/pull/871) feat(transport-interop): add nim-libp2p v2.4.1
- [iftech/nim-libp2p#3385](https://github.com/iftech/nim-libp2p/pull/3385) feat(nameresolving): bound and expand composed DNS multiaddresses
- [iftech/nim-libp2p#3384](https://github.com/iftech/nim-libp2p/pull/3384) feat(nameresolving): add system resolver worker pool and factory
- [iftech/nim-libp2p#3379](https://github.com/iftech/nim-libp2p/pull/3379) feat(nameresolving): add system DNS discovery
6 changes: 3 additions & 3 deletions content/p2p/ift/2026q4-nimlibp2p-mdns.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,10 +24,10 @@ handling, expiration, peerstore integration, and application-controlled dialing.
### Discovery Lifecycle And Records

* fully qualified name: `ift-ts:p2p:ift:2026q4-nimlibp2p-mdns:discovery`
* owner: not assigned yet
* status: not started
* owner: Vlado
* status: done
* start-date: 2026/10/01
* end-date: 2026/12/31
* end-date: 2026/11/17

#### Description

Expand Down
11 changes: 10 additions & 1 deletion content/qa/ift/2026q4-nim-libp2p-testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ Handle issue-driven validation that does not require a separate feature-specific

* fully qualified name: `ift-ts:qa:ift:2026q4-nim-libp2p-testing:gossipsub-topic-streams`
* owner: Radek
* status: in progress (25%)
* status: in progress (50%)
* start-date: 2026/11/03
* end-date: 2026/12/31

Expand All @@ -72,6 +72,15 @@ Test GossipSub topic streams ([stack 3274](https://github.com/iftech/nim-libp2p/
- [iftech/nim-libp2p#3390](https://github.com/iftech/nim-libp2p/issues/3390) gossipsub: a peer that reconnects while still graylisted is disconnected on its first topic stream
- [iftech/nim-libp2p#3391](https://github.com/iftech/nim-libp2p/pull/3391) test(topic-streams): negotiation and graylisted ControlExtensions repro [1]
- [iftech/nim-libp2p#3398](https://github.com/iftech/nim-libp2p/pull/3398) test(topic-streams): forwarding over topic streams, send budgets and TopicStreamsRecorder [2]
- [iftech/nim-libp2p#3405](https://github.com/iftech/nim-libp2p/pull/3405) test(topic-streams): stream and byte limits, readers side [3]
- [iftech/nim-libp2p#3413](https://github.com/iftech/nim-libp2p/pull/3413) test(topic-streams): message routing, protocol violations and behaviour penalties [4]
- [iftech/nim-libp2p#3419](https://github.com/iftech/nim-libp2p/pull/3419) test(topic-streams): receive side, configuration validation and byte budgets [5]
- [iftech/nim-libp2p#3424](https://github.com/iftech/nim-libp2p/pull/3424) test(topic-streams): stream cleanup, negotiation edges, graylisting and rate limiting [6]
- [iftech/nim-libp2p#3403](https://github.com/iftech/nim-libp2p/issues/3403) gossipsub: a topic stream reader still delivers one frame after a protocol violation
- [iftech/nim-libp2p#3404](https://github.com/iftech/nim-libp2p/issues/3404) gossipsub: a topic handler can still receive a message after GossipSub stops
- [iftech/nim-libp2p#3406](https://github.com/iftech/nim-libp2p/issues/3406) gossipsub: should frames for new topics be dropped silently once incoming and outgoing topic streams reach maxStreams?
- [iftech/nim-libp2p#3411](https://github.com/iftech/nim-libp2p/issues/3411) gossipsub: publish with empty data counts topic stream peers it never sends to
- [iftech/nim-libp2p#3418](https://github.com/iftech/nim-libp2p/issues/3418) gossipsub: topic streams drop messages that the control stream sends when byte budgets are below maxMessageSize

### GossipSub Byte Queues

Expand Down
4 changes: 4 additions & 0 deletions content/qa/logos/2026q4-messaging-testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -114,3 +114,7 @@ Update tests for messaging component changes, investigate failing or flaky tests
- [logos-co/logos-delivery-module#171](https://github.com/logos-co/logos-delivery-module/pull/171) test(e2e): tests with RLN membership
- [logos-co/logos-delivery-module#175](https://github.com/logos-co/logos-delivery-module/pull/175) test(e2e): logosctl instead of logoscore
- [logos-messaging/logos-delivery#4650](https://github.com/logos-messaging/logos-delivery/pull/4650) ci: run every job in the nightly through ci.yml
- [logos-co/logos-delivery-module#178](https://github.com/logos-co/logos-delivery-module/pull/178) test(e2e): fleet tests with RLN
- [logos-co/logos-delivery-module#179](https://github.com/logos-co/logos-delivery-module/pull/179) test(e2e): refactor node setup
- [logos-co/logos-delivery-module#181](https://github.com/logos-co/logos-delivery-module/pull/181) test(e2e): service disco test via plugin
- [logos-co/logos-delivery-module#182](https://github.com/logos-co/logos-delivery-module/pull/182) test(e2e): extend service disco tests
7 changes: 7 additions & 0 deletions content/qa/logos/2026q4-source-code-level-qa.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,3 +85,10 @@ Prototype an AI code analysis workflow covering:
- Added `bork triage advise --all` to run the advisor across all audits in parallel.
- Linked a `bork/proof/<handle>` proof branch from each filed finding.
- Added optional incremental specification and security audits that reuse previous proofs and coverage.
- [iftech/bork#6](https://github.com/iftech/bork/pull/6) feat(tui): guidance dashboard in bork window
- [iftech/bork#7](https://github.com/iftech/bork/pull/7) feat(install): the install is a copy under ~/.bork, apart from the source checkout
- [iftech/bork#8](https://github.com/iftech/bork/pull/8) feat(window): home lists the repositories, each with its next step
- [iftech/bork#9](https://github.com/iftech/bork/pull/9) feat(window): one console per repository behind the dashboard
- [iftech/bork#10](https://github.com/iftech/bork/pull/10) feat(window): a repository opens into its tasks, findings and evidence
- [iftech/bork#11](https://github.com/iftech/bork/pull/11) feat(window): what a finding rests on, console activity, clearer keys
- [iftech/bork#12](https://github.com/iftech/bork/pull/12) docs: bring the documentation in line with the code
1 change: 1 addition & 0 deletions content/qa/status/2026q4-status-go-functional-testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,3 +71,4 @@ Select concrete scenarios from the existing backlog and issues found during desk
- [status-im/status-go#7978](https://github.com/status-im/status-go/issues/7978) test(functional): run_functional_tests.sh does not wait for the Foundry contract deployment
- [status-im/status-go#7956](https://github.com/status-im/status-go/pull/7956) test(functional): functional tests thread RPCs
- [status-im/status-go#7969](https://github.com/status-im/status-go/pull/7969) test(functional): cover thread permission, reaction control and participants
- [status-im/status-go#8053](https://github.com/status-im/status-go/pull/8053) test(functional): cover muted thread behavior
1 change: 1 addition & 0 deletions content/qa/status/2026q4-status-qa-desktop.md
Original file line number Diff line number Diff line change
Expand Up @@ -132,6 +132,7 @@ Choose scenarios as feature scope and the automation backlog are clarified with
- [status-im/status-app#22951](https://github.com/status-im/status-app/pull/22951) tests(@e2e): scan qr code from image
- [status-im/status-app#23031](https://github.com/status-im/status-app/pull/23031) tests: browser tests coverage
- [status-im/status-go#8024](https://github.com/status-im/status-go/pull/8024) test(functional): tests for browser
- [status-im/status-app#23112](https://github.com/status-im/status-app/pull/23112) tests(@e2e): add test to check pin messages panel after chat is left

### Performance tests for desktop application on Mac

Expand Down
12 changes: 11 additions & 1 deletion content/qa/status/2026q4-status-qa-mobile.md
Original file line number Diff line number Diff line change
Expand Up @@ -75,6 +75,9 @@ Perform exploratory and regression testing, test new features in each release, a
- Checked Keycard end-to-end coverage against the specification and identified 13 scenarios without tests.
- [status-im/status-app#22998](https://github.com/status-im/status-app/pull/22998) chore(status-go): bump status-go to fix the iOS login crash
- [status-im/status-app#23070](https://github.com/status-im/status-app/pull/23070) perf(StatusQ): replace chat text views with highly optimised renderers
- [status-im/status-app#23134](https://github.com/status-im/status-app/issues/23134) [QA - Mobile] Threads: compatibility
- Revised the Threads and Keycard test plans using developers’ answers.
- Confirmed fixes for the share-screen chat ordering and full-width contact-request button bugs.

### Maintenance

Expand All @@ -97,6 +100,8 @@ Address flaky tests and assist developers with test changes in pull requests as
- Built the `/e2e-android` PR-comment trigger for the Android end-to-end gate.
- [status-im/status-app#22973](https://github.com/status-im/status-app/pull/22973) test(e2e_appium): find chat messages after the WindowedView change
- [status-im/status-app#23083](https://github.com/status-im/status-app/pull/23083) test(e2e_appium): turn off "Stay logged in" during onboarding
- [status-im/status-app#23128](https://github.com/status-im/status-app/issues/23128) Run status-go and status-app builds on GitHub Actions
- Restored clean nightly end-to-end runs after updating chat-message lookup for WindowedView.

### Coverage for existing features

Expand Down Expand Up @@ -151,7 +156,7 @@ Improve the mobile test harness in the following areas:

* fully qualified name: `ift-ts:qa:status:2026q4-status-qa-mobile:performance`
* owner: Magnus
* status: in progress (25%)
* status: in progress (50%)
* start-date: 2026/10/01
* end-date: 2026/12/31

Expand All @@ -164,3 +169,8 @@ Keep measurements useful for comparing releases and identifying performance regr
- [status-im/status-app#21248](https://github.com/status-im/status-app/issues/21248) \[QA - Android/iOS\] add test to measure Battery consumption, CPU and RAM usage
- Restored Android performance runs and published RC7 measurements.
- Restored performance dashboard publishing after GitHub's signed-commits rule.
- [status-im/status-app#23088](https://github.com/status-im/status-app/pull/23088) revert(chat): keep optional message parts built in pooled rows
- [status-im/status-app#23067](https://github.com/status-im/status-app/issues/23067) [QA - Android] benchmark Status battery usage against these other apps
- Measured Android RAM before and after the pooled-message-row change: the UI process used 27.6 MB less, with status-go unchanged.
- Completed three Android battery benchmark A/B pairs on two phones; Status in the background woke the phone about every 30 seconds, 14–16 times as often as with Status stopped in both A36 pairs.
- Fixed the Android performance nightly.
Loading
Loading