Skip to content
#software testing Open access

Beyond Node Counts: Correlated-Failure Audits for Multi-Role Permissioned Ledgers

Oct 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

Reproducibility artifact for “Beyond Node Counts: Correlated-Failure Audits for Multi-Role Permissioned Ledgers” Version 1.0.0 accompanies the ETECOM 2026 paper by Son Huu Trung Dang, An Van Nguyen, and Tam Huu Tran. Beyond Node Counts examines how shared dependencies affect threshold availability in permissioned-ledger deployments. Given a fixed component placement, an inventory of disruptive actions, positive integer action weights, and role-specific thresholds, the implementation computes minimum-weight disruption witnesses for validator outage, committee outage, pipeline OR, and simultaneous AND. The model describes each action through the components it disables and combines selected actions by set union. The artifact implements the mixed-integer linear formulation, exhaustive integer enumeration, a quota-cover greedy baseline, and independent bounded checks. Numerical acceptance checks validate returned witnesses and objective values; a bounded exact fallback handles specified numerical discrepancies. This record contains the executable implementation and the experimental material supporting the paper: constructed configurations, benchmark inputs, reference results, sampled trace mappings, behavioral tests, and recorded ledger and dependency experiments. FILES - etecom-2026-artifact-1.0.0.zip: the execution archive, including Docker setup, Python source, experiment runners, input data, reference outputs, and supplementary evidence.- SHA256SUMS: SHA-256 checksums for the prepared release files. ARTIFACT_MANIFEST.json records the delivered inventory and individual file hashes. EVIDENCE_PROVENANCE.json identifies the selected historical evidence, its original hashes, and the entries omitted from this execution package. HOW TO RUN Extract the archive and run these commands from its root directory: docker build -t etecom-artifact:1.0.0 . docker run --rm --network=none etecom-artifact:1.0.0 The build requires Internet access to obtain the Python image and dependencies. Experiment execution then runs offline with networking disabled. Docker provides the Python environment; no local scientific packages or LaTeX installation are required. The container checks the delivery manifest, executes the test suite, recomputes the primary evaluation, and verifies the saved supplementary evidence. Successful execution ends with: experiment reproduction passed Results appear in /artifact/evaluation/generated/ inside the container, with execution logs in /artifact/build_logs/. The README provides commands for retaining a container and copying these outputs to the host. The archive also includes reference outputs for inspection. For native execution, use Python 3.11, 3.12, or 3.13. On Windows, run setup.bat followed by run.bat; on Linux, run sh setup.sh followed by sh run.sh. Setup installs the dependencies specified in requirements.lock. The Docker workflow has been tested from the extracted release archive on Linux containers with networking disabled. DATASETS The artifact uses both Google ClusterData 2011 and Microsoft 1999 desktop reachability data. The Google machine-event shard resides under data/external/google_clusterdata_2011/. The default workflow recomputes 100,000 paired host mappings and compares 800,000 outage durations against an independent interval oracle. The Microsoft material resides under supplementary/microsoft1999/. It includes 100,000 saved mappings, replay summaries, statistical checks, source provenance, and two independent duration-oracle implementations. The default workflow verifies the saved records. Full replay from source requires the supplied download script, which checks pinned hashes before extracting the input. The archive omits the raw Microsoft trace because the recorded provenance review did not establish permission for downstream redistribution. WHAT THE

Results

COVER The default workflow passes 126 tests. Computational checks include 720 MILP-to-enumeration objective comparisons, 599 bounded Set Cover reduction cases, and 179,520 bounded quota instances. Constructed experiments examine inventory omissions, incidence uncertainty, action-weight sensitivity, approximation behavior, and runtime scaling. Supplementary numerical stress records cover 2,000 small instances, with zero accepted mismatches and 100 exact fallbacks. A separate script supports rerunning this stress experiment. The recorded CometBFT experiment tests quorum conformance under controlled validator-process pauses on one host. The prospective dependency experiment examines a synthetic authorization path through 56 primary relay windows, with original controls and separately recorded corrective controls. Offline verification checks the underlying observations; the default workflow does not launch new live ledger experiments.

Interpretation

The historical traces support counterfactual ledger-role assignments and conditional availability comparisons. They do not supply observed ledger-role inventories, causal failure domains, or calibrated disruption costs. The dependency experiment identifies configurations that violate the union-incidence assumption. Its targeted route change matches a simple placement heuristic and does not improve the mean outage count of the tested matrix. The reported evidence supports the stated model checks and experimental comparisons, without establishing production effectiveness or optimizer superiority.

Funding

AND ATTRIBUTION Vietnamese-German University (VGU) funded this research. The authors acknowledge ChatGPT assistance with evaluation and plotting code and take responsibility for the final implementation. Licence: MIT for authored software. Google inputs retain CC BY 4.0 attribution, and supplementary materials retain their applicable source notices. See LICENSE, THIRD_PARTY_NOTICES.md, and the dataset-specific notices inside the archive.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

GPT-Lab Sep 23, 2026

Requirements Don’t Live in Isolation: What We’re Exploring with Req-Space

Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…

GPT-Lab Sep 17, 2026

Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering

AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.