Should we set prefixed amounts for users to deposit?

[acuarica]

Migrated from card https://github.com/Ethernautas/renpool/projects/1#card-66247820

Instead of allowing the user to insert any amount to deposit, they should be presented with a set of predefined amounts to choose from, for example, 5k, 10k, 20k, 25k.

This could be set on pool creation. For instance one pool might be for 5k deposits, while other might be for 10k and so on.

[acuarica]

I've moved this to the app repo. I assume that this feature is part of the client: the contract itself allows a user to deposit any amount, including decimal. Is this correct @fede-rodes?

[fede-rodes]

I think this is a feature that should be implemented in both the front and backend (users could bypass the FE). Also, this is related with the kind of approach we want to follow. In case we go the Lido way, no minimum amount should be required. However, if we allow users to deploy their own pools, then we should probably set prefixed amounts to avoid situations where small amount are missing to complete the pool target (no one will be willing to pay a high transaction fee to deposit a small amount of tokens just to fulfill the pool)

[acuarica]

I see it more on the client side. The contract does not need to know how much is missing to complete the pool. To remediate the small amount issue, at most we could define that the last deposit, i.e., the one that locks the pool, should be greater than some amount.

But on the client we could have some predefined values to select from and no decimals.

[fede-rodes]

ok, let’s iterate over this to understand what other options we have