Skip to content

fix: re-add verifier parse functions#14

Merged
alanshaw merged 2 commits into
mainfrom
ash/fix/re-add-verifier-parse
May 19, 2026
Merged

fix: re-add verifier parse functions#14
alanshaw merged 2 commits into
mainfrom
ash/fix/re-add-verifier-parse

Conversation

@alanshaw
Copy link
Copy Markdown
Member

@alanshaw alanshaw commented May 19, 2026

These were removed in #7 but are used in libforge, indexing-service and piri.

The parse functions per key type allow you to support multiple keys but restrict parsing to a specific one. They also return the verifier type for the specific key (not the interface), allowing users to access type specific methods (in the future).

@alanshaw alanshaw requested a review from Peeja May 19, 2026 12:17
@alanshaw alanshaw changed the title fix: re-add verifier parse function fix: re-add verifier parse functions May 19, 2026
@alanshaw alanshaw merged commit 8ad39e5 into main May 19, 2026
1 check passed
alanshaw added a commit to fil-forge/libforge that referenced this pull request May 19, 2026
Renames `capabilities` to `commands` and renames
`capabilities.MustNew(...)` to `capabilities.MustParse(...)`.

depends on fil-forge/ucantone#14
alanshaw added a commit to fil-forge/libforge that referenced this pull request May 19, 2026
Adds a "proof store" interface and implementation allowing you to create
one from a UCAN container.

The interface is a thin wrapper around the lower level utility functions
for obtaining proof chains (and attestations) for invocations.

Note: this was implemented in fil-forge/sprue#2
originally but I need it also in indexing service.

Renames `capabilities` to `commands` and renames `capabilities.MustNew(...)` to `capabilities.MustParse(...)`.

depends on fil-forge/ucantone#14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants