feat(server): put foreign ring-VRF key use to the user - #424
Draft
filvecchiato wants to merge 2 commits into
Draft
feat(server): put foreign ring-VRF key use to the user#424filvecchiato wants to merge 2 commits into
filvecchiato wants to merge 2 commits into
Conversation
RFC-0024 gates this on a manifest allowlist no manifest carries yet, so the core matches Android's prompt instead of refusing every cross-product call.
filvecchiato
marked this pull request as draft
August 17, 2026 11:26
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.
Part of #373. Resolves ask 1: one interim behaviour for the core, matching Android.
key_handleoncreate_account_proof/ring_vrf_signraisesForeignRingVrfKey, naming caller, owner, and whether the output is a context-scoped proof or an unscoped signature. Declined isRejected;NotAllowlistedstays for a manifest allowlist.The playground example for this call can no longer assert a fixed outcome — it accepts approved-or-
Rejected.