The number of NEAR that a person will receive when Unstaked his stNEAR tockens is not displayed if you press the "max" button.
In order for it to be displayed, you must enter quantity manually. After this it it will displayed.

NB:
OB = OBSERVATION
EXP = EXPECTATION

1. OB:

• Wallet automatic lock time seems very short.

EXP: Wallet lockout time should persist some time longer (maybe 30 mins or till system shut down)

2. OB:

• On page reload of https://www.narwallets.com/dapp/testnet/meta; the Dapp get disconnected and Wallet is again automatically locked out

EXP: On page reload of https://www.narwallets.com/dapp/testnet/meta; the Dapp should remain connected and Wallet not automatically locked out

3. OB:

• Liquidity Providers: when the LPs button is clicked; the asynchronous request has no feedback

EXP: Liquidity Providers: when the LPs button is clicked; the asynchronous request should show user a visual processing feedback upon loading

4. OB:

• The label for the adding liquidity Input field specifies a Max number of Near (with a reference to total Near balance in account)

EXP: The label for the adding liquidity Input field could specify a Minimum requirements so User is aware in order to avoid showing 'Add at least {Near #} errors message' upon submission

5. OB:

• When I passed in 100.-1 as quantity to Liquidity; I get error as "panicked at: 'Failed to deserialize input from JSON.: Error(\invalid digit found in string, line: 1, column: 36)'"

EXP: I expect a simple error message as : "Input value not valid' instead of a stacktrace - (line: 1, column: 36)

6. OB:

• Validator Stake Loan Request: Validator Stake Loan button when clicked has no visual feedback for async call

EXP: Validator Stake Loan button should show user a visual processing feedback upon loading

7. OB: The Request Draft

• Modify Request Data form should specify minimum committed fee.
• Modify Request Data form should define the a unit of Epoch is and also specify minimum committed fee Duration.
• Modify Request Data form should explain the what Information URL refers to.

8. OB: Unstacking
9. When I unstacked any amount of stacked NEAR; I get a feedback without a timeline

EXP: I want to see the specified hours (eg 50hrs) count down feedback

On NEAR web wallet, NEAR balance doesn't change after staking and stNEAR is always 0.

On metapool staking page, the balances are correct.

Two feedback about user experience ① after adding mobility, it will automatically jump to the main page, which will not be the case for other operations. If I want to add mobility again, I need to click this page again. ② I click the wallet without any response. I can't copy the wallet address or disconnect the link of the wallet. It's very inconvenient.

1. You guys can change the word below, just "Not enough balance". It will make UX much better https://prnt.sc/10rntu2
2. You should add some features to let users know how much fee they will gonna cost. Just a simple method but very useful to make a better experience for users https://prnt.sc/10rnxku
3. Available https://prnt.sc/10rnxku
4. I expect to see the stNEAR to be shown on near wallet, it might need in some situation https://prnt.sc/10roqld
5. It should have some kind of feature or number that let users know how much $META token is minted, for example using APY like others blockchain. It just a suggestion. https://prnt.sc/10rot9s

I have implemented ability for my contract to manage staking with metapool.
It is actually quite cumbersome, so I propose an easy fix to make this straightforward for others to integrate.

Problem:

1. You need to get your stake balance to know what your balance is to liquid unstake (not a problem IMO)
2. You need to understand what amount is available so you can compute min_expected_near as it is required here: https://github.com/Narwallets/meta-pool/blob/master/metapool/src/lib.rs#L553-L557, for now I am using: https://github.com/Narwallets/meta-pool/blob/master/metapool/src/lib.rs#L534 but more callbacks makes expensive
3. Once I know both balance and min_expected_near I can do the final call to liquid_unstake

My problem is more with efficiency, if I was able to get the min_expected_near of the total staked during the balance call, id be able to compute a ratio to calculate all other liquid unstake amounts.

Solution:

1. Add min_expected_near_total to the response of https://github.com/Narwallets/meta-pool/blob/master/metapool/src/owner.rs#L163
2. Add liquid_unstake_fee to the same response ^^, which allows for any other amount of st_near to be computed for accurate NEAR transfer (I want 5 NEAR, how much st_near does that actually mean?)

Open MetaMask
Connect on it
Select BSC chain or another one and go on https://metapool.app/dapp/testnet/metapool-aurora/

Autodetect wrong chain and ask with a popup to switch chain

I have 0STNEAr in my balance
I try to stake 66

Maybe change "in buffer" by "in balance", "in account" or something like this.

Connect on with a account with nothing
Click on "Max" Button

Deployment costs per byte of code are going to be increased by a factor of ~5 with this change to NEAR protocol: near/nearcore#6397

Probably this will happen with protocol version 53, which would be released on testnet by March 23 and on mainnet by April 20.

I listed all the indirect deployments from the past that would fail with the new cost. Deployments of meta-pool.near have showed up 10 times in this list, for example this transaction. Meaning that your current setup for redeploying might break with the planned increase of deployment cost.

It looks like migration currently reserves exactly 20Tgas, as defined here.

Now, I don't know how large your contract is exactly, which is the key factor. 20Tgas is only enough to cover deployment of a 274kB contract under the new costs. And not all 20Tgas is actually available, some will be used for executing the function. So the real maximum contract size will be smaller.

Please check if my understanding is correct that this will break you remote-update mechanism and if you can update your deployed contract before the protocol version 53 is released. I am not familiar with all the details of your contract but I am happy to assist in solving any problems caused by this. I am also available to answer any questions you might have, for example on Zulip

I tried withdrawing 0 stnear using the liquid unstake feature and got a weird code. I have no problem with this as a dev but what about the average internet user?

Open MetaMask
Connect on it
Select BSC chain or another one and go on https://metapool.app/dapp/testnet/metapool-aurora/

Bug: Signout button visible

Expected : No Signout Btn

How does meta-pool prevent a malicious operator / owner from setaling coins via a malicious staking pool? A attack vector i'm thinking of:

1. A malicious actor gets voted in as an operator
2. The owner creates malicious contract that implements the staking pool NEP. The malicious bit is deposit simply increases their balance in the staking pool, regardless of the sender. And withdraw only ever withdraws to the attacker's address
3. The owner adds the staking pool to the list of staking pools in metapool, and overweights it in the following line:

4. When people run ping or stake, then coins are "stolen" into the malicious staking pool that implements the NEP, but is otherwise malicious

I feel like I'm missing something - or is such attacks simply possible?

Use new tab instead of current tab for the link.

Example: https://metapool.app/Tokenomics__Governance_-_Meta_Pool_v4.pdf, https://metapool.app/legal-notice-risk-disclosures.html etc

There's a point where all those accounts are read into memory, updated (sell, fees, etc) and then stored again.
IF any one of those accounts is the same as another, the latest account to be stored will write-over other changes.
Solution: Ensure user|operator|treasury|developer are all DIFFERENT ACCOUNTS