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

Update top-level README: post meeting 84 #789

Merged
merged 2 commits into from
Apr 1, 2024

Conversation

rphair
Copy link
Collaborator

@rphair rphair commented Mar 19, 2024

@rphair rphair requested review from Ryun1 and Crypto2099 March 19, 2024 18:13
@Ryun1
Copy link
Collaborator

Ryun1 commented Mar 23, 2024

Since we are doing house keeping, do you mind fixing the Copywright section in the template;
we need to add a end comment here, otherwise the uncommenting of different licenses doesnt work properly.
🤓

@rphair
Copy link
Collaborator Author

rphair commented Mar 24, 2024

@Ryun1 I see what you mean... to someone who does a lot of HTML editing the whole of the uncommenting is intuitive, but the lack of symmetry in the comment closures requires more editing attention & makes it error-prone. Have fixed it in both the CIP and CPS templates.

@rphair rphair requested a review from Ryun1 March 24, 2024 14:30
Copy link
Collaborator

@Crypto2099 Crypto2099 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

@rphair rphair merged commit 97a41c4 into cardano-foundation:master Apr 1, 2024
@polinavino
Copy link

Here is an idea of a usecase for intents : Light Clients that never query the ledger state, and instead use an intents API to describe what kind of transaction they want constructed for them. The API would have things like

  • pay value from key to key
  • mint an nft, etc.
  • make a DEX trade/offer
  1. An LC constructs an intent, sends it out to a service provider (SP) to fill.
  2. The SP responds with a transaction that can be demonstrated to satisfy the intent, but is neither valid nor contains enough data for the LC to construct a valid transaction from it (in particular, it is missing all output references except one, which is from the SPs wallet). This transaction includes a payment to the SP for their service.
  3. The LC signs this transaction, and sends it back to the SP.
  4. The SP then constructs another transaction such that the two transactions together in a validation zone constitute a complete valid transaction (missing references are supplied), and sends this across the Cardano network.

If this sounds interesting, I can elabourate.

@rphair
Copy link
Collaborator Author

rphair commented Jun 10, 2024

@polinavino yes, it sounds interesting! Can you please re-post & elaborate in:

and maybe also in:

@rphair rphair added the Bi-Weekly Notes / Editorial Housekeeping Publishing Bi-weekly meetings minutes / Mintor edits of public surrounding information label Aug 7, 2024
@rphair rphair changed the title Update top-level README: post meeting #84 Update top-level README: post meeting 84 Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bi-Weekly Notes / Editorial Housekeeping Publishing Bi-weekly meetings minutes / Mintor edits of public surrounding information
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants