As a user, I want to receive a token, so I can see what this is all about.

[owocki]

User Story

As a user, I want to receive a token, so I can see what this is all about.

How it Works

As a user, I want to receive a token, so I can see what this is all about.

Happy Path

(This ticket starts with a 'send artifact' flow)

User receives an email
Subject: You've received a "Python" artifact
Body: username sent you a python artifact on Gitcoin. Click here to claim it - LINK. Click here to learn more LINK TO MEDIUM POST

When user clicks the claim link, they are taken to the receive page.
The receive page shows the information about the artifact -- title, description, rareness, who it came from.
The user may click 'receive', at which time they will be presented with a Metamask confirmation modal. When that tx is confirmed, the artifact will be added to their profile.

On the users profile, will be a trophy case of all the artifacts they've been sent. On each trophy, if one clicks on it, a modal will pop up saying what it is title, description, rareness.

Description

Type:
Feature

[PixelantDesign]

Sounds good!

[thelostone-mc]

What happens when the user decides not to accept the token ?
Do we assign it to the owner / issue a refund ?

[owocki]

i think it should live on their profile / in their wallet by default.

if its important from a product perspective for someone to be able to 'reject' a token, maybe we can have a 'reject' button that sends it to 0x0?

[thelostone-mc]

Which means we'd have an additional field to keep track of whether we display the token on the profile or not !

Rejct button with address as 0x0 makes sense

[jasonrhaas]

This one also can be closed soon, barring testing/QA. Recommend opening up new tickets for bugs and/or new features.

[owocki]

are the emails for this done? @octavioamu @jasonrhaas

[jasonrhaas]

Nope still need to get the email templates in. If the image thing is holding us up, lets at least it updated without the images, and add that later.

[owocki]

yeah i agree