-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CHIP-0039: Fee Service Standard #138
base: main
Are you sure you want to change the base?
Conversation
995cd03
to
e92fdc0
Compare
bca97a3
to
04c9fd9
Compare
04c9fd9
to
49a702e
Compare
This CHIP is a |
Great CHIP! I can see some situations where services might need a few mojos to start a transaction. For example:
Would it make sense to have the same services be able to provide a one-sided offer to get the mojos required to build transactions with? This is what I did for the warp.green welcome kits. The fee could very well still be attached at the end (when the final spend bundle is available), but could also be included in the initial offer if the app knows what fee it'll need. That way, you also remove some trust in the service, as the dApp itself can push the spend bundle to the mempool. |
This is certainly something that could be added to a fee paying service, but I'm not sure if it belongs in the CHIP. Let's plan to have a public zoom call to discuss this, and other ideas pertaining to the CHIP, early in 2025. |
We had a discussion of this CHIP, with several ideas for improving it and implementing it. |
No description provided.