LAYRS LABPrivate trading strategies.
Public, verifiable outcomes.
Layrs Lab is building a venue-neutral marketplace for private trading vaults. Creators and curators can evaluate a committed strategy without publishing its rules; depositors can assess approved performance summaries and vault terms.
Founder: Devendra Tanwar · Horizen Acceleration Season, Week 1 & 2 · 21 September 2026
Integration architecture
Rust services coordinate quotes, finalized payments, jobs and report verification. A Go/TinyGo WASM interpreter executes bounded JSON strategies inside Vela. Clients encrypt strategy payloads before submission; execution is bound to the strategy, policy, module and dataset commitments. The broader test-funds creation workflow uses an on-demand Nitro/Vela worker, while this deliverable demonstrates the local Docker environment.
What stays restricted
Strategy rules and parameters, salts, strategy state, detailed decisions and execution records. Only specifically approved aggregate results should be disclosed on a public vault page. The public interpreter is separate from each private strategy.
What is public / onchain
The local run records deployment and execution requests, commitment metadata, encrypted user events and state-root updates. The broader vault-creation contracts handle deployment-payment escrow, verified report resolution or refunds, and deterministic vault creation. This video does not demonstrate real-value settlement.
What the local demonstration proves
The official Vela v0.2.0 Docker services execute Layrs’ own WASM module. A client registers an encrypted public-example strategy, submits two synthetic bars, decrypts the resulting long and flat decisions, and verifies that resubmitting the same semantic request returns an identical receipt. The onchain requests and completions are recorded on local Anvil, chain ID 31337. Raw evidence and the exact executed WASM are linked with the video.
Progress and current boundaries
The repository separately records an annual 525,600-bar backtest on Nitro/Vela, including client encryption and restart/replay verification, and a test-funds paid strategy-deployment canary. These are recorded engineering results, not independent certification or blanket production-readiness claims. Local software emulation offers no hardware attestation or confidentiality from the host administrator. External venue execution can reveal order flow to the venue; running strategy logic in a TEE does not automatically make all exchange activity private.
Independent audit, production data permissions, multi-party governance/recovery, and additional operational qualification remain pre-beta work. Vaults integrate with venues through approved adapters and APIs; Layrs Pro is the first planned natural integration, not a shared vault/perps accounting engine.
Support we would value
Review of Vela’s WASM/runtime compatibility and production key-recovery integration; guidance on the supported path from local emulation to measured, attested deployment; and an engineering review of commitment/report boundaries. We will share reproducible compatibility findings rather than treat a local run as proof of the complete financial system.
Supporting repository evidence: recorded annual Nitro/Vela execution. Public local example only; no production keys or private user strategies are included in this package.