As an admin, I want to create a flow where users can mint new tokens, so tokens can be limited only by users' imaginations and the money they want to give us!

[owocki]

User Story

As an admin, I want to create a flow where users can mint new tokens, so tokens can be limited only by our imaginations and money!

How it Works

As an admin, I want to create a flow where users can mint new tokens, so tokens can be limited only by our imaginations and money!

Happy Path 1

We enter this flow from the 'mint' token flow, where we stores each of the form fields in the database in a new table called TokenCreationRequests, and manages the token creation. (See Token Creation Ticket)

TokenCreationRequest has the following fields

• Title
• Description
• Price
• from_user
• status

When a new TokenCreationRequest is created, an admin-email is sent to settings.ERC721_ADMIN, which will initially map to founders@gitcoin.co.

Django Admin

There is a django admin index for the TokenCreationRequest, we will use that to manage requests that are status == pending. Each row in this table will have a 'process' link if status != 'done'.

There will be a django admin area where we (or a contractor we hire) can process each TokenCreationRequest.

This area will show all of the info above, and a comment thread. On this screen, we can also add staff-only comments to discuss each request. For each comment, one can optionally attach an svg. Each time a new comment is posted, it will send an email to settings.ERC721_ADMIN letting them know about the comment and linking to the thread.

There will be a "Deliver" button which allows a staff member to upload a final SVG to the TokenCreationRequest object. When this happens, status will become done, fulfiller_user will be the staff username, and an email will be sent to the user letting them know their "minting" process is complete.

Subject: Your artifact mint is complete!
Body: img of the new artifact.
manage artifact LINK

Description

Type:
Feature

[thelostone-mc]

Does the creator automatically get a copy of the token he created once the minting is complete ?

Or would it be a two step process where once it's minted, he'd have to go and buy it like everyone else despite being a creator ?

And I'm assuming we will have a guideline doc to the users which they need to abide by if they would like to request minting

Also does the rarity influence the price or the other way around

I know the user enters the rarity aka number of clones but he also sets the price ! So it could a super rare token but dirt cheap / a super expensive token with multiple copies ( based on how the user wants it )

They need to figure out the sweet spot to make money ?

Oh this is exciting :D

[owocki]

Does the creator automatically get a copy of the token he created once the minting is complete ?

yes

And I'm assuming we will have a guideline doc to the users which they need to abide by if they would like to request minting

yes we already have guidelines for these assets. they were posted recently in the erc721 channel

Also does the rarity influence the price or the other way around

i certainly think it should! here is a ticket to track pricing discussions #35

They need to figure out the sweet spot to make money ?

amen 🙏

[owocki]

There will be a django admin area where we (or a contractor we hire) can process each TokenCreationRequest.

What if, instead of custom baking a review area in the django admin, we use github issues on a new repo, to manage the creation of the assets. This way (1) the user can be involved in the creation of their art (2) we don't reinvent the wheel from a work management perspective ( messages / assignee / uploads all dont have to be custom baked )

[owocki]

@PixelantDesign

can we start doing this with miaden? @mbeacom and i can create a new github issues board for you if you want

What if, instead of custom baking a review area in the django admin, we use github issues on a new repo, to manage the creation of the assets. This way (1) the user can be involved in the creation of their art (2) we don't reinvent the wheel from a work management perspective ( messages / assignee / uploads all dont have to be custom baked )

[jasonrhaas]

There is a django admin index for the TokenCreationRequest, we will use that to manage requests that are status == pending. Each row in this table will have a 'process' link if status != 'done'.

Why do we need the TokenCreationRequest? If this ticket as "as an admin", can't we just mint it, wait for it to mint and, sync it to the database, and then have it show up in the Marketplace for cloning? Is it necessary to send an email in this case?

[owocki]

Why do we need the TokenCreationRequest?

Because there is going to be several revisions of the artistic asset in between the request for a new token and the actual creation of the token, (bc design / art is never perfect in the first rev) and we need to have a place to persist the request during that time. Also, it'd be ncie to have analytics around which artists are performing and which aren't.

[jasonrhaas]

Because there is going to be several revisions of the artistic asset in between the request for a new token and the actual creation of the token

Ok, so this ticket is like "Create a Sandbox Working Area for designing new Kudos". But we want it to be "admin only", so not available to new users. In this case, it would be a Sandbox of "In progress" Kudos that are being designed. Once the design in finalized, there will be some kind of flow for turning the "In Progress" Kudos to "Complete". At that point it will be minted on the blockchain.

[PixelantDesign]

I was thinking something like this? Let's discuss...

[jasonrhaas]

The flow looks good. @owocki also had the idea of using Github issues or PR's for approvals. That might make sense here, and this way we don't have to re-invent the whole workflow/review process.

[owocki]

strongly in favor of leveraging github issues (or similar) instead of building our own content creation task management system

above flow looks good. instead of having it go to alisa then to the user, i was thinking of doing 2 rounds of review where anyone on the core team AND the funder of the art are able to comment

[octavioamu]

We really want to do this one for v1? I'm thinking this can be good for v2 or maybe for v1 we can just use github for all the process, I mean just a link to a template isse "mint new kudos request" with the fields we need, until we validate how people use kudos. (like a new icon request of font awesome)

[owocki]

i like the idea of using github for this. we could have a repo with all of the kudos on it, and users could just open up a new issue with a specified template to mint a new request, which we could them assign to one of the illustrators on the team

[PixelantDesign]

I think this is V1.5 or V2.

[jasonrhaas]

For this one, the mint page will be directed to a Github Issue for V1. For V.next we will have the option of improving this or having a more integrated flow for creating original Kudos tokens.