Merged
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…n check On L2s like Base, the sequencer's block.timestamp can lag behind real-world time, causing valid attestations to be rejected as "future". This adds a configurable futureAttestationBuffer (default 10 minutes) so that attestations with issuedAt slightly ahead of block.timestamp are accepted. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
feat: add configurable forward-tolerance buffer for future attestation check
deploy.sh had a bug where step 1 compiled with via_ir=true but steps 2-5 ran forge script with FOUNDRY_PROFILE=ci, which recompiled with via_ir=false and overwrote the optimized artifacts. Fix FORGE_PROFILE to "default". Also add a --prebuilt flag for building optimized artifacts on a VPS and deploying them locally without recompilation: - `make build-deploy-artifacts` builds via_ir contracts + ci scripts, tarballs out/ - `./script/deploy.sh sepolia --prebuilt` extracts and deploys with --skip-compilation Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
fix: deploy via_ir=true bytecode and add --prebuilt workflow
Rewrote deploy.sh to solve the forge via_ir recompilation problem: - Step 1: Two-step build (ci scripts + via_ir contracts) keeps peak memory at ~1.2 GB instead of 16+ GB - Steps 2 & 5: Deploy contracts via `cast send --create` with pre-built bytecode from out/, completely bypassing forge's recompilation - Steps 3 & 4: Run forge script with ci profile (scripts already compiled) - Rebuild via_ir artifacts after steps 3-4 for BaseScan verification Removed the --prebuilt workflow (tarball + VPS build) since local builds work fine with the two-step approach. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
fix: deploy via_ir=true contracts without OOM recompilation
Adds Step 6 after deployment that automatically verifies all contracts (CredentialRegistry, DefaultScorer, ScorerFactory) on BaseScan using forge verify-contract. Requires BASESCAN_API_KEY in .env. Each verification gracefully handles failures with a warning instead of aborting the script. Skipped in dry-run mode. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
feat: add BaseScan verification step to deploy script
Update CredentialRegistry, DefaultScorer, ScorerFactory, and Owner addresses across all documentation files to reflect the new deployment. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
docs: update deployed contract addresses
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
2 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.
Summary
Test plan
devvia individual PRs (feat: add configurable forward-tolerance buffer for future attestation check #32–docs: update deployed contract addresses #36)🤖 Generated with Claude Code