feat: add RPC endpoints to manipulate time by benesjan · Pull Request #22084 · AztecProtocol/aztec-packages

benesjan · 2026-03-27T03:17:10Z

The goal of this PR is to give devs an easy way to manipulate L2 block time in test environments. Since this only for testing we don't want to clutter AztecNodeService with too much of this functionality. For this reason the following approach was implemented:

On the node we expose only new mineBlock function on a new AztecNodeDebug interface and this endpoint is functional only in test environment,
the actual time manipulation happens by warping the time on anvil - we use EthCheatCodes class for this,
once the time is warped on L1, then the next mined block on L2 will have the warped timestamp because we use AnvilTestWatcher in those environments - this automatically updates inner sequencer's DateProvider based on Anvil's time (AnvilTestWatcher was mentioned by Palla, is there a risk of us not using in some test env?)
to have good devex I introduced new functionality on the CheatCodes class that performs this L1 warping and L2 mining automatically.

`AZTEC_NODE_DEBUG` env var

The debug endpoint (mineBlock) is gated behind a new AZTEC_NODE_DEBUG env var / --node-debug CLI flag. When set, it exposes the AztecNodeDebug interface on the main RPC port.

--local-network auto-enables it — devs running aztec start --local-network get mineBlock by default without extra config.
Standalone --node requires explicit opt-in via AZTEC_NODE_DEBUG=true or --node-debug.

Composed e2e test

The e2e_cheat_codes test was rewritten as a composed test (src/composed/e2e_cheat_codes.test.ts) that runs against a remote local-network node via RPC, rather than spinning up an in-process node. This validates that the time manipulation cheat codes work end-to-end over the JSON-RPC boundary.

Why we need `mineBlock` on node?

Note that I tried to minimize the impact on the node but we need to add the mineBlock method on the node because we need to trigger block getting mined and we cannot get a hold of the SequencerClient in all the places where we want to use this functionality - this is typically on Sandbox when we connect to the node via JSON-RPC (and hence we need to have this exposed on that RPC).

Closes F-407

Note for me

Ping Hao here once this is merged

benesjan · 2026-03-30T03:37:13Z

feat: add RPC endpoints to manipulate time #22084 👈 (View in Graphite)
merge-train/fairies

This stack of pull requests is managed by Graphite. Learn more about stacking.

benesjan · 2026-04-02T13:42:00Z

    signalHandlers.push(stop);
    services.node = [node, AztecNodeApiSchema];
    adminServices.node = [node, AztecNodeAdminApiSchema];
+    adminServices.nodeDebug = [node, AztecNodeDebugApiSchema];


This code is quite foreign to me so I asked this to AI:

so this seems reasonable.

If the debug interface got accidentally exposed in prod in its current form then there would not be much damage to do as the function would error out with the warping methods but anyway there is a danger of us adding more powerful methods on the interface, then accidentally exposing this in prod and then bad things happening.

Do you think we should somehow guardrail this more such that via some code changes we don't accidentally expose this?

Yeah, we introduced the idea of a debug API recently to support testing. I would only create add this schema if a particular env var is turned on (e.g. AZTEC_DEBUG=true)

alexghr · 2026-04-09T14:36:19Z

    signalHandlers.push(stop);
    services.node = [node, AztecNodeApiSchema];
    adminServices.node = [node, AztecNodeAdminApiSchema];
+    adminServices.nodeDebug = [node, AztecNodeDebugApiSchema];


Yeah, we introduced the idea of a debug API recently to support testing. I would only create add this schema if a particular env var is turned on (e.g. AZTEC_DEBUG=true)

benesjan · 2026-04-10T07:55:33Z

-    --local-network.noPXE                                                                                                                        ($NO_PXE)
-          Do not expose PXE service on local network start


The NO_PXE flag was archaic and no longer used (pxe is never exposed as standalone service) so I sneaked this change here.

benesjan · 2026-04-10T07:56:36Z

    signalHandlers.push(stop);
    services.node = [node, AztecNodeApiSchema];
    adminServices.node = [node, AztecNodeAdminApiSchema];
+    services.nodeDebug = [node, AztecNodeDebugApiSchema];


In local network mode we automatically expose this so that people don't need to go through the hassle of setting the env var in test environments.

benesjan · 2026-04-10T07:56:58Z

      const { startNode } = await import('./cmds/start_node.js');
      const networkName = getActiveNetworkName(options.network);
      ({ config } = await startNode(options, signalHandlers, services, adminServices, userLog, networkName));
