Bump local d14n to newest

[mkysel]

Update local d14n Docker Compose images and anvil contract addresses to bump environment to newest versions in docker-compose-d14n.yml and anvil.json

Update image SHAs in docker-compose-d14n.yml and refresh on-chain addresses in anvil.json.

📍Where to Start

Start with image tag changes in docker-compose-d14n.yml, then review contract address updates in anvil.json.

---

Macroscope summarized 19e0b5b.

[graphite-app]

How to use the Graphite Merge Queue

Add the label mergequeue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[claude]

Claude finished @mkysel's task —— View job

---

Code Review — November 21, 2025, 20:02 UTC

• Read changed files
• Analyze changes for issues
• Provide review feedback

Summary

This PR updates Docker images and contract addresses for the local d14n (xmtpd) environment. The changes are straightforward dependency updates with no code quality or security concerns.

Changes Reviewed

dev/docker/docker-compose-d14n.yml:4

• Docker images updated from sha-ba66d54 → sha-824683a (xmtpd components)
• Contracts image changed from v0.5.5 → sha-7efe09f (switched from version tag to SHA reference)

dev/environments/anvil.json:4,18

• Gateway addresses updated from null addresses (0x0000...) to actual deployed addresses
• 11 contract addresses updated (likely redeployed contracts with new logic)

Findings

✓ No Issues Found

The changes are consistent with a dependency bump and contract redeployment:

• All Docker image SHAs updated in sync
• Gateway addresses now properly configured (previously null)
• Contract addresses follow Ethereum address format
• JSON structure valid

Recommendations

Low Priority:

• Consider adding the PR description explaining what changed in the new xmtpd version (sha-824683a) and why contracts were redeployed
• If breaking changes exist in the new xmtpd version, verify compatibility with existing code

---