Add p2p.org as Staking as a Service Provider to the website #11279
Labels
content 🖋️
This involves copy additions or edits
feature ✨
This is enhancing something existing or creating something new
needs triage 📥
This issue needs triaged before being worked on
Project name
P2P.org
Product type
Staking as a service
If other product type, please describe
No response
Logo
Description
P2P.org provides secure non-custodial staking services for professional investors.
Website
https://p2p.org/networks/ethereum
If software is involved, is everything open source?
Portions of code are open source:
https://github.com/p2p-org/p2p-eth2-depositor
https://github.com/p2p-org/eth-staking-fee-distributor-contracts
Is the project a fork? If yes, which project was forked?
No
Is the product out of beta development?
The product is out of beta and in production since January 2023 and actively maintained by p2p.org development team.
What wallets support the product or service?
MetaMask, Safe, Ledger, Trust, MetaMak Mobile, WalletConnect
If the product or service enables staking with <32 ETH, what is the minimum ETH required to stake?
Minimum amount is 32 ETH.
If a service, what are the fees associated with using the service?
The fee is 5%.
If the product or service involved a liquidity token, what are the tokens involved?
No response
What date did the project or service go live?
Since January 10th 2023, two weeks after our first depositor contract have passed it's security audit
Has the project undergone an external security audit?
First security audit of depositor smart-contract (Dec 2022) https://github.com/mixbytes/audits_public/blob/79cd8153bfb6098227b43dfba8d061881a94a248/P2P.org/ETH2%20Depositor%20%26%20ETH%20Staking%20Fee%20Distributor%20(v.1)/P2P.org_ETH2%20Depositor%20%26%20ETH%20Staking%20Fee%20Distributor%20Smart%20Contracts%20Audit%20Report.pdf
Second security audit of renewed depositor and fee-divider smart-contracts (April 2023)
https://github.com/mixbytes/audits_public/blob/79cd8153bfb6098227b43dfba8d061881a94a248/P2P.org/ETH2%20Depositor%20%26%20ETH%20Staking%20Fee%20Distributor%20(v.2)/ETH2%20Depositor%20%26%20ETH%20Staking%20Fee%20Distributor%20Security%20Audit%20Report%20(v.2).pdf
Has the project undergone any security bug bounties?
No, we don't have bug bounty.
Is the project being actively maintained?
Yes
Is the product or service free of trusted/human intermediaries?
Yes, the product is free of trusted/human intermediaries. No KYC.
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 sign-up needed.
If listing as staking-as-a-service, who has access to the signing keys?
And from perspective of signing keys no one in P2P have access to whole key. Each key is split 2-of-3 Threshold schema, and each part is completely isolated from each other (no one in our team has access to the whole key and keys are stored separately in infrastructure repositories). Client have no access to the signing keys.
If a pooled staking service or SaaS provider, what type of withdrawal credentials are being utilized / who holds the withdrawal keys?
We use ETH address as Withdrawal credentials. Usually the withdrawal address is the same as from one the client is signing their deposit transaction. But he can enter a separate withdrawal address in the options before requesting deposit data. We also support Eigenpod instance as withdrawal address. As our service are non-custodial, the client only give us their withdrawal credentials.
Regarding withdrawal keys — we don't use BLS addresses so no withdrawal keys are involved in the operations. But even if we'll be able to accept BLS as withdrawal credentials, we'll be only need for the address, not the keys.
If a pooled staking service or SaaS provider, what percent of node operators are running a super-majority client?
For all our validators we use 3 CL (Lighthouse, Teku, Prysm) & 2 EL (Besu, Geth). We're planing to extend to 4 CL and 4 EL operators in the future.
If listing node or client tooling, which consensus layer clients (Lighthouse, Teku, Nimbus, or Prysm) are supported?
No response
What platforms are supported?
Linux, macOS, Windows, iOS, Android — any platform with a Browser and supported wallet
What user interfaces are supported?
Browser app (desktop & mobile ready)
Social media links
Twitter https://twitter.com/P2Pvalidator
Telegram https://t.me/P2Pstaking
GitHub https://github.com/p2p-org
YouTube https://www.youtube.com/channel/UC9pRzyJx5YrUNfmg1vLZ-bQ/
LinkedIn https://www.linkedin.com/company/p2p-org/
Would you like to work on this issue?
The text was updated successfully, but these errors were encountered: