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

[ERTP] Basic non-fungible use case in ERTP tests (event tickets) #545

Closed
katelynsills opened this issue Feb 12, 2020 · 2 comments · Fixed by #558
Closed

[ERTP] Basic non-fungible use case in ERTP tests (event tickets) #545

katelynsills opened this issue Feb 12, 2020 · 2 comments · Fixed by #558
Assignees
Labels
ERTP package: ERTP

Comments

@katelynsills
Copy link
Contributor

katelynsills commented Feb 12, 2020

For Zoe Alpha, we need a basic non-fungible use case in the ERTP tests. We can start with the documentation that @DavidBruant wrote for event tickets.

This non-fungible use case would probably use the natListExtentOps or handleExtentOps from the Minimum Extent Ops (#521). If we want to use strings rather than Nats or handles, we could do that, but we will have to spend time implementing the strListExtentOps (#538) as part of Zoe Alpha.

This is a precursor to #543, which is taking this example and putting it in a Zoe contract to deploy to the testnet.

@DavidBruant
Copy link
Contributor

I'm going to go with handleExtentOps because it feels the most relevant to the use case. Also the concept and the code is new, so it'll be a good occasion to exercise it
I'm going to create a branch/PR on top of no-config-add-brand. I'll rebase regularly as this branch changes

@katelynsills
Copy link
Contributor Author

Closed by #558

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

Successfully merging a pull request may close this issue.

2 participants