Algonics
☰
Dashboard
QUANT
Data
Strategies
Bots
Alerts
CONFIG
Connections
Channels
Settings

Strategies示例数据 · SAMPLE/strategies

Compiled algorithm DLLs registered with the platform. Backtest a strategy, or run it as one or more bots.
⌕Name or type name
All▼
All▼
7SearchReset
+Add strategy1Showing archived8
StrategyMarketAlgorithm3 · assembly / versionStatus4Bots5Actions6
VegasTunnel2CRYPTOAlgonics.Crypto.VegasTunnelAlgorithmAlgonics.Crypto.dll · v7 · 6 paramsActive●2 runningBinance · Bybit
GridSpotCRYPTOAlgonics.Crypto.GridSpotAlgorithmAlgonics.Crypto.dll · v2 · 5 paramsDraft—
MomentumRotationEQUITYAlgonics.Equity.MomentumRotationAlgonics.Equity.dll · v4 · 8 paramsActive●1 running · 1 stoppedIBKR live · IBKR paper
CashSecuredPutOPTIONAlgonics.Option.CashSecuredPutAlgonics.Option.dll · v3 · 7 paramsActive—
DualEmaCrossEQUITYQuantConnect.Algorithm.CSharp.DualEmaCrossqclean.Algorithm.CSharp.dll · v1 · 6 paramsInactive●1 runningTradier paper
OldBreakoutCRYPTOAlgonics.Crypto.OldBreakoutAlgonics.Crypto.dll · v1 · 4 paramsArchived—
Rows per page: 10 ▾1–6 of 6‹›
Sample data. The Add strategy dialog is a MUI Dialog (maxWidth md) with a 3-step Stepper: Source → Review → Confirm. Step 1 offers two sources: Local folder (a project folder on the Algonics server, recognized by its .csproj; the newest dll under bin/** is used, after waiting until the file is stable. If none exists the option shows No build found · build in Rider first with Rescan, and Scan stays disabled; the first release does not run dotnet build. The folder is remembered as the strategy source and re-read on every Backtest; no folder watching) and Upload DLL (a .dll or .zip copied into platform storage, named by hash). Bots always pin an existing version. Scanning uses metadata-only reflection (System.Reflection.MetadataLoadContext); no code from the uploaded or scanned DLLs is executed. Step 3 shows the registration result with links to the new strategies. Review statuses: New (new class, v1), Changed (algorithm fingerprint changed, new vN+1), Unchanged (assembly hash unchanged, or fingerprint unchanged in a rebuilt assembly). The dll AssemblyVersion is not used for versioning. New and Changed rows are pre-selected; registration adds the new strategies as Draft.
Add strategy示例数据 · SAMPLE✕
✓Source
2Review
3Confirm
ⓘScanned project Algonics.Strategies.csproj · newest build bin/Debug/net9.0 (built 2026-10-24 23:41) · 3 assemblies (1 changed) · 5 algorithm classes in 1.8 s.
Each assembly's SHA-256 is checked first; only in changed assemblies is each algorithm's fingerprint (IL, fields, parameter signatures) compared, and a changed fingerprint creates a new version.
Strategy · algorithm · assembly · version · paramsStatus
MeanReversionBandsAlgonics.Crypto.MeanReversionBandsAlgonics.Crypto.dll · v1 · 5 paramsNew
New class in a changed assembly
VegasTunnelAlgonics.Crypto.VegasTunnelAlgorithmAlgonics.Crypto.dll · v7 → v8 · 6 paramsChanged
Assembly hash changed · algorithm fingerprint changed
GridSpotAlgonics.Crypto.GridSpotAlgorithmAlgonics.Crypto.dll · v2 · 5 paramsUnchanged
Assembly hash changed · algorithm fingerprint unchanged
MomentumRotationAlgonics.Equity.MomentumRotationAlgonics.Equity.dll · v4 · 8 paramsUnchanged
Assembly hash unchanged
CashSecuredPutAlgonics.Option.CashSecuredPutAlgonics.Option.dll · v3 · 7 paramsUnchanged
Assembly hash unchanged
ⓘ Newly registered strategies start as Draft. Changed strategies get a new version and keep their status, bots and backtests. Unchanged strategies are already registered and cannot be selected. No strategy code is executed (metadata-only reflection).
2 of 5 selected · 1 new, 1 changedCancelBackRegister 2 strategies
☰ All ‹ › 3/22