From 2a2117bb1559286fb65cb87cfb3a59dfff999df5 Mon Sep 17 00:00:00 2001 From: Gustavo Inacio Date: Tue, 26 Mar 2024 10:36:06 -0300 Subject: [PATCH] docs: update readme and signed_message Signed-off-by: Gustavo Inacio --- README.md | 7 ++++--- tap_core/src/signed_message.rs | 4 ++-- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 2b9889fe..2cb20ad6 100644 --- 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 index 602c9aa3..53edc3c5 100644 --- a/tap_core/src/signed_message.rs +++ b/tap_core/src/signed_message.rs @@ -48,8 +48,8 @@ pub struct EIP712SignedMessage { /// 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