docs: update readme and signed_message

Signed-off-by: Gustavo Inacio <gustavo@semiotic.ai>
semiotic-ai · Mar 26, 2024 · 2a2117b · 2a2117b
1 parent 7f4f6cb
commit 2a2117b
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 5 deletions.
diff --git a/README.md b/README.md
@@ -54,9 +54,10 @@ and network limitations for sending requests to the tap_aggregator.
 
 ## Use Cases
 
-- The TAP protocol is suitable for systems with sequential operations that are 
-too expensive to redeem individually on-chain. By aggregating operations 
-off-chain and redeeming them in one transaction, costs are drastically reduced.
+- The TAP protocol is suitable for systems that need unidirectional, parallel 
+micro-payments that are too expensive to redeem individually on-chain. By 
+aggregating operations off-chain and redeeming them in one transaction, costs 
+are drastically reduced.
 
 ## Compatibility
 

diff --git a/tap_core/src/signed_message.rs b/tap_core/src/signed_message.rs
@@ -48,8 +48,8 @@ pub struct EIP712SignedMessage<M: SolStruct> {
 
 /// Unique identifier for a message
 ///
-/// This is equal to the hash of the hash of the contents of a message. This means
-/// that two receipts signed by two different signers will have the same id.
+/// This is equal to the hash of the contents of a message, excluding the signature.
+/// This means that two receipts signed by two different signers will have the same id.
 ///
 ///
 /// This cannot be used as a unique identifier for a message, but can be used as a key