As Beta Tester

Meta Pool values its community and is open to participation. We value collaboration with our community.

First of all, thank you for being part of the early beta testers community of Meta Pool.

This article works as the basis for testing the different Meta Pool Team domain products. Contains the general guidelines for Beta Testing Process.

If you want to become part of the beta testing team, follow the updates on our Discord beta-tester channel.

About beta testers

It is an open program who participate in the exclusive process of Meta Pool to validate that new products are working fine and present no problems.

Beta testers should have the following skills: Proactivity and curiosity about testing new products. Deep knowledge about NEAR or Aurora or Ethereum Protocol and usage of DApps. Deep knowledge about Meta Pool, including what are stNEAR and META Tokens in NEAR Protocol or stNEAR and stAUR in Aurora Protocol or mpETH in Etherum Protocol. General knowledge about how Decentralized Finances works. Reading and writing in English. Commitment with Meta Pool, willing to participate in more than one process. Some time and flexibility that will help us.

Beta testing process

Meta Pool will deliver to beta testers individual documents that include test cases and scenarios that will be reproduced. While steps of testing are being completed, beta tester should recover the following:

  1. Bugs founded.

  2. Screenshots.

  3. Extra steps required.

  4. Videos, in case of need.

  5. Textual descriptions.

  6. User experience improvements.

  7. Others that can be required in each individual process of beta testing.

Once done, present evidence of high value that can be graded for internal reference as:

Rewards for beta testing

By every beta testing process completed there will be an amount of rewards that will be distributed to beta testers depending on their contributions made. A budget will be assigned for this and announced previous to beta testing.

Extra rewards could be awarded to those who find critical bugs, outside of the test cases that are designed on the beta testing process, based on the grading table.

The amount that will be paid will be defined in individual documents for every beta testing process, depending on the work spent you will get a proportional payment. For every point you get based on the table of Beta testing process you will get $1 USD. In case of required, it can be put in consideration by Meta Pool team to increase this budget.

The reward is paid in USDT, stNEAR or mpDAO token, depending on the availability of the treasury.

Format to report beta testing What we need to get from you when beta testing is mainly the following, and can vary depending on requirements of the beta testing process being runed:

  • Testnet wallet ID

  • Test case.

  • Expected behavior.

  • Actual result (unexpected behavior).

  • Steps to reproduce.

  • Screenshots.

Every beta testing process document will have its own form to submit information.


  1. Poor performance on documenting the testing process.

  2. Finding bugs and not reporting them.

  3. Vulnerabilities on sites hosted by third parties unless they lead to a vulnerability on the main website.

  4. Vulnerabilities contingent on physical attack, social engineering, spamming, DDOS attack, etc.

  5. Vulnerabilities affecting outdated or unpatched browsers.

  6. Vulnerabilities in third party applications that make use of Meta Pool tokens.

  7. Vulnerabilities publicly disclosed in third party libraries or technology used in Meta Pool products, services, or infrastructure earlier than 30 days after the public disclosure of the issue.

  8. Vulnerabilities that have been released publicly prior to Meta Pool issuing a comprehensive fix.

  9. Vulnerabilities already known to us, or already reported by someone else (reward goes to first reporter).

  10. Issues that aren't reproducible.

  11. Vulnerabilities that require an improbable level of user interaction.

  12. Vulnerabilities that require root/jailbreak on mobile.

  13. Missing security headers without proof of exploitability.

  14. TLS Cipher Suites offered.

  15. Suggestions on best practices.

  16. Software version disclosure.

  17. Any report without an accompanying proof of concept exploit.

  18. Issues that we can't reasonably be expected to do anything about, such as issues in technical specifications that Meta Pool must implement to conform to those standards.

  19. The output from automated tools/scanners.

  20. Any other that the team considers.

Apply to be a beta tester

We have identified our most proactive beta testers who have already accompanied us from previous products, however we do not want to leave the possibility of new Beta Testers being integrated. For this, we will make a call if we require more support and this will depend on the size of the project and the amount of testing that we are going to need.

Form to apply: Be a beta tester.

Last updated