chore: Updated HIP-1313 with latest protobuf changes (#1399)

Signed-off-by: Neeharika-Sompalli <neeharika.sompalli@swirldslabs.com>
Signed-off-by: Neeharika Sompalli <52669918+Neeharika-Sompalli@users.noreply.github.com>
Co-authored-by: Joseph S. <121976561+jsync-swirlds@users.noreply.github.com>

Author: Neeharika-Sompalli

HIP/hip-1313.md

@@ -13,7 +13,7 @@ hedera-reviewed-date: 2025-12-16
 hedera-acceptance-decision: Accepted
 last-call-date-time: 2025-12-30T07:00:00Z
 created: 2025-10-17
-updated: 2026-01-16
+updated: 2026-02-04
 requires: 1261
 ---
 
@@ -222,17 +222,11 @@ message ServiceFeeDefinition {
 message VariableRateDefinition {
   /**
    * Maximum multiplier to prevent extreme pricing (cost ceiling).
+   * This value SHOULD be greater than or equal to 1000, any value less than 1000 SHALL be treated as 1000.
+   * This value SHALL be divided by 1000 before it is applied as a multiplier, a value of `1000` is therefore a multiplier of `1.000`.
    * Given the normal price of the transaction, the computed variable price
-   * will not exceed `max_multiplier` * `standard_fee`. Provides predictability
-   * for users regardless of utilization. The minimum price will be the
-   * `standard_fee`. This value is divided by 1,000,000 and then added to the
-   * minimum value of 1.
-   * <p>
-   * ##Example
-   * A value of `2,450,300` results in an _effective_ floating point multiplier
-   * of `3.4503`.<br/>
-   * A value of `0` results in an _effective_ floating point
-   * multiplier of `1.0`.
+   * will not exceed this multiplier * `standard_fee`. Provides predictability
+   * for users regardless of utilization.
    */
   uint32 max_multiplier = 2;
 
@@ -277,11 +271,11 @@ message PricingCurve {
 message PiecewiseLinearCurve {
   /**
    * A list of points defining the piecewise linear curve.
-   * Each point is a pair of (utilization_percentage, multiplier). The list
-   * must be sorted by utilization_percentage in ascending order, and
+   * Each point is a pair of (utilization_basis_points, multiplier). The list
+   * must be sorted by utilization_basis_points in ascending order, and
    * sub-ordered by multiplier in ascending order for points with the same
-   * utilization percentage. It is legal to have two points with the same
-   * utilization percentage, but they must have different multipliers.
+   * utilization basis points. It is legal to have two points with the same
+   * utilization basis points, but they must have different multipliers.
    * This allows the creation of stepped pricing curves.
    */
   repeated PiecewiseLinearPoint points = 1;
@@ -293,17 +287,33 @@ message PiecewiseLinearCurve {
  */
 message PiecewiseLinearPoint {
   /**
-   * The utilization percentage for this point, in thousandths of one percent.
-   * This value must be between 0 and 100,000, inclusive.
+   * The utilization percentage for this point, in hundredths of one percent.
+   * This value must be between 0 and 10,000, inclusive.
    */
-  uint32 utilization_percentage = 1;
+  uint32 utilization_basis_points = 1;
 
   /**
    * The multiplier to apply at this utilization percentage.
-   * This value is divided by 1,000,000 then added to 1.
+   * This value SHOULD be greater than or equal to 1000, any value less than 1000 SHALL be treated as 1000
+   * This value SHALL be divided by 1000 before it is applied as a multiplier, a value of `1000` is therefore a multiplier of `1.000`.
    */
   uint32 multiplier = 2;
 }
+```
+Adds the high volume multiplier to the `transaction_result`
+```protobuf
+syntax = "proto3";
+message TransactionResult {
+  // ... existing fields ...
+  /**
+   * A high volume pricing multiplier.
+   * <p>
+   * This SHALL be the multiplier that was applied to the transaction
+   * fees charged for this transaction, if the high volume flag was set.
+   */
+  uint64 high_volume_pricing_multiplier = 13;
+}
+
 ```
 
 Limits and pricing are configured independently for flexibility.