Thanks for reaching out with these great questions. Here are some clarifications that might help:
1. Accepted languages:
The project primarily uses Rust and Go, as you noticed, but we’re generally open to other languages as long as the submission can meet the interface requirements and packaging standards. The main goal is that your code provides both a runnable binary and optionally a reusable package/library. The language choice should allow for easy integration and testing within the Betanet ecosystem.
2. Tests and benchmarks:
Yes, there are some baseline tests and benchmarks your submission should pass to ensure compatibility and performance. These typically include conformance to protocol specifications, performance thresholds (e.g., latency, throughput), and security tests (e.g., correct crypto operations). The exact test suite and benchmark limits vary by component but expect automated CI runs covering these areas.
3. Binary vs package:
The preferred format is a runnable binary (executable) to simplify deployment, accompanied by a package/library if applicable to the language, so others can build on your work. For some languages (like Go), a single binary is typical; for others (like Rust), you might provide both a crate and a binary. If you’re unsure, please reach out with your language of choice and intended format.

Thanks for reaching out with these great questions. Here are some clarifications that might help: 1. Accepted languages: The project primarily uses Rust and Go, as you noticed, but we’re generally open to other languages as long as the submission can meet the interface requirements and packaging standards. The main goal is that your code provides both a runnable binary and optionally a reusable package/library. The language choice should allow for easy integration and testing within the Betanet ecosystem. 2. Tests and benchmarks: Yes, there are some baseline tests and benchmarks your submission should pass to ensure compatibility and performance. These typically include conformance to protocol specifications, performance thresholds (e.g., latency, throughput), and security tests (e.g., correct crypto operations). The exact test suite and benchmark limits vary by component but expect automated CI runs covering these areas. 3. Binary vs package: The preferred format is a runnable binary (executable) to simplify deployment, accompanied by a package/library if applicable to the language, so others can build on your work. For some languages (like Go), a single binary is typical; for others (like Rust), you might provide both a crate and a binary. If you’re unsure, please reach out with your language of choice and intended format.

That should be seen since if it is done in Python I can make a binary as a package, but in terms of benchmark we will have to see what is done since it is not like I can compare in terms of rust vs python

Thanks for reaching out with these great questions. Here are some clarifications that might help: 1. Accepted languages: The project primarily uses Rust and Go, as you noticed, but we’re generally open to other languages as long as the submission can meet the interface requirements and packaging standards. The main goal is that your code provides both a runnable binary and optionally a reusable package/library. The language choice should allow for easy integration and testing within the Betanet ecosystem. 2. Tests and benchmarks: Yes, there are some baseline tests and benchmarks your submission should pass to ensure compatibility and performance. These typically include conformance to protocol specifications, performance thresholds (e.g., latency, throughput), and security tests (e.g., correct crypto operations). The exact test suite and benchmark limits vary by component but expect automated CI runs covering these areas. 3. Binary vs package: The preferred format is a runnable binary (executable) to simplify deployment, accompanied by a package/library if applicable to the language, so others can build on your work. For some languages (like Go), a single binary is typical; for others (like Rust), you might provide both a crate and a binary. If you’re unsure, please reach out with your language of choice and intended format.

That should be seen since if it is done in Python I can make a binary as a package, but in terms of benchmark we will have to see what is done since it is not like I can compare in terms of rust vs python

Glad I could help clarify, feel free to reopen with additional questions if related to the original issue or to open a new one, and tag me if needed.