Piconbello Incident Reporting

Incident

While doing our checks, we have realized that one sequencer was left in an older version, 6 blocks were misconfigured, with details as below:

Slot Epoch L2 Block Date/time (UTC) Reward L1 Proposal TX
116289 3634 76077 2026-06-09 17:42:47 350 AZTEC 0x7119528213b4b0e612815ea62f52caab62afd2dc26dac11d185c2bcaf09f0255
119342 3729 79050 2026-06-12 06:46:23 350 AZTEC 0xabae275d2f632a50b557a22e5a45ca8cb2dddc134cc04e6e6ceac1879aea6b50
119347 3729 79055 2026-06-12 06:52:23 350 AZTEC 0x48246e97d5f526e7c9484034e7aaeae4824e326e80c9f978571d8674823e7bb7
123952 3873 83593 2026-06-16 02:58:23 350 AZTEC 0x453beffd9281b091046dbf573e9be4a14fd8d910b90da16472163ff10fb1b2f9
123959 3873 83600 2026-06-16 03:06:47 350 AZTEC 0xd215b19c0c80498d09b5368f477a9dacb37a899dff9941c5cc4fa68f8053113e
128983 4030 88434 2026-06-20 07:35:35 350 AZTEC 0xefbb49cb8959eb957434b726c47ec1abec53d935c8d4a72fb99a6e659073e04c

Review

The problem caused by our misconfiguration on one of our HA nodes after update, there is no need for the mentioned sequencer to contact us for reimbursement. To observe the difference for the mentioned sequencer: Sequencer 0xe862...fe18 | Aztec Vision .

We have calculated the amount to be reimbursed as 500 AZTEC per block, 70% sequencer bps, for all 6 blocks, which are forwarded to the split address of the sequencer already. Here is the transaction record for the reimbursement, as announced before, we will not be changing fees for the existing stakers: Ethereum Transaction Hash: 0xc19c05adc3... | Etherscan .

For any concerns regarding our services, feel free to contact us through Telegram. To follow everything live, through our public dashboard, feel free to reach Grafana .