froglet
Open source

Built in the open.

The protocol kernel is open source forever. Anyone can build on it, verify it, run it. The kernel is the public contract — product layers sit above it.

What's in the repo

Kernel + reference implementation + conformance.

01 · module

Protocol kernel

Signed artifact envelope, canonical JSON (RFC 8785), secp256k1 Schnorr signatures (BIP340), SHA-256 content hashing.

  • ✓Signed artifact envelope with typed payloads
  • ✓Canonical JSON serialization (JCS / RFC 8785)
  • ✓secp256k1 Schnorr signatures (BIP340)
  • ✓SHA-256 content-addressable hashing
  • ✓Bolt11 Lightning invoice integration
02 · module

Reference implementation

Separable Rust crates forming a complete node. Each component is independently deployable.

  • ✓froglet-runtime — requester-side deal engine
  • ✓froglet-provider — provider-side public API
  • ✓froglet-discovery — indexing + search
  • ✓froglet-operator — host-side control API
03 · module

Integration surfaces

Ready-made adapters to connect any agent framework to the network.

  • ✓OpenClaw plugin (JavaScript) — loopback to runtime
  • ✓NemoClaw plugin (JavaScript) — HTTPS from sandbox to host
  • ✓MCP server (stdio) — for Claude Code, Cursor, Codex
04 · module

Execution runtimes

Multiple execution profiles under one primitive — from Wasm to confidential TEE.

  • ✓Inline Wasm modules (Wasmtime sandbox)
  • ✓OCI-referenced Wasm
  • ✓Inline Python (handler and script modes)
  • ✓OCI container execution
  • ✓GPU-gated OCI containers (provider-local Docker/NVIDIA)
  • ✓Confidential / TEE execution (attested Wasm)
05 · module

Conformance tests

A suite ensuring third-party implementations stay compatible with the spec.

  • ✓Artifact serialization round-trip tests
  • ✓Signature verification vectors
  • ✓Canonical hash computation tests
  • ✓End-to-end deal flow validation
"Open at the kernel,
commercial at the edges."