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

getting started dapp doesn't demonstrate quid-pro-quo asset exchange #744

Closed
dckc opened this issue Jan 4, 2023 · 3 comments
Closed

getting started dapp doesn't demonstrate quid-pro-quo asset exchange #744

dckc opened this issue Jan 4, 2023 · 3 comments
Assignees

Comments

@dckc
Copy link
Member

dckc commented Jan 4, 2023

One of the main distinctions of our platform is the primitive is not "send A assets to X" but rather "offer A in exchange for B". The default getting started app, the fungible faucet, doesn't exhibit this pattern.

In Nov 16 office hours I went over a sell1 contract where Alice sells an item to Bob in exchange for a price.

It's pretty close to our simple exchange example contract, but I think it's simpler in useful ways.

@Tyrosine22 showed some interest in building a dapp UI around this "Alice sells an item to Bob" scenario.

@dckc
Copy link
Member Author

dckc commented Jan 5, 2023

@Tyrosine22 points out we have one, thought it needs some love: https://github.com/Agoric/dapp-simple-exchange

@dckc
Copy link
Member Author

dckc commented Apr 3, 2023

looks like @samsiegart gave https://github.com/Agoric/dapp-card-store a little polish and I gather that's a candidate for addressing this issue. Seems plausible.

@dckc dckc changed the title fungible faucet doesn't demonstrate quid-pro-quo asset exchange getting started dapp doesn't demonstrate quid-pro-quo asset exchange Apr 10, 2023
@dckc
Copy link
Member Author

dckc commented Apr 10, 2023

fixed in #790 . yay!

@dckc dckc closed this as completed Apr 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants