Boundless (@ boundless_xyz) project one click node script After several days of testing and reading many scripts written by experts, I used @ 0xMoei's translation because each person's machine is different for one click scripts. This expert wrote a script that is suitable for many people, and then optimized it Script link https://(GitHub)/mumumusf/Boundless The usage method is also very simple wget https://raw. (githubusercontent.com)/mumumusf/Boundless/main/Boundless.sh -O http://Boundless.sh chmod +x http://Boundless.sh bash http://Boundless.sh Then we will focus on introducing Configuration issues may cause you to be unable to outperform others During the installation process, you need to configure the following key parameters **Peak_prove_khz * * | System order processing speed | Set according to actual performance| 1. * * peak_prove-khz * * - Key Parameters -Function: System order processing speed, the higher the value, the more orders will be obtained -Risk: Setting too high may result in timeout and slash -Test Network: Bold experimentation is possible |Mcycle_price * * | The price per million cycles is close to the minimum limit| 2. * * mcycle_price * * - Price Strategy -Function: Price quotation per million cycles -Strategy: Approach the minimum limit of the system to gain competitiveness -Risk: Low price may result in little profit -Suggestion: You can set very low prices on the testing website |* * lockinpriority_gas * * | Lock additional gas for transactions| 3. * * lockinpriority_gas * * - Bid Advantage -Function: Defeat other claimants in bidding -Recommended value: 4000 Gwei -Risk: Setting too high (such as 40000) may result in errors -Advantage: Improve the chances of winning bids |Max cycles limit | Maximum number of accepted cycles | Based on hardware capability| 4. * * maxim_cyclelimit * * - Capacity limit -Function: Maximum number of cycles accepted (in millions) -Suggestion: Set according to hardware capabilities -Entry level: 8000-50000 -Mid end level: 50000-200000 -High end level: 200000-500000 |Maximum number of parallel proofs| 5. * * max_currentpyrofs * * - Parallel Processing -Function: Maximum number of proofs processed simultaneously -Recommended value: 2 (safe value) -Risk: 3-4 may receive more orders but may not be able to complete them **Min_deadline * * - Minimum remaining time to accept orders -Function: Minimum remaining time for accepting orders (seconds) -Meaning: "How many seconds of remaining time do I have to accept an order -Recommended value: 150-200 seconds -Suggestion: 150-200 seconds -Test Network: Can set lower value experiments The above configurations need to be set in conjunction with your own machine RTX 4090 Configuration Example peak_prove_khz = 751 mcycle_price = "0.000000000000000111" lockin_priority_gas = 4000 max_mcycle_limit = 500000 max_concurrent_proofs = 2 min_deadline = 200 And then I used the Vast machine Reference tutorial https://(x.com)/YOYOMYOYOA/status/1708092314708242 The official recommendation is to start mining with 4090 codes for 10 cards. Based on the analysis of the code, some of them do not rely on GPU resources. The total amount of zkc is 1 billion, and the zkc allocation ratio of the testing network is 0.5% of the reward So everyone can decide whether to run or not in July based on the situation If you have any questions, please join the TG communication group: https://t.me/YOYOZKS