fix: make Van Rossem hard fork ready - #53
Merged
Merged
Conversation
Upgrade yaci-store starters 0.1.2 -> 0.1.7, the latest stable release in the 0.1.x line (Van Rossem / protocol v11). yaci-core is left to resolve transitively from the starter (0.3.10) rather than pinned explicitly, so the project stays on the version combination the 0.1.x starters are built and tested against. cardano-client-lib follows transitively to 0.6.6. Bump project version to 0.1.5. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
matiwinnetou
force-pushed
the
feat/van-rossem-hard-fork-ready
branch
from
June 2, 2026 12:29
fb21ae5 to
926fb69
Compare
matiwinnetou
changed the title
Adds a remote-driven QA harness to validate hard-fork (Van Rossem) readiness end-to-end against mainnet, modelled on cf-token-metadata-registry: - docker-compose.yml + .env: Postgres + API (built from source), syncing mainnet from the first ADA Handle mint (slot 47931310) to tip. DNS-TTL relay-wedge mitigation applied via JAVA_TOOL_OPTIONS (the image entrypoint is a fixed `java -jar`, so JAVA_OPTS would be ignored). - .claude/skills/cf-adahandle-resolver-mainnet-integration-test-full-sync: SSH-driven skill (preflight -> prepare -> compose up -> tunnels -> monitor sync to tip -> parse-error scan -> REST round-trip spot-checks). Pass = full sync through Conway with zero genuine block-parse errors + DB-vs-API consistency on sampled handles. - .gitignore: track .claude/, ignore skill runtime config (config.env, tunnels.pid) and settings.local.json. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
yaci-store stores cursor_.era as a numeric ordinal (7 = Conway), not the string "Conway". Map the ordinal to an era name and gate the hard-fork readiness note on era 7, so crossing into the Conway / Van Rossem window is detected correctly during the mainnet full-sync regression. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
matiwinnetou
marked this pull request as ready for review
June 2, 2026 13:56
- golden-handles.txt: 25 commonly-known mainnet handles (cardano, hosky, minswap, bigpey, charles, ... incl. enterprise-address eth/satoshi/crypto), all verified present on mainnet. Names only — handles are transferable NFTs, so addresses are asserted by shape + round-trip, not pinned (drift-proof). - run-golden-handles.sh: forward lookup (well-formed addr1.../stake1...) + reverse-by-payment-address round-trip for each golden handle. - run-rest-spotchecks.sh: fix stdin/heredoc collision (data now passed via argv, not a pipe that the heredoc program shadowed) and switch the DB sampler to JSON output so arbitrary UTF-8 handle names parse safely; skip empty names. - SKILL.md: document the golden step and files. Validated live against the in-progress mainnet sync: golden 25/25, sample 10/10. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
matiwinnetou
changed the title
matiwinnetou
changed the title
matiwinnetou
changed the title
nemo83
requested changes
Jun 3, 2026
nemo83
left a comment
nemo83
left a comment
Contributor
There was a problem hiding this comment.
it looks like .claude and .env were added by mistake, please remove, everything else looks 👌
A full mainnet sync to tip (~317k handles, ~14.7M ada_handle_history_item rows) exhausted the 2g heap with recurring OutOfMemoryError, wedging the HTTP server while the indexer thread limped on. 4g runs comfortably (steady-state heap ~650MB) and the REST API stays responsive at tip. Surfaced by the mainnet full-sync integration-test harness. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Address PR review (nemo83): a real .env shouldn't be in version control. Rename .env -> .env.example, gitignore .env, and have the full-sync skill's start-remote.sh create .env from .env.example on the remote when missing (a fresh checkout no longer carries .env). The .claude skill folder stays — it's the intentional QA-engineer full-sync harness. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
nemo83
approved these changes
Jun 3, 2026
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.
What
Make the ADA Handle Resolver ready for the Van Rossem hard fork (Cardano protocol version 11, intra-era Conway upgrade).
Changes
0.1.2→0.1.7— the latest stable release in the0.1.xline.cardano-client-libfollows transitively0.6.2→0.6.6.0.1.4→0.1.5.Verification
./mvnw clean teston JDK 21 → 10 tests pass, BUILD SUCCESS.dependency:treeconfirmsyaci/yaci-core/yaci-helperresolve to0.3.10(the starter's native version).Tests