proto: make more precise DisperseBlobRequest.data comment

Layr-Labs · Oct 19, 2024 · 795868e · 795868e
1 parent 5bb9efc
commit 795868e
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 6 deletions.
diff --git a/api/grpc/disperser/disperser.pb.go b/api/grpc/disperser/disperser.pb.go
diff --git a/api/proto/disperser/disperser.proto b/api/proto/disperser/disperser.proto
@@ -78,12 +78,11 @@ message AuthenticationData {
 
 message DisperseBlobRequest {
 	// The data to be dispersed.
-	// The size of data must be <= 16MiB. Every 32 bytes of data chunk is interpreted as an integer in big endian format
+	// The size of data must be <= 16MiB. Every 32 bytes of data is interpreted as an integer in big endian format
 	// where the lower address has more significant bits. The integer must stay in the valid range to be interpreted
 	// as a field element on the bn254 curve. The valid range is 
 	// 0 <= x < 21888242871839275222246405745257275088548364400416034343698204186575808495617
-	// If any one of the 32 bytes chunk is outside the range, the whole request is deemed as invalid, and rejected. 
-	// Note that the max allowed field element is a 254 bit number, meaning the first 2 bits of each chunk will always be 00.
+	// If any one of the 32 bytes elements is outside the range, the whole request is deemed as invalid, and rejected. 
 	bytes data = 1;
 	// The quorums to which the blob will be sent, in addition to the required quorums which are configured
 	// on the EigenDA smart contract. If required quorums are included here, an error will be returned.