chore(deps-dev): bump the aztec-dependencies group with 11 updates by dependabot[bot] · Pull Request #158 · defi-wonderland/aztec-fee-payment

dependabot · 2026-06-08T09:15:13Z

Bumps the aztec-dependencies group with 11 updates:

Package	From	To
@aztec/accounts	`4.3.0`	`4.3.1`
@aztec/aztec.js	`4.3.0`	`4.3.1`
@aztec/constants	`4.3.0`	`4.3.1`
@aztec/entrypoints	`4.3.0`	`4.3.1`
@aztec/ethereum	`4.3.0`	`4.3.1`
@aztec/foundation	`4.3.0`	`4.3.1`
@aztec/noir-contracts.js	`4.3.0`	`4.3.1`
@aztec/protocol-contracts	`4.3.0`	`4.3.1`
@aztec/pxe	`4.3.0`	`4.3.1`
@aztec/stdlib	`4.3.0`	`4.3.1`
@aztec/wallets	`4.3.0`	`4.3.1`

Updates @aztec/accounts from 4.3.0 to 4.3.1

Release notes

Sourced from @aztec/accounts's releases.

v4.3.1

Date: 2026-06-04 Tag: v4.3.1 Base: v4.3.0 Range: v4.3.0..v4.3.1 — three bug fixes

Summary

v4.3.1 is a recommended patch on top of v4.3.0. It ships three bug fixes: a partial-epoch-proof failure mode in the prover-node when the prior epoch is still pending, a block-stream tips-store bug where finalized drifting ahead of proven could orphan still-live block data, and a release-tooling fix that re-stamps the actual aztec_version into published noir-contracts artifacts (v4.3.0 shipped them with "dev").

All sequencers should upgrade to v4.3.1: #23505 closes a block-stream wedge that, under unusual finalization ordering, could stall attestations and lead to slashable downtime. Provers running partial epoch proofs should also upgrade — #23457 fixes the spurious failures when the previous epoch is still pending.

No breaking changes. No migration steps required.

What contract developers should care about

Published contract artifacts now carry the correct aztec_version (#23851, backport of #23470): The v4.3.0 release of @aztec/noir-contracts.js shipped artifact JSONs with aztec_version: "dev" baked in (REF_NAME wasn't being populated during the release-image build). From v4.3.1 onward, artifact JSONs are stamped with the actual release version, so any tooling that asserts artifact-version compatibility against the installed aztec version will work correctly.

What node operators should care about

Prover-node — partial epoch proofs no longer race the previous epoch (#23457): The prover-node would attempt to generate a partial proof for epoch N while epoch N−1 was still pending, producing spurious failures. It now waits for the previous epoch to be proven before kicking off a partial proof. If you've been seeing intermittent partial-proof errors on testnet, this is the fix.

L2 tips store — finalized no longer orphans live block data (#23505): handleChainFinalized previously assumed the finalized tip was always the oldest live tip, and deleted block hashes / checkpoints below it. Under conditions where finalized drifted ahead of proven, this orphaned data referenced by a still-live tip and locked the block stream into an error loop. The patch caps every deletion bound at the lowest live tip (proposed / checkpointed / proven).

What changed since v4.3.0

Three PRs — all bug fixes, no features:

#23457 — fix(prover): wait for previous epoch to be proven

#23505 — chore(backport-to-v4): fix(stdlib): guard tip-store finalize against deleting live tips

#23851 — chore(backport-to-v4): fix: released contract artifact aztec version (backport of #23470)

Reference

v4.3.0 release notes — full breaking-change list, detailed highlights

CHANGELOG.md — complete categorized commit list

Commits

22b8ee1 chore(v4): add release-image fix to v4.3.1 changelog (#23854)
a22a5d3 chore(v4): add release-image fix to v4.3.1 changelog
7d80b2d chore(backport-to-v4): fix: released contract artifact aztec version (#23470)...
a8a3940 fix: released contract artifact aztec version (#23470)
9c4598b chore(v4): release 4.3.1 (#23826)
6f0b815 chore(v4): release 4.3.1
bdc777b chore(backport-to-v4): fix(stdlib): guard tip-store finalize against deleting...
a1dedf3 chore(backport-to-v4): fix(stdlib): guard tip-store finalize against deleting...
fd89d46 fix(prover): wait for previous epoch to be proven (#23457)
4475d8c fix(prover): wait for previous epoch to be proven
See full diff in compare view

Updates @aztec/aztec.js from 4.3.0 to 4.3.1

Release notes

Sourced from @aztec/aztec.js's releases.

v4.3.1

Date: 2026-06-04 Tag: v4.3.1 Base: v4.3.0 Range: v4.3.0..v4.3.1 — three bug fixes

Summary

v4.3.1 is a recommended patch on top of v4.3.0. It ships three bug fixes: a partial-epoch-proof failure mode in the prover-node when the prior epoch is still pending, a block-stream tips-store bug where finalized drifting ahead of proven could orphan still-live block data, and a release-tooling fix that re-stamps the actual aztec_version into published noir-contracts artifacts (v4.3.0 shipped them with "dev").

All sequencers should upgrade to v4.3.1: #23505 closes a block-stream wedge that, under unusual finalization ordering, could stall attestations and lead to slashable downtime. Provers running partial epoch proofs should also upgrade — #23457 fixes the spurious failures when the previous epoch is still pending.

No breaking changes. No migration steps required.

What contract developers should care about

Published contract artifacts now carry the correct aztec_version (#23851, backport of #23470): The v4.3.0 release of @aztec/noir-contracts.js shipped artifact JSONs with aztec_version: "dev" baked in (REF_NAME wasn't being populated during the release-image build). From v4.3.1 onward, artifact JSONs are stamped with the actual release version, so any tooling that asserts artifact-version compatibility against the installed aztec version will work correctly.

What node operators should care about

Prover-node — partial epoch proofs no longer race the previous epoch (#23457): The prover-node would attempt to generate a partial proof for epoch N while epoch N−1 was still pending, producing spurious failures. It now waits for the previous epoch to be proven before kicking off a partial proof. If you've been seeing intermittent partial-proof errors on testnet, this is the fix.

L2 tips store — finalized no longer orphans live block data (#23505): handleChainFinalized previously assumed the finalized tip was always the oldest live tip, and deleted block hashes / checkpoints below it. Under conditions where finalized drifted ahead of proven, this orphaned data referenced by a still-live tip and locked the block stream into an error loop. The patch caps every deletion bound at the lowest live tip (proposed / checkpointed / proven).

What changed since v4.3.0

Three PRs — all bug fixes, no features:

#23457 — fix(prover): wait for previous epoch to be proven

#23505 — chore(backport-to-v4): fix(stdlib): guard tip-store finalize against deleting live tips

#23851 — chore(backport-to-v4): fix: released contract artifact aztec version (backport of #23470)

Reference

v4.3.0 release notes — full breaking-change list, detailed highlights

CHANGELOG.md — complete categorized commit list

Commits

22b8ee1 chore(v4): add release-image fix to v4.3.1 changelog (#23854)
a22a5d3 chore(v4): add release-image fix to v4.3.1 changelog
7d80b2d chore(backport-to-v4): fix: released contract artifact aztec version (#23470)...
a8a3940 fix: released contract artifact aztec version (#23470)
9c4598b chore(v4): release 4.3.1 (#23826)
6f0b815 chore(v4): release 4.3.1
bdc777b chore(backport-to-v4): fix(stdlib): guard tip-store finalize against deleting...
a1dedf3 chore(backport-to-v4): fix(stdlib): guard tip-store finalize against deleting...
fd89d46 fix(prover): wait for previous epoch to be proven (#23457)
4475d8c fix(prover): wait for previous epoch to be proven
See full diff in compare view

Updates @aztec/constants from 4.3.0 to 4.3.1

Updates @aztec/entrypoints from 4.3.0 to 4.3.1

Release notes

Sourced from @aztec/entrypoints's releases.

v4.3.1

Date: 2026-06-04 Tag: v4.3.1 Base: v4.3.0 Range: v4.3.0..v4.3.1 — three bug fixes

Summary

v4.3.1 is a recommended patch on top of v4.3.0. It ships three bug fixes: a partial-epoch-proof failure mode in the prover-node when the prior epoch is still pending, a block-stream tips-store bug where finalized drifting ahead of proven could orphan still-live block data, and a release-tooling fix that re-stamps the actual aztec_version into published noir-contracts artifacts (v4.3.0 shipped them with "dev").

All sequencers should upgrade to v4.3.1: #23505 closes a block-stream wedge that, under unusual finalization ordering, could stall attestations and lead to slashable downtime. Provers running partial epoch proofs should also upgrade — #23457 fixes the spurious failures when the previous epoch is still pending.

No breaking changes. No migration steps required.

What contract developers should care about

Published contract artifacts now carry the correct aztec_version (#23851, backport of #23470): The v4.3.0 release of @aztec/noir-contracts.js shipped artifact JSONs with aztec_version: "dev" baked in (REF_NAME wasn't being populated during the release-image build). From v4.3.1 onward, artifact JSONs are stamped with the actual release version, so any tooling that asserts artifact-version compatibility against the installed aztec version will work correctly.

What node operators should care about

Prover-node — partial epoch proofs no longer race the previous epoch (#23457): The prover-node would attempt to generate a partial proof for epoch N while epoch N−1 was still pending, producing spurious failures. It now waits for the previous epoch to be proven before kicking off a partial proof. If you've been seeing intermittent partial-proof errors on testnet, this is the fix.

L2 tips store — finalized no longer orphans live block data (#23505): handleChainFinalized previously assumed the finalized tip was always the oldest live tip, and deleted block hashes / checkpoints below it. Under conditions where finalized drifted ahead of proven, this orphaned data referenced by a still-live tip and locked the block stream into an error loop. The patch caps every deletion bound at the lowest live tip (proposed / checkpointed / proven).

What changed since v4.3.0

Three PRs — all bug fixes, no features:

#23457 — fix(prover): wait for previous epoch to be proven

#23505 — chore(backport-to-v4): fix(stdlib): guard tip-store finalize against deleting live tips

#23851 — chore(backport-to-v4): fix: released contract artifact aztec version (backport of #23470)

Reference

v4.3.0 release notes — full breaking-change list, detailed highlights

CHANGELOG.md — complete categorized commit list

Commits

22b8ee1 chore(v4): add release-image fix to v4.3.1 changelog (#23854)
a22a5d3 chore(v4): add release-image fix to v4.3.1 changelog
7d80b2d chore(backport-to-v4): fix: released contract artifact aztec version (#23470)...
a8a3940 fix: released contract artifact aztec version (#23470)
9c4598b chore(v4): release 4.3.1 (#23826)
6f0b815 chore(v4): release 4.3.1
bdc777b chore(backport-to-v4): fix(stdlib): guard tip-store finalize against deleting...
a1dedf3 chore(backport-to-v4): fix(stdlib): guard tip-store finalize against deleting...
fd89d46 fix(prover): wait for previous epoch to be proven (#23457)
4475d8c fix(prover): wait for previous epoch to be proven
See full diff in compare view

Updates @aztec/ethereum from 4.3.0 to 4.3.1

Updates @aztec/foundation from 4.3.0 to 4.3.1

Updates @aztec/noir-contracts.js from 4.3.0 to 4.3.1

Updates @aztec/protocol-contracts from 4.3.0 to 4.3.1

Release notes

Sourced from @aztec/protocol-contracts's releases.

v4.3.1

Date: 2026-06-04 Tag: v4.3.1 Base: v4.3.0 Range: v4.3.0..v4.3.1 — three bug fixes

Summary

v4.3.1 is a recommended patch on top of v4.3.0. It ships three bug fixes: a partial-epoch-proof failure mode in the prover-node when the prior epoch is still pending, a block-stream tips-store bug where finalized drifting ahead of proven could orphan still-live block data, and a release-tooling fix that re-stamps the actual aztec_version into published noir-contracts artifacts (v4.3.0 shipped them with "dev").

All sequencers should upgrade to v4.3.1: #23505 closes a block-stream wedge that, under unusual finalization ordering, could stall attestations and lead to slashable downtime. Provers running partial epoch proofs should also upgrade — #23457 fixes the spurious failures when the previous epoch is still pending.

No breaking changes. No migration steps required.

What contract developers should care about

Published contract artifacts now carry the correct aztec_version (#23851, backport of #23470): The v4.3.0 release of @aztec/noir-contracts.js shipped artifact JSONs with aztec_version: "dev" baked in (REF_NAME wasn't being populated during the release-image build). From v4.3.1 onward, artifact JSONs are stamped with the actual release version, so any tooling that asserts artifact-version compatibility against the installed aztec version will work correctly.

What node operators should care about

Prover-node — partial epoch proofs no longer race the previous epoch (#23457): The prover-node would attempt to generate a partial proof for epoch N while epoch N−1 was still pending, producing spurious failures. It now waits for the previous epoch to be proven before kicking off a partial proof. If you've been seeing intermittent partial-proof errors on testnet, this is the fix.

L2 tips store — finalized no longer orphans live block data (#23505): handleChainFinalized previously assumed the finalized tip was always the oldest live tip, and deleted block hashes / checkpoints below it. Under conditions where finalized drifted ahead of proven, this orphaned data referenced by a still-live tip and locked the block stream into an error loop. The patch caps every deletion bound at the lowest live tip (proposed / checkpointed / proven).

What changed since v4.3.0

Three PRs — all bug fixes, no features:

#23457 — fix(prover): wait for previous epoch to be proven

#23505 — chore(backport-to-v4): fix(stdlib): guard tip-store finalize against deleting live tips

#23851 — chore(backport-to-v4): fix: released contract artifact aztec version (backport of #23470)

Reference

v4.3.0 release notes — full breaking-change list, detailed highlights

CHANGELOG.md — complete categorized commit list

Commits

22b8ee1 chore(v4): add release-image fix to v4.3.1 changelog (#23854)
a22a5d3 chore(v4): add release-image fix to v4.3.1 changelog
7d80b2d chore(backport-to-v4): fix: released contract artifact aztec version (#23470)...
a8a3940 fix: released contract artifact aztec version (#23470)
9c4598b chore(v4): release 4.3.1 (#23826)
6f0b815 chore(v4): release 4.3.1
bdc777b chore(backport-to-v4): fix(stdlib): guard tip-store finalize against deleting...
a1dedf3 chore(backport-to-v4): fix(stdlib): guard tip-store finalize against deleting...
fd89d46 fix(prover): wait for previous epoch to be proven (#23457)
4475d8c fix(prover): wait for previous epoch to be proven
See full diff in compare view

Updates @aztec/pxe from 4.3.0 to 4.3.1

Updates @aztec/stdlib from 4.3.0 to 4.3.1

Updates @aztec/wallets from 4.3.0 to 4.3.1

Release notes

Sourced from @aztec/wallets's releases.

v4.3.1

Date: 2026-06-04 Tag: v4.3.1 Base: v4.3.0 Range: v4.3.0..v4.3.1 — three bug fixes

Summary

v4.3.1 is a recommended patch on top of v4.3.0. It ships three bug fixes: a partial-epoch-proof failure mode in the prover-node when the prior epoch is still pending, a block-stream tips-store bug where finalized drifting ahead of proven could orphan still-live block data, and a release-tooling fix that re-stamps the actual aztec_version into published noir-contracts artifacts (v4.3.0 shipped them with "dev").

All sequencers should upgrade to v4.3.1: #23505 closes a block-stream wedge that, under unusual finalization ordering, could stall attestations and lead to slashable downtime. Provers running partial epoch proofs should also upgrade — #23457 fixes the spurious failures when the previous epoch is still pending.

No breaking changes. No migration steps required.

What contract developers should care about

Published contract artifacts now carry the correct aztec_version (#23851, backport of #23470): The v4.3.0 release of @aztec/noir-contracts.js shipped artifact JSONs with aztec_version: "dev" baked in (REF_NAME wasn't being populated during the release-image build). From v4.3.1 onward, artifact JSONs are stamped with the actual release version, so any tooling that asserts artifact-version compatibility against the installed aztec version will work correctly.

What node operators should care about

Prover-node — partial epoch proofs no longer race the previous epoch (#23457): The prover-node would attempt to generate a partial proof for epoch N while epoch N−1 was still pending, producing spurious failures. It now waits for the previous epoch to be proven before kicking off a partial proof. If you've been seeing intermittent partial-proof errors on testnet, this is the fix.

L2 tips store — finalized no longer orphans live block data (#23505): handleChainFinalized previously assumed the finalized tip was always the oldest live tip, and deleted block hashes / checkpoints below it. Under conditions where finalized drifted ahead of proven, this orphaned data referenced by a still-live tip and locked the block stream into an error loop. The patch caps every deletion bound at the lowest live tip (proposed / checkpointed / proven).

What changed since v4.3.0

Three PRs — all bug fixes, no features:

#23457 — fix(prover): wait for previous epoch to be proven

#23505 — chore(backport-to-v4): fix(stdlib): guard tip-store finalize against deleting live tips

#23851 — chore(backport-to-v4): fix: released contract artifact aztec version (backport of #23470)

Reference

v4.3.0 release notes — full breaking-change list, detailed highlights

CHANGELOG.md — complete categorized commit list

Commits

22b8ee1 chore(v4): add release-image fix to v4.3.1 changelog (#23854)
a22a5d3 chore(v4): add release-image fix to v4.3.1 changelog
7d80b2d chore(backport-to-v4): fix: released contract artifact aztec version (#23470)...
a8a3940 fix: released contract artifact aztec version (#23470)
9c4598b chore(v4): release 4.3.1 (#23826)
6f0b815 chore(v4): release 4.3.1
bdc777b chore(backport-to-v4): fix(stdlib): guard tip-store finalize against deleting...
a1dedf3 chore(backport-to-v4): fix(stdlib): guard tip-store finalize against deleting...
fd89d46 fix(prover): wait for previous epoch to be proven (#23457)
4475d8c fix(prover): wait for previous epoch to be proven
See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the aztec-dependencies group with 11 updates: | Package | From | To | | --- | --- | --- | | [@aztec/accounts](https://github.com/AztecProtocol/aztec-packages) | `4.3.0` | `4.3.1` | | [@aztec/aztec.js](https://github.com/AztecProtocol/aztec-packages) | `4.3.0` | `4.3.1` | | @aztec/constants | `4.3.0` | `4.3.1` | | [@aztec/entrypoints](https://github.com/AztecProtocol/aztec-packages) | `4.3.0` | `4.3.1` | | @aztec/ethereum | `4.3.0` | `4.3.1` | | @aztec/foundation | `4.3.0` | `4.3.1` | | @aztec/noir-contracts.js | `4.3.0` | `4.3.1` | | [@aztec/protocol-contracts](https://github.com/AztecProtocol/aztec-packages) | `4.3.0` | `4.3.1` | | @aztec/pxe | `4.3.0` | `4.3.1` | | @aztec/stdlib | `4.3.0` | `4.3.1` | | [@aztec/wallets](https://github.com/AztecProtocol/aztec-packages) | `4.3.0` | `4.3.1` | Updates `@aztec/accounts` from 4.3.0 to 4.3.1 - [Release notes](https://github.com/AztecProtocol/aztec-packages/releases) - [Commits](AztecProtocol/aztec-packages@v4.3.0...v4.3.1) Updates `@aztec/aztec.js` from 4.3.0 to 4.3.1 - [Release notes](https://github.com/AztecProtocol/aztec-packages/releases) - [Commits](AztecProtocol/aztec-packages@v4.3.0...v4.3.1) Updates `@aztec/constants` from 4.3.0 to 4.3.1 Updates `@aztec/entrypoints` from 4.3.0 to 4.3.1 - [Release notes](https://github.com/AztecProtocol/aztec-packages/releases) - [Commits](AztecProtocol/aztec-packages@v4.3.0...v4.3.1) Updates `@aztec/ethereum` from 4.3.0 to 4.3.1 Updates `@aztec/foundation` from 4.3.0 to 4.3.1 Updates `@aztec/noir-contracts.js` from 4.3.0 to 4.3.1 Updates `@aztec/protocol-contracts` from 4.3.0 to 4.3.1 - [Release notes](https://github.com/AztecProtocol/aztec-packages/releases) - [Commits](AztecProtocol/aztec-packages@v4.3.0...v4.3.1) Updates `@aztec/pxe` from 4.3.0 to 4.3.1 Updates `@aztec/stdlib` from 4.3.0 to 4.3.1 Updates `@aztec/wallets` from 4.3.0 to 4.3.1 - [Release notes](https://github.com/AztecProtocol/aztec-packages/releases) - [Commits](AztecProtocol/aztec-packages@v4.3.0...v4.3.1) --- updated-dependencies: - dependency-name: "@aztec/accounts" dependency-version: 4.3.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: aztec-dependencies - dependency-name: "@aztec/aztec.js" dependency-version: 4.3.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: aztec-dependencies - dependency-name: "@aztec/constants" dependency-version: 4.3.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: aztec-dependencies - dependency-name: "@aztec/entrypoints" dependency-version: 4.3.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: aztec-dependencies - dependency-name: "@aztec/ethereum" dependency-version: 4.3.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: aztec-dependencies - dependency-name: "@aztec/foundation" dependency-version: 4.3.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: aztec-dependencies - dependency-name: "@aztec/noir-contracts.js" dependency-version: 4.3.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: aztec-dependencies - dependency-name: "@aztec/protocol-contracts" dependency-version: 4.3.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: aztec-dependencies - dependency-name: "@aztec/pxe" dependency-version: 4.3.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: aztec-dependencies - dependency-name: "@aztec/stdlib" dependency-version: 4.3.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: aztec-dependencies - dependency-name: "@aztec/wallets" dependency-version: 4.3.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: aztec-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>

github-actions · 2026-06-08T09:20:16Z

Benchmark Comparison

CPU	Cores	RAM	Arch
AMD EPYC 9V74 80-Core Processor	16	63 GiB	x64

Contract: private

🚦	Function	Gates			DA Gas			L2 Gas			Proving Time (ms)
		Base	PR	Diff	Base	PR	Diff	Base	PR	Diff	Base	PR	Diff
⚪	`increment`	415,462	415,462		192	192		626,754	626,754		N/A	N/A
⚪	`increment_private`	531,289	531,289		768	768		648,529	648,529		N/A	N/A
⚪	`increment_private_mint_and_pay_fee`	687,462	687,462		864	864		739,645	739,645		N/A	N/A
⚪	`mint_private`	397,098	397,098		736	736		483,700	483,700		N/A	N/A

dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jun 8, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps-dev): bump the aztec-dependencies group with 11 updates#158

chore(deps-dev): bump the aztec-dependencies group with 11 updates#158
dependabot[bot] wants to merge 1 commit into
devfrom
dependabot/npm_and_yarn/aztec-dependencies-ced9f272f1

dependabot Bot commented on behalf of github Jun 8, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jun 8, 2026

Uh oh!

Reviewers

Assignees

Labels

Milestone

Development

Uh oh!

0 participants

Conversation

dependabot Bot commented on behalf of github Jun 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

v4.3.1

Summary

What contract developers should care about

What node operators should care about

What changed since v4.3.0

Reference

v4.3.1

Summary

What contract developers should care about

What node operators should care about

What changed since v4.3.0

Reference

v4.3.1

Summary

What contract developers should care about

What node operators should care about

What changed since v4.3.0

Reference

v4.3.1

Summary

What contract developers should care about

What node operators should care about

What changed since v4.3.0

Reference

v4.3.1

Summary

What contract developers should care about

What node operators should care about

What changed since v4.3.0

Reference

Uh oh!

github-actions Bot commented Jun 8, 2026

Benchmark Comparison

Contract: private

Uh oh!

Reviewers

Assignees

Labels

Milestone

Development

Uh oh!

0 participants

dependabot Bot commented on behalf of github Jun 8, 2026 •

edited

Loading