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

docs(examples): simple asset transfer in the new architecture #334

Open
petermetz opened this issue Oct 30, 2020 · 3 comments
Open

docs(examples): simple asset transfer in the new architecture #334

petermetz opened this issue Oct 30, 2020 · 3 comments
Assignees
Labels
API_Server Developer_Experience documentation Improvements or additions to documentation enhancement New feature or request P1 Priority 1: Highest
Milestone

Comments

@petermetz
Copy link
Contributor

petermetz commented Oct 30, 2020

Description

As a developer/contributor I want to have updated documentation about the simple asset transfer demo that I saw during the Hyperledger Global Forum 2020 talk so that I am not confused about the fact that (currently) there is no such documentation since we've moved over to the new architecture.

Context:
A fully fledged example has been developed as part of v0.2.0, but it does not do asset transfer yet so it only partially resolved the
original version of this issue (OG is here: #189 )

See also my comment: #189 (comment)


Update 2023-09-15

More information about what a simple asset transfer was in the old architecture

See the code of it: https://github.com/hyperledger/cacti/tree/feadee73f350b5ffb84aa9aba0435eeb7697fecb/packages/core/examples/simple-asset-transfer

See a demo of it from way back when we moved up from the labs to be an incubation project: https://youtu.be/fgYrUIc_-sU?t=679

Simple asset transfer logic of the code that I linked above:

  1. Lock assets on both ledgers
  2. Generate proofs
  3. Validate proofs
  4. Mint new assets
  5. Transfer newly minted assets (locally)

It's not an atomic transfer.

Acceptance Criteria

1.The simple asset transfer use-case is re-written from scratch to match the new arch
7. The new documentation closes the loop regarding asset export verification and error handling as well (thanks to Arnaud for pointing out the lack of these)

Depends upon #2655

@petermetz petermetz added documentation Improvements or additions to documentation enhancement New feature or request Developer_Experience labels Oct 30, 2020
@petermetz petermetz added this to the v0.3.0 milestone Oct 30, 2020
@petermetz petermetz self-assigned this Oct 30, 2020
@petermetz petermetz modified the milestones: v0.3.0, v0.4.0 Jan 8, 2021
@petermetz petermetz modified the milestones: v0.4.0, v0.5.0 Apr 29, 2021
@petermetz petermetz modified the milestones: v0.5.0, v0.6.0 May 19, 2021
@petermetz petermetz modified the milestones: v0.6.0, v0.7.0 Jul 20, 2021
@petermetz petermetz modified the milestones: v0.7.0, v0.8.0 Aug 10, 2021
@petermetz petermetz modified the milestones: v0.8.0, v0.9.0 Aug 17, 2021
@petermetz petermetz modified the milestones: v0.9.0, v0.10.0 Sep 2, 2021
@petermetz petermetz added P1 Priority 1: Highest API_Server labels Jul 24, 2023
@petermetz petermetz modified the milestones: v0.10.0, v2.0.0-alpha.2 Jul 24, 2023
@ruzell22
Copy link
Contributor

Hello @petermetz can you assign this to me? Thank you

@aldousalvarez
Copy link
Contributor

Hello @jagpreetsinghsasan I am also helping on this one, Thanks!

@jagpreetsinghsasan
Copy link
Contributor

Created spike #2655 so that @ruzell22 and @aldousalvarez can estimate the complexity of this task

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API_Server Developer_Experience documentation Improvements or additions to documentation enhancement New feature or request P1 Priority 1: Highest
Projects
None yet
Development

No branches or pull requests

6 participants