CIP-???? | Native Token Fee Payment API #1052
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
rphair
added
Category: Tools
rphair
reviewed
Jul 9, 2025
There was a problem hiding this comment.
thanks @TotallyNotChase - there are some formatting things that need to be fixed before next meeting review though there's no reason to wait until then to start reviewing the idea. Tagged Triage to put on the next agenda: https://hackmd.io/@cip-editors/116
rphair
changed the title
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.
This CIP proposes to standardize an API that can be used to provide babel-fees like functionality that dApps and wallets can easily integrate with. The hope is that the API can be supported by both stopgap solutions in the present (in absence of babel fees) and also babel fees in the potential future.
(rendered document)