P5 · StratHub

A code-sharing community, never a signal marketplace.

Name: strathub — vajraquant
Brand: vajraquant

the retail algo framework in India restricts signal following and validates public performance claims. this rules out a leaderboard of user returns — and it is the right constraint. so strathub is a place to share and read logic: publish a strategy with its code visible, fork it into your workspace, discuss it, review it. nobody follows anybody's trades. every user takes responsibility for what runs in their account, because they can read what it does.

in the terminal

repo-style card · fork + run in your account · no performance leaderboard

strathub · orb-nifty-15mbrowseyour forks+

MIT · code shared for study kill · global

vq/samples/orb-nifty-15m

python · updated 3d ago

opening-range breakout · nifty · 15m

buy on 15-minute range break with above-average volume, trail 1%, EOD exit.

214forks892stars37discussions

forkrun in my accountopen discussion

class OpeningRangeBreakout(Strategy):
    instrument = "NIFTY-FUT"
    timeframe  = "15m"

    def on_bar(self, bar):
        if self.position.is_flat and bar.close > self.or_high:
            if bar.volume > self.avg_vol.value:
                self.buy(1, stop=trail(pct=0.01))

code shared for study. not a recommendation. backtest results do not indicate future returns.

⌘ K command bar · ? hotkey mapverifiable · reproducible artefact

what ships

publish a strategymvp: logic visible, always. no hidden branches, no black-box modes. the white-box positioning, applied to community.
fork into your workspacemvp: one click. modify, run your own backtest, deploy under your own risk limits. the original is untouched; your fork is a new version tree.
discussion and code reviewmvp: line-annotated review on a published strategy. the closest thing retail trading has to a peer-review loop.
ranked by community signalmvp: forks, stars, code quality, discussion quality. never by claimed returns. never by a leaderboard of P&L.
reproducible-artifact resultsv1: backtest results shown as artifacts anyone can rerun against the same config and snapshot. verifiability, not a claim.
pull-request contributionsv1: propose a change back to the original author, get it merged, get credited. the author decides.
signal-following or copy-tradingv2: not built without written counsel sign-off — and, if the shape requires it, RA registration under a separate legal entity. see the risk register.

non-negotiables

every publish carries the standard disclosure

code shared for study, not a recommendation. backtest results do not indicate future returns. plain, unmissable, on every listing.

no performance leaderboard

returns are not a ranking axis. the ranking axes are engineering ones — how many people use the code, how good the code is, how alive the discussion is.

the other four surfaces

P1 · Terminal

data, news, charts, screeners — the surface you watch.

P2 · Strategy coder

plain english compiles to code you can read.

P3 · Orchestration

deploy, monitor, kill — the kill switch is two taps away.

P4 · Capital allocator

position sizing, risk budgets, drawdown governors.

waitlist

start when we're ready.

we'll email once when there's something to sign up for. no drip, no digest.