|
| 1 | +--- |
| 2 | +title: Libp2p Evaluation |
| 3 | +tags: |
| 4 | + - "2026q4" |
| 5 | + - "dst" |
| 6 | + - "ift" |
| 7 | +draft: false |
| 8 | +description: "Test libp2p on each new version or feature |
| 9 | +and look for regressions, |
| 10 | +learn scaling properties and run scaling studies." |
| 11 | +--- |
| 12 | + |
| 13 | +`ift-ts:dst:ift:2026q4-libp2p-evaluation` |
| 14 | + |
| 15 | + |
| 16 | +## Description |
| 17 | + |
| 18 | +Test libp2p on each new version or requested feature |
| 19 | +and look for regressions, |
| 20 | +learn scaling properties and run scaling studies, |
| 21 | +understand the limits of Waku and its behaviour. |
| 22 | +Deliver reports and actionable insights. |
| 23 | +Do this monthly, reliably, with documentation of findings. |
| 24 | + |
| 25 | +The scope of this commitment depends on the P2P team |
| 26 | +work and improvements, and it is subjected to change. |
| 27 | + |
| 28 | +## Task list |
| 29 | + |
| 30 | +### Regression testing (recurring) |
| 31 | + |
| 32 | +* fully qualified name: `ift-ts:dst:ift:2026q4-libp2p-evaluation:regression-testing` |
| 33 | +* owner: TBD |
| 34 | +* status: not started |
| 35 | +* start-date: 2026/10/01 |
| 36 | +* end-date: 2026/12/31 |
| 37 | + |
| 38 | +#### Description |
| 39 | +Run different scenarios |
| 40 | +and collect evidence and data |
| 41 | +of libp2p's behaviour. |
| 42 | + |
| 43 | +Test for known regressions |
| 44 | +that have occurred in the past |
| 45 | +and ensure they don't happen again. |
| 46 | + |
| 47 | +#### Deliverables |
| 48 | + |
| 49 | +- Code: |
| 50 | +- Reports: |
| 51 | + |
| 52 | + |
| 53 | +### Interop at scale |
| 54 | + |
| 55 | +* fully qualified name: `ift-ts:dst:ift:2026q4-libp2p-evaluation:interop-at-scale` |
| 56 | +* owner: TBD |
| 57 | +* status: not started |
| 58 | +* start-date: 2026/10/01 |
| 59 | +* end-date: 2026/12/31 |
| 60 | + |
| 61 | +#### Description |
| 62 | +Run different scenarios |
| 63 | +and collect evidence and data |
| 64 | +of libp2p's behaviour using |
| 65 | +different implementations. |
| 66 | + |
| 67 | + |
| 68 | +#### Deliverables |
| 69 | +- Code: |
| 70 | +- Reports: |
| 71 | + |
| 72 | + |
| 73 | +### Automatic reporting |
| 74 | + |
| 75 | +* fully qualified name: `ift-ts:dst:ift:2026q4-libp2p-evaluation:automatic-reporting` |
| 76 | +* owner: TBD |
| 77 | +* status: not started |
| 78 | +* start-date: 2026/10/01 |
| 79 | +* end-date: 2026/12/31 |
| 80 | + |
| 81 | +#### Description |
| 82 | +Make use of the main tools available in the main repository to perform automatic analysis and reporting for |
| 83 | +libp2p team, either by commit, each X amount of time or triggered manually. |
| 84 | + |
| 85 | + |
| 86 | +#### Deliverables |
| 87 | +- Code: |
| 88 | +- Reports: |
0 commit comments