Release 0.4.0#7
Merged
Merged
Conversation
A leading "z" SHOULD indicate multibase base58btc per the W3C Data Integrity spec, but standard base64 also contains "z" in its alphabet. ~1/64 of Ed25519 signatures encode with a leading "z" in plain base64, causing the verifier to misroute them to the base58btc decoder, fail decode, and return None instead of validating. The verifier now tries base58btc first when the prefix matches and falls back to base64 if that decode fails or yields empty bytes. Tests: the round-trip test is now seeded for reproducibility, and a new regression test searches the seed space for a leading-"z" base64 signature and asserts the verifier accepts it. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Bump pyproject.toml + uv.lock to 0.4.0 - Datestamp CHANGELOG entry (2026-05-08) - Document the verifier proofValue decoding fix under Fixed Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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
Cuts the 0.4.0 release. Headline change: first-class UNTP DPP 0.7.0 support alongside existing 0.6.x — both wire formats coexist and are auto-detected from
@context/$schemaURLs.dppvalidator.models.v0_7.*) covering every required field per the upstream UNTP 0.7.0 schema._MODEL_BY_VERSION,ALL_RULES_BY_VERSION,LINK_PATHS_BY_VERSION); engine selects the right artefact set per detected version.dppvalidator.compat.upgrade_0_6_to_0_7.upgrade); CLI surface:dppvalidator migrateandvalidate --upgrade-from.proofValuedecoding: base64 signatures whose first character iszno longer get misrouted to the base58btc decoder (~1.5% of random Ed25519 signatures).See
CHANGELOG.md[0.4.0]for the full set.Test plan
1b7120e(lint + 15-cell test matrix + pip-audit + license check + ty)pyproject.toml,uv.lock, andCHANGELOG.mdaligned at0.4.0/2026-05-08uv run pytest tests/unit/— 1880 passed, 13 skippedtest_ed25519_proof_with_leading_z_base64_signature) covers the proofValue decode bugv0.4.0onmainto trigger PyPI publish🤖 Generated with Claude Code