Rendezvous v1.0.0 Roadmap

[BowTiedRadone]

Version 1.0.0 consolidates the must-have features, fixes, and improvements needed to make Rendezvous stable and production-ready as a robust fuzzer for Clarity smart contracts. This release focuses on core functionality, reliability, feature completeness, documentation, and overall developer experience.

Scope

Bug Fixes

• Handle missing trait implementations gracefully instead of crashing #157
• Node 18: Dialer files in Clarinet projects fail to load #174
• Normalize contract paths in isolated Rendezvous directory #219

UX

• Support wildcards for test selection #60
• Support failure persistence via seed replay #130
• Implement fuzzing plans to fuzz multiple contracts at a time #148
• Allow tests with specific wallet #183
• Quickstart tutorial
• Smooth integration with Clarinet (once Conditionally deploy code in Simnet stx-labs/clarinet#2022 is implemented)

Maintainability

• Use a structured command-line argument parsing library #165
• Remove sBTC terminology from public function/API surface #180
• Dependencies housekeeping #181
• Setup CI linter and formatter for code standards enforcement #194

Clarity Property-Based Testing

• Export random argument generation and ClarityValue conversion #168

Notes

• Although Add Support for Customizing Fuzzing Parameters via rv-config.json #7 is currently closed, reopening it is being considered. While Support wildcards for test selection #60 and Support for user-defined generators #66 target similar outcomes, a configuration file may offer a cleaner and more flexible approach for Rendezvous users, especially in scenarios where new configuration options may be introduced as part of Implement fuzzing plans to fuzz multiple contracts at a time #148 and Allow tests with specific wallet #183.

---

This list may evolve as development progresses and priorities are refined.

[moodmosaic]

On #66, perhaps this could wait until after v1 — unless there’s already some work or a clear example that shows the usage of a user-defined generator and proposes a DSL.

[BowTiedRadone]

@moodmosaic Thanks for the suggestion. Issue #66 was added with this note in mind:

• Although Add Support for Customizing Fuzzing Parameters via rv-config.json #7 is currently closed, reopening it is being considered. While Support wildcards for test selection #60 and Support for user-defined generators #66 target similar outcomes, a configuration file may offer a cleaner and more flexible approach for Rendezvous users, especially in scenarios where new configuration options may be introduced as part of Implement fuzzing plans to fuzz multiple contracts at a time #148 and Allow tests with specific wallet #183.

But I think the user-defined generators can wait, indeed.