Skip to content
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

CIP-???? | Cardano URIs - Enhanced Payments #843

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Crypto2099
Copy link
Collaborator

@Crypto2099 Crypto2099 commented Jun 16, 2024

Rendered Version

This proposal seeks to extend the CIP-13 payment URIs and address some of the issues raised here: #836

We need an enhanced and more explicit Payment type of Cardano URI in the modern era of native assets, smart contracts, and transactional metadata.

Because of legacy integrations with existing URI payments (lacking a dedicated authority) I have chosen to break this extension out into a new CIP with an explicit authority to avoid having to change or update CIP-13.

@rphair
Copy link
Collaborator

rphair commented Jun 16, 2024

@Crypto2099 good to have a stub here for the current discussion of how a comprehensive and ambiguity-free payment URI syntax would look. Cross-referencing my #836 (comment) and #836 (comment) to be sure scenarios involving these boundary cases will be handled properly by any proposed syntax:

  • keyword(s) used to specify metadata collide with token name(s)

... including these cases if payment handles are supported by this protocol (I would insist that they should be):

  • payment handles (if supported by this protocol) are ambiguous as per CPS-0008? | Domain Name Resolution #605 (cc @SIDANWhatever)
  • keyword(s) used to disambiguate payment handles collide with token name(s)
  • payment handles collide with bare payment addresses (unlikely but possible)

@Crypto2099
Copy link
Collaborator Author

Thanks @rphair excited to start the conversation and hoping to have some first-draft specs delivered over the course of the next week for discussion! These are great starting points for consideration though!

@rphair
Copy link
Collaborator

rphair commented Jun 16, 2024

you're welcome @Crypto2099 & if you feel potential specs could use community brainstorming then feel free to add this to the agenda in a week-plus time: https://hackmd.io/@cip-editors/91

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants