fix: revise HIP response code and mirror node consideration (#1267)

Signed-off-by: Luke Lee <luke.lee@hashgraph.com>
Co-authored-by: Michael Garber <michael.garber@hashgraph.com>

Author: lukelee-sl

HIP/hip-1249.md

@@ -12,7 +12,7 @@ created: 2025-06-30
 last-call-date-time: 2025-08-13T07:00:00Z
 discussions-to: https://github.com/hiero-ledger/hiero-improvement-proposals/pull/1249
 replaces: 185
-updated: 2025-08-04
+updated: 2025-08-20
 ---
 
 # Abstract
@@ -88,7 +88,7 @@ Under this proposal:
 - Each transaction specifies a gas limit (must not exceed network maximum).
 - At execution:
     - Ops units are deducted from the throttle bucket based on executed opcodes.
-    - If the bucket is exhausted, remaining transactions fail with THROTTLED_AT_CONSENSUS and incur only the intrinsic
+    - If the bucket is exhausted, remaining transactions fail with CONSENSUS_GAS_EXHAUSTED and incur only the intrinsic
       gas fee (covering network costs).
 
 This maintains the current behavior where over-submitted transactions may fail and incur fees, but improves overall
@@ -153,6 +153,11 @@ operations not covered by other throttles.
 
 If a precompile/system call exhausts ops mid-transaction, handle as in Execution Outcomes.
 
+## Mirror Node Considerations
+The mirror node computes a value called `gasConsumed` in order to provide a more accurate representation of gas used by
+the evm.  As the `gasUsed` value will accurately reflect the gas used by the evm, the `gasConsumed` value will equal `gasUsed`
+going forward. `gasConsumed` will still exist for backwards compatibility, but `gasUsed` should be used in all new code.
+
 # Backwards Compatibility
 
 This change is backward-compatible for developers:
@@ -189,8 +194,9 @@ Educate developers on key changes:
 
 1. **Simplified Billing**: No more 80% minimum charge—pay only for gas used. This reduces costs for overestimated limits
    and eases gas estimation.
-2. **Throttle Failures**: Transactions may still fail due to exhausted ops/sec (error: THROTTLED_AT_CONSENSUS), even if
-   valid. Advise retry logic and monitoring network load.
+2. **Throttle Failures**: A transaction may overfill the ops per second throttle up to a 15M gas per transaction limit.  
+   Subsequent transactions will fail (error: CONSENSUS_GAS_EXHAUSTED) until enough time passes to refill some throttle capacity, 
+   even if valid. Advise retry logic and monitoring network load.
 3. **Performance Gains**: Highlight potential for faster, higher-throughput applications without code changes.
 4. **Precompile/System Call Costs**: Explain that these now factor into throttling for better performance limits.
    Developers using HTS or crypto functions should note potential failures if ops exhaust, but no code changes