First off, I hope everyone on the team is doing well and I hope the conflict in Ukraine ends soon with Ukraine's victory.

I've read your stance on token whitelist, and this is not a request to whitelist a token in particular, but I was hoping to get clarification on an inconsistency that I've noticed between v1 version and the current version.

To the best of my knowledge the v1 uses this whitelist I'm going to use Materia as an example which is on the line 422 on the link above).

On v1 fill the box of the output that says "Enter token name or contract address..." and type "mate" your auto complete shows the token MTRIA.

If you try to do the same on the current version it doesn't show up on the autocomplete leaving me thinking that the token is not whitelisted or that might be a bug. This issue is on the event that this is a bug and not a request to whitelist it.

Steps to reproduce:

1. access https://quipuswap.com/
2. press "Start Trading" from the "Trade Any Tezos-based token box
3. you are taken to this url press QUIPU box on the To field and type "mate" the auto complete doesn't show the token.

And if you explicitely add the KT1 you see this warning saying its not whitelisted:

At this point, if I click on MTRIA and search for it again it doesn't show. I suspect it doesnt show because its already selected (a better UX will be having it show, but have a disabled state to indicate the user can't choose it because its already selected).

Further more, if I change to another token instead of MTRIA, and search again the token displays. So I'm thinking this is likely a bug.

On PAGE https://docs.quipuswap.com/baker-rewards-lite-version

Thereby for a longer period with different multiple durations but stale constant total supply and user shares during the period the wollowed following formulas can be applyed applied:

/GRAPHICS 2/ —> MISSING

At point B the rewards per second should be changed however in the contract it only happens at point C when the Bob invested more liquidity, incremented the total supply and updated the conrtact contract state. As there are more shares in the pool than according to (4), with stale reward per second reward per share will increase slower.

At point D the curve slightly cahnges changes as the reward per second is recalculated based on the rewards collected during the cycle.
…
Considering the users' reward alter (???), total reward linearly grows all the time after the first cycle has ended.

….
Bob's rewards start to be assesed assessed at point C because the user doesn't have any shares before and thus can't get any reward.

Older FA1.2 tokens have been created with their token metadata included in the "metadata" bigmap and not in a dedicated "token_metadata" bigmap (the specific token_metadata was later added in TZIP12 for FA2). Though this token_metadata specification request has been retroactively introduced in TZIP7 (which is highly debatable for what is supposed to be a standard), it is not possible to redeploy historic tokens. Therefore, it would be useful that Quipuswap handle the token metadata stored in the generic metadata bigmap. Thanks for your help for this. If needed we can work on a merge request.