+      if (options.nodeDebug && services.node) {


In the non-local-network setting the env var has to be explicitly set.

AztecBot · 2026-04-10T09:38:57Z

❌ Failed to cherry-pick to v4-next due to conflicts. (🤖) View backport run.

…o v4-next (#22460)

BEGIN_COMMIT_OVERRIDE fix: passing in user call info from wallet (#21937) feat: add RPC endpoints to manipulate time (#22084) END_COMMIT_OVERRIDE

…23213) ## Summary Fixes the merge-queue failure in `e2e_blacklist_token_contract/shielding` ([CI run](http://ci.aztec-labs.com/d5485e6652b3f32a)) where every test fails in `applyMint` with `Invalid tx: Invalid expiration timestamp`. ## Root cause `warpL2TimeAtLeastTo` (introduced in #22084) calls `eth.warp` followed by `node.mineBlock()`. The sequencer's polling loop captures `nowSeconds`/`slot` at the top of each `work()` cycle. An in-flight cycle that started just before the warp will mine an L2 block at the *pre-warp* slot — L1 sync prunes that block from the canonical chain, but it lingers in local world state and the PXE anchors subsequent txs against it. With `MAX_TX_LIFETIME == CHANGE_ROLES_DELAY == 86400s`, the resulting `expiration_timestamp` lands exactly on the post-warp slot boundary and the validator rejects the tx as soon as the wall-clock crosses to the next slot. ## Fix After `eth.warp`, retry `mineBlock` until the latest L2 block's slot is at or past the slot corresponding to the warped timestamp. The first `mineBlock` may return a stale block produced by an in-flight cycle; the next triggers a fresh sequencer cycle that reads the post-warp time and builds a block at the post-warp slot. Subsequent txs then anchor against a fresh block whose `expiration_timestamp` is well in the future. The signature of `warpL2TimeAtLeastTo`/`warpL2TimeAtLeastBy` widens from `AztecNodeDebug` to `AztecNode & AztecNodeDebug` so we can read the latest block via `getBlockData('latest')`. All current callers already type their node as the intersection. This re-applies the diagnosis from the prior #22796 (which never merged), adapted to the current `getBlockData('latest')` API. Full analysis: https://gist.github.com/AztecBot/67815cbe3c3f853d97ec3345dfb0c985 ## Test plan - `e2e_blacklist_token_contract/shielding` (originally failing) - `e2e_blacklist_token_contract/{access_control,burn,minting,transfer_*,unshielding}` — share `applyBaseSetup` → `crossTimestampOfChange` - `e2e_contract_updates` - `composed/e2e_cheat_codes` (verifies the type-widening change still resolves the methods correctly) ClaudeBox log: https://claudebox.work/s/28594b4dc64f1cd0?run=1

benesjan marked this pull request as draft March 27, 2026 03:31

benesjan mentioned this pull request Mar 27, 2026

sketching timetravel rpc #22008

Closed

Base automatically changed from merge-train/fairies to next March 27, 2026 07:58

benesjan changed the base branch from next to graphite-base/22084 March 30, 2026 03:36

benesjan force-pushed the jan/f-407-add-an-rpc-endpoint-to-manipulate-time branch from 0d144cb to 9d67fa9 Compare March 30, 2026 03:36

benesjan changed the base branch from graphite-base/22084 to merge-train/fairies March 30, 2026 03:36

benesjan commented Mar 30, 2026

View reviewed changes

Comment thread yarn-project/yarn.lock

benesjan force-pushed the jan/f-407-add-an-rpc-endpoint-to-manipulate-time branch from 51b33a2 to 5d00440 Compare March 30, 2026 13:42

benesjan marked this pull request as ready for review March 30, 2026 13:42

nventuro added the backport-to-v4-next label Mar 30, 2026

nventuro reviewed Mar 30, 2026

View reviewed changes

Comment thread yarn-project/stdlib/src/interfaces/aztec-node-admin.ts Outdated

benesjan marked this pull request as draft March 31, 2026 01:36

benesjan force-pushed the jan/f-407-add-an-rpc-endpoint-to-manipulate-time branch 2 times, most recently from c7c7580 to b715407 Compare April 2, 2026 10:53

benesjan commented Apr 2, 2026

View reviewed changes

benesjan force-pushed the jan/f-407-add-an-rpc-endpoint-to-manipulate-time branch from b715407 to 061ad4f Compare April 9, 2026 03:55

benesjan commented Apr 9, 2026

View reviewed changes

Comment thread yarn-project/aztec/src/testing/cheat_codes.ts

benesjan added the ci-draft Run CI on draft PRs. label Apr 9, 2026

benesjan force-pushed the jan/f-407-add-an-rpc-endpoint-to-manipulate-time branch 2 times, most recently from 0749b9f to fcfc5d6 Compare April 9, 2026 13:43

benesjan marked this pull request as ready for review April 9, 2026 14:11

benesjan force-pushed the jan/f-407-add-an-rpc-endpoint-to-manipulate-time branch from 77c7a7c to 41bb0d0 Compare April 9, 2026 14:11

benesjan requested a review from alexghr April 9, 2026 14:20

alexghr reviewed Apr 9, 2026

View reviewed changes

mverzilli reviewed Apr 9, 2026

View reviewed changes

Comment thread yarn-project/aztec-node/src/aztec-node/server.ts

mverzilli reviewed Apr 9, 2026

View reviewed changes

Comment thread yarn-project/aztec/src/testing/cheat_codes.ts

nventuro and others added 3 commits April 10, 2026 03:59

sketching timetravel rpc

8ec6f3b

compilation fixes and readability improvements

62074c1

wip

3c0a6f1

better test naming

b4ebb21

benesjan marked this pull request as draft April 10, 2026 06:00

benesjan removed the ci-draft Run CI on draft PRs. label Apr 10, 2026

more reasonable timeout

3ee69b3

benesjan force-pushed the jan/f-407-add-an-rpc-endpoint-to-manipulate-time branch from 41bb0d0 to 3ee69b3 Compare April 10, 2026 06:06

benesjan added 5 commits April 10, 2026 07:06

introducing AZTEC_NODE_DEBUG + making e2e_cheat_codes test composed

7c45ec7

test setup fix

9ea3af8

improved tests

afcaecb

updated CLI reference

9d3e66e

dropping stale no_pxe flag

670e5c1

benesjan commented Apr 10, 2026

View reviewed changes

cleanup

240322c

benesjan marked this pull request as ready for review April 10, 2026 08:06

benesjan requested a review from spypsy April 10, 2026 08:34

spypsy approved these changes Apr 10, 2026

View reviewed changes

benesjan merged commit 53b278e into merge-train/fairies Apr 10, 2026
19 checks passed

benesjan deleted the jan/f-407-add-an-rpc-endpoint-to-manipulate-time branch April 10, 2026 09:37

AztecBot mentioned this pull request Apr 10, 2026

feat: merge-train/fairies #22456

Merged

AztecBot pushed a commit that referenced this pull request Apr 10, 2026

cherry-pick: feat: add RPC endpoints to manipulate time (#22084)

738611c

AztecBot mentioned this pull request Apr 10, 2026

chore: backport #22084 (feat: add RPC endpoints to manipulate time) to v4-next #22460

Merged

benesjan added a commit that referenced this pull request Apr 10, 2026

chore: backport #22084 (feat: add RPC endpoints to manipulate time) t…

bccebf9

…o v4-next (#22460)

github-merge-queue Bot pushed a commit that referenced this pull request Apr 10, 2026

feat: merge-train/fairies (#22456)

378f0d2

BEGIN_COMMIT_OVERRIDE fix: passing in user call info from wallet (#21937) feat: add RPC endpoints to manipulate time (#22084) END_COMMIT_OVERRIDE

AztecBot mentioned this pull request Apr 11, 2026

fix: stabilize blacklist token shielding test after time warp #22487

Closed

2 tasks

critesjosh pushed a commit that referenced this pull request Apr 14, 2026

feat: add RPC endpoints to manipulate time (#22084)

b1d9897

AztecBot mentioned this pull request Apr 27, 2026

fix(cheat-codes): wait for post-warp L2 block in warpL2TimeAtLeastTo #22796

Closed

AztecBot mentioned this pull request May 12, 2026

fix(cheat-codes): wait for post-warp L2 block in warpL2TimeAtLeastTo #23213

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: add RPC endpoints to manipulate time#22084

feat: add RPC endpoints to manipulate time#22084
benesjan merged 22 commits into
merge-train/fairiesfrom
jan/f-407-add-an-rpc-endpoint-to-manipulate-time

benesjan commented Mar 27, 2026 •

edited

Loading

Uh oh!

benesjan commented Mar 30, 2026

Uh oh!

Uh oh!

Uh oh!

benesjan Apr 2, 2026

Uh oh!

alexghr Apr 9, 2026

Uh oh!

Uh oh!

alexghr Apr 9, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

benesjan Apr 10, 2026

Uh oh!

benesjan Apr 10, 2026

Uh oh!

benesjan Apr 10, 2026

Uh oh!

Uh oh!

AztecBot commented Apr 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

		--local-network.noPXE ($NO_PXE)
		Do not expose PXE service on local network start

Conversation

benesjan commented Mar 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

AZTEC_NODE_DEBUG env var

Composed e2e test

Why we need mineBlock on node?

Note for me

Uh oh!

benesjan commented Mar 30, 2026

Uh oh!

Uh oh!

Uh oh!

benesjan Apr 2, 2026

Choose a reason for hiding this comment

Uh oh!

alexghr Apr 9, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

alexghr Apr 9, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

benesjan Apr 10, 2026

Choose a reason for hiding this comment

Uh oh!

benesjan Apr 10, 2026

Choose a reason for hiding this comment

Uh oh!

benesjan Apr 10, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

AztecBot commented Apr 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

benesjan commented Mar 27, 2026 •

edited

Loading

`AZTEC_NODE_DEBUG` env var

Why we need `mineBlock` on node?