Latest Repo Discovered
bid-optimization
CSS
·
No license
Top Contributor of the Month
11060 commits in all time
Jan 21, 2026 08:16 – Apr 21, 2026 08:16 UTC
refactor: apply generic constant-index handling to setbit, getbyte, setbyte
Mirrors the recent getbit change: match a constant-bytes shape first (tight bound against the constant length), then fall through to a generic case that catches cases where the index is known constant but the first arg is runtime — index >= 8 * MAX_BYTES_LENGTH (or MAX_BYTES_LENGTH for byte ops) is statically impossible regardless of the runtime value.
7e0ffc47
feat/statically-failing-op-validator
1/24 ++ 7 --
refactor: generalise _bytes_length_lower_bound pattern to substring3, replace2, replace3
Follow the same approach as getbit/setbit/getbyte/setbyte: accept any bytes arg for the first operand and use `_bytes_length_lower_bound` to get a tight bound for `BytesConstant` and the AVM maximum (MAX_BYTES_LENGTH) otherwise. Unifies substring3's previously separate constant-bytes and runtime-bytes arms into one. Doesn't touch the extract family since its immediate-form offsets are capped at 255 (can't exceed MAX_BYTES_LENGTH on its own).
42246337
feat/statically-failing-op-validator
1/12 ++ 19 --