Prop 225: Approve AutoStake as Crescent Liquid Staking Validator
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 9 candidates.
Voting YES to this proposal means that you approve ‘Autostake’ 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:
Here’s the scoring system that was discussed before: : https://commonwealth.im/crescent-forum/discussion/11043-the-feedback-period-for-lsv-candidates-scoring
Qualitative Scoring Criteria submitted by Autostake
How will you contribute to the Crescent Ecosystem in the future?
:1. Big IBC Relayer https://ibc.autostake.net we are also in a somewhat unique position to add to our dedicate SecretNetwort IBC (strict hardware requirements 2. Daily pruned mainnet snaphots: https://snapshots.autostake.net/chain-1/ 3. Daily updated addrbook: https://snapshots.autostake.net/chain-1/addrbook.json 4. State-sync server: chain-mainnet-rpc.autostake.net:443 5. Testnet nodes and snapshots snaphots 6. Seeds nodes: https://snapshots.autostake.net/chain-1/seed.txt 7. Peers for all the chains we validate: https://snapshots.autostake.net/chain-1/peer.txt 8. Auto-Compounding staking: https://wallet.autostake.net 9. Explorer: https://explorer.autostake.net/ 10. LCD/REST API for all chains we validate: https://chain.mainnet.lcd.autostake.net:443 11. RPC for all chains we validate: https://chain.mainnet.rpc.autostake.net:443 12. gRPC for all chains we validate: https://chain.mainnet.grpc.autostake.net:443
What is your long-term plan to sustain the Crescent node?
: We are already self-sustaining
Infra specs and operation specs
: How is the validator key protected? We use a form of Secrets Management, so that the key is encrypted and only available to the validator process. How do you protect your servers? The normal stuff but quick overview: * External hardware firewall & internal software firewall (SSH port has whitelisted ip's) * Automatic security updates * Non-root users (including applications) * Yubikeys + 2FA where possible (SSH, Git, etc) Do you operate sentries? We do not believe this is effective architecture and it just adds latency and complexity which is an enemy; instead we prefer to have many standby backup nodes distributed across many different hardware providers and regions. Do we use Horcrux or Tmkms? Why Secrets Management over HSM? Again similar to the sentries this adds latency and complexity; and we have decided because of this is actually increases risk rather than diminish it; that being said this is still something we think about a lot internally and is under constant consideration. What monitoring & alerting tools do we use? We use all of the below stacks: 1. Prometheus + Grafana + Alertmanager 2. Panic Cosmos 3. Tenderduty