feat: Circle v2 strategies + 4 v1-vs-v2 benches (industry-default → Helix discovery)#7
Merged
Merged
Conversation
…ity analysis 20 real Arc Testnet tx in Group A (idempotencyKey strip). 20 correct holds in Group C (UUID format violation). Group B revealed refresh_metadata action is design-intent only — Circle's actual tokenId error shapes route to hold_and_notify via uuid_format (Rule 2) or catch-all (no errors[] array). Documented for PR #4 numeric-code routing.
Companion script to commit fd3ccf7 which captured Bench 2.4 results and refresh_metadata reachability analysis. Tests the three groups: - Group A: idempotencyKey deliberate trigger (strip_field path) - Group B: nil-UUID tokenId trigger (uuid_format violation path) - Group C: 'not-a-uuid' walletId trigger (hold_and_notify path) Allows independent reproduction of Bench 2.4 findings.
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
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.
Circle v2 Strategies + V1-vs-V2 Benches — PR #3
Follow-up to merged PR #1 (Circle Foundation) and PR #2 (Experimental Capsules). Adds 3 new v2 strategies + 4 v1-vs-v2 comparison benches. Reveals industry-default approaches have limitations Helix discovers through systematic experimentation.
Headline Results
serialize_and_backoff— 76% success, 24/100 lostchunk_concurrent— 100% success, 0 losthold_and_notify— 0% auto-fixsmart_param_repair— 80% routing to auto-fixoverride_api_decimals— decimals onlymetadata-trust-on-chain— decimals + symbol + audit-sourcestrip_field— 20/20 real Arc Testnet tx submittedReal data, real Arc Testnet (220 total live transactions), JSON in
scripts/circle-bench/results/.Honest Anomalies Surfaced
PR #3 includes 2 documented findings that PR #4 will address:
v1-serialize-and-backoff-anomaly.md: v1 retries fire concurrently and re-trigger rate limit under sustained load, losing 24% of transfers.refresh-metadata-reachability.md: v2'srefresh_metadataaction is currently unreachable on live Circle (Circle's tokenId errors take other paths). PR feat: Circle experimental capsules — decimals & stale_quote (2 of 2) #4 will add numeric-code routing forcode 156002→refresh_metadata.This is research-grade honesty: surface findings, document, address in next PR.
Code Delivered
3 standalone v2 strategies (not yet integrated into PCEC engine — Gene Map multi-strategy is PR #4):
packages/core/src/strategies/circle-v2/chunk-concurrent.ts(100 lines)packages/core/src/strategies/circle-v2/smart-param-repair.ts(255 lines)packages/core/src/strategies/circle-v2/metadata-trust.ts(207 lines)4 bench scripts:
scripts/circle-bench/v1-vs-v2-rate-limit.tsscripts/circle-bench/v1-vs-v2-param-repair.tsscripts/circle-bench/v1-vs-v2-metadata-trust.tsscripts/circle-bench/v2-smart-param-e2e.ts(PR feat: Circle Developer Wallets integration (foundation PR, 1 of 4) #3.4)5 JSON result files + 2 analysis docs in
scripts/circle-bench/results/Test Coverage
53 new tests added. Full suite: 623/623 passing. No regressions.
Scope Boundaries (intentional)
v2 strategies are validated standalone via bench. They become first-class Gene Map citizens in PR #4 with proper Thompson Sampling between v1/v2 alternatives.
Roadmap (estimated)
code 156002(closes refresh_metadata reachability gap from Bench 2.4)See Section 9 of the walkthrough document (
circle-walkthrough-v2.md) for full self-improving roadmap.Verification
JSON results land in
scripts/circle-bench/results/for inspection.