# Help us test Secure Cadence release candidate!

**URL:** <https://forum.flow.com/t/help-us-test-secure-cadence-release-candidate/3112>\
**Category:** 🏄🏻‍♀️ Cadence\
**Created:** [May 18, 2022, 12:23am UTC](https://forum.flow.com/t/help-us-test-secure-cadence-release-candidate/3112 "2022-05-18T00:23:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jan](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.flow.com/jan/32/672_2.png) [@Jan](https://forum.flow.com/u/Jan)\
**Post date:** [May 18, 2022, 12:23am UTC](https://forum.flow.com/t/help-us-test-secure-cadence-release-candidate/3112/1 "2022-05-18T00:23:07Z")

</div>

Dear Flow Community,

As you may be aware, the upcoming release of Secure Cadence is the last step on the journey to [enabling permissionless contract deployment](http://forum.flow.com/t/permissionless-contract-deployment-progress/2981). We have a Secure Cadence release candidate ready and would like to invite community members to participate in testing the release. New issues found will be subject to the [bug bounty program](https://docs.onflow.org/bounties/), in line with the [Flow Responsible Disclosure Policy](https://www.onflow.org/flow-responsible-disclosure).

As always, we welcome disclosures of all issues you may find and they all are subject to the bug bounty. That being said, the main goal of testing this release candidate is to find vulnerabilities exploitable through smart contract code execution, which could lead to:

1. Modifying non-public state of an account without having access to its private key.
2. Gaining control of the host machine.
3. Destabilizing the Flow network (e.g. by crashing or significant slow-down of network nodes).

To receive access to a _test environment_ running the Secure Cadence release candidate, please fill in [this form](https://forms.gle/TCGQZG4FULfKHbX9A) or DM Jan.#6550 on Discord.

To **report potential vulnerabilities** follow the [Flow Responsible Disclosure process](https://www.onflow.org/flow-responsible-disclosure) by emailing details to [security@onflow.org](mailto:security@onflow.org?subject=Secure%20Cadence%20Testing) and adding “Secure Cadence Testing” in the subject line. **Do not**  **discuss potential vulnerabilities in public channels**.

> For questions **regarding the bug bounty program** please respond to this thread or ask in the [Cadence Discord channel](https://discord.com/channels/613813861610684416/717035372248432660).  
> If you are unsure about anything and would like to discuss - please [email the Cadence team](mailto:flow-cadence-eng@dapperlabs.com) and we will get back to you.

> Please note that this testing network is for security research purposes and the resources are limited, it is not meant to be used for testing real-world transaction loads - it is not a testnet replacement.