Affordances for rate limiting posts and minimum eth balance

[sachben91]

Description

Based on the decision in #8268 , we have decided to rate limit number of posts that a user can make within a contest, along with requiring that every participant in a contest has a non dust value of eth (> 0.0005). This ticket addresses the user affordances related to this change.

Project Owner

No response

Bucket ID

No response

User Stories / Acceptance Criteria

• When a user attempts to submit a third post to an active contest within a topic, the "create thread" button should be disabled and the reason communicated to the user as shown below

• If a topic has more than one contest, then the user should be shown which contests they are eligible to submit entries to and which ones have reached the rate limit of two posts per contest

• If the wallet that the user has connected has less than the non dust value of eth required, they should be shown the following message below the text box

Design Devlink

designs

Design Screenshot

No response

Additional Context

No response

[sachben91]

related ticket #8466

[timolegros]

@sachben91 just checking in on the affordances for admins creating contests and potentially crippling their communities by selecting the wrong topics. Also shouldn't the copy for the token warning say "with at least 0.0005 ETH" rather than "tokens"?

[sachben91]

@timolegros creating a separate ticket for the admin affordance and yes thanks for the catch, will change that to 0.0005 eth

[sachben91]

Related ticket #8474

[masvelio]

@sachben91

1. The designs are based on the updated new thread page while we still have old new thread page. The main difference is that we want to show Insufficient balance error below the user address dropdown, however, we don't have possibility to select the address currently in this view.

In this case we should either :

• allow user to click create button but then throw the toast error
• disable create button and place the insufficient balance "inline error" somewhere in the form

Below is comparison between new vs current design for more context:

NEW DESIGN

CURRENT DESIGN

2. For those two points:

When a user attempts to submit a third post to an active contest within a topic, the "create thread" button should be disabled and the reason communicated to the user as shown below

and

If a topic has more than one contest, then the user should be shown which contests they are eligible to submit entries to and which ones have reached the rate limit of two posts per contest

we need a backend logic from @rbennettcw. Basically, when we load new thread page we need to be able to display the data right away. Ideally for FE, we should extend GET /topics endpoint. We would need structure like this:

  topics: {
    //existing
    topicId: number;
    topicName: string;
    // added (only active contests)
    contests: { 
      contestId: string;
      contestAddress: string;
      contestName: string;
      submittedEntries: number;
    }[];
  }[];

TLDR:
@sachben91 => let me know whats the decision on point 1
@rbennettcw => let us know if point numer 2 works for you

[sachben91]

@masvelio @jessmart1213

disable create button and place the insufficient balance "inline error" somewhere in the form
I think this would be ideal solution because the information is really important. Perhaps the inline error can be under the "topic has ongoing contest" banner and to the left of create thread - Leaving this to jess

[sachben91]

@masvelio ticket has been updated