BowTiedRadone

@lgalabru Users can now write property-based tests and define invariants to fuzz test their Clarity smart contracts directly in Clarity, using [Rendezvous](https://github.com/stacks-network/rendezvous). Rendezvous allows randomly generated arguments to be passed...

@moodmosaic and I have an implementation in place to publish contracts and execute contract calls on a specified testnet. However, when deploying contracts to `Naka-2`, we frequently encounter an issue...

Here is the response from calling the nonces endpoint: ```sh $ curl https://api.nakamoto-2.hiro.so/extended/v1/address/ST31X86B33XYDVXY34ZMBY09SAX1GR9V2CH9G2RZ4/nonces { "last_executed_tx_nonce": 22, "last_mempool_tx_nonce": 49, "possible_next_nonce": 50, "detected_missing_nonces": [ 48, 47, 46, 45, 44, 43, 42, 41,...

@gustavo-grieco Updated the test so it runs `forge init`. This required adding a Foundry installation step in CI.

@gustavo-grieco Anything left to be covered in this PR?

@gustavo-grieco Thanks for the update and looking forward to 2.3! 🚀 > Are you interested in keep expanding this in a future PR? Sure! Also, two more Foundry test generation...

Hi @elopez! Just checking in on this PR. If it’s still on hold, I can give it a shot and see if I can make progress. It would be helpful...

Hi @monperrus. I will give this a shot, if you have anything that would help reproduce it would be highly appreciated 🙏

@monperrus Picking up this issue now, trying to fix the following days. For the contract name bug, I don't necessarily think we want a dynamic approach (`Test` if contract name...

@cjlapao yes, the UI one.