Developer feature proposal: Displaying the project validators in the list of validators

[Solniechniy]

Story

There is an announcement about project validators that will validate and give a possibility to farm tokens. The proposal in changing the UI of validators in order to show additional project-validators information.

Acceptance Criteria

[ ] Change the logic of near wallet to parse two types of validators: project validators and simple one [ ] Create new component for displaying project validator with tooltip where additional info will be shown [ ] Add possibility to claim tokens on the staking page

[Solniechniy]

• In order to change the render component, we should type the project validators and others validators. By which criteria we should differ the project validator on the frontend from the simple one?
• Is there any project validator running on testnet?

[referencedev]

• I suggest there is a decision on deploying the factory under some account name, something like poolv2.near which is taken. Then determining the type will be done via prefix match .poolv2.near.

• There is one here - validator2.factory01.littlefarm.testnet

[Solniechniy]

@referencedev Ok, so we will make a decision based on prefix match .poolv2.near.

• There is one here - validator2.factory01.littlefarm.testnet

Does it actually returned by the indexer with the list of all validators? I've been created validator3 and didn't see any

[ilblackdragon]

Let's use pool.near for new factory given it will allow to manage upgradable contracts and doesn't need version identifier. Thanks to community member for reserving it.

[Solniechniy]

@ilblackdragon Got it. Is any information on how to get the project validators list? Will it be with return with common validators?

[ilblackdragon]

All validators, independent of which contract they are using, that have submitted the proposal will show up in proposals RPC request.

If you are creating a new validator - it needs to have minimum stake (10k $NEAR I think or something like that) for staking proposal to go through.

[Solniechniy]

@ilblackdragon so the proposal should be sent to https://reskin-testnet.sputnik.fund/select-dao in addition to adding a test validator to the list of all validators?

[Solniechniy]

@ilblackdragon For getting any information about the user and future development there are two ways, as I understand

1. Deploy to mainnet, whitelist the contract, create validator and then submit a proposal
2. Create a validator on testnet and submit the proposal So if the difference is only on deploying and whitelisting, should we proceed with mainnet?

[ilblackdragon]

Staking proposals are sent by the contract itself, when there is enough stake on the contract. Yes, this all can be setup on mainnet early next week.

[stefanopepe]

@Solniechniy how's the progress of this on Testnet?

In order to proceed, we need to build a few tests against:

• a small set of validators running this new type of pool
• a small set of users adopting these pools and receiving rewards

By now I can see only https://explorer.testnet.near.org/accounts/validator2.factory01.littlefarm.testnet - do we have more than one?

[Solniechniy]

@stefanopepe we've been trying to set up a new testnet validator but always have different troubles with it. If you will have a possibility to run any testnet validator with a new type of pool it will be helpful.