Support sponsored Umbra fee payer secrets#325
Closed
enzotar wants to merge 1 commit into
Closed
Conversation
3559bed to
d038b96
Compare
d038b96 to
bd0483f
Compare
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.
Adds backend support for sponsored Umbra fee payer secrets so private passkey payments can use a server fee payer without requiring SOL on the passkey wallet.\n\nChanges:\n- accepts base58 64-byte secret strings for Umbra fee_payer\n- adds neutral fee_payer_secret input to avoid Flow wallet materialization converting fee_payer to pubkey\n- prefers fee_payer_secret when present\n- adds focused tests for sponsored fee payer parsing and rewrite behavior\n\nVerified:\n- bun test ./crates/cmds-bun/src/umbra/umbra_common.ts