Where the arguments happen
Trading communities usually optimise for confidence. This one is set up for the opposite: it lives on the public repository, product proposals are argued before they are built, every review happens in the open, and the threads worth reading are the ones about trades that lost.
Issues
Bugs, configuration questions and post-mortems on trades that went wrong, on the public repository. The most useful threads are the ones about losses.
Public. Answered by the maintainer; not a support queue with a guarantee.
Proposals
Changes to the product, argued in a proposal issue before they are built. The form asks for evidence — for anything that touches trading decisions, the backtest or forward-test record.
Where roadmap decisions happen.
Strategy exchangeplanned
Not built yet. The plan: published strategies with their full parameter history and out-of-sample record attached, and no listing without the record.
Planned — not available today.
Reading needs nothing; opening an issue or a proposal needs a GitHub account. Open the issue tracker.
From proposal to change
Every change to the product can be traced back through the same five steps, and every step is public — so the reason something was built, or declined, is on record rather than in someone's memory.
A proposal that touches trading decisions needs evidence, and an improvement is a hypothesis until a backtest and a forward test say otherwise.
- ProposalAn issue on the proposal form: the problem, the change, the evidence.
- ArgumentComments on the issue, in public, until the approach is agreed or declined.
- Pull requestThe change, with a test that fails before it and passes after, linked to the issue.
- ChecksCI runs every test suite, both front-end builds and all four SDK suites.
- MergeReviewed in public by the maintainer; the issue closes with the pull request.
Code of conduct
Four rules, enforced. They exist because a community around money attracts a specific kind of noise, and a policy nobody applies is decoration.
Breaches are raised privately first. Repeated ones lead to comments being removed and, if needed, the account being blocked from the repository. The rules are in CODE_OF_CONDUCT.md.
- 01No signal-selling, no referral links, no performance claims without the record attached. A screenshot of a P&L is not evidence of anything.
- 02Disagree with the argument. Reviews and threads are public and permanent, and a technical disagreement is not a personal one.
- 03No financial advice, given or requested. Discuss method and mechanism; leave 'should I buy this' to a licensed adviser who knows your situation.
- 04Assume the person asking a basic question has been trading for a week. Everyone here was.
If you would rather contribute code than conversation, the open-source page covers what is public and how contributions are reviewed. Security findings go through the private disclosure route on the security page, never a public channel.