Home /
Input Output /
ouroboros-leios
Mar 13, 8-9 AM (0)
Mar 13, 9-10 AM (4)
Mar 13, 10-11 AM (0)
Mar 13, 11-12 PM (0)
Mar 13, 12-1 PM (0)
Mar 13, 1-2 PM (1)
Mar 13, 2-3 PM (1)
Mar 13, 3-4 PM (0)
Mar 13, 4-5 PM (0)
Mar 13, 5-6 PM (0)
Mar 13, 6-7 PM (0)
Mar 13, 7-8 PM (0)
Mar 13, 8-9 PM (0)
Mar 13, 9-10 PM (0)
Mar 13, 10-11 PM (0)
Mar 13, 11-12 AM (0)
Mar 14, 12-1 AM (0)
Mar 14, 1-2 AM (0)
Mar 14, 2-3 AM (0)
Mar 14, 3-4 AM (0)
Mar 14, 4-5 AM (0)
Mar 14, 5-6 AM (0)
Mar 14, 6-7 AM (0)
Mar 14, 7-8 AM (0)
Mar 14, 8-9 AM (0)
Mar 14, 9-10 AM (0)
Mar 14, 10-11 AM (0)
Mar 14, 11-12 PM (0)
Mar 14, 12-1 PM (0)
Mar 14, 1-2 PM (0)
Mar 14, 2-3 PM (0)
Mar 14, 3-4 PM (0)
Mar 14, 4-5 PM (0)
Mar 14, 5-6 PM (0)
Mar 14, 6-7 PM (0)
Mar 14, 7-8 PM (0)
Mar 14, 8-9 PM (0)
Mar 14, 9-10 PM (0)
Mar 14, 10-11 PM (0)
Mar 14, 11-12 AM (0)
Mar 15, 12-1 AM (0)
Mar 15, 1-2 AM (0)
Mar 15, 2-3 AM (0)
Mar 15, 3-4 AM (0)
Mar 15, 4-5 AM (0)
Mar 15, 5-6 AM (0)
Mar 15, 6-7 AM (0)
Mar 15, 7-8 AM (0)
Mar 15, 8-9 AM (0)
Mar 15, 9-10 AM (0)
Mar 15, 10-11 AM (0)
Mar 15, 11-12 PM (0)
Mar 15, 12-1 PM (0)
Mar 15, 1-2 PM (0)
Mar 15, 2-3 PM (0)
Mar 15, 3-4 PM (0)
Mar 15, 4-5 PM (0)
Mar 15, 5-6 PM (0)
Mar 15, 6-7 PM (0)
Mar 15, 7-8 PM (0)
Mar 15, 8-9 PM (0)
Mar 15, 9-10 PM (0)
Mar 15, 10-11 PM (0)
Mar 15, 11-12 AM (0)
Mar 16, 12-1 AM (0)
Mar 16, 1-2 AM (0)
Mar 16, 2-3 AM (0)
Mar 16, 3-4 AM (0)
Mar 16, 4-5 AM (0)
Mar 16, 5-6 AM (0)
Mar 16, 6-7 AM (0)
Mar 16, 7-8 AM (0)
Mar 16, 8-9 AM (0)
Mar 16, 9-10 AM (0)
Mar 16, 10-11 AM (1)
Mar 16, 11-12 PM (0)
Mar 16, 12-1 PM (0)
Mar 16, 1-2 PM (1)
Mar 16, 2-3 PM (0)
Mar 16, 3-4 PM (0)
Mar 16, 4-5 PM (0)
Mar 16, 5-6 PM (0)
Mar 16, 6-7 PM (0)
Mar 16, 7-8 PM (0)
Mar 16, 8-9 PM (0)
Mar 16, 9-10 PM (0)
Mar 16, 10-11 PM (0)
Mar 16, 11-12 AM (0)
Mar 17, 12-1 AM (0)
Mar 17, 1-2 AM (0)
Mar 17, 2-3 AM (0)
Mar 17, 3-4 AM (0)
Mar 17, 4-5 AM (0)
Mar 17, 5-6 AM (0)
Mar 17, 6-7 AM (0)
Mar 17, 7-8 AM (0)
Mar 17, 8-9 AM (0)
Mar 17, 9-10 AM (0)
Mar 17, 10-11 AM (0)
Mar 17, 11-12 PM (0)
Mar 17, 12-1 PM (1)
Mar 17, 1-2 PM (1)
Mar 17, 2-3 PM (0)
Mar 17, 3-4 PM (0)
Mar 17, 4-5 PM (0)
Mar 17, 5-6 PM (0)
Mar 17, 6-7 PM (0)
Mar 17, 7-8 PM (0)
Mar 17, 8-9 PM (0)
Mar 17, 9-10 PM (0)
Mar 17, 10-11 PM (0)
Mar 17, 11-12 AM (0)
Mar 18, 12-1 AM (0)
Mar 18, 1-2 AM (0)
Mar 18, 2-3 AM (0)
Mar 18, 3-4 AM (0)
Mar 18, 4-5 AM (0)
Mar 18, 5-6 AM (0)
Mar 18, 6-7 AM (0)
Mar 18, 7-8 AM (0)
Mar 18, 8-9 AM (2)
Mar 18, 9-10 AM (0)
Mar 18, 10-11 AM (0)
Mar 18, 11-12 PM (0)
Mar 18, 12-1 PM (0)
Mar 18, 1-2 PM (1)
Mar 18, 2-3 PM (1)
Mar 18, 3-4 PM (0)
Mar 18, 4-5 PM (0)
Mar 18, 5-6 PM (2)
Mar 18, 6-7 PM (0)
Mar 18, 7-8 PM (0)
Mar 18, 8-9 PM (0)
Mar 18, 9-10 PM (0)
Mar 18, 10-11 PM (0)
Mar 18, 11-12 AM (0)
Mar 19, 12-1 AM (0)
Mar 19, 1-2 AM (0)
Mar 19, 2-3 AM (0)
Mar 19, 3-4 AM (0)
Mar 19, 4-5 AM (0)
Mar 19, 5-6 AM (0)
Mar 19, 6-7 AM (0)
Mar 19, 7-8 AM (1)
Mar 19, 8-9 AM (0)
Mar 19, 9-10 AM (1)
Mar 19, 10-11 AM (0)
Mar 19, 11-12 PM (1)
Mar 19, 12-1 PM (0)
Mar 19, 1-2 PM (0)
Mar 19, 2-3 PM (0)
Mar 19, 3-4 PM (0)
Mar 19, 4-5 PM (0)
Mar 19, 5-6 PM (0)
Mar 19, 6-7 PM (0)
Mar 19, 7-8 PM (0)
Mar 19, 8-9 PM (0)
Mar 19, 9-10 PM (0)
Mar 19, 10-11 PM (0)
Mar 19, 11-12 AM (0)
Mar 20, 12-1 AM (0)
Mar 20, 1-2 AM (0)
Mar 20, 2-3 AM (0)
Mar 20, 3-4 AM (0)
Mar 20, 4-5 AM (0)
Mar 20, 5-6 AM (0)
Mar 20, 6-7 AM (0)
Mar 20, 7-8 AM (1)
Mar 20, 8-9 AM (1)
21 commits this week
Mar 13, 2026
-
Mar 20, 2026
Add timestamp quantization and TX batching to sequential engine
The sequential engine was never quantizing timestamps, so each event had a unique timestamp and rayon parallelism never kicked in during TX-only periods. Two independent optimizations, each configurable separately: - Timestamp quantization: now applied to all events in the sequential engine, controlled by existing timestamp-resolution-ms (turbo.yaml sets 1.0ms) - TX batch generation: new tx-batch-window-ms config option batches all TX generation events within a time window into one timestamp (turbo.yaml sets 10ms). Independent of timestamp resolution. Also lowers parallel-threshold from 10 to 4 in turbo.yaml. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Moved report to docs
deploy: ffe6a61f0379b536c3672cb0d19174a85f30ba13
Merge pull request #812 from input-output-hk/prc/ui-auto-layout
UI: Add graph layout modes (force, circular, Mercator)
Add tx backlog instrumentation and configurable cap
Track the maximum tx backlog length (overflow queue behind the mempool) via events, and add a leios-tx-backlog-max-size config parameter that applies backpressure on the tx generator when the backlog is full. Peer transactions are unaffected by the cap. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Make parallel-threshold configurable, default 10, add to schema
Extract the hardcoded PARALLEL_THRESHOLD constant into a configurable parallel-threshold parameter (default 10, was 32). Add engine and parallel-threshold to config.schema.json. Disable rayon in the determinism test since event channel ordering is non-deterministic under parallel execution. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Warn when attacker config is used with sequential engine
The sequential engine does not run Actor-based attackers (EBWithholdingAttacker). Log a warning so the config isn't silently ignored. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Refactor: extract actor engine to actor.rs, clean up sim.rs
- Extract actor-model simulation (NodeListWrapper, ActorSimulation, init_nodes, run logic) into sim/actor.rs - sim.rs is now a thin dispatch layer: Simulation newtype wrapping SimulationInner enum (Actor vs Sequential) - Unify sequential single-shard and multi-shard builders into a single build_typed() function - Group cross-shard state into CrossShardState sub-struct - build() takes event_sender directly, creates its own infrastructure - Remove dead code (per_shard_node_configs, init_node_impls) - Net -407 lines across sim.rs + sequential.rs Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
demo: 1. Use bursty mux 2. set TCP_NOTSENT_LOWAT socket option
Add configurable shard allocation strategies and single-shard fast path
- Add ShardStrategy enum (round-robin, zero-latency-clusters) configurable via shard-strategy in YAML parameters - Extract sharding logic into sim-core/src/sharding/ module with pluggable strategy files - zero-latency-clusters uses union-find to keep 0-latency-connected nodes on the same shard, improving CMB lookahead - Log shard sizes after assignment for balance diagnostics - Restore single-shard select! fast path (avoids tokio::spawn overhead that caused 50% regression vs pre-sharding baseline) - Update config schema and test parameter files Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
filip(feat): add iframe design implementation with latest main changes
demo: fix network emulation
TOSQUASH add synthetic field in logical ER diagram
TOSQUASH elaborating RelationalStorage.md
Add redirects and move monthly-reviews page
Use local SVG assets for What is Leios graphics