PowerPool Biweekly Update — 29 March 2024
Hello, PowerPool Community!
We are excited to present a summary of the most recent progress made by PowerPool in the past weeks.
This article covers:
1. PowerAgent incentivized testnet: Latest updates and stats
2. PowerAgent Code & UI Enhancements
3. Results from PowerPool’s research team
PowerAgent incentivized testnet: Updates and stats
PowerAgent V2 is now operating smoothly on three networks: Gnosis Chain, Sepolia testnet, and Arbitrum One. The Ethereum testnet is paused, and the team and selected community members are testing Polygon.
Weekly CVP airdrops incentivize network participation to the best-performing Keepers [1][2][3]. Each week, 30 testers at the top of the leaderboard receive 100 CVP.
To participate in the PowerAgent testnet, join the PowerPool Discord!
Network stats
The team preliminary tested all the updates, reported bugs & improvement proposals to the tech team, and provided ongoing technical support to PowerAgent testers on all supported networks.
In addition to the incentivized testnet, PowerPool has two running campaigns for the community to participate in and earn rewards:
- GitBook Community Challenge: To claim part of the $2,000 prize fund, the community can help enhance PowerPool’s technical documentation with instructions, user guides, templates, and other commits.
- Auto-claiming Staking Rewards Program for Gnosis validators: Gnosis validators can streamline their claiming process by creating a simple Job in PowerAgent and secure a bonus CVP airdrop in the process.
PowerAgent Code & UI Updates
Contracts:
- Implemented automatic Resolver call if the CFG_CALL_RESOLVER_BEFORE_EXECUTE Job flag is enabled. In that case, the Resolver is called automatically during transaction execution, and the returned calldata is checked against the calldata provided by the Keeper.
- Deployed new Agent implementation on Gnosis
- Deployed new Agent implementation on Arbitrum
Power Agent node (TS implementation):
- Added additional tests for API safety: responses without RPC URLs and API keys.
- Solved a problem where incorrect timing for execution interval tasks led to blacklisting.
- Fixed the problem of initiating KeeperSlashing transactions for the new Job configuration in cases where the Resolver function requires a proper ‘from’ address during the call.
Power Agent node (Rust implementation):
- Finished all event handlers.
UI
- Fixed some incompatibilities between the new version of ethers.js and UI logic.
- Solved the problem where the farming page was not displaying connected account data.
- Added the callResolverBeforeExecute flag to edit the Job if it’s Gnosis or Arbitrum.
- Fixed some errors when changing the network.
Explorer
- Fixed some issues with the Explorer page breaking due to problems with Arbitrum RPC.
- Implemented functionality to use alternative RPC servers upon connection errors with the current ones.
Subquery:
- Added Sentry monitoring for subquery status.
- Configured nginx for parallel SubQuery networks.
- Added the callResolverBeforeExecute flag to the Job model. It should be set to false by default, — with the SetJobConfig event checked to determine if it should be set to true.
- Added the ability to have two instances for the same network.
Subgraph:
- Added the ability to check for SubGraph nodes in the monitoring script.
- Completely remade the Power Agent page for both desktop and mobile versions.
Research team results
Work with grantees, supporting them on the delivering pathway and providing tech specs for updating PowerAgent in order to comply with tech requests from grantees' projects.
The R&D team proposals for PowerAgent improvement
The Partitura integraion
1. Introduction of the additional 32 bytes of jobkey into the calldata to enable assertion of the correctness of the keeper for this job
2. Addition of a flag in the Agent to enable validation of the resolver calldata against a simulated resolver call output at an execution attempt to provide the users with an additional inbuilt security measure
The Dencun upgrade
- The update of the minimal balance required from the job owner to run a job and the compensation for keepers following the gas price decrement on rollups is also needed. The proposal was based on on-chain statistics of Arbitrum operation and suggests to decrease:
(a) minimal Job balance 0.01ETH -> 0.001ETH (b) Keeper compensation 0.001ETH -> 0.0001ETH
The R&D team grantee supporting results
- The R&D team closely works with Partitura on tech and marketing stuff.
Partitura’s team regularly registers test Jobs and provides us with code updates. They are almost ready to launch the UI and PowerAgent Jobs integration and the marketing campaign. - The Breadchain team provided a detailed Job design explanation of their automated yield disbursement strategy and submitted a first Job to PowerAgent for testing.
-> We published the Breadchain Job architecture article
-> Breadchain moves its operations to Gnosis, featuring the PowerAgent network as an automation back-end. - Marketing work has been carried out with Daoism’s team, resulting in the formulation of their launch plan. The first publications are expected next week.
Infrastructure building & prototyping
- The PowerPool VRF Javascript prototype has been developed and tested using a verification contract deployed on Sepolia. Find the code on PowerPool GitHub: https://github.com/powerpool-finance/powerpool-research/tree/main/vrf
- The generalized DCA/limit order Job smart contract was deployed on the Goerli testnet last month and is undergoing other necessary tests now.
- The Liquidation Protection template code has been developed and passed testing in a local environment.
Easter egg: an exotic PowerAgent v2 use case
At DAppNode’s suggestion and in collaboration with a Gnosis validator from the DAppNode community, we have formulated a new automation use case — the automatic unregistering validators from the MEV Smoothing Pool. Because of the Smoothing pool design, if your user has multiple validators, it’s not optimal to unsubscribe them all at the same time, but it’s optimal to unsubscribe each one of them after the validator proposes a block, claim the reward, and then unsubscribe.
Twitter | Discord | YouTube | Telegram | CMC Community | Debank | Medium
