Remote procedure call (RPC) is one of the critical tools of the blockchain ecosystem. With the help of RPC, it is possible to implement almost any service based on blockchain data.
Decentralized applications (dApps), require access to a huge amount of information from the blockchain. This can be in the form of historical data, transaction history, node connections, block numbers, etc. and to access this data, it is necessary to query the blockchain.
There are several reasons why having a dedicated RPC node is a good idea:
Overall, running your own RPC Ethereum node can provide greater control, security, privacy, independence, performance and compliance for your specific needs.
However, doing it yourself would require a lot of DevOps team resources. Not only for deploying the solution, but also for further maintenance. That's why it's often better to turn to professionals on this issue. P2P can help you maintain your own dedicated nodes with low latency, with servers in the US, EU and Asia Pacific. You get the benefits of a dedicated machine without the headache of having to manage it.
There are several use cases for Remote Procedure Call (RPC) nodes in blockchain:
These are just a few examples of the many ways that RPC nodes can be used.
Typically, an RPC endpoint is a point on the network where a program sends RPC requests to access server data. With an RPC endpoint, you can easily perform operations that use real-time blockchain data in your dApp.
The appropriate software needs to be installed on a node in order to respond to RPC requests. RPC endpoints run on nodes connected to the blockchain service through which your dApp receives information for its users. Therefore, all RPC endpoints run on RPC nodes, and all RPC nodes have RPC endpoints.
Depending on your use case, the type of node you need will vary. RPC nodes can also be divided into two main types - full nodes and archive nodes. The difference is in the depth of history that the nodes keep.
A full node keeps the current state of the blockchain and contains all the data on the network except trace data for transactions beyond the most recent blocks.
An archive node is a type of node that stores the entire blockchain history. This allows the node to provide access to historical data and transactions, which can be useful for various purposes such as analyzing the blockchain's past performance or auditing the network's activity. These nodes typically require a large amount of storage and computational resources to run, as they must maintain a copy of the entire blockchain. They are also known as full archive nodes or simply archive nodes.
To sum up, an archive node is a full node that additionally maintains a database of historical blockchain states. Full nodes can calculate historical states, but archive nodes have the information readily available locally and have better performance for this type of request.
Blockchains use the JSON-RPC standard for RPC. Data requests are received and processed quickly by this system. JSON-RPC is a stateless, lightweight protocol for remote procedure calls (RPCs). Several data structures are defined in this protocol, along with rules for their processing. It is transport agnostic in that the concepts can be used within the same process, over sockets, over HTTP, or in various message-passing environments.
P2P is happy to provide assistance in deploying or maintaining your Web3 infrastructure. We will help you find the best configuration for your RPC nodes and address any infrastructure needs you may have. You'll get the benefits of a dedicated node without the headache of managing your own machine. Ideal for Dex's Financial services and dApps.
Contact us at [email protected]
<p>RPC nodes allow external applications to communicate with the blockchain network to execute commands or retrieve information. These nodes serve as a bridge between the blockchain network and external systems, enabling these external systems to interact with the blockchain. You can find a more detailed overview of this functionality at this link – <a href="https://p2p.org/economy/rpc-node/">https://p2p.org/economy/rpc-node/</a></p><p>In this article, we look at the differences between shared and dedicated nodes.</p><h3 id="shared-rpc-nodes">Shared RPC nodes</h3><p>Shared RPC nodes can be a cost-effective solution for accessing a blockchain network, as it eliminates the need for each user or application to set up and maintain its own node. The downside is that a shared RPC node may not be as performant as a dedicated node since the resources and processing power are shared among multiple users, leading to slower response times and lower overall productivity.</p><p>Shared nodes are often used by smaller organizations, developers, and individuals who need access to the blockchain, but do not have the resources to support a dedicated node. They are a cost-effective solution for those who need to make occasional or low-volume queries.</p><p>Advantages of a shared RPC node include:</p><ul><li>Lower maintenance costs: A shared node requires a smaller hardware and technical support investment, making it a more affordable option for organizations and individuals who need occasional or low-volume access to the blockchain.</li><li>Advanced Features: Some of these services may offer advanced features, such as data analytics and monitoring tools, making it easier to manage and monitor interactions with a blockchain network.</li><li>Fast Scalability: These services can scale to accommodate a large number of users or applications, making it possible to access the blockchain network at a large scale.</li></ul><p>However, it is important to note that shared nodes have some disadvantages, including:</p><ul><li>Reduced control over node configuration: Users have limited control over the configuration of their shared node, which may limit their ability to make changes to the node's settings, run custom scripts, and implement additional security measures.</li><li>Potential security risks: Sharing a server with other users increases the risk of potential security threats, as unauthorized access to the server could compromise the security of the node and its users.</li><li>Dependence on server provider: Shared nodes are dependent on the reliability and security of the shared server provider, which can be a concern for organizations and individuals who require a high level of security and control over their connection to the network.</li></ul><p>In conclusion, shared RPC nodes are a good choice for organizations and individuals who need occasional or low-volume access to the blockchain, and who have limited resources to support a dedicated node. These may include developers, small organizations, and individuals who need to build and test dApps or access data. In some cases, sharing a node is also an excellent choice for specific tasks that do not require a high level of performance. However, one should be aware of the potential security risks and limitations of using a shared node, and should carefully evaluate their needs and requirements before making a decision.</p><h3 id="dedicated-rpc-nodes">Dedicated RPC nodes</h3><p>Dedicated nodes are often used by organizations that require a higher level of security and control over their connection to the network. They are ideal for enterprise-level dApps, exchanges, wallet providers, and other organizations that need to access a blockchain network on a regular basis.</p><p>Advantages of a dedicated RPC node include:</p><ul><li>An unlimited number of requests: The main benefit of using a dedicated RPC node is the ability to handle unlimited requests, as the node is not shared among multiple users or applications. This allows the user to make as many requests as needed, without having to worry about the impact on other users or applications. This is particularly useful for applications or users with high volumes of requests, as it ensures that the requests can be processed quickly and efficiently, without the risk of slowing down or disrupting the network. Hardware is the only factor that limits performance. </li><li>Full control over node configuration: Users have complete control over the configuration of their dedicated node, including the ability to make changes to the node's settings, run custom scripts, and implement additional security measures.</li><li>High performance: Dedicated nodes have the processing power and memory necessary to handle high volumes of transactions and data. This is especially important for dApps and clients that require real-time data access and updates.</li></ul><p>However, it is important to note that dedicated nodes have some disadvantages, including:</p><ul><li>High maintenance costs: Maintaining a dedicated node requires ongoing investment in hardware and technical support, which can be a significant cost for some organizations.</li><li>Complexity: Setting up and configuring a dedicated node can be complex, requiring a high level of technical expertise.</li></ul><p>In conclusion, dedicated RPC nodes are a good choice for organizations that require a high level of security and control over their connection to the network, and that have the resources to support the ongoing maintenance and storage requirements of a full node. These may include enterprise-level dApps, exchanges, wallet providers, and other organizations that need regular access to the blockchain.</p><p>Nevertheless, maintaining the nodes yourself may not always be necessary. It is possible to order a dedicated RPC node service from third-party contractors, who specialize in providing blockchain infrastructure and support services. These contractors can set up and maintain a dedicated node on behalf of the user, offering a more convenient and cost-effective solution compared to setting up and maintaining a node in-house. Third-party contractors typically have the technical expertise and resources to manage and maintain dedicated nodes, providing a high level of reliability and performance. This can be an attractive option for organizations or individuals who want the benefits of a dedicated node but lack the resources or expertise to set one up themselves.</p><h3 id="conclusion">Conclusion</h3><p>In complex projects, both shared and dedicated RPC nodes can be used in combination, depending on the specific needs and requirements. For example, a shared node could be used for general-purpose requests, while a dedicated node could be used for more resource-intensive tasks or for handling high volumes of requests. This approach allows organizations or individuals to balance the benefits of shared nodes, such as accessibility and affordability, with the benefits of dedicated nodes, such as reliability and performance. By using a combination of both shared and dedicated nodes, organizations can create a scalable and flexible infrastructure that can meet the demands of their project and evolve as the project grows and changes over time.</p><p>It is important to seek advice from professionals when designing and implementing an RPC infrastructure, as they can help to ensure that the right solution is chosen. Professional consultants can help organizations or individuals understand the different options available, including shared and dedicated nodes, and can recommend the best solution based on factors such as cost, performance, scalability, and security. By working with professionals, organizations can avoid making costly mistakes and ensure that their infrastructure is set up correctly, which can save time and money in the long run. </p><p>P2P offers support in setting up or maintaining your Web3 infrastructure. We can assist in determining the optimal configuration for your RPC nodes and addressing any related infrastructure needs.</p><p>Contact us at [email protected]<br></p><p><br></p>
from p2p validator
<!--kg-card-begin: markdown--><h3 id="table-of-contents">Table of Contents</h3> <ul> <li><a href="#T1"><span style=" font-size:16px"> What is Ethereum (ETH) Staking? </span></a></li> <li><a href="#T2"><span style=" font-size:16px"> Why stake Ethereum (ETH) with P2P? </span></a></li> <li><a href="#T3"><span style=" font-size:16px"> What does the Ethereum (ETH) staking process look like?<br> </span></a></li> <li><a href="#T4"><span style=" font-size:16px"> Ethereum (ETH) staking guide </span></a></li> <li><a href="#T5"><span style=" font-size:16px"> P2P Ethereum (ETH) Staking FAQ </span></a></li> </ul> <h2 id="what-is-ethereum-eth-staking-a-namet1a">What is Ethereum (ETH) Staking? <a name="T1"></a></h2> <p>When staking Ethereum (ETH) we are supporting the network with the additional benefit of earning additional ETH! Ethereum uses “Proof-of-stake” (PoS) as a consensus mechanism, where validators are responsible for reaching a consensus on adding new transaction blocks to the blockchain.</p> <p>To stake Ethereum we need a minimum of 32 ETH. This is because each validator requires 32 ETH to set up and for this same reason staking can only be done in increments of 32 ETH. For example, someone holding 320 ETH will have to set up 10 different validators. Anyone can take part in this consensus mechanism, all we have to do is run a validator (or ask to run it staking-as-a-service provider like P2P.org) and deposit 32 ETH to a special smart contract to activate a validator. This act is called staking.</p> <h2 id="why-stake-ethereum-eth-with-p2p-a-namet2a">Why stake Ethereum (ETH) with P2P? <a name="T2"></a></h2> <p>P2P has been running Ethereum validators since the launch of the Beacon Chain, in December 2020 as part of Lido Validator set. We take care of all the server maintenance and set-up.</p> <p>P2P's Ethereum staking solution is completely non-custodial and each validator is personally set up so there is never any comingling of customer's funds throughout the process.</p> <p>Those that choose to stake with P2P can also benefit from our insurance coverage against slashing events.</p> <p>In short, the benefits are:</p> <ul> <li>High performance and uptime</li> <li>Slashing insurance</li> <li>Personal staking dashboard</li> <li>Secure non-custodial staking</li> <li>Experienced DevOps team</li> <li>Part of the LIDO validator core set since inception</li> <li>24/7 monitoring of machine and protocol metrics</li> </ul> <h2 id="what-does-the-ethereum-eth-staking-process-look-like-a-namet3a">What does the Ethereum (ETH) staking process look like? <a name="T3"></a></h2> <p>To set up a validator we first need the following information:</p> <ol> <li>Specify the amount of stake - 1 validator per 32 ETH;</li> <li>The withdrawal address.</li> </ol> <p>Please note that once set, the withdrawal address cannot be changed. A different address can also be specified to receive rewards.</p> <p>Following the reception of this information, the validators are set up and a link to the deposit page will be sent out. This process can take up to 24 hours.</p> <p>Once the staking deposit is sent, the validator will be created via our <a href="https://github.com/mixbytes/audits_public/tree/master/P2P.org?ref=p2p.org">audited immutable smart contract</a>. After a period of 16 to 24 hours, the validators will become active and start earning rewards.</p> <p>Ethereum staking rewards are divided into 2 parts. Around 30% of the rewards can be withdrawn and are paid on a monthly basis while the rest is locked and can only be withdrawn after the Shanghai upgrade coming in 2023. Please note that this lock on rewards is not imposed by P2P but is a current feature of the Ethereum network.</p> <p>Once the validators are up and running P2P will set up and email each staker a personalized dashboard that can be used to track rewards and validator metrics.</p> <h2 id="ethereum-eth-staking-guide-a-namet4a">Ethereum (ETH) staking guide <a name="T4"></a></h2> <ol> <li>To start staking go to <a href="https://ethereum-staking.p2p.org/?ref=p2p.org">ethereum-staking.p2p.org</a> and click Stake now.</li> </ol> <p align="center"> <img src="https://p2p.org/economy/content/images/2023/01/Captura-de-ecr--2023-01-25-163236.png" alt="ETH staking"> </p> <ol start="2"> <li> <p>A new window will pop up and we can set how much ETH we want to stake and optionally a different withdrawal address. It's important to keep in mind that once the withdrawal address is set it can't be changed.</p> <p>Here we can also set up an alternative wallet to receive MEV rewards. MEV rewards constitute around 30% of the APR and are paid on a monthly basis.</p> </li> </ol> <p align="center"> <img src="https://p2p.org/economy/content/images/2023/01/Manual-stake---2-1.jpg"> </p> <ol start="3"> <li> <p>Once everything is set up, we can press continue and we will be taken to a confirmation screen. Here we have one last chance to change the withdrawal and the MEV reward address.</p> <p>After reading and accepting the Ethereum Staking Terms and the Privacy policy we can continue.</p> </li> </ol> <p align="center"> <img src="https://p2p.org/economy/content/images/2023/01/3.1.png" alt="ETH staking confirmation"> </p> <ol start="4"> <li>A confirmation screen will pop up requesting that we check our email inbox to verify our email address. The reason why an email address is required is so that P2P can send out the URL to the staking page once the validator is set up.</li> </ol> <p align="center"> <img src="https://p2p.org/economy/content/images/2023/01/4.png" alt="ETH staking confirmation"> </p> <ol start="5"> <li>Once the email address is verified the process of setting up a validator will begin. This process can take from 1 to 24 hours.</li> </ol> <p align="center"> <img src="https://p2p.org/economy/content/images/2023/01/5.png" alt="ETH staking cverify"> </p> <ol start="6"> <li> <p>After the validators are set we will receive a link to resume the staking process (this email should come from a @p2p.org domain). The next and final step is to deposit the ETH into the validators. To proceed click "Send deposits".</p> <p>For clarification, the ETH is being deposited to the validators via a smart contract. This is the Ethereum equivalent of staking and is necessary to activate the validators.</p> </li> </ol> <p align="center"> <img src="https://p2p.org/economy/content/images/2023/01/Aptos-letter-1.jpg" alt="ETH staking cverify"> </p> <ol start="7"> <li> <p>Next, we need to connect our Ethereum wallet.</p> <p>This will be our personal staking page with a prepared staking transaction. What does it mean?</p> </li> </ol> <ul> <li> <p>P2P has set up the validators</p> </li> <li> <p>P2P has prepared a special deposit data file that contains information about the validators' addresses where the ETH will be deposited and the withdrawal address we have set up previously, to unstake in the future.</p> <p>All of this information is available in the Deposit data file.</p> </li> </ul> <p align="center"> <img src="https://p2p.org/economy/content/images/2023/01/2.jpg" alt="ETH staking cverify"> </p> <ol start="8"> <li> <p>We can stake with a Metamask or a Ledger wallet. There is currently no direct support for Trezor devices. We can stake with a Trezor wallet by first connecting it to a Metamask wallet.</p> <p>Other wallets are also available but the process is more complicated. To use a different wallet please contact P2P via <a href="https://t.me/P2Pstaking?ref=p2p.org">Telegram</a>.</p> </li> </ol> <p align="center"> <img src="https://p2p.org/economy/content/images/2023/01/3.jpg" alt="ETH staking cverify"> </p> <ol start="9"> <li> <p>After connecting the wallet we can set the gas price for our ETH transaction. When staking conventionally each validator would require an individual transaction but with a smart contract, we can stake up to 100 validators with a single transaction. This greatly reduces the cost of staking and the chance of human error.</p> <p>Before signing the transaction we should once again check:</p> </li> </ol> <ul> <li>That the withdrawal address is set up correctly;</li> <li>If the recipient address in the transaction matches P2P's deposit smart contract.</li> </ul> <p align="center"> <img src="https://p2p.org/economy/content/images/2023/01/5-1.jpg" alt="ETH staking cverify"> </p> <ol start="10"> <li>After we set the fee we just need to sign the transaction and wait for it to be processed. Once the transaction is processed we are all done. It can take from 16 to 24 hours for the validators to become active. Once they are in the active set you will get access to a personal dashboard with information about your validator metrics.</li> </ol> <p align="center"> <img src="https://p2p.org/economy/content/images/2023/01/8.jpg" alt="ETH staking cverify"> </p> <p>Those that stake Ethereum with P2P are encouraged to join a personal Telegram chat with some members of our team.</p> <p>To note that while MEV rewards are paid on a monthly basis, 1 Validator only produces on average one block every 62 days. Those staking with only 1 validator should expect their first reward after 2 months. The more validators are staked, the sooner it will happen.</p> <h2 id="p2p-ethereum-eth-staking-faq-a-namet5a">P2P Ethereum (ETH) Staking FAQ <a name="T5"></a></h2> <h3 id="do-i-need-to-pass-kyc-to-stake-eth">Do I need to pass KYC to stake ETH?</h3> <p>No, when working with P2P, there is no need to go through KYC because staked assets never touch our account and are sent directly to the Ethereum network.</p> <h3 id="what-is-the-minimum-amount-of-ethereum-required-to-stake">What is the minimum amount of Ethereum required to stake?</h3> <p>No Ethereum is necessary to run a node. However, it is necessary to stake 32 ETH x [amount of validators] to activate the validators and start getting rewards.</p> <h3 id="what-is-a-withdrawal-address-and-who-owns-it">What is a withdrawal address, and who owns it?</h3> <p>The withdrawal address is the Ethereum address used to unstake and receive rewards. This address is specified once and it can't be changed after the staking deposit is sent, because the network cements the association of a particular validator and withdrawal address. Access to the private key for this withdrawal address is required to unstake (seed phrase). It is also important to note that P2P is not a custodian and has no exposure to the client’s withdrawal private key. P2P will never ask, under any circumstance, at any time for access to the withdrawal key.</p> <h3 id="what-is-a-validator-key-and-who-owns-it">What is a validator key, and who owns it?</h3> <p>A validator key is a private key for maintaining the validator’s work (setting up validators, updating software etc.). P2P owns the validator keys and guarantees the highest standards for protecting these keys from being compromised, breached, or otherwise misused. This is accomplished through Threshold signatures, which are the gold standard for internal/external security threats. This solution is used by leading custodians, crypto banks, and Multi-Party Computation solutions.</p> <h3 id="why-use-smart-contracts-to-stake-eth">Why use smart contracts to stake ETH?</h3> <p>By design, ETH staking requires one staking transaction per 32 ETH. By using smart contracts we significantly simplify staking, reduce the cost of staking and minimize the risk of any human error. Thanks to our <a href="https://github.com/mixbytes/audits_public/tree/master/P2P.org?ref=p2p.org">audited</a> smart contracts it is possible to activate up to 100 validators with a single transaction.</p> <h3 id="can-i-stake-ethereum-with-a-hardware-wallet">Can I stake Ethereum with a hardware wallet?</h3> <p>Yes, it is possible to stake ETH with a Ledger (via native connection) or a Trezor wallet (via Metamask).</p> <h3 id="how-do-i-earn-rewards-from-staking-ethereum">How do I earn rewards from staking Ethereum?</h3> <p>Ethereum rewards are comprised of 2 parts associated with performing validation duties and block creation.</p> <ol> <li>Validation rewards are taken by performing the validator’s duties as an attestation for a block created by another validator, attestation for a block in sync committee and for creating a block. Validation rewards are accrued every 6.4 min and account for around 70% of the total rewards. Currently, these rewards aren’t withdrawable until the Shanghai upgrade. Following Shanghai, it will be possible to:</li> </ol> <ul> <li>Fully withdraw all the staked ETH + rewards and deactivate the validator;</li> <li>Partially withdraw all the Ethereum over 32 to the withdrawal address periodically.</li> </ul> <ol start="2"> <li>Block rewards (priority transaction fees + an additional fee from MEV) are accrued with block creation as a payment from transactions to the validator for including them in the block. It appears once every 62 days on average and accounts for around 30% of the total reward. MEV-boost isn’t a separate type of reward but is a technique used to build a block that will yield the maximum fee. Transaction fees accumulate on a p2p smart contract which is then automatically delivered to the client on a monthly basis after the P2P service fee has been deducted.</li> </ol> <h3 id="can-i-still-use-my-staked-ethereum-while-it-is-staked">Can I still use my staked Ethereum while it is staked?</h3> <p>No, the staked ETH is locked in the Ethereum smart contract and cannot be used.</p> <h3 id="how-does-p2p-take-its-service-fee">How does P2P take its service fee?</h3> <p>P2P takes its service fee from the execution layer rewards. By default, a special immutable smart contract is used to automatically split rewards between the user and P2P by the previously agreed rules. Other invoicing strategies can be employed by prior agreement.</p> <h3 id="how-do-i-unstake-my-ethereum">How do I unstake my Ethereum?</h3> <p>Unstaking will be available after the Shanghai upgrade, which is planned for March 2023. The ustaking time is projected to be 2-3 days depending on the number of validators that want to exit. This process consists of four steps:</p> <ol> <li>There will be an unstaking page, where it is possible to authorize the unstaking process with the withdrawal address via the click of a button.</li> <li>P2P sends the validator a voluntary exit message to the Ethereum network, and your validators move into the exit queue. The validator then ceases participating in block attestation and creation (and stops getting rewards). The exit can take from 16 to 24 hours, but right after Shanghai, this queue may be much longer.</li> <li>After exit, the validator waits 27 hours as the network wants to ensure that it hasn't been slashed.</li> <li>Finally, the validator is moved into the second and final queue. This time, the validator is totally deleted from the network and returns its ETH with consensus layer rewards. This process can take from 16 to 24 hours.</li> </ol> <h3 id="how-does-slashing-work-in-ethereum">How does slashing work in Ethereum?</h3> <p>Slashing punishes validators for actions that are very difficult to do accidentally, and it’s very likely a sign of malicious intent. It’s a really rare event: there's only been 5 slashed validators within the whole network over the last month (or 0.001%). <a href="https://beaconcha.in/validators/slashings?ref=p2p.org">beaconcha.in/validators/slashings</a></p> <p>What is “slashable” behaviour? In a nutshell, it’s a violation of consensus rules in the network. As of right now, it needs to meet three conditions: proposal of two conflicting blocks at the same time, double vote attestation and surround attestation. This can happen due to either an intentional malicious action or misconfiguration of the validator (the most often being, running two of the same validators in the network).</p> <p>Slashing results in burning 1,0 ETH at once, and removing the validator from the network forever, which takes 36 days. During this time, the validator continues to work but can no longer participate in validation and block creation, getting a penalty of around 0.1 ETH in total.</p> <p>For the most part that's the sum of the penalty incurred, but there is also an additional midpoint (Day 18) penalty that scales with the number of slashed validators. This is called "correlation penalty” and it's currently only theoretical and has never been encountered on the Ethereum mainnet. This mechanism is there to protect the network from large attacks. The math for calculation penalty is pretty complicated, but the summary is if there are only 1, 100, or even 1000 slashed validators within 36 days the penalty will equal zero ETH. However, if the number of slashed validators increases to roughly 1.1% of all validators (currently 5.1k), this penalty becomes 1 ETH and an additional 1 ETH for every additional 1.1% validator slashed. So if 1/3 of the network is slashed, the penalty will nullify the whole stake (32 ETH). This mechanism is in place to prevent an attack on the network and it should never be triggered by accident.</p> <h3 id="how-can-slashing-be-prevented">How can slashing be prevented?</h3> <p>There are special mechanisms in place to prevent validators from meeting the slashing conditions called <a href="https://medium.com/prysmatic-labs/eth2-slashing-prevention-tips-f6faa5025f50?ref=p2p.org">slashing protection</a>. These mechanisms usually consist of a database with a signing history which the validator uses to check if the block can be signed (coupled with the default levels of monitoring and alerting protection). Additional protection levels will depend on the validator’s setup. P2P uses double-checking with a separate database at the key-manager stage and secures validators' key’s by Threshold, which means that no single person, even a P2P engineer, can run a second validator and a quorum is required for that. The final level of protection we have in place is an institutional grade slashing insurance.</p> <h3 id="how-can-staking-activity-be-tracked">How can staking activity be tracked?</h3> <p>Anyone who stakes with P2P gets access to a personal staking dashboard that can be used to track rewards and the validators' performance (APR, staking balance, % of blocks created with MEV, attestation rate, missed block, market comparisons, etc.)</p> <h3 id="in-what-geographic-location-is-p2ps-validator-infrastructure-running">In what geographic location is P2P's validator infrastructure running?</h3> <p>P2P direct staking infrastructure is located in Europe and distributed among 5 separate physical locations for protection from downtime.</p> <h3 id="how-does-p2p-protect-its-validators-from-widespread-outages">How does P2P protect its validators from widespread outages?</h3> <p>P2P validators have no single point of failure and are downtime resistant with back-ups of all critical infrastructure parts between 5 different physical locations, including:</p> <ol> <li> <p>Signing infrastructure - 3 location-independent key managers with 2-of-3 threshold quorum required for consensus;</p> </li> <li> <p>Validators Nodes - we have a reserve in a secure region ready to be activated within a maximum of 1 minute in case of an outage;</p> </li> <li> <p>Consensus layer nodes - our setup has top-3 consensus layer clients (Lighthouse, Prysm, Teku) simultaneously for diversity and preventing outrages related to soft bugs in one client. It also increases availability for validators.</p> </li> </ol> <!--kg-card-end: markdown-->
from p2p validator