Closed
Conversation
…o production-devnet
…o production-devnet
…ct instance verification Bytecode mismatch and address mismatch are client errors (bad input), not server errors. Changed both status codes from 500 to 400.
… parsing Zod's .parse() throws on invalid data rather than returning falsy, making the previous if (!dbContractClass) check dead code. A ZodError would have propagated as a misleading 400 instead of the intended 500.
…tion The addArtifactData call during instance verification was missing the contractName parameter, causing artifactContractName to be null in the DB. Now destructures artifactContractName from verifyArtifactPayload result and passes it to both addArtifactData and the cache entry.
…t comparison Raw JSON string comparison is fragile — semantically identical artifacts with different key ordering or whitespace would fail. Now uses verifyArtifactPayload to compare compiled bytecode instead.
…ta is absent Previously, successful verification without deployerMetadata would return 200 without updating the Redis cache, causing stale data (missing verifiedDeploymentArguments) to be served until TTL expired (~60s).
Devnet uses Envoy Gateway which defaults to ~1MB max body size. Large contract artifacts (e.g. Train at ~1.1MB) would be rejected with 413. Added ClientTrafficPolicy with 50MB limit to match nginx's proxy-body-size on testnet/mainnet.
…t bodies" This reverts commit d672602.
Merges production-devnet into production-testnet to bring: - Aztec v4 (4.0.0-devnet.2-patch.1) support - Buffer-based block serialization (replacing JSON string) - L2BlockProposed -> CheckpointProposed rename - contentCommitment removal, spongeBlobHash addition - DB migrations for v4 schema changes - Envoy Gateway compatible auth controller - All package version updates to v4
…1 and regenerate yarn.lock The 4.0.3 upgrade changed @defi-wonderland/aztec-standards to 4.0.3 which does not exist on npm. Revert to 4.0.0-devnet.2-patch.1 (the latest published version) and regenerate yarn.lock so all @aztec/ packages resolve to 4.0.3 correctly.
The @aztec/bb.js native bb binary requires glibc 2.39+ (C23 symbols). Alpine (musl) and Debian Bookworm (glibc 2.36) cannot run it. Debian Trixie provides glibc 2.39+, matching what event-cannon already uses.
Override uncleaned z.coerce.bigint() fields that cause generateSchema to throw 'Cannot convert undefined to a BigInt' during isOptional() checks: balance in contractInstanceBalance, and nested l1BlockNumber in proposedOnL1/proofVerifiedOnL1 block schemas.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.