-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Description
Project name
Serenita
Product type
Staking as a service
If other product type, please describe
No response
Logo
Description
Serenita is a staking service provider specialized in Ethereum with a primary focus on minimizing risk.
Website
If software is involved, is everything open source?
Yes, everything is open source: provide link(s) to project repo(s)
Smart contracts: https://github.com/stakewise/v3-core
UI: https://github.com/stakewise/vault-interface
Is the project a fork? If yes, which project was forked?
No
Is the product out of beta development?
Yes, we've been operating mainnet validators professionally since 2023.
What wallets support the product or service?
No response
If the product or service enables staking with <32 ETH, what is the minimum ETH required to stake?
N/A
If a service, what are the fees associated with using the service?
We charge a base fee of 5% of the staking rewards which is automatically deducted on the smart contract level.
If the product or service involved a liquidity token, what are the tokens involved?
N/A
What date did the project or service go live?
2023-11-28 . Proof https://x.com/SerenitaIO/status/1729533995921072513
Has the project undergone an external security audit?
The underlying smart contracts have undergone multiple security audits which can be found here: https://github.com/stakewise/v3-core/tree/main/audits
Has the project undergone any security bug bounties?
There is an open bug bounty program for the underlying smart contracts: https://immunefi.com/bug-bounty/stakewise/information/
Is the project being actively maintained?
Yes
Is the product or service free of trusted/human intermediaries?
It's as trustless as it can be at the moment.
- Serenita never takes custody of customer funds - these only touch the Vault smart contract and cannot be extracted.
- Withdrawing ETH is possible even if we, at Serenita, do not cooperate. Pre-signed exit messages are split among 11 StakeWise oracles which can trigger validator exits if requested by the customer. A future update will enable the use of the recently introduced EL-triggerable exits at which point even the oracles won't be needed.
If a pooled staking service, can users participate as a node operator without permission?
No response
If listing a staking-as-a-service, are users required to sign-up for an account?
No
If listing as staking-as-a-service, who has access to the signing keys?
Serenita operates the entire staking infrastructure, this includes the validator private keys. Noone else has access to these.
The customer remains in control of the depositing address which can trigger a withdrawal at any time.
If a pooled staking service or SaaS provider, what type of withdrawal credentials are being utilized / who holds the withdrawal keys?
0x01 withdrawal are used which point to the smart contract that distributes rewards.
If a pooled staking service or SaaS provider, what percent of node operators are running a super-majority client?
0%!
We are a pioneer when it comes to reducing the impact of client bugs and exclusively use client-diverse multi-node setups powered by the Vero validator client. This means none of our validators are exposed to any single-client bug, and we plan to reduce client-bug risk this even further.
On a related note, I believe this would be a good candidate for another criterium on your website – is the staking service provider using multi-node bug-resistant setup? Happy to help define this further, if you want to learn more about Vero check out the talk I did at EthCC recently.
If listing node or client tooling, which consensus layer clients (Lighthouse, Teku, Nimbus, or Prysm) are supported?
No response
What platforms are supported?
All platforms
What user interfaces are supported?
Browser
Social media links
X: https://twitter.com/serenitaio
GitHub: https://github.com/serenita-org
TG: https://t.me/+LjdyzOcSsLhkNjg0
Would you like to work on this issue?
- Yes
- No