Add more responseCodes (#75)

* added response codes for if we a denominatig token type is a NFT and one for when and NFT has a fractional fee in its feeSchedule Signed-off-by: anighanta <[email protected]> * Added INVALID_CUSTOM_FEE_SCHEDULE_KEY code. Signed-off-by: ljianghedera <[email protected]> * Fix typo. Signed-off-by: Quan Nguyen <[email protected]> * Update from upstream. Signed-off-by: Quan Nguyen <[email protected]> Co-authored-by: ljianghedera <[email protected]> Co-authored-by: Quan Nguyen <[email protected]>
hashgraph · Jul 6, 2021 · 8699be4 · 8699be4
1 parent 26b8933
commit 8699be4
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/src/main/proto/ResponseCode.proto b/src/main/proto/ResponseCode.proto
@@ -254,4 +254,7 @@ enum ResponseCodeEnum {
   INVALID_CUSTOM_FRACTIONAL_FEES_SUM = 242; // The sum of all custom fractional fees must be strictly less than 1
   FRACTIONAL_FEE_MAX_AMOUNT_LESS_THAN_MIN_AMOUNT = 243; // Each fractional custom fee must have its maximum_amount, if specified, at least its minimum_amount
   CUSTOM_SCHEDULE_ALREADY_HAS_NO_FEES = 244; // A fee schedule update tried to clear the custom fees from a token whose fee schedule was already empty
+  CUSTOM_FEE_DENOMINATION_MUST_BE_FUNGIBLE_COMMON = 245; // Only tokens of type FUNGIBLE_COMMON can be used to as fee schedule denominations
+  CUSTOM_FRACTIONAL_FEE_ONLY_ALLOWED_FOR_FUNGIBLE_COMMON = 246; // Only tokens of type FUNGIBLE_COMMON can have fractional fees
+  INVALID_CUSTOM_FEE_SCHEDULE_KEY = 247; // The provided custom fee schedule key was invalid
 }