Skip to content

feat(avm)!: Remove is_infinite flag from AVM (PIL and EC points only)#22795

Merged
MirandaWood merged 8 commits into
mw/avm-derive-is-inffrom
mw/avm-explore-remove-is-inf
May 12, 2026
Merged

feat(avm)!: Remove is_infinite flag from AVM (PIL and EC points only)#22795
MirandaWood merged 8 commits into
mw/avm-derive-is-inffrom
mw/avm-explore-remove-is-inf

Conversation

@MirandaWood
Copy link
Copy Markdown
Contributor

@MirandaWood MirandaWood commented Apr 27, 2026

This branch includes the changes to remove the is_infinite flag from our point representation and conceptually treating a point as infinite iff its coordinates are (0, 0).

It only contains logic changes within the AVM for the above and does not touch the opcode - this is in a lower PR - so the CI will probably fail.

Will close Foundation AVM Issue 18


Stack:

@MirandaWood MirandaWood changed the base branch from mw/avm-derive-is-inf to mw/avm-rem-inf-point-wrapper April 30, 2026 15:51
@MirandaWood MirandaWood force-pushed the mw/avm-explore-remove-is-inf branch from 678ee83 to 1a0e853 Compare April 30, 2026 15:53
@MirandaWood MirandaWood changed the title feat(avm)!: WIP explore removing is_infinite field from AVM EC points feat(avm)!: WIP explore removing is_infinite flag from AVM (PIL and EC points) May 5, 2026
@MirandaWood MirandaWood force-pushed the mw/avm-explore-remove-is-inf branch from c591fb3 to 21e39fc Compare May 7, 2026 12:41
@MirandaWood MirandaWood marked this pull request as ready for review May 7, 2026 12:41
@MirandaWood MirandaWood removed the request for review from jeanmon May 7, 2026 12:41
@MirandaWood MirandaWood changed the title feat(avm)!: WIP explore removing is_infinite flag from AVM (PIL and EC points) feat(avm)!: Remove is_infinite flag from AVM (PIL and EC points only) May 7, 2026
@MirandaWood MirandaWood force-pushed the mw/avm-explore-remove-is-inf branch from b5782ae to 76989f9 Compare May 8, 2026 10:54
MirandaWood added a commit that referenced this pull request May 12, 2026
…#22921)

This branch solely contains the changes needed to remove the
`is_infinite` flag from our `StandardAffinePoint` C++ wrapper. Now, we
check whether `x` and `y` are zero to assign an `inf` underlying point.

Will close [Foundation AVM Issue
17](https://linear.app/aztec-foundation/issue/AVM-17/remove-is-inf-flag-from-avms-standardaffinepoint)

---

Stack:

- #22745
- #22564
- `mw/avm-rem-inf-point-wrapper` <-- here
- #22795
- #22945
- #23031
Base automatically changed from mw/avm-rem-inf-point-wrapper to mw/avm-derive-is-inf May 12, 2026 16:17
@MirandaWood MirandaWood merged commit dfaf685 into mw/avm-derive-is-inf May 12, 2026
17 of 21 checks passed
@MirandaWood MirandaWood deleted the mw/avm-explore-remove-is-inf branch May 12, 2026 16:22
MirandaWood added a commit that referenced this pull request May 13, 2026
…#22945)

This branch includes the changes to remove the `is_infinite` flags from
the ECADD opcode fn signature. The actual EC logic changes come above
this PR in the stack, and any changes outside the AVM will be below.

For ease of review, I've separated into commits:

- **feat: remove inf flags from ecadd opcode - ec flow only** Isolated
to the EC flow only (does not change registers so non avm tests will
fail)
- f**eat: rem infs from fuzzer (only gadget fuzzer tested)** Isolated
fixes to get the fuzzer(s) compiling

Will partially close [Foundation AVM Issue
19](https://linear.app/aztec-foundation/issue/AVM-19/) (the following PR
#23031 with ts/rs changes will fully close it).

Note that the opcode mismatches that in ts so **CI will fail** until
#23031 is merged into this branch!

---

Stack:
- #22745
- #22564
- #22921
- #22795
- `mw/avm-rem-inf-opcode-ecadd` <-- here
- #23031
MirandaWood added a commit that referenced this pull request May 15, 2026
… AVM only) (#23031)

This branch includes the changes to remove the `is_infinite` flags from
the ECADD opcode fn signature which reside outside `vm2`. This includes
the transpiler, ts simulator, and anything required in ACIR.

Note that ACIR and noir's black box still use [the
flags](https://github.com/AztecProtocol/aztec-packages/blob/b30fe8f401d7af45148071924b22b3f377750eaf/barretenberg/cpp/src/barretenberg/dsl/acir_format/ec_operations.hpp#L34)
and represent points by a[ triple of
elements.](https://github.com/noir-lang/noir/blob/bc4a37e2994ebc7d44ae98be81e18606b2231c61/acvm-repo/bn254_blackbox_solver/src/embedded_curve_ops.rs#L98)
Since this touches both private and public execution, I think it's out
of scope of this task to update these.

Will partially close [Foundation AVM Issue
19](https://linear.app/aztec-foundation/issue/AVM-19/) (the previous PR
with AVM changes will close the initial portion)

---

Stack:
- #22745
- #22564
- #22921
- #22795
- #22945
- `mw/avm-rem-inf-opcode-ecadd-ext` <-- here
MirandaWood added a commit that referenced this pull request May 15, 2026
…#22921)

This branch solely contains the changes needed to remove the
`is_infinite` flag from our `StandardAffinePoint` C++ wrapper. Now, we
check whether `x` and `y` are zero to assign an `inf` underlying point.

Will close [Foundation AVM Issue
17](https://linear.app/aztec-foundation/issue/AVM-17/remove-is-inf-flag-from-avms-standardaffinepoint)

---

Stack:

- #22745
- #22564
- `mw/avm-rem-inf-point-wrapper` <-- here
- #22795
- #22945
- #23031
MirandaWood added a commit that referenced this pull request May 15, 2026
…y) (#22795)

This branch includes the changes to remove the `is_infinite` flag from
our point representation and conceptually treating a point as infinite
iff its coordinates are `(0, 0)`.

It only contains logic changes within the AVM for the above and does not
touch the opcode - this is in a lower PR - so the **CI will probably
fail**.

Will close [Foundation AVM Issue
18](https://linear.app/aztec-foundation/issue/AVM-18/remove-is-inf-flag-from-resulting-ec-points-in-avm-circuits)

---

Stack:
- #22745
- #22564
- #22921
- `mw/avm-explore-remove-is-inf` <-- here
- #22945
- #23031
MirandaWood added a commit that referenced this pull request May 15, 2026
…#22945)

This branch includes the changes to remove the `is_infinite` flags from
the ECADD opcode fn signature. The actual EC logic changes come above
this PR in the stack, and any changes outside the AVM will be below.

For ease of review, I've separated into commits:

- **feat: remove inf flags from ecadd opcode - ec flow only** Isolated
to the EC flow only (does not change registers so non avm tests will
fail)
- f**eat: rem infs from fuzzer (only gadget fuzzer tested)** Isolated
fixes to get the fuzzer(s) compiling

Will partially close [Foundation AVM Issue
19](https://linear.app/aztec-foundation/issue/AVM-19/) (the following PR

Note that the opcode mismatches that in ts so **CI will fail** until

---

Stack:
- #22745
- #22564
- #22921
- #22795
- `mw/avm-rem-inf-opcode-ecadd` <-- here
- #23031
MirandaWood added a commit that referenced this pull request May 15, 2026
… AVM only) (#23031)

This branch includes the changes to remove the `is_infinite` flags from
the ECADD opcode fn signature which reside outside `vm2`. This includes
the transpiler, ts simulator, and anything required in ACIR.

Note that ACIR and noir's black box still use [the
flags](https://github.com/AztecProtocol/aztec-packages/blob/b30fe8f401d7af45148071924b22b3f377750eaf/barretenberg/cpp/src/barretenberg/dsl/acir_format/ec_operations.hpp#L34)
and represent points by a[ triple of
elements.](https://github.com/noir-lang/noir/blob/bc4a37e2994ebc7d44ae98be81e18606b2231c61/acvm-repo/bn254_blackbox_solver/src/embedded_curve_ops.rs#L98)
Since this touches both private and public execution, I think it's out
of scope of this task to update these.

Will partially close [Foundation AVM Issue
19](https://linear.app/aztec-foundation/issue/AVM-19/) (the previous PR
with AVM changes will close the initial portion)

---

Stack:
- #22745
- #22564
- #22921
- #22795
- #22945
- `mw/avm-rem-inf-opcode-ecadd-ext` <-- here
MirandaWood added a commit that referenced this pull request May 16, 2026
…#22921)

This branch solely contains the changes needed to remove the
`is_infinite` flag from our `StandardAffinePoint` C++ wrapper. Now, we
check whether `x` and `y` are zero to assign an `inf` underlying point.

Will close [Foundation AVM Issue
17](https://linear.app/aztec-foundation/issue/AVM-17/remove-is-inf-flag-from-avms-standardaffinepoint)

---

Stack:

- #22745
- #22564
- `mw/avm-rem-inf-point-wrapper` <-- here
- #22795
- #22945
- #23031
MirandaWood added a commit that referenced this pull request May 16, 2026
…y) (#22795)

This branch includes the changes to remove the `is_infinite` flag from
our point representation and conceptually treating a point as infinite
iff its coordinates are `(0, 0)`.

It only contains logic changes within the AVM for the above and does not
touch the opcode - this is in a lower PR - so the **CI will probably
fail**.

Will close [Foundation AVM Issue
18](https://linear.app/aztec-foundation/issue/AVM-18/remove-is-inf-flag-from-resulting-ec-points-in-avm-circuits)

---

Stack:
- #22745
- #22564
- #22921
- `mw/avm-explore-remove-is-inf` <-- here
- #22945
- #23031
MirandaWood added a commit that referenced this pull request May 16, 2026
…#22945)

This branch includes the changes to remove the `is_infinite` flags from
the ECADD opcode fn signature. The actual EC logic changes come above
this PR in the stack, and any changes outside the AVM will be below.

For ease of review, I've separated into commits:

- **feat: remove inf flags from ecadd opcode - ec flow only** Isolated
to the EC flow only (does not change registers so non avm tests will
fail)
- f**eat: rem infs from fuzzer (only gadget fuzzer tested)** Isolated
fixes to get the fuzzer(s) compiling

Will partially close [Foundation AVM Issue
19](https://linear.app/aztec-foundation/issue/AVM-19/) (the following PR

Note that the opcode mismatches that in ts so **CI will fail** until

---

Stack:
- #22745
- #22564
- #22921
- #22795
- `mw/avm-rem-inf-opcode-ecadd` <-- here
- #23031
MirandaWood added a commit that referenced this pull request May 16, 2026
… AVM only) (#23031)

This branch includes the changes to remove the `is_infinite` flags from
the ECADD opcode fn signature which reside outside `vm2`. This includes
the transpiler, ts simulator, and anything required in ACIR.

Note that ACIR and noir's black box still use [the
flags](https://github.com/AztecProtocol/aztec-packages/blob/b30fe8f401d7af45148071924b22b3f377750eaf/barretenberg/cpp/src/barretenberg/dsl/acir_format/ec_operations.hpp#L34)
and represent points by a[ triple of
elements.](https://github.com/noir-lang/noir/blob/bc4a37e2994ebc7d44ae98be81e18606b2231c61/acvm-repo/bn254_blackbox_solver/src/embedded_curve_ops.rs#L98)
Since this touches both private and public execution, I think it's out
of scope of this task to update these.

Will partially close [Foundation AVM Issue
19](https://linear.app/aztec-foundation/issue/AVM-19/) (the previous PR
with AVM changes will close the initial portion)

---

Stack:
- #22745
- #22564
- #22921
- #22795
- #22945
- `mw/avm-rem-inf-opcode-ecadd-ext` <-- here
MirandaWood added a commit that referenced this pull request May 18, 2026
…#22921)

This branch solely contains the changes needed to remove the
`is_infinite` flag from our `StandardAffinePoint` C++ wrapper. Now, we
check whether `x` and `y` are zero to assign an `inf` underlying point.

Will close [Foundation AVM Issue
17](https://linear.app/aztec-foundation/issue/AVM-17/remove-is-inf-flag-from-avms-standardaffinepoint)

---

Stack:

- #22745
- #22564
- `mw/avm-rem-inf-point-wrapper` <-- here
- #22795
- #22945
- #23031
MirandaWood added a commit that referenced this pull request May 18, 2026
…y) (#22795)

This branch includes the changes to remove the `is_infinite` flag from
our point representation and conceptually treating a point as infinite
iff its coordinates are `(0, 0)`.

It only contains logic changes within the AVM for the above and does not
touch the opcode - this is in a lower PR - so the **CI will probably
fail**.

Will close [Foundation AVM Issue
18](https://linear.app/aztec-foundation/issue/AVM-18/remove-is-inf-flag-from-resulting-ec-points-in-avm-circuits)

---

Stack:
- #22745
- #22564
- #22921
- `mw/avm-explore-remove-is-inf` <-- here
- #22945
- #23031
MirandaWood added a commit that referenced this pull request May 18, 2026
…#22945)

This branch includes the changes to remove the `is_infinite` flags from
the ECADD opcode fn signature. The actual EC logic changes come above
this PR in the stack, and any changes outside the AVM will be below.

For ease of review, I've separated into commits:

- **feat: remove inf flags from ecadd opcode - ec flow only** Isolated
to the EC flow only (does not change registers so non avm tests will
fail)
- f**eat: rem infs from fuzzer (only gadget fuzzer tested)** Isolated
fixes to get the fuzzer(s) compiling

Will partially close [Foundation AVM Issue
19](https://linear.app/aztec-foundation/issue/AVM-19/) (the following PR

Note that the opcode mismatches that in ts so **CI will fail** until

---

Stack:
- #22745
- #22564
- #22921
- #22795
- `mw/avm-rem-inf-opcode-ecadd` <-- here
- #23031
MirandaWood added a commit that referenced this pull request May 18, 2026
… AVM only) (#23031)

This branch includes the changes to remove the `is_infinite` flags from
the ECADD opcode fn signature which reside outside `vm2`. This includes
the transpiler, ts simulator, and anything required in ACIR.

Note that ACIR and noir's black box still use [the
flags](https://github.com/AztecProtocol/aztec-packages/blob/b30fe8f401d7af45148071924b22b3f377750eaf/barretenberg/cpp/src/barretenberg/dsl/acir_format/ec_operations.hpp#L34)
and represent points by a[ triple of
elements.](https://github.com/noir-lang/noir/blob/bc4a37e2994ebc7d44ae98be81e18606b2231c61/acvm-repo/bn254_blackbox_solver/src/embedded_curve_ops.rs#L98)
Since this touches both private and public execution, I think it's out
of scope of this task to update these.

Will partially close [Foundation AVM Issue
19](https://linear.app/aztec-foundation/issue/AVM-19/) (the previous PR
with AVM changes will close the initial portion)

---

Stack:
- #22745
- #22564
- #22921
- #22795
- #22945
- `mw/avm-rem-inf-opcode-ecadd-ext` <-- here
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants