You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users should be able to create collection atomic-swaps
the main difference between this and other atomic-swaps is that the user has not selected adesiredItem inside the desiredCollection
so any owner of nfts in that desiredCollection can accept the atomic-swap
@exezbcz designs for creating and accepting these kind of swaps are needed
simplified requirements
Only a desiredCollection is needed and also
for swaps: offeredItem, surcharge
for offers: offer amount
how to create one
Swaps
maybe we have. button inside a collection that redirects to the swap landing page but step "2" (where the user selects the nft they want is skipped) , swap review step should accommodate for this
this is how i am thinking about the collection offer and collection swap
the main improvements i think are needed on the incoming offers and swap table on the profile, otherwise it's two simple modals for each flow that reuses lot of components
Users should be able to create collection atomic-swaps
the main difference between this and other atomic-swaps is that the user has not selected a
desiredItem
inside thedesiredCollection
so any owner of nfts in that
desiredCollection
can accept the atomic-swap@exezbcz designs for
creating
andaccepting
these kind of swaps are neededsimplified requirements
Only a desiredCollection is needed and also
how to create one
Swaps
maybe we have. button inside a collection that redirects to the swap landing page but step "2" (where the user selects the nft they want is skipped) , swap review step should accommodate for this
Offer
issue: #11116
maybe we have. button inside a collection that opens this modal without the nft section
how to accept one
Any owner of nfts in the
desiredCollection
of that atomic-swap can accept that trade andselect
a nft from any that they ownThe text was updated successfully, but these errors were encountered: