From 62924a033cb2a0130cc6a072e03590f8eec5ac72 Mon Sep 17 00:00:00 2001 From: Dimitri Staessens Date: Sat, 8 Nov 2025 08:11:24 +0100 Subject: ouroboros: Flow compatibility with O7s 0.22 O7s 0.22 moved the cypher strength from QoS to the service name properties and removed QoS spec from the broadcast API (flow_join). --- README.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index a7b3a8c..36c3613 100644 --- a/README.md +++ b/README.md @@ -83,13 +83,12 @@ You can specify a QoSSpec for flow allocation. For instance, ```Python -qos = QoSSpec(loss=0, cypher_s=256, timeout=60000) +qos = QoSSpec(loss=0, timeout=60000) f = flow_alloc("name", qos) ``` -will create a new flow with FRCP retransmission enabled and encrypted -using a 256-bit ECDHE-AES-SHA3 cypher that will timeout if the peer is -not responsive for 1 minute. +will create a new flow with FRCP retransmission enabled that will +timeout if the peer is not responsive for 1 minute. ## Manipulating flows -- cgit v1.2.3