mirror of
https://github.com/logos-blockchain/research.git
synced 2026-08-07 11:43:20 +00:00
f51630e509
The study started as a peering-degree question and grew well past it: propagation, adversary exposure, deanonymization and time-to-link, reliability under uniform and correlated churn, messaging redundancy, and cover traffic. The pd name no longer describes it. tools/simulators/blend/pd/ -> tools/simulators/blend/, package src/pd -> src/blend, and reports/blend/pd/ -> reports/blend/. Moved with git mv so history follows. The text substitutions are deliberately narrow. pd is also the conventional pandas alias, and pandas genuinely has a pd.plotting submodule, so a blanket pd. -> blend. rewrite would have corrupted four files. Only package-unambiguous forms were changed: from pd.X, -m pd.X, pd.<our module>, PD_BYTES_BUDGET, src/pd, and the pyproject name. All four import pandas as pd lines are untouched and verified. Both READMEs reframed: peering degree is now presented as the primary axis that ties the others together rather than as the subject, and the relative links, which lost a directory level in the move, are corrected. Verified after the move: ruff clean, 101 tests, 45 verify anchors, make targets, the script shims, an end-to-end smoke run, and data/report_numbers.py still reproducing the report tables from the checked-in evidence. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
16 lines
509 B
YAML
16 lines
509 B
YAML
# Fast end-to-end smoke run (seconds): tiny N, few rounds/seeds, both adversary modes.
|
|
# Numbers here are far too noisy to interpret -- the point is that every code path runs and every
|
|
# figure builder renders, including the multi-cascade (redundancy > 1) aggregation.
|
|
n_nodes: [1000]
|
|
degree: [4, 8]
|
|
blend_hops: [2, 3]
|
|
max_blend_delay: [0, 3]
|
|
unresponsive_frac: [0.0, 0.2, 0.5]
|
|
redundancy: [1, 2]
|
|
f_adv: [0.1, 0.33]
|
|
adversary_mode: [random, worstcase_coverage]
|
|
seeds: 2
|
|
base:
|
|
n_rounds: 20
|
|
n_placements: 2
|