From 4c5e83623f12579713ae363d23894ad5a0fc3091 Mon Sep 17 00:00:00 2001 From: Ulf Wiger Date: Wed, 1 Apr 2026 16:11:46 +0900 Subject: [PATCH] Update State Channels --- State-Channels.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/State-Channels.md b/State-Channels.md index 9d1e785..f278cff 100644 --- a/State-Channels.md +++ b/State-Channels.md @@ -18,7 +18,7 @@ On one state channel session, you can roughly execute: * 500+ coin transfers per second * 3000+ plain messages per second -(or a mix of the above). These are estimates based on a rudimentary benchmark suite, running on an M2 Macbook, and can be updated on request. It's important to note that these interactions come with an ordering guarantee, i.e. they are all performed sequentially. Multiple concurrent channels allow for much higher throughput when transactions can be serviced in parallel. +(or a mix of the above). These are estimates based on a rudimentary benchmark suite, running on an M4 Macbook, and can be updated on request. It's important to note that these interactions come with an ordering guarantee, i.e. they are all performed sequentially. Multiple concurrent channels allow for much higher throughput when transactions can be serviced in parallel. An intuition for the number "500+ coin transfers per second" would be that given that the test measured round-trip time for both parties of a coin transfer (2 ms), one might estimate the processing overhead of serving one side of a State Channel payment to be **less than 1 ms**.