Sequencer charged actual_fee 3644x beyond signed resource_bounds — 15,518 STRK overcharged

[ttendoscopie-creator]

Summary

On March 12, 2026, 8 transactions were charged fees vastly exceeding their signed resource_bounds. The primary TX was charged 1,845 STRK while the signed max_amount × max_price_per_unit was 0.506 STRK — a 3644x overcharge. Total loss across 8 TXs: 15,518 STRK (~$3,100 at the time).

This was first reported in starknet-io/starknet.js#1597, where the starknet.js maintainer acknowledged the issue and suggested escalating to StarkWare.

The problem

According to Starknet fee documentation, the ZK proof enforces that the sequencer cannot charge more than max_amount × max_price_per_unit. If this enforcement held, the overcharge should have been impossible.

Either:

1. The sequencer charged beyond the signed bounds (protocol-level bug)
2. estimateInvokeFee returned insane bounds that were then signed (SDK bug, but sequencer should still cap)
3. Something modified the resource_bounds between signing and inclusion

Evidence

• Primary TX: 0x3b8da656f920607a8b529f204e15037c877c74c727defc93890fdab292695bc (block 7654710)
• 8 affected TXs, blocks 7654710–7654901
• All TXs were AVNU swaps via account.execute (starknet.js v6)
• Detailed analysis with all TX hashes in the original issue

Request

1. Reproduce: Call estimateInvokeFee on the historical blocks where each TX was included, and compare with the actual_fee charged
2. Verify: Check if the resource_bounds in the signed TX match what getTransactionByHash reports
3. Explain: What caused the 3644x multiplier?
4. Refund: If this is a sequencer bug, we request a refund of the overcharged amount (15,518 STRK)

Related

• Original report: starknet-io/starknet.js#1597