Steer Network

The products share one compute fabric

Markets need to be observed. Strategies need to process data. Portfolios need lifecycle decisions. Contracts need correctly formatted calls. Much of that work is too data-intensive, too application-specific, or too expensive to perform entirely inside a blockchain transaction.

Steer Network runs that work as WebAssembly across a distributed node quorum, then makes the agreed output available to the product or infrastructure that requested it.

Follow one workload

A Network job starts with an application and a payload—not with a hardcoded financial use case.

1. A product supplies the workload configuration and the data required for the run.
2. The logic executes as a WebAssembly bundle in isolated node environments.
3. The participating nodes evaluate the same workload and submit their results.
4. The quorum process resolves the output expected by the consuming application.
5. That output can become data, a decision, or a transaction payload for downstream execution.

Because the workload boundary is general, the same compute system can support market strategies, data transformations, automation jobs, portfolio logic, and other application-defined processes.

What it powers

The Network sits beneath the user-facing products rather than beside them as a generic node service.

IDE produces workloads for the Network. Products configure when and where those workloads apply. Matador separately governs covered onchain execution paths. The Network computes; it does not replace the product’s authority model.

Managed today, staked in the planned network

The current and future operating models should not be collapsed into one claim.

Token-staked node operation is a network objective, not a description of the current managed service. The product should be evaluated today on its workload model, quorum behavior, operating reliability, and the products it already supports.

Why WebAssembly

WebAssembly lets developers choose the language that fits the workload rather than learn a Steer-specific language. If it compiles to WASM, the resulting bundle becomes a portable artifact the Network can execute consistently across its node environments.

Major language ecosystems with established WebAssembly toolchains include:

• Rust;
• C and C++;
• Go;
• C# and other .NET languages;
• Java and Kotlin;
• Swift;
• Zig; and
• AssemblyScript, a TypeScript-like language designed for WebAssembly.

That gives Steer a common runtime without forcing every strategy team, data provider, or product developer into the same toolchain. The language can change; the artifact delivered to the Network does not.

The WebAssembly project maintains a broader language and toolchain directory.

Read about Steer applications · Explore data connectors

Next: see how strategies are developed before they reach the Network →