Skip to content

feat: allow custom addresses to be prefunded with fee juice in local network#21000

Merged
mverzilli merged 1 commit intomerge-train/fairiesfrom
martin/allow-custom-prefunded-addresses
Mar 2, 2026
Merged

feat: allow custom addresses to be prefunded with fee juice in local network#21000
mverzilli merged 1 commit intomerge-train/fairiesfrom
martin/allow-custom-prefunded-addresses

Conversation

@mverzilli
Copy link
Contributor

@mverzilli mverzilli commented Mar 2, 2026

Closes F-282 (see #19890)

@mverzilli mverzilli requested a review from spalladino March 2, 2026 13:38
@mverzilli mverzilli changed the title allow custom addresses to be prefunded with fee juice in local network feat: allow custom addresses to be prefunded with fee juice in local network Mar 2, 2026
const prefundAddresses = (aztecNodeConfig.prefundAddresses ?? []).map(a => AztecAddress.fromString(a));
const fundedAddresses = [
...initialAccounts.map(a => a.address),
...(initialAccounts.length ? [bananaFPC, sponsoredFPC] : []),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The bananaFPC is still a think when users start our local network? Wow.

Comment on lines +264 to +273
prefundAddresses: {
env: 'PREFUND_ADDRESSES',
description: 'Comma-separated list of Aztec addresses to prefund with fee juice at genesis.',
parseEnv: (val: string) =>
val
.split(',')
.map(a => a.trim())
.filter(a => a.length > 0),
defaultValue: [],
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd rather make this a list of AztecAddress rather than strings, and have the AztecAddress.fromString run as part of the parseEnv. But it's just a nit. And I don't recall if the package dependencies will allow you to do it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'd end up with circular deps indeed (without further refactoring)

Comment on lines +40 to +49
prefundAddresses: {
env: 'PREFUND_ADDRESSES',
description: 'Comma-separated list of Aztec addresses to prefund with fee juice at genesis.',
parseEnv: (val: string) =>
val
.split(',')
.map(a => a.trim())
.filter(a => a.length > 0),
defaultValue: [],
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I hate that we have duplicate config across the board.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

;(

@mverzilli mverzilli merged commit 173e732 into merge-train/fairies Mar 2, 2026
28 of 35 checks passed
@mverzilli mverzilli deleted the martin/allow-custom-prefunded-addresses branch March 2, 2026 15:43
@AztecBot
Copy link
Collaborator

AztecBot commented Mar 2, 2026

❌ Failed to cherry-pick to v4 due to conflicts. Dispatching ClaudeBox to resolve. View backport run.

AztecBot added a commit that referenced this pull request Mar 2, 2026
…network (backport #21000)

Cherry-pick of PR #21000 via `git apply --reject`.
Hunk #1 of start_node.ts rejected (import context mismatch between next and v4).
AztecBot added a commit that referenced this pull request Mar 2, 2026
…network (backport #21000)

Cherry-pick of PR #21000 with conflicts.
start_node.ts has conflict markers where the AztecAddress import
could not be cleanly applied (import context differs between next and v4).
ludamad pushed a commit that referenced this pull request Mar 2, 2026
…network (backport #21000) (#21004)

## Summary
Backport of #21000
to v4.

### Commit 1: Cherry-pick with conflict markers
Applied PR #21000 diff to v4. The `start_node.ts` import section has
conflict markers where the `AztecAddress` import could not be cleanly
applied (the surrounding import context differs between `next` and `v4`
— v4 has additional imports like `RegistryContract`, `sleep`,
`EthAddress` that were removed on `next`).

### Commit 2: Resolve conflict
Added `import { AztecAddress } from '@aztec/stdlib/aztec-address'` in
the correct location for v4 and removed the conflict markers.

Original PR by @mverzilli.
mverzilli pushed a commit that referenced this pull request Mar 2, 2026
…network (backport #21000) (#21004)

## Summary
Backport of #21000
to v4.

### Commit 1: Cherry-pick with conflict markers
Applied PR #21000 diff to v4. The `start_node.ts` import section has
conflict markers where the `AztecAddress` import could not be cleanly
applied (the surrounding import context differs between `next` and `v4`
— v4 has additional imports like `RegistryContract`, `sleep`,
`EthAddress` that were removed on `next`).

### Commit 2: Resolve conflict
Added `import { AztecAddress } from '@aztec/stdlib/aztec-address'` in
the correct location for v4 and removed the conflict markers.

Original PR by @mverzilli.
ludamad added a commit that referenced this pull request Mar 3, 2026
BEGIN_COMMIT_OVERRIDE
fix(aztec-nr): account for AES PKCS#7 padding in message plaintext
length (#20840)
feat: remove epk sign from message payload (#20926)
chore: increase mainnet local ejection threshold to 190k (#20884)
feat: add pinned-build support for protocol contracts in noir-contracts
(v4) (#20982)
fix!: undo bad fix (#20987)
chore: backport #20967 to v4 (metric on how many epochs validator has
been on committee) (#20989)
chore(sequencer): e2e tests for invalid signature recovery in checkpoint
attestations (#20971)
feat: allow custom addresses to be prefunded with fee juice in local
network (backport #21000) (#21004)
chore: increase max fee bots use in tests (#20867)
END_COMMIT_OVERRIDE
github-merge-queue bot pushed a commit that referenced this pull request Mar 3, 2026
BEGIN_COMMIT_OVERRIDE
feat: allow custom addresses to be prefunded with fee juice in local
network (#21000)
docs(claude): add Noir early return idiom to CLAUDE.md (#21021)
feat: add compile-time size check for events and error code links
(#21024)
feat: use warn_log_format for discarded messages (#21053)
END_COMMIT_OVERRIDE
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants