Skip to main content

Wickra Radar — a liquidation-cascade early-warning radar over open interest, funding, order-book and liquidation events

Built on Wickra Status CI CodeQL codecov GitHub release crates.io PyPI npm NuGet Maven Central Go module R-universe License: MIT OR Apache-2.0 OpenSSF Scorecard OpenSSF Best Practices Build provenance Docs Verified across 10 languages Live demo


See liquidation cascades before they happen — open-interest, funding, order-book and liquidation signals scored across every perp in parallel.

▶ Live demos: the backtester compiled to WebAssembly, an equity curve building bar by bar — backtest-live.wickra.org; one StrategySpec side by side in Python, Rust, JS and Go — playground.wickra.org; all 514 indicators of the core over a real Binance feed — live.wickra.org. Zero backend, all of them.

Part of the Wickra ecosystem: the same data-driven core and ten-language binding surface also power wickra-exchange, wickra-backtest, wickra-terminal and 20 more — see the full list.

Wickra Radar is one data-driven core, wickra-radar-core: a serde RadarSpec is folded over a perp universe — open interest, funding, order-book and liquidation events — into a RadarReport of severity-scored RadarAlerts. Each symbol runs a handful of O(1) streaming signals; the per-signal scores are aggregated with weights into a single severity in [0, 1]. Thousands of symbols update in parallel, turning the whole market into a crash early-warning seismograph that price-only tools never see.

Because the alert is data, not code, the exact same output crosses the C ABI and WASM unchanged — and stays byte-for-byte identical between the parallel (rayon) and sequential (the WASM fallback) builds. The core is exposed as a JSON-over-C-ABI data API (Radar::command) in Rust, Python, Node.js, WASM, C, C++, C#, Go, Java and R, with a command-line reference consumer.

  • OI delta — a burst in open interest over a rolling window.
  • Funding flip — funding rate crossing zero (longs ↔ shorts pay).
  • Book imbalance — resting bid/ask liquidity skew.
  • Liquidation cluster — liquidation events bunching in a short window.
  • OI / price divergence — open interest rising while price stalls or falls.
# Scan a perp universe from a spec + an event batch, raw RadarReport JSON
# (the same bytes every binding returns):
cargo run -p wickra-radar -- --spec golden/specs/composite.json --stdin --format json < golden/events.json

# Human-readable table of alerts:
cargo run -p wickra-radar -- --spec golden/specs/composite.json --stdin < golden/events.json

Status

0.2.1 — the current release. The core, the CLI, all ten language bindings, the byte-exact golden corpus, property + fuzz tests, benchmarks and one runnable example per language are in place and green across the full CI matrix (10 languages × 3 OS). Track progress in ROADMAP.md.

Documentation

Quickstart

The --spec file is a RadarSpec; events are read either from --stdin (one JSON object {"SYMBOL":[event, …], …}) or from --events <dir>, a directory of per-symbol <SYMBOL>.jsonl files (one JSON Event per line). --limit and --threshold override the spec.

RadarSpec / signals

A spec is a JSON (or TOML) document: a list of signals, an optional severity threshold, and an optional top-N limit. Each signal names a kind, its numeric params, and an optional weight (default 1.0). The report scores every symbol, keeps those at or above threshold, and returns the top limit sorted by severity (descending), then symbol (ascending).

{
  "signals": [
    { "kind": "oi_delta", "params": [2.0, 0.1], "weight": 1.0 },
    { "kind": "funding_flip", "params": [0.0005], "weight": 2.0 },
    { "kind": "book_imbalance", "params": [1.0], "weight": 1.0 },
    { "kind": "liq_cluster", "params": [5.0, 30.0], "weight": 1.5 },
    { "kind": "oi_price_divergence", "params": [2.0, 0.1], "weight": 3.0 }
  ],
  "threshold": 0.2,
  "limit": 3
}
  • Signals (kind): oi_delta, funding_flip, book_imbalance, liq_cluster, oi_price_divergence.
  • Alert — RadarAlert { symbol, severity, factors, ts }; factors is the per-signal score map plus the aggregated severity, so every alert explains itself. The report is RadarReport { alerts, scanned }.

Streaming, and why it is deterministic

scan folds a whole batch at once; feed / feed_batch drive the same per-symbol state incrementally and alerts reads the report at any point — the streaming path and the batch path go through one shared report_from_states, so they return byte-identical JSON. The parallel (rayon) and sequential builds agree bit-for-bit too: alerts sort by a total order (f64::total_cmp on severity, then symbol), never a partial float compare.

Use in any language

The same Radar handle — construct from a JSON spec, drive with command(json) -> json, read version — is reachable from every binding:

from wickra_radar import Radar
r = Radar('{"signals":[{"kind":"funding_flip","params":[0.0005]}],"threshold":0.0}')
report = r.command('{"cmd":"scan","events":{"AAA":['
                   '{"kind":"derivatives","ts":1,"open_interest":1.0,"funding_rate":0.0003,"mark_price":50.0},'
                   '{"kind":"derivatives","ts":2,"open_interest":1.0,"funding_rate":-0.0004,"mark_price":50.0}]}}')
# report is a JSON RadarReport: {"alerts":[{"symbol":"AAA","severity":1.0,...}],"scanned":1}

The C ABI hub (bindings/c) backs C, C++, C#, Go, Java and R; Rust, Python, Node.js and WASM are native. See each bindings/<lang>/README.md and the runnable examples/.

Project layout

crates/radar-core     the data-driven core (RadarSpec, Universe, signals, aggregate, scan, command_json)
crates/radar-cli      the CLI (bin: wickra-radar)
crates/radar-bench    criterion benchmarks
bindings/{python,node,wasm,c,go,csharp,java,r}   the ten-language surface
golden/               a deterministic event universe, specs, and byte-exact expected reports
fuzz/                 cargo-fuzz targets (spec_parse, command_json, scan)
examples/             one runnable "scan a universe" example per language

Building everything from source

cargo build --workspace
cargo test  --workspace --all-features
cargo test  --workspace --no-default-features   # sequential build path
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo run -p wickra-radar -- --spec golden/specs/composite.json --stdin --format json < golden/events.json

Each binding builds from its own directory — see the per-binding READMEs under bindings/.

Testing

Run the suites with the commands in Building everything from source.

  • wickra-radar-core — unit tests per signal, the scoring and aggregation path, the parallel-versus-sequential parity, property tests over the event stream and the command envelope. The golden fixtures in golden/ are the anchor: the same (spec, events) pair must scan to the same report bytes here as in every binding.
  • Every binding asserts the same golden bytes. That is the whole cross-language claim, so it is checked the same way in each one rather than approximated per language: Python with pytest (and a plain runner on 3.9), Node with node --test, WASM through the nodejs build, C and C++ through ctest, C# with dotnet test, Go with go test, Java with JUnit, and R with the shipped tests/smoke.R plus the repository's run_tests.R.
  • Examples — every example under examples/ runs in CI and is held to the version and the alerts it prints.
  • Fuzz — fuzz/ holds libFuzzer targets over spec parsing, the command envelope and the scan; CI runs each for a short smoke.

Requirements

  • Rust 1.87+ — the workspace MSRV; the Node binding needs Rust 1.88.
  • Python 3.9+ — the Python binding.
  • Node 22+ — the Node binding.
  • Go 1.23+ — the Go binding.
  • Java 22+ — the Java binding.
  • R 4.1+ — the R package.
  • .NET 8+ — the C# binding.
  • A C11 / C++17 compiler with CMake 3.15+ for the C and C++ examples.

See each bindings/<lang>/README.md for the per-language build and install.

Benchmarks

crates/radar-bench measures scan scaling by universe size and events per symbol, parallel vs sequential. See BENCHMARKS.md.

Ecosystem

Part of the Wickra family — each one a data-driven core with a CLI and the same ten-language binding surface:

  • wickra — main library (Rust core + Python / Node.js / WASM bindings + a C ABI for C / C++ / C# / Go / Java / R)
  • wickra-playground — a polyglot strategy playground: one StrategySpec live side by side in Python, Rust, JS and Go, entirely in the browser
  • wickra-exchange — unified market-data + execution across ten crypto exchanges
  • wickra-backtest — event-driven backtester over the Wickra core
  • wickra-terminal — the trading terminal: a TUI and a browser renderer over the stack
  • wickra-screener — parallel multi-symbol screening over 495 streaming indicators
  • wickra-xray — market-microstructure explorer: footprint, order-book heatmap, liquidation map, funding/OI divergence
  • wickra-copilot — local market copilot grounded in real order-book, liquidation and funding microstructure
  • wickra-shazam — match an asset's current microstructure fingerprint against its entire history
  • wickra-benchmark — reproducible, golden-verified benchmark suite — recompute any (strategy, dataset, report) in ten languages and confirm it byte-for-byte
  • wickra-strategy-ci — Jest for trading strategies: golden-pin the report, catch regressions in CI, property-test against fuzzed data
  • wickra-verify — confirm or refute a claimed backtest report against its strategy and data, in ten languages
  • wickra-proof — Proof-of-Backtest: deterministic (spec, data) → report + blake3 hash, recomputable byte-for-byte in ten languages
  • wickra-zk — prove a backtest zero-knowledge — on-chain-verifiable performance without revealing the data or the strategy
  • wickra-impact — the backtester that knows you would have moved the market: agent-based fills on the real historical L2 order book
  • wickra-darwin — evolutionary strategy search at millions of backtests per second, mutating and crossing JSON specs across the 495-indicator space
  • wickra-gym — a Gymnasium-compatible, microstructure-aware backtest environment with O(1) steps for deterministic RL rollouts
  • wickra-feature-store — OHLCV and microstructure streams into ML-ready feature matrices over 495 O(1) streaming indicators
  • wickra-genome — a vector database of the whole market: every asset a 495-dim live vector, for similarity search, clustering and anomaly detection
  • wickra-timemachine — scrub the whole market like a video — every symbol, full order book, rewound to any moment via deterministic re-fold
  • wickra-synth — deterministic synthetic market microstructure: OHLCV, order book, trades and funding from a single seed
  • wickra-compile — compile a strategy spec into a standalone deployable: a WASM module, a self-contained binary, or a no_std artifact
  • wickra-embed — allocation-free, no_std streaming indicators for bare-metal and HFT, byte-for-byte identical to the core
  • wickra-pico — the O(1) indicator core running bare-metal on a $5 Raspberry Pi Pico — the LED blinks on the EMA cross

Docs at docs.wickra.org; the marketing site and in-browser demo at wickra.org.

Contributing

See CONTRIBUTING.md and CODE_OF_CONDUCT.md. Commits are signed and in English; open a PR against main.

Security

See SECURITY.md and THREAT_MODEL.md. Report vulnerabilities privately — never in a public issue.

License

Licensed under either of

at your option. Use it, fork it, modify it, redistribute it — commercially or not — file issues, send pull requests; all welcome.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

Disclaimer

Wickra Radar is analysis software: it computes early-warning signals over historical and live market data. It is provided "as is", without warranty of any kind, and is not financial advice — it places no orders. Trading carries risk of loss; review the code and use at your own discretion.


GitHub stars GitHub forks GitHub issues

Built on Wickra. If it saved you time, the cheapest way to say thanks is to ⭐ the repo.

wickra-radar star history

Metadata

Release files for wickra-radar 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for wickra-radar 0.2.1
File Size Uploaded Provenance Actions
wickra_radar-0.2.1.tar.gz 78.1 kB Without provenance Details for wickra_radar-0.2.1.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for wickra-radar 0.2.1
File Actions
wickra_radar-0.2.1-cp39-abi3-win_arm64.whl CPython 3.9 abi3 Windows ARM64 Details for wickra_radar-0.2.1-cp39-abi3-win_arm64.whl
wickra_radar-0.2.1-cp39-abi3-win_amd64.whl CPython 3.9 abi3 Windows x86-64 Details for wickra_radar-0.2.1-cp39-abi3-win_amd64.whl
wickra_radar-0.2.1-cp39-abi3-musllinux_1_2_x86_64.whl CPython 3.9 abi3 Linux musl 1.2+ x86-64 Details for wickra_radar-0.2.1-cp39-abi3-musllinux_1_2_x86_64.whl
wickra_radar-0.2.1-cp39-abi3-musllinux_1_2_aarch64.whl CPython 3.9 abi3 Linux musl 1.2+ ARM64 Details for wickra_radar-0.2.1-cp39-abi3-musllinux_1_2_aarch64.whl
wickra_radar-0.2.1-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.9 abi3 Linux glibc 2.17+ x86-64 Details for wickra_radar-0.2.1-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
wickra_radar-0.2.1-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.9 abi3 Linux glibc 2.17+ ARM64 Details for wickra_radar-0.2.1-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
wickra_radar-0.2.1-cp39-abi3-macosx_11_0_arm64.whl CPython 3.9 abi3 macOS 11.0+ ARM64 Details for wickra_radar-0.2.1-cp39-abi3-macosx_11_0_arm64.whl
wickra_radar-0.2.1-cp39-abi3-macosx_10_12_x86_64.whl CPython 3.9 abi3 macOS 10.12+ x86-64 Details for wickra_radar-0.2.1-cp39-abi3-macosx_10_12_x86_64.whl

Total release size: 3.0 MB

Release files / wickra_radar-0.2.1.tar.gz

Download URL wickra_radar-0.2.1.tar.gz
Size 78.1 kB
Tags Source
SHA-256 checksum
How to use checksums
147125a160d6561aa4719da94ec8441ce40e46cf7a821c8302fc32148b4e55cc
BLAKE2b-256 checksum
How to use checksums
f3a8e389b61b991903677da3dd7183a41176ac307d9fbf59df0dd8a5d5dcfcd7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via maturin/1.15.0

Release files / wickra_radar-0.2.1-cp39-abi3-win_arm64.whl

Download URL wickra_radar-0.2.1-cp39-abi3-win_arm64.whl
Size 239.1 kB
Tags CPython 3.9 Windows ARM64 abi3
SHA-256 checksum
How to use checksums
15f1dd14637783f7b81ac59c0a2ee3ab24f8c1c5ffd8c5ae29d9169c8da71936
BLAKE2b-256 checksum
How to use checksums
fa7da5a3062e7c44a54dd81448a1e16376c79489fd6bd7ea9e4cc8da10273e33
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via maturin/1.15.0

Release files / wickra_radar-0.2.1-cp39-abi3-win_amd64.whl

Download URL wickra_radar-0.2.1-cp39-abi3-win_amd64.whl
Size 257.8 kB
Tags CPython 3.9 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
1f6cd594001702984a337d9cbe7f05a0d0256cba18aa1b866741a796c2997f79
BLAKE2b-256 checksum
How to use checksums
4e61147cf0d32f06ee395a3f6919154bf4d50c36343ea8b0805b189ab2b93e17
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via maturin/1.15.0

Release files / wickra_radar-0.2.1-cp39-abi3-musllinux_1_2_x86_64.whl

Download URL wickra_radar-0.2.1-cp39-abi3-musllinux_1_2_x86_64.whl
Size 573.1 kB
Tags CPython 3.9 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
2c2b851ae459dbb87d9ff2a1ae3284fc5ec583dce0158f4f23be5c7ec246011a
BLAKE2b-256 checksum
How to use checksums
33b5b5ddc613384bcdb21c5cdb18ce474f3bc62e1d61513ad138d814f4edded5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via maturin/1.15.0

Release files / wickra_radar-0.2.1-cp39-abi3-musllinux_1_2_aarch64.whl

Download URL wickra_radar-0.2.1-cp39-abi3-musllinux_1_2_aarch64.whl
Size 514.1 kB
Tags CPython 3.9 Linux musl 1.2+ ARM64 abi3
SHA-256 checksum
How to use checksums
0db3b6541c1d2689e2296daf987e73ec90973490475b27c2821400a55ed6aa8a
BLAKE2b-256 checksum
How to use checksums
ba70749609bee837620b02df615026fedbbd177b84f760265f41c998d8c0061a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via maturin/1.15.0

Release files / wickra_radar-0.2.1-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL wickra_radar-0.2.1-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 360.8 kB
Tags CPython 3.9 Linux glibc 2.17+ x86-64 abi3
SHA-256 checksum
How to use checksums
c21a0215902593db223c98f77ed90f1b875a59853cf19ffd76219bbabe92b62d
BLAKE2b-256 checksum
How to use checksums
b99b1eb57e796ca9bd1373be362ab5ec7e39f7e8efd70f9477d2d81a70683a06
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via maturin/1.15.0

Release files / wickra_radar-0.2.1-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL wickra_radar-0.2.1-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 335.7 kB
Tags CPython 3.9 Linux glibc 2.17+ ARM64 abi3
SHA-256 checksum
How to use checksums
0a4c3956906ec1f064e557554ff8e07224fb47bd7aa2940d374798cf886e4179
BLAKE2b-256 checksum
How to use checksums
865dd00394fa278dcbb46bbcbb40fa376915eb03cd02d067fb5cd407432913d3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via maturin/1.15.0

Release files / wickra_radar-0.2.1-cp39-abi3-macosx_11_0_arm64.whl

Download URL wickra_radar-0.2.1-cp39-abi3-macosx_11_0_arm64.whl
Size 309.2 kB
Tags CPython 3.9 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
4b0379c69cb533c7d6070b06db50fb8cc4568e9aa98e0f57ac26fc47a26f1af7
BLAKE2b-256 checksum
How to use checksums
2e7fe697b4936b1a2fd7b6c92ccee73427acc7bd864862b7b97fe7acb3e1b039
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via maturin/1.15.0

Release files / wickra_radar-0.2.1-cp39-abi3-macosx_10_12_x86_64.whl

Download URL wickra_radar-0.2.1-cp39-abi3-macosx_10_12_x86_64.whl
Size 338.1 kB
Tags CPython 3.9 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
7f4998b7dd66a6ffa510d92e67dbb9c98d52c4fabb0f82dc8f7248497dcedb72
BLAKE2b-256 checksum
How to use checksums
9a82a596c8ecf549b254071e030d2f6125b54baf8c8917b1befac8aae1ac7efc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via maturin/1.15.0

Security for wickra-radar 0.2.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page