Sensor-Subscription-Protocol.md

@@ -30,7 +30,7 @@ If a node receives a message whose `receiver` address does not match the node's
 
 This protocol is used to establish, maintain, and revoke subscriptions. It is specified by the following state machine:
 
-![subscription-protocol.svg](uploads/9505ae8889b2d7a79b237de07352c8ec/subscription-protocol.svg)
+![subscription-protocol.svg](uploads/741526c76a24685a46e124b4fa82eda7/subscription-protocol.svg)
 
 Subscriptions are established with a 2-way-handshake.
 
@@ -49,7 +49,7 @@ When the publisher receives an `UNSUBSCRIBE` message, it deletes the matching su
 
 This protocol defines how publishers notify subscribers about new sensor readings of sensors they have subscribed to. It is specified by the following state machine:
 
-![subscription-notification-protocol.svg](uploads/9afe1f59640930aa8f33bab917fef805/subscription-notification-protocol.svg)
+![subscription-notification-protocol.svg](uploads/fbcc42a5f7e5ec7c6c85fbf7f04f5076/subscription-notification-protocol.svg)
 
 When a node receives a new sensor reading from one of its local sensors, it looks in its local database whether any subscribers exist for the given sensor. If none are present, nothing further happens. If some subscribers are present, the new reading is sent to each subscriber via a `READING` message.