Skip to content

Commit

Permalink
chore: fix migration notes (#7133)
Browse files Browse the repository at this point in the history
Moves a breaking change into the next release as opposed to the former
release
This happens every so often when a PR was started in the previous
release but PR gets merged after the sandbox release happens
  • Loading branch information
rahul-kothari authored Jun 20, 2024
1 parent cdd1cbd commit 14917d3
Showing 1 changed file with 6 additions and 7 deletions.
13 changes: 6 additions & 7 deletions docs/docs/migration_notes.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,13 +61,6 @@ These changes were done because having the note hash exposed allowed us to not h
+ }
```


## 0.43.0

### [Aztec.nr] break `token.transfer()` into `transfer` and `transferFrom`
Earlier we had just one function - `transfer()` which used authwits to handle the case where a contract/user wants to transfer funds on behalf of another user.
To reduce circuit sizes and proof times, we are breaking up `transfer` and introducing a dedicated `transferFrom()` function like in the ERC20 standard.

### [Aztec.nr] `note_getter` returns `BoundedVec`

The `get_notes` and `view_notes` function no longer return an array of options (i.e. `[Option<Note>, N_NOTES]`) but instead a `BoundedVec<Note, N_NOTES>`. This better conveys the useful property the old array had of having all notes collapsed at the beginning of the array, which allows for powerful optimizations and gate count reduction when setting the `options.limit` value.
Expand Down Expand Up @@ -96,6 +89,12 @@ To further reduce gate count, you can iterate over `options.limit` instead of `m
+ for i in 0..options.limit {
```

## 0.43.0

### [Aztec.nr] break `token.transfer()` into `transfer` and `transferFrom`
Earlier we had just one function - `transfer()` which used authwits to handle the case where a contract/user wants to transfer funds on behalf of another user.
To reduce circuit sizes and proof times, we are breaking up `transfer` and introducing a dedicated `transferFrom()` function like in the ERC20 standard.

### [Aztec.nr] `options.limit` has to be constant

The `limit` parameter in `NoteGetterOptions` and `NoteViewerOptions` is now required to be a compile-time constant. This allows performing loops over this value, which leads to reduced circuit gate counts when setting a `limit` value.
Expand Down

0 comments on commit 14917d3

Please sign in to comment.