Add Near Intents charge intent#284
Open
IkerAlus wants to merge 3 commits into
Open
Conversation
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.
Summary
Adds the
nearintentspayment method implementing the existingchargeintent. It settles one-time, cross-chain payments through the NEAR Intents 1Click Swap API: the client pays a source asset on any supported origin chain and the merchant receives an exact destination asset on any supported destination chain, with the NEAR Intents solver network executing the swap in between.Notes for reviewers
type="hash"): The source asset must be deposited before settlement, so there is no server-submitted/pull flow; the client always paysits own origin-chain network fee.
amount/currency/recipientdescribe the client's origin-chain deposit, withrecipient= the 1Click deposit address; the merchant's destination leg lives inmethodDetails. This keeps push-mode verification ("confirm a transfer ofamountcurrencytorecipient") directly applicable.recipientis challenge-specific and bound into the challengeid— a depositcannot be replayed against a different challenge.
refundToon any non-success terminal state.Registers a new method against the already-standardized
chargeintent; it does not define a new intent.Checklist
make checkpassesmake lintpassesspecs/methods/nearintents/AI assistance
Drafting and formatting were done with AI assistance. All content has been reviewed by the author for RFC compliance and technical correctness.