PowerPool

The PowerAgent Automation NetworkPowerPool believes that the PowerAgent Keeper network for automatic smart-contract execution will be able to enrich the Ethereum ecosystem (and other EVM-compatible blockchains soon after) by enabling the creation of new and improved automated on-chain strategies that were previously impossible due to the lack of reliable and cost-effective automation technologies<a href="https://medium.com/powerpool/poweragent-automation-network-value-proposition-functions-f40fd71d817e" rel="noopener noreferrer nofollow">[1]</a>.To ensure a seamless launch on the Ethereum mainnet, the PowerAgent incentivized testnet was launched in mid to late May 2023 on the Sepolia network.The testnet was launched by <a href="https://medium.com/powerpool/powerpool-dappnode-partner-to-bundle-decentralized-smart-contract-automation-with-blockchain-node-ff85dea51c15" rel="noopener noreferrer nofollow">combining forces with DAppNode</a>. This partnership made the PowerAgent node easy to install and operate full nodes and independent validators alongside such as GnosisChain, Ethereum, and test networks like Sepolia. This makes PowerAgent accessible to a big community of independent Ethereum validators.In this article, we would like to share the progress made on the DAppNode integration and following PowerAgent Sepolia testnet, update our community on its status, and discuss future plans for PowerAgent v2 and its upcoming mainnet rollout.Let’s dive into the details.Status of the PowerAgent testnetSo, at the moment the PowerAgent Sepolia testnet is ongoing. Testers have installed the Sepolia node and the PowerAgent node using the software provided by <a href="https://dappnode.com/" rel="noopener noreferrer nofollow">DAppNode</a>.As part of the<a href="https://gov.powerpool.finance/t/proposal-57-poweragent-incentivized-testnet-and-bug-bounty-program/1318/6" rel="noopener noreferrer nofollow"> incentivization program</a>, PowerPool plans to distribute up to 200,000 $CVP in grants to testnet participants. Currently, the Sepolia testnet has 28 Keepers, 11 of which are from the team and are not eligible for grants. More than 400 testers applied via the <a href="https://forms.gle/HTpLFtGNpuBvJzte8" rel="noopener noreferrer nofollow">Google form</a> and they will be added to the testnet gradually in the following weeks.<blockquote>Stay tuned to the<a href="https://twitter.com/powerpoolcvp" rel="noopener noreferrer nofollow"> PowerPool Twitter</a> to keep track of all updates on the PowerAgent testnet and PowerPool in general!</blockquote>At this time, the correct execution of Jobs is being checked. There are 3 main types of Jobs that PowerAgent can handle and we’ve successfully tested the 1st type of Jobs (signature Jobs) and moved forward to the 2nd Jobs type (with predefined CallData)<a href="https://medium.com/powerpool/poweragent-automation-network-value-proposition-functions-f40fd71d817e" rel="noopener noreferrer nofollow">[1]</a>. These are the two simplest types of Jobs. They are intended to be used when a certain smart contract (with and without CallData) needs to be called at regular intervals.Unfortunately, there was a delay in early June while the bug-fix update to the PowerAgent Node package was being prepared. The Job registration processing update took longer than expected. It was a tricky bug to fix and it prevented Jobs from being executed and hindered the progress of the testnet. However, the PowerPool team was able to overcome this hurdle and the fix for handling Jobs registration was incorporated into the last PowerAgent update.Overall, our testers are doing a great job! Most of them are very active, reporting bugs and helping the PowerPool team by supporting each other when someone is in need of assistance.We found that one of the initial difficulties for some users was creating the “Key” file when setting up a Keeper Node. One of our testers was kind enough to create a video guide in which he explained and showcased all the necessary steps. This guide was incredibly helpful for other members of the testnet and significantly accelerated the rollout of new Keepers.<blockquote>The PowerPool team greatly values such active engagement in the PowerAgent testnet, and is thinking of further ways to encourage more active participation from the community.</blockquote>Along with the incentivized testnet, PowerPool has launched the<a href="https://gov.powerpool.finance/t/proposal-57-poweragent-incentivized-testnet-and-bug-bounty-program/1318/6" rel="noopener noreferrer nofollow"> PowerAgent Bug Bounty program</a>. Any user who discovers any major exploits and vulnerabilities in the PowerAgent architecture and reports them to the PowerPool team will be eligible to receive a Bug Bounty in USDT. The initial size of the Bug Bounty is 1000 USDT, but it will probably increase in time with new testnet stages and mainnet deployment. ATTOW, no Bug Bounties have yet been claimed.Fixes to the PowerAgent NodeQuite a number of small to medium bugs have already been found by our testers. The PowerPool team is working tirelessly to fix all the issues as soon as they arise. Some of them can be fixed by simply updating the Agent, but some require editing the code of the Keeper node itself. This requires all testers to update their node, however, this is extremely easy thanks to thepartnership with DAppNode. All it takes is to click the “Update” button in the DAppNode UI.<blockquote>PowerPool believes that sharing all information on its inner workings is crucial for maintaining the trust of our community.</blockquote>A couple of days ago, a major node package update was released. It includes fixes for various bugs as well as minor to medium errors in the network. We would like to provide an overview of the main bugs and issues that were found while testing PowerAgent. For the most part, they fall into one of these three categories:<ol><li>Issues in the Jobs registration mechanics. These are the sorts of issues that occur during the creation of Jobs. For example an error in the processing of Job registration events, the stop in tracking of new Job announcements, or errors in the encoding-decoding process in Job registration.</li><li>Issues that led to the inability of Keepers to timely execute Jobs. These are the problems in the execution of Jobs, where a Keeper is successfully assigned to a Job but is unable to execute it. There were several reasons for this kind of issue: if a previous transaction signed by the Keeper was not mined by the time the next transaction of the same Job was due, or if the minimum CVP stake for a particular Job was set lower than the global minimum stake, etc.</li><li>Minor bugs unrelated to the execution of Jobs. Some bugs were discovered that didn’t interfere with either Job registration or its execution, but led to economic losses for the Keepers. For instance, there was a typo in the formula for calculating gas compensations.</li></ol>Most of these issues have been fixed in the last node package update and other bugs will be addressed in the next ones.What to expect next?The next steps for the PowerAgent testnet are the following:<ol><li>Begin testing Jobs with an external Resolver (the 3rd type).</li><li>Open Job submissions to testnet participants.</li><li>Gradually start admitting new testers to the testnet.</li></ol>After we finish testing Jobs with predefined CallData (2nd type) we will move on to Jobs with an external Resolver (the 3rd type). This process will hopefully take around a week and we plan to proceed to the next testnet stage in early July.When the testing of all the types of Jobs will conclude and we make sure that they are working well, testers will be encouraged to add their own test Jobs to the network and check for possible issues at the Job creation stage.Also, around this time we will start admitting new batches of testers to begin testing the redundancy of the Keeper network. Overall, we will expand the number of Keepers in the Sepolia network to over 100.After all the subtleties are addressed and we see that every part of the PowerAgent network is working flawlessly on the Sepolia network, it will be deployed on GnosisChain for its approbation in the real-world environment.The GnosisChain approbation phase is meant for PowerAgent to prove its worth and demonstrate its capabilities and economic viability for both Keepers and protocols. At this stage, we will provide $CVP tokens required for the initial Keeper stake (1000 $CVP) to all testers who successfully complete the previous Sepolia testnet phase.Then, after some time on GnosisChain, PowerAgent will finally migrate to the Ethereum mainnet.

The status of the PowerAgent v2 testnet: What has been done and what’s next?

PowerPool

Autres articles publiés le 9 août 2023

FedEx Stock Price Prediction: What FDX Price targets For Aug-23?

Microsoft Collaborates With Aptos to Explore Digital Payments and CBDCs

Kentucky Approves $25M Cryptomining Facility

CoinEasy and Neo Blockchain Partner to Elevate the Neo APAC Hackathon

Ethereum ETFs Gaining Momentum, TOADS is An Elite Token To Buy Now Says Analyst

PlayWay Adopts Polygon, Borroe Leads MATIC Ahead of 5X Altcoin Season

Join our free newsletter for daily crypto updates!