chips icon indicating copy to clipboard operation
chips copied to clipboard

CHIP-0039: Fee Service Standard

Open freddiecoleman opened this issue 1 year ago • 5 comments

freddiecoleman avatar Dec 17 '24 10:12 freddiecoleman

This CHIP is a Draft. It proposes a standard way for a service to include fees with transactions. Feel free to leave a review here, or to comment in the #chips channel of our Discord.

danieljperry avatar Dec 19 '24 17:12 danieljperry

Great CHIP! I can see some situations where services might need a few mojos to start a transaction. For example:

  • Minting singletons (e.g., vaults/NFTs) requires 1 mojo
  • Minting CATs currently requires 1000 mojos/CAT
  • A 'subset' of minting CATs is finishing bridging operations, where one needs to provide the mojos needed to mint the wrapped tokens

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.

Yakuhito avatar Dec 19 '24 18:12 Yakuhito

Great CHIP! I can see some situations where services might need a few mojos to start a transaction. For example:

* Minting singletons (e.g., vaults/NFTs) requires 1 mojo

* Minting CATs currently requires 1000 mojos/CAT

* A 'subset' of minting CATs is finishing bridging operations, where one needs to provide the mojos needed to mint the wrapped tokens

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.

danieljperry avatar Dec 23 '24 18:12 danieljperry

We had a discussion of this CHIP, with several ideas for improving it and implementing it. https://youtu.be/kWXT4WXtkC4

danieljperry avatar Jan 17 '25 02:01 danieljperry

This CHIP has had a working implementation in production for several months. It is now in Review. Please leave your reviews here.

danieljperry avatar Sep 12 '25 23:09 danieljperry

This CHIP is now in Last Call. If no changes are required in the next two weeks, it will be moved to Final status.

danieljperry avatar Nov 07 '25 05:11 danieljperry