Всем привет ! А ктото в курсе - какие требования к ноде будут ? Обеспечение монетами, требования к железу, каналу ? И когда собственно механизм будет запуще в работу ? Софт поставил, к кошельку "привязал" - а дальше "Ждите новостей" и все
Привет ! Каких то супер требований к железу не вижу, упоминается свободное место на диске, аптайм и трафик )
very little CPU, memory or network traffic should be consumed
Uptime (i.e., Online 24/7)
Good internet connection (fast and stable)
(initially) ability to open ports on local router
Adequate processor and memory (check table for recommendations)
Previous contributions to the Pi community
Security circles
Это будет оплачиваемый тестнет, залога на ноду я так понимаю тоже не будет.
По срокам сложно спрогназировать, но то что сейчас все перевели в лайтмод говорит о том что то делают, так же не забудь подать заявку\пройти опрос в приложении.
https://minepi.com/node-infoSelection Criteria for Nodes and SuperNodes
After an initial screening period, Nodes and SuperNodes will be selected based on the following criteria. While both will be assessed on similar criteria, the threshold for Nodes will be lower than SuperNodes.
Uptime (i.e., Online 24/7)
Good internet connection (fast and stable)
(initially) ability to open ports on local router
Adequate processor and memory (check table for recommendations)
Previous contributions to the Pi community
Security circles
Based on your node reliability and trust score in Pi Network, you will be invited to KYC. Applicants that complete KYC will be enrolled to serve as a SuperNode and Node in Pi’s Testnet.
During the initial Testnet period, the primary goal is to stress test the network’s consensus algorithm. While not all Pioneers will have the hardware, software, and network reliability to participate in the initial Testnet, Pi always aims to be as inclusive as possible. All Pioneers will continue to be able to participate via Pi’s mobile application. Furthermore, over time, we also aim to make the Node role more accessible by developing additional ways that Pioneers can contribute to the network.
Testnet Roadmap
Testnet will be composed of three stages.
Roadmap Outline
Selection Stage
Revision Stage
Live Testnet
Goals
- Calibrate selection criteria for Nodes and SuperNodes
- Test the blockchain
- Achieve safety
- Tackle liveness
- Scalability
- Test the blockchain
- Achieve safety
- Tackle liveness
- Scalability
Activities
- Analyze Nodes availability and reliability in relation to the performance of the network
- Stress scenario testing
- Revise consensus algorithm
- Test the blockchain with real participants’ actions
- Revise consensus algorithm
Selection stage
The Core Team will run the consensus algorithm with Pioneers who have applied to become Nodes and successfully completed installing all necessary packages for the blockchain component on their computer. These tests will enable us to understand the requirements for individual Nodes (e.g., hardware, duration online, bandwidth, stability of connection etc.) needed to achieve a reliable and secure network. While our hope is to include as many Pioneers as possible when defining the Node requirements, the availability and reliability of individual nodes in the network affect the safety and liveness of the network. Hence, we need to balance the two aspects above by testing in the Selection Stage and properly define the thresholds for Nodes and SuperNodes.
Revision stage
The Revision Stage will comprise an iterative process of two activities: scenario testing and consensus algorithm revision. Scenario testing refers to stress testing the consensus algorithm, its scalability, and configurations given different scenarios. The data produced from the scenario tests then will provide guidance as to where and how we should revise and adapt the consensus algorithm to ensure safety, improve liveness, and to achieve scalability.
This fast, iterative process is important for making improvements on the consensus algorithm to meet the needs of Pi Network. Thus during this phase, the blockchain component of this Node version contains a centralized layer that will allow the Core Team to quickly assign simulated data of the network graph and configurations to different Nodes, to more efficiently test a wide range of scenarios and states of the network. For example, instead of only relying on the current data from security circles to test the consensus algorithm, which is only one scenario, this feature enables the Core Team to create hundreds or even thousands of scenarios of quorums by assigning simulated security circles to different nodes in the network. Interesting scenarios also include: What happens if half of the network gets isolated? What happens when a percentage of nodes in the network suddenly drops out or enters the network? This centralized layer will be removed in the mainnet after it serves its testing purpose.
In turn, the data generated from these tests can feed the revision of the consensus algorithm. Pi will face unique challenges as it adapts and scales the Stellar Consensus Protocol to meet the needs of Pi’s blockchain (e.g., a large number of participants, highly distributed, personal computer as nodes, incorporation of trust graph generated from mobile miners etc.) The revision stage will allow the network to test things like scaling messaging and the voting process of the network while maintaining safety and liveness. The activity of revising consensus algorithms entails data analysis and research to innovate solutions tailored to Pi Network’s needs.
Live Testnet
Live Testnet will be the stage when different types of nodes actively perform the responsibilities defined in the tables above (See Section Levels of Node Participation). Nodes will be able to submit testing transactions that get recorded on the distributed ledger by nodes through the consensus algorithm. The purpose is still to test the performance of the network, but with real data from security circles generated by mobile miners and real activities of participants of the network. It also contains an iterative process of testing, data analysis, debugging, revising and innovating to achieve safety and tackle liveness and scalability.
Node FAQ
What is the relationship between the Pi Node software and the Pi Network mobile application?
Nodes and mobile apps are not mutually exclusive but complementary to each other. You will log into the Node software through your Mobile app account, which means both desktop and mobile apps are pointing to the same Pi account. As Pi policy, one person will only be allowed to have one Pi account, and as of now, one account should run only one node. Mobile mining can only be started from the mobile app, while the desktop Pi App interface of the node will allow you to check balances, chat and watch any media content on the homescreen. Whether an account has a node or not does not affect any functionality in the mobile app.
What impact will the Node have on my device? Will it drain my CPU and battery?
If you do not turn on the Node or SuperNode part, then the impact is minimal, very little CPU, memory or network traffic should be consumed, making it accessible to everyone. Turning on the Node or SuperNode functionality will be using CPU, memory, hard drive and network resources. Over the course of Testnet, we will be collecting data to more clearly determine the impact of running the Nodes on specific devices.
Will there be a reward for running a Pi Node?
One of the goals of Pi’s Testnet is to determine what, if any, rewards there should be for running a Node. While we collect the relevant data needed to determine the most appropriate incentive mechanism, there will be no mining rewards for Testnet Nodes.
Is Pi Node Software Open Source?
The blockchain component of the Node will be open sourced. We are in the process of tidying up the github repository so that we can proceed with the open sourcing. We aim to maintain a list of open issues directly on the github repository, which community members will be able to contribute to, if they like. Stay tuned.