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

spike: understand simple-asset-transfer example #2655

Closed
jagpreetsinghsasan opened this issue Sep 6, 2023 · 3 comments
Closed

spike: understand simple-asset-transfer example #2655

jagpreetsinghsasan opened this issue Sep 6, 2023 · 3 comments
Assignees
Labels
SPIKE Exploratory work to better scope additional effort

Comments

@jagpreetsinghsasan
Copy link
Contributor

Description

As a developer I want to explore the code and understand the simple asset transfer use-case.
This will help me in estimating and thus completing #334

Acceptance Criteria

  1. Should be able to estimate docs(examples): simple asset transfer in the new architecture #334
@ruzell22
Copy link
Contributor

ruzell22 commented Sep 6, 2023

Commenting here so this ticket can be assigned to me. Thank you.

@aldousalvarez
Copy link
Contributor

@jagpreetsinghsasan Can you assign me on this one as well. Thank you

@jagpreetsinghsasan
Copy link
Contributor Author

Based on this spike learning, I will create one more spike where @ruzell22 can look into the connectors and how they interact with the smartcontracts.
The initial acceptance criteria was to estimate the main task via this spike but upon completion of the spike, the need to understand connector interaction with the ledgers is also seen and thus the need for another spike story as a subsequent action to this one. The acceptance criteria will get carried forward in the new spike I will create and will tag the same here for reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
SPIKE Exploratory work to better scope additional effort
Projects
None yet
Development

No branches or pull requests

3 participants