Registry Engine: Content-Addressed (BLAKE3 Digest)
Storage Backend: Iroh Blobs + Anycast Edge CDN
Runtime Sandbox: Wasmtime WASI v1 (Zero Network Escape)
Signature Verification: Ed25519 Author Attestation
DECENTRALIZED EXTENSION ECOSYSTEM

SIAR Plugin Marketplace & Extension Registry

Discover, audit, and install cryptographically verified hardware drivers (LoRa, Satellite, Packet Radio), off-grid map tile caches, and automated emergency bot scripts running in strict WASI sandboxes.

Official & Community Extensions

Loading extensions...
πŸ”
SANDBOXED RUNTIME ARCHITECTURE

WASI Sandbox & Security Attestation

Third-party extensions execute inside isolated WebAssembly (WASI) sandboxes with fine-grained hardware capability granting.

πŸ›‘οΈ

Zero Network Socket Escape

Plugins cannot open unauthorized TCP/UDP sockets to the public internet, preventing telemetry exfiltration and malware beaconing.

⚑

Strict Memory Ceilings

Every extension is restricted to a declared heap boundary (e.g. 16MB) and a maximum CPU execution budget per cycle (50ms).

πŸ”

BLAKE3 Immutability

Artifacts are content-addressed by BLAKE3 cryptographic hashes, guaranteeing bit-for-bit immutability against supply-chain tampering.

DEVELOPER TOOLCHAIN

Publishing an Extension to the Registry

Build, test, and publish your own custom hardware transport or mesh bot in 4 commands:

# 1. Scaffold new WebAssembly plugin workspace
siar plugin new my-custom-extension --type transport

# 2. Compile to WebAssembly WASI target
cargo build --target wasm32-wasi --release

# 3. Test execution inside local sandbox runner
siar plugin test --manifest siar-plugin.toml

# 4. Sign with Ed25519 developer key and publish to registry
siar plugin publish --key ~/.siar/dev-signing-key.pem

πŸ› οΈ Interactive siar-plugin.toml Manifest Generator

Generated Manifest (siar-plugin.toml):