From 4e50db56db226cef10f8a8a06deff6e1d69d1080 Mon Sep 17 00:00:00 2001
From: Dean Eigenmann <7621705+decanus@users.noreply.github.com>
Date: Thu, 11 Jun 2020 14:41:33 +0200
Subject: [PATCH] Update waku-1.md

---
 specs/waku/waku-1.md | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/specs/waku/waku-1.md b/specs/waku/waku-1.md
index 271e1e94..1a2d46e4 100644
--- a/specs/waku/waku-1.md
+++ b/specs/waku/waku-1.md
@@ -427,14 +427,7 @@ Light nodes are identified by the `light_node` value in the Status packet.
 
 Nodes MAY implement accounting, keeping track of resource usage. It is heavily inspired by Swarm's [SWAP protocol](https://www.bokconsulting.com.au/wp-content/uploads/2016/09/tron-fischer-sw3.pdf), and works by doing pairwise accounting for resources.
 
-Each node keeps track of resource usage with all other nodes. Whenever an envelope is received from a node that is expected (fits bloom filter or topic interest, is legal, etc) this is tracked.
-
-Every epoch (say, every minute or every time an event happens) statistics SHOULD be aggregated and saved by the client:
-
-| peer  | sent | received |
-|-------|------|----------|
-| peer1 | 0    | 123 |
-| peer2 | 10   | 40  |
+Each node SHOULD keep track of resource usage of all other nodes. Whenever an envelope is received from a node that is expected (fits bloom filter or topic interest, is legal, etc) or sent, it SHOULD be tracked.
 
 In later versions this will be amended by nodes communication thresholds, settlements and disconnect logic.