Probably the best reason for developers to create and extend automation-intensive Templates incorporating PowerAgent Automation Network tasks is that PowerAgent enables automatic collection of native token royalties as part of every task execution. Tasks entrusted to PowerAgent are executed by Keeper nodes, in return for native token automation fees collected automatically. In addition, each task execution also results in a PowerPool Treasury Charge automatically collected in native tokens for the benefit of the DAO Treasury and $lsCVP passive stakers. It is therefore easy to add a third native token Template developer royalty stream on top of the Treasury Charge for each registered Template. Developers can also determine how often their earnings are swept from the Treasury and paid into their wallets to minimise gas costs.
One of the largest problems in developing open source blockchain based protocols has been how best to remunerate developers of open source code, not only for developing useful services and features, but perhaps even more importantly, continuously improving and hardening them against attack. Many protocols have jumped through many hoops trying to create value-accruing tokens that will incentivise continuous developer attention via community token value accrual. And the problem of continuously remunerating developers is even more challenging when it comes to ensuring on-going development of so-called ‘common goods’ that benefit an entire blockchain ecosystem, without any specific token or means of licensing the code.
PowerAgent Templates that are registered Job Owners can specify developer royalty fee ‘take rates’ to be enforced automatically on every task execution. These embedded royalties cannot be altered or removed permissionlessly by anyone forking the Template, since every individual Template must be uniquely registered as a PowerAgent Job Owner as part of specifying tasks to be automated. Template developers will compete to offer the best package of services, features, gas efficiency and fee take rates. Templates are also composable, meaning that Templates can be ‘nested’, or incorporated in other Templates by reference, such that anyone using a given Template will also automatically be using other Templates incorporated by reference when the Template is registered as a Job Owner.
The composability of Templates and inability of developer royalty ‘take rates’ to be forked away without re-registering a new variant of a given Template opens the door to a generally-beneficial approach of using PowerAgent Templates to directly fund common goods in the native token of each chain ecosystem. Organisations promoting common goods funding can create composable ‘charitable’ Templates that gather fees for specific designated ‘common goods’ wallets. Each of these organisations will also register one or more official ‘kitemarks’ indicating that incorporating that Template inside another Template will result in a task-by-task fee stream being collected and paid to the designated wallet(s). Royalty-seeking Template developers eager to show alignment with each ecosystem may choose to feature one or more ‘common goods’ Templates within their own royalty-earning Templates. When they do so, they will be entitled to show the kitemarks of all incorporated common goods Templates on the profile of their own Template(s), chain by chain.
In terms of royalty-earning Template marketing, this is similar to coffee shops attracting customers by advertising ’FairTrade’ coffee, and collecting tips for charities. Thus, an end user looking at the available PowerPool library of Templates for each EVM chain/ecosystem may choose to use a DCA or Limit Order Template that not only pays a royalty to the DCA/Limit Order developer, but also automatically collects small donations for specific common goods wallets. Organisations pursuing common goods funding, such as Github, would retain full control over the wallets and amounts registered in their own common-goods funding Templates, which royalty-oriented developers can choose to incorporate (unmodified) by reference into their own Templates, or not.
To join our discussion of Templates, developers royalties, forking opportunities and protections and funding common goods please join our Discord channel: