chore(nightly): bump to v4.4.0-nightly.20260522

[AztecBot]

Nightly bump: v4.3.0-rc.1 -> v4.4.0-nightly.20260522

Automated nightly bump driven by the upstream tagging workflow.

• Source run: https://github.com/AztecProtocol/aztec-packages/actions/runs/26325258404 (nightly-release-tag-v4-next.yml, conclusion success, head_sha 7a5e050e555d85e0fe5d435b41cb681e8a68e5fa)
• New nightly: v4.4.0-nightly.20260522 (latest @aztec/aztec.js nightly on npm)

What changed

• scripts/update.js rewrote every workspace package.json (@aztec/* deps) and every Nargo.toml git tag to v4.4.0-nightly.20260522, refreshed yarn.lock, and recompiled the Aztec contracts.
• apps/swap/src/config/networks/testnet.json updated with the freshly deployed testnet contract addresses and subscriptionFPC signups.

Verification (success path — no migration fixes needed)

• yarn build passed
• yarn test passed (10/10 turbo tasks, e2e 6/6)
• yarn setup:testnet passed

Testnet deployment (yarn setup:testnet)

Deployed against https://rpc.testnet.aztec-labs.com (chain 11155111, rollup version 4127419662):

Contract	Address
Swap admin (deployer)	0x26362fead2a62806e67fce1b4dc855cb5c0640d4299b7b40a2e61bc97f4a5db4
GoCoin (Token)	0x0c44d6b3003e072ed4fb2c80a14e24505d11da4d9b9f236fef6a5e703c6486c0
GoCoinPremium (Token)	0x12be02aa3cd27fad3016301010aff7665caabd2e536fd113f3f759557cb2b8d6
AMM	0x290ac3143fece078212f539f71995d68a3cf34892c7356ee4d006aaa0c1e9e5a
Liquidity token	0x2db93f553acb5a2ad0dcc6413c3da518d5b9c39b6ffc1e1f86de4192ba8369d7
ProofOfPassword	0x0e6342a6f4b2129c40109d62c87e139698b006ed7ec40d8d8366649815ea4065
SubscriptionFPC	0x23d84dcb46d5a998e8f9897f8a0aba70ae30c1754a329152b8ccb659973a1765
FPC admin	0x0000b0ce547a78c00ab2e5de19efe9afced73d2864293efca37adf07670d301e
SponsoredFPC (canonical)	0x08b888c4be63ed67f61a622fdd013ea028326bac22a8982a3b5a7e9ec62f765b

FPC signups registered for: pop.check_password_and_mint, amm.swap_tokens_for_exact_tokens_from, goCoin.transfer_in_private_deliver_offchain, goCoinPremium.transfer_in_private_deliver_offchain.

Notes

• First testnet deploy attempt failed at the FPC step with Tx dropped by P2P node — transient testnet issue, not a code regression. Retrying produced the addresses above.
• The e2e fpc-setup spec also flaked once before tests ran clean against a fresh .state/ — root cause was stale local-network checkpoints from an earlier attempt, no source change needed.

Commit shape: single commit (success path).

---

Created by claudebox · group: aztec-kit-nightly