# Payouts At CodeCall, we ensure that participants are fairly compensated for their contributions based on the type, quality, and impact of their work. ### Payment Method * **Currency:** Payouts are done in USDC (USD Coin), a stablecoin that ensures value stability. * **Withdrawal Options:** You can choose to withdraw your USDC using MoonPay or other supported methods. * **Tax Responsibilities:** Participants are responsible for handling their own tax obligations related to their earnings. ### Transfer Options **Wallet Transfers:** You have the option to transfer your earnings to another wallet such as metamask. Ensure you double-check the wallet address to prevent any loss of funds. ### Payout Criteria Payouts are awarded based on the number and quality of contributions. Here is how the payout structure works: * **Contribution Type:** * **Bugs:** Identifying and fixing critical bugs are highly valued and therefore receive higher payouts. * **Features:** Implementing new features that align with project requirements and add significant value are rewarded generously. * **Optimizations:** While optimizations are important, they generally receive lower payouts compared to bugs and features unless they result in substantial performance improvements. * **Quality and Impact:** * **Above and Beyond:** Contributions that exceed the basic requirements and align closely with the goals of the company are eligible for higher payouts. For instance, a feature implementation that not only meets the specified requirements but also enhances user experience or performance will be rewarded more. * **Thoroughness:** Detailed submissions with comprehensive documentation and clear explanations are valued higher. * **Innovation:** Unique solutions that demonstrate creativity and innovation are rewarded to encourage out-of-the-box thinking. ### Example of Payouts * **High-Priority Bug Fix:** A critical security vulnerability that is fixed promptly may receive a higher payout due to its importance. * **Feature Development:** Developing a complex new feature that significantly enhances the platform could earn a substantial reward. * **Optimization:** Improving the efficiency of a core algorithm might receive a moderate payout unless it drastically enhances performance, in which case it could be higher. ### Payouts for multiple tasks If a project has multiple tasks, for example 10 and you do 2 of them and your contribution is approved over someone another engineer, then you get paid for those 2 tasks. In addition, if another engineer is working on task 3, as you are also and his contribution get approved over yours, they will get paid for task 3 and you will still get paid for your 2 tasks that you were approved on. By adhering to these criteria, we ensure that participants are fairly compensated for their valuable contributions, promoting a high standard of work and fostering a collaborative and innovative environment. ## **Note: Please review the** [**invoicing guidelines**](/code-call/engineers-docs/invoicing-guidelines.md) **to send your invoice after your submisions were approved** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://codecall.gitbook.io/code-call/engineers-docs/payouts.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.