Registration accepts bearer party envelopes - #8
Merged
Conversation
Party envelopes carry no audience binding (spec §8.3): the request token is the delivery intent and who eligibility gates registration. Audiences on subject signatures are ignored as legacy hop artifacts. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
VerifyParty reads the subject from the party's own gobl: endpoint, attested by a valid self-signature — signature order carries no meaning, and a party document declaring an address its signer does not control can no longer be registered. Co-Authored-By: Claude Fable 5 <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.
Companion to invopop/gobl#925: party envelopes in the identity flow are bearer documents — the subject signs once, audience-free, and the same envelope registers, publishes, and verifies.
Registerdrops the audience requirement entirely (VerifyEnvelope(ctx, env, "")): the request token carries delivery intent, and the who eligibility check remains the gate on who can register (which also keeps deferred-disclosure/B2C parties unregistrable by third parties — their/whoanswers 202 and registration is refused). Audiences on subject signatures are accepted and ignored as legacy hop artifacts, so envelopes signed under the previous revision keep working. The own-countersignature integrity check is unchanged.🤖 Generated with Claude Code