bosonprotocol / interface Goto Github PK

New Seller --> Sell on Boson
Profile, No offers --> Create Products
At least one offer created once --> Seller Center

https://github.com/bosonprotocol/interface/actions/runs/4616885744/jobs/8162616456

Change spelling of email from e-Mail or e-mail to email on profile creation form.

Mandatory fields (*) not consistent here with the form

Allow Sellers to resize or refine their images to fit neatly into the dApp guidelines

Enhance Token Gating dApp experience

https://miro.com/app/board/uXjVMDNFjuw=/

As it stands the dapp assumes that all offers are created from the dapp, this isn't the case, and this is a false assumption.

We need to start checking the values of an offer against the fair exchange policy and highlighting it to buyers if an offer's parameters sit outside of the prescribed best practises.

Here is the Figma for the Product Landing Page

https://www.figma.com/file/IqwvzHvdDRDld8aGjwxNII/v2-dApp-Master-file-(Copy)?type=design&node-id=12556-119455&t=EHefMeetvTAKF9lR-0

In the Redemption workflow, remove the FATF countries from the list.

If 2 variants have been added, and one is removed, the option to add information for one variant is no longer available.

1. Check if the protocol records the dates in UTC
2. Align on whether the UX should show time zone chosen or UTC

The storefront feature has some fields that were needed for Brandverse and can be removed from the main experience.

As a Seller, I shall be able to extend the Dispute Timeout of a dispute that is in Resolving status.
Note: the command shall be available only for the seller of the disputed exchange.
The core-sdk methods extendDisputeTimeout()/signMetaTxExtendDisputeTimeout() exist.
They expect the exchangeId and the new disputeTimeout (that must be greater than the current dispute period deadline).
Suggestion: propose by default to extend the dispute period by 15 days (newDisputeTimeout = current timeout + 15 days)

Engage the community by setting up reward tiers, that allow members to get a token which they can redeem for free Boson merch.

Keep size of boxes for royalties & wallet address to be the same length

Call out somewhere on the dApp that we are on Polygon

https://github.com/coinbase/coinbase-wallet-sdk

Help Section, the question currently reads 'What are tag used for?'

It should read 'What are tags used for?'

Add 'Coming Soon' label to Phygital option show at Offer create

https://miro.com/app/board/uXjVMIxZhwM=/

As a seller, if my wallet owns several LENS tokens, I should be able to switch from a token to another one
This will call updateSeller() protocol method to change the authTokenId of the seller account

Add a conditional * to royalty payment address

During offer create, when defining the variants, the token box gets cut off.

https://docs.lens.xyz/docs/sdk-react-getting-started

Let's consider an offer with a quantity of 100
The seller is preminting 40 vouchers
The other 60 items are available through the dApp.
However the dApp shows the remaining quantity is 100 (but formally only 60 of them can be committed via the dApp)

images that can be changed by the user should be protected against XSS and/or HTML injections, one way to do so is to use pointer-events: none on all img tags

Give Sellers the ability to easily re-list an offer after it has expired

check uniswap website

potential for a malicious user to DDOS our app when creating a custom storefront

When you log in as a Seller (specifically the assistant) and you navigate to the Dispute page, then you can see disputes for other sellers, we should filter these accordingly so one can only see the relevant ones.

As the tokenID is no longer equal to the exchangeID, the dApp should fix that when building the opensea link for an existing exchange

see similar issue already fixed on boson-dcl bosonprotocol/boson-dcl#63

In seller creation/update modals:

Communication channel preference
Set up how you want to communicate with the buyer after redemption
Email/XMTP chat (dropdown options)

(copies to be confirmed)

if email is selected, the email must be mandatory in redemption modal, otherwise optional (right now it's always mandatory)

xmtp flow should not be changed: communication via xmtp should still be possible

the offer should also have this contactPreference set to that value

Issue for sell everywhere release, introduction of sales channels.

Figma: https://www.figma.com/file/IqwvzHvdDRDld8aGjwxNII/v2-dApp-Master-file-(Copy)?type=design&node-id=12388-116025&t=NqfwWkgkdhIIgBTc-0

Hi @albertfolch-redeemeum ,

Here are the revised product create FAQs.

Miro Board: https://miro.com/app/board/uXjVM9RcqU4=/
shows which FAQ in which screen

Doc: With the FAQ text if it is easier for you (same content in Miro)
https://docs.google.com/document/d/1Rg696iCLB0cuAxrzdYv9k02xYcfPxUSQp64J9mg9otM/edit#heading=h.xsplotbzigxm

At the moment, the Retract button is only shown for an exchange that is Disputed and not Escalated
It should be possible to Retract even if the Dispute is Escalated

@sukrita3

Allow Sellers to preview their profiles before creating their account.

On the exchange widget, rename Raise a problem to Raise a dispute

We need to ensure that all of the external links from the interface do not allow for malicious links to be linked to to tabnap.

In order to fix this issue you can simply add noreferrer and noopener values to the rel attribute on the link.

    <a href="https://www.google.com/" target="_blank" rel="noopener noreferrer">External link</a>
noopener
rel="noopener" prevents a new page from being able to access the window.opener property, which will stop things like the new page redirecting to a malicious URL.

noreferrer
rel="noreferrer" has the same effect as rel="noopener" but also prevents the Referer header from being sent to the new page.

Have a consistent image / offer card experience on the dApp.

https://miro.com/app/board/uXjVME7vWks=/

Buyers can still raise a dispute after the dispute period has ended. The MR dispute reaches the Seller, with available CTAs. When a Seller clicks the CTA and attempts to sign a transaction, the transaction fails (just spins).

first suggestion of links in the footer:

Buy
Explore
Chat
Dispute

Sell
Create Product
Create Storefront
Chat
Dispute

investigate #533

Following meeting about legal aspects and tech catch-up, we assume:

• we are following a whitelisting approach
• the whitelist will be managed as a hosted file (not a production variable as now - REACT_APP_SELLER_CURATION_LIST), so that upgrading the whitelist does not require to rebuild / redeploy the dApp
• the whitelist applies to every rendering action on the dApp: if the seller X is NOT in the whitelist, rendering the seller X profile page (.../#/seller/X), or any of their offers / products should not be possible, EXCEPT for the seller itself (based on the connected wallet):
  • #/account/X: list of Offers must be empty if X is not in seller whitelist and not currently connected
  • #/seller/X: is not rendered if X is not in seller whitelist and not currently connected
  • #/products/N: is not rendered if the product N's seller is not in seller whitelist and not currently connected
  • #/offers/O: is not rendered if the offer O's seller is not in seller whitelist and not currently connected
  • #/offer-uuid/U: is not rendered if the offer U's seller is not in seller whitelist and not currently connected
• a custom storefront brings its own seller/offer curation list as query arguments. However it won't be possible to render any seller/offer/product/exchange related to an offer of a not whitelisted seller. In other words, the custom storefront offer/seller curation list comes after the "main" whitelist to reduce the scope of the custom storefront compared to the original dApp.

Cannot upload same video already used in a previous listing. Video is in mp4 and below size requirement

add "A deposit is not mandatory and is up to you as the seller to set one or set it to 0."