Crescent

Orderbook DEX

Proposal Details

Proposal #87

Passed

Proposal title

Approve Stakely.io as Crescent Liquid Staking Validator

Submit time

Deposit end time

Voting start time

Voting end time

Tally result

86.25%

Proposal #87 description

According to the last announcement for adding a new Liquid Staking Validator, we had got an LSV application form for 2 weeks. Based on the scoring system that we opened and discussed on the commonwealth, we extracted the top 3 candidates out of 13 candidates.

Voting YES to this proposal means that you approve ‘Stakely.io’ to be adopted as a new liquid staking validator.

only YES votes will be counted. Voting NO, NO WITH VETO, or ABSTAIN will have no effect on which candidate is adopted. (However, when the number of the voting amount is significantly different among each candidate, No votes can be reflected)

Voting procedures summary:

  • Existing LSV should not vote, and votes by existing LSV will not be counted for this proposal
  • Only one candidate that receives the highest number of CRE for ‘Yes’ voting, can only proceed to the next step
  • The final validator needs to be agreed upon via on-chain governance(existing LSV need to vote)
  • New LSV is added upon the passing of the governance proposal

Link to the docs for all candidates scoring:

https://docs.google.com/spreadsheets/d/1s8O1O_q_byugOOznhhUPQo9IM2YGxNbG/edit?usp=sharing&ouid=103096296126293453015&rtpof=true&sd=true

Here’s the scoring system that was discussed before: https://commonwealth.im/crescent-forum/discussion/5199-discussion-liquid-staking-validator-scoring-system

Qualitative Scoring Criteria submitted by Stakely

How will you contribute to the Crescent Ecosystem in the future?

:We commit to providing detailed and up-to-date information about Crescent on our website, as well as facilitating staking tutorials and tutorials on the main Crescent tools, and answering any major questions that users may have about Crescent, both through our FAQ section and by providing support in our English and Spanish communities. Currently, we provide support and create content in both English and Spanish, but we will open a community in French and translate Crescent-related content into French to also bring Crescent to the French-speaking community. We always vote on all governance proposals and we make all of our community aware by communicating our decisions via Twitter. We also have an RPC/LCD endpoint load balancer service. It aggregates several public and private nodes and the requests are routed among them. This service has many features like health checks, retires on errors and 10s timeouts, CORS-enabled requests, caching, etc. We could integrate Crescent into it if the team thinks it would be helpful. Another service we provide is a multi-coin mainnet faucet, where we currently have Crescent integrated (https://stakely.io/en/faucet/crescent). This service distributes a small amount of mainnet tokens to the users that have run out of gas. It can help bring more people to the project and improve the network's user experience. We will continue maintaining this service and refilling the faucet with our own funds. We can deploy a testnet faucet if needed too.

What is your long-term plan to sustain the Crescent node?

:We estimate that the rewards obtained from delegations will be enough to pay for the maintenance of the validator. There are other income sources that we can study, like offering archive RPCs and white-label validators. In case running the validator is not profitable in the future, we have enough income from other networks to continue maintaining it.

Infra specs and operation specs

:Our Crescent validator runs on a bare metal server in Tokyo with the following specifications: CPU: Intel Xeon E-2286G - 6c/12t - 4 GHz/4.9 GHz Memory: 32GB Storage: 2 x 1TB SSD Raid 1 Bandwidth: 1000 Mbps We also have a full-node running for redundancy that we will use in case of any issues. It has the state-sync feature enabled which will help in case we needed to launch a new server. We have previously used tools like TMKMS but we decided to stop using them due to latency. We have also heard about Horcrux in the last months, and we are discussing using it in our setup. We use Prometheus, Zabbix, Grafana, and custom scripts for our monitoring system.

**For more details, qualitative answers can be found here :**https://docs.google.com/document/d/1F1lxjAP77ZkBdMFH6HMjP7HZGuHFnY05PJfGZdI63bM/edit?usp=sharing ****

Proposal #87 overview

Total votes
527
Voters
458
Total deposit
2,000 CRE

Proposal #87 votes

#

Validator

Account Address

Options
1Frens (🤝,🤝)Abstain
2StakeflowAbstain
3Klub StakingAbstain
4🙏 uGaenn ⛅Yes
5Bro_n_BroYes
6jabbeyAbstain
7Lex_PrimeYes
8Simply StakingAbstain
9blockscapeYes
10Citadel.oneAbstain
11DSRVAbstain
12apploadNo
13ForboleYes
1401nodeAbstain
15Nodes.GuruAbstain
16CosmostationAbstain
17Shutdown - please redelegateAbstain
18天照☀Yes
19✅ CryptoCrew Validators #IBCgangNo
20ProvalidatorAbstain
21REDELEGATE PLZYes
22GPSYes
23JustLuckYes
24OldcatAbstain
25noneAbstain
260% fees 🚀 | BlueStakeAbstain
27StakeLabAbstain
28Cosmos CatsAbstain
29Please redelegateAbstain
30Imperator.coAbstain
31Stakin | Discontinued | RedelegateAbstain
32Stakewolle.com | Auto-compoundAbstain
33AutoStake 🛡️ Slash ProtectedAbstain

View